Built by Vu · Solihull, United Kingdom
70+ tools · one account · one record
01The workspace
Raq.com is a business workspace that holds 70+ tools under a single account. People use it in the browser; systems such as Codex and Claude Code use the same tools over MCP. Both work on the same records, so agent activity stays visible instead of disappearing into a terminal.
No card required · One use of each AI tool during the trial
Team work & records
Messages, boards, project hubs, notes, files.
Customers & service
CRM, portals, support, forms, campaigns.
Documents & approvals
Signing, document production and the controlled exchange of files and secrets.
AI chat, research & decisions
Several models compared, ranked or combined, with the decision kept in the account.
Media & design
Image, video, music, brand.
Sites & monitoring
Hosting, uptime, change watch.
Personal & specialist
Compliance, spreadsheets, health.
Agent operations
Automations, supervision and the two routes to extending the platform.
One login, one bill and one permission set for the whole catalogue, with role-based access and audit records across it. The plan is a diagram of the account rather than a to-scale drawing; the full schedule of all 75 tools by name follows below.
02Why it exists
A small or medium business rarely buys its software in one decision. It adds a chat product, a task board, a signing service, a file-sharing account, a form builder, a monitoring service and several AI subscriptions — each one reasonable on its own.
An agent becomes less useful when it can see only one piece of that setup.
Raq.com puts those jobs in one account and gives agents a common route into them. A task can start with a message, use a file from File Drop, create a document, request an approval, update a board, and leave the result somewhere the team can inspect it.
The product is built around that continuity between tools, rather than around any single one of them. Raq.com does not claim to match every mature specialist product feature for feature — its comparisons describe overlapping workflows, not exact replacements.
Where a specialist system is genuinely needed, it can stay. APIs, Automations and Custom Modules are the routes that connect it back into the account.
03One record
The browser and the agent surfaces work against the same records. A person can see and amend work an agent created; an agent can continue work a person started. Six steps, one history.
Someone describes the job in Team Comms, where the rest of the team can already see it.
An agent pulls the brief from File Drop using a structured operation, not an imitation of a click.
Pretty Docs turns the material into a designed document, in the account's own templates.
Ask My Agent puts the decision to a person and waits. Nothing sensitive leaves the account unapproved.
Task Board is updated — card, owner, dependency and time tracking included.
The files, the messages, the approval and the history stay in the account, inspectable by the team.
Work is done the way a team already expects, with normal screens and normal roles.
Role-based access and audit records show who did what, on which account.
Raq.com exposes its tools to compatible agents through the Model Context Protocol.
Access is account-scoped, and tool access can be limited. An agent does not need to imitate clicks in the browser when a direct operation exists.
04Catalogue
Every public tool is included in each paid plan; what changes between plans is AI usage and service limits. The schedule below groups the catalogue by the job each tool does. Some tools belong to more than one group.
The daily surface: messages, boards, project hubs, notes and files.
From first enquiry to signed client, including the support that follows.
Producing, reviewing and moving documents and secrets under control.
Several models, compared, ranked or combined — with the decision kept.
Generation, editing and review of media, with the source material kept in the account.
Build the things a business runs on, then watch them and measure them.
Tools that belong to a person rather than to a whole team.
Automations, supervision of long jobs, and the two ways to extend the platform.
A single tool can be useful on its own. The shared records are what make longer work possible: files, tasks, approvals, messages and project notes do not need a new integration for every pair of products.
05Workflows
Four kinds of work that run end to end inside Raq.com, using the tools the account already has. Each step leaves its own trace, and an agent can check the chain and prepare whatever is missing.
A prospect completes a form. An Automation creates or updates the CRM record, opens an onboarding card and spins up a Client Portal. The agreement goes out for signature; the signed document and the client's uploads land in the account's files.
The internal discussion and the next actions stay on the board and in Team Comms rather than in somebody's inbox.
The team stores its rules in Brand Guidelines and starts from a campaign brief. Marketing Campaigns prepares the plan; Rewriter and Ghostwriter produce copy; the image and video labs produce media.
Creative Review collects the decisions in one place, and Social Scheduler prepares channel-specific versions and publishes them after approval.
A site is created or updated, then reviewed: Page Feedback collects pinned comments on a frozen copy of the page, and the SEO & AEO Checker reads it for search performance, answer-engine readiness and visibility to AI systems.
Site Uptime and Page Watch keep checking afterwards. Alerts connect to the person responsible through a task or an Automation, and the support inbox handles what arrives.
A person records the desired outcome. Orchestrator starts the relevant agent workflow across managed Codex and Claude sessions, and Nature Work or Agent Operator HQ shows the active terminals so the work can be supervised.
When the job reaches a controlled boundary, Ask My Agent requests a decision. The final files go to File Drop or Project Base, and the task record carries the result and its history.
06The agent layer
Many business products add a chat box to an existing application. Raq.com exposes the operational tools themselves, so an agent can take structured actions against the account while the browser stays available for people to supervise and correct the work.
Boundary
Users, data, tools, permissions and AI usage are scoped to the selected account. A person can belong to several accounts and switch between them.
Interface
The Model Context Protocol gives an agent structured operations rather than a screen to click through, with access that can be limited tool by tool.
Clients
All of them work against the same account, files and team.
The built-in agent. Describe the job in plain English and it selects suitable Raq.com tools and runs them. It gives a non-technical user an agent route without anyone having to configure a coding environment — and it works with the same account, files and team as a connected external agent.
Sensitive or external actions can require explicit approval. Ask My Agent supports structured exchanges between a person and an agent with two-stage approval controls. Voice Calls is approval-controlled as well, so an approved assistant can make a business call with recording and transcription on the record.
A daily view that separates human, mixed and agent-owned work, so an operator can see where attention is actually needed.
Runs templated, repeatable workflows across managed Codex and Claude sessions instead of one-off scripts.
Connects terminal sessions to a browser-based viewer, so an operator can supervise work away from the desk.
Several agent terminals in one command view, with keyboard controls and a live message queue.
Instructions can persist across sessions too: Personas stores reusable tones and system instructions, Prompt Library keeps versioned prompts with variables, and Skill Library versions the instructions that guide Supercomputer.
07Extensions
The distinction matters, because who builds the software, where it runs and who maintains it are all different. One is a self-build; the other is a managed service.
| Attribute | Custom ToolSelf-built | Custom ModuleManaged by Raq.com |
|---|---|---|
| Who builds it | The customer, or the customer's own coding agent. | Raq.com and Vu. |
| Price | Included with a Raq.com plan. | £190 per month for each module, on top of a plan. |
| Runtime | A sandboxed application hosted through the Custom Tools system. | A native module inside the Raq.com product. |
| Product fit | A self-built application embedded into the account. | A first-class, account-specific module in the normal sidebar. |
| Maintenance | The customer owns the application work. | Raq.com designs, builds, hosts, updates and maintains it while the subscription runs. |
| Access | Draft and published visibility, with scoped permissions. | Explicit access for the customer's account and its team permissions. |
| Agent access | Approved Raq.com operations through scoped MCP access. | An MCP surface can be built into the module alongside its screens and workflows. |
Each tool runs in an isolated container. Draft tools are limited to their creator; published tools can be shared with the account, and outbound access back into Raq.com uses approved, limited scopes. Raq.com supplies the place to run it and the connection into the account — but not the development work.
Describe the workflow; Raq.com reviews it and, where suitable, produces a first mock-up — normally within one working day, with a working module within five working days or less after approval. Larger jobs are identified at the mock-up stage. The monthly fee covers design, development, hosting, maintenance and changes requested while subscribed. One module covers one area of work; a CRM and a quoting system would be two.
08Pricing
The entry plan, for a small team that wants the whole catalogue without buying it tool by tool.
Website Build & Host is a paid per-site add-on on this plan£14 per user, per month
More AI usage and higher service limits than Starter.
Voice Calls is available from this plan£45 per user, per month
Higher AI usage and service limits again, for accounts running agent work as part of the ordinary day.
Increasing website allowances on higher plans£200 per user, per month
The highest AI usage and service limits in the public range.
The top of the four public plans£500 per user, per month
AI work draws on the account's monthly allowance, shown as AI usage rather than as internal credit counts. Different tools consume different amounts: a short rewrite, a multi-model report and a generated video have different provider costs, so the pricing page gives examples per tool instead of one universal request count.
If the allowance runs out, AI tools pause until renewal or a plan change. Non-AI tools remain part of the subscription.
New accounts receive a free trial with no card required: one use of each AI tool, and limited monitoring.
Monitoring tools and FinUK have plan-specific quantity limits. Custom Modules sit outside the plan price, and their AI features use the account's normal AI allowance.
Figures shown are UK monthly prices, excluding VAT where applicable, and are per user.
09Privacy & security
Raq.com separates the way it handles core text AI from the image, video and voice providers it uses. That distinction is worth reading carefully rather than skimming.
Core text and chat requests use Zero Data Retention routes by default: under those routes the model provider cannot keep prompts or responses for training. A user can change the AI Privacy setting to reach models that do not support this protection. Live web search has its own setting, because a current-information lookup may need a standard provider route.
Image and video tools send the prompt and the required generation parameters to a specialist provider. Voice and transcription tools send the text or audio needed for the job. Completed media is downloaded to Raq.com's own storage. Those providers operate under their own API retention terms, so the Zero Data Retention statement should not be applied to every media tool.
Raq.com keeps its own service records for billing and reliability, separate from AI provider handling. Customers assessing the service for regulated or sensitive data should read the current privacy policy, the AI Privacy & Security page and the subprocessors list, then map their own legal and sector requirements onto the specific tools they plan to use.
10Fit
Breadth of useful tools, a shared account and an agent layer across them is the value. That is a different thing from being the deepest product in any one category, and it is better to say so.
In those cases Raq.com can still sit around the existing system through Automations, APIs or a Custom Module — but the connection work and the compliance work need assessment rather than assumption.
11Notes
No card required · One use of each AI tool · Limited monitoring