Business workspace
70+ tools, one account
Built by Vu, Solihull UK
People& agents.Oneaccount.
Raq.com is a business workspace designed for people, teams and AI agents to use
together. Your team works in the browser. Supercomputer, Codex or Claude Code work
through MCP. Both act on the same records, under the same permissions.
Shared record
Client onboarding
01
Form Builder
A prospect completes the branded intake form on your site.
Person
02
Automations → CRM, Task Board, Client Portal
One trigger updates the contact record, opens an onboarding card and creates the portal.
Automation
03
E-Sign
The agreement goes out for signature and keeps its audit record.
Agent
04
File Drop & Team Comms
The signed document and client uploads land in the account; the discussion and next actions stay with the board.
Team
Team CommsTask BoardProject BaseCRMClient PortalE-SignHelp DeskForm BuilderAutomationsOrchestratorAI Image LabAI Video LabContract AuditorKnowledgeSecure SendMarket IntelSpreadsheet AISite UptimeTranscribeSupercomputerTeam CommsTask BoardProject BaseCRMClient PortalE-SignHelp DeskForm BuilderAutomationsOrchestratorAI Image LabAI Video LabContract AuditorKnowledgeSecure SendMarket IntelSpreadsheet AISite UptimeTranscribeSupercomputer
01The workspace
Most companies build their operating system by accumulation.
A chat product. A task board. A signing service. A file account. A form builder. A
monitoring service. Several AI subscriptions. Each one arrives with its own login,
billing, permissions, data and audit history — and an agent that can only see one
piece of the setup is not much of an agent.
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, produce a document,
request approval, update a board and leave the result where the team can inspect
it. The product is built around that continuity, not around a single hero feature.
We do not claim feature-for-feature equivalence with every mature specialist
product. Our comparisons describe overlapping workflows, not exact replacements.
The value is the breadth of useful tools, the shared account, and the agent layer
running across them. Keep the specialist systems you depend on and connect them
through APIs, Automations or a Custom Module.
Where it fits best
- Small teams that want fewer separate subscriptions and logins.
- Companies already using Codex, Claude Code or other agents for operational work.
- Agencies managing several client accounts and projects.
- Operators who need human approvals and an inspectable record of agent activity.
- Teams that need a broad set of occasional tools without buying a specialist product for each one.
-
70+
Tools in the public catalogue. Every one of them is included in every paid plan — higher plans raise AI usage and service limits rather than unlocking features.
-
1
Account holds the users, data, permissions, tools and AI usage. People can belong to more than one account and switch between them.
-
2
Routes to extend the platform: a sandboxed Custom Tool your own coding agent builds, or a managed Custom Module we design, build, host and maintain.
-
£0
To begin. New accounts get a free trial with no card required, allowing one use of each AI tool and limited monitoring.
02Surfaces
Three ways in. One set of records.
Raq.com exposes its tools to compatible agents through the Model Context Protocol.
An agent gets structured operations — list the boards, create a card, upload a file,
run an image batch, read a project record — instead of imitating clicks in a browser.
Surface 01◼
The browser
Normal interfaces for the team. Write messages, manage boards, upload files, review
generated media, approve requests, edit documents, inspect reports.
- Role-based access across the account
- Audit records showing who did what
- Correct or continue anything an agent started
Surface 02◼
Supercomputer
The built-in agent. Describe a job in plain English and it selects and runs suitable
Raq.com tools against your account, your files and your team.
- No coding environment to configure
- Guided by your Skill Library across sessions
- Leaves its work in the product, not in a chat log
Surface 03◼
Your own agent
Connect Codex, Claude Code or another compatible client over MCP and work against the
same account with scoped, account-level access.
- Tool access can be limited per connection
- Sensitive or external actions can require approval
- Ask My Agent and Voice Calls are approval-controlled
04Continuity
A single tool is useful. Shared records make the longer job possible.
Nothing below needs an integration built between two vendors. These are ordinary
sequences inside one account, and an agent can pick up any step in them.
Sequence A
Marketing production
- The team's rules live in Brand Guidelines; work starts from a campaign brief.
- Marketing Campaigns prepares the plan and the collection points.
- Rewriter or Ghostwriter produces the copy, sentence by sentence.
- AI Image Lab and AI Video Lab produce the media in batches.
- Creative Review collects the decisions in one place.
- Social Scheduler publishes channel-specific versions after approval.
Sequence B
Website & service operations
- Website Build & Host creates or updates the site.
- Page Feedback collects pinned review comments from the people reviewing it.
- SEO & AEO Checker reviews the result for search and answer engines.
- Site Uptime and Page Watch monitor availability and content changes.
- Help Desk and Website Chatbox AI handle what comes in.
- A task or Automation connects each alert to the person responsible.
Sequence C
Agent-led project work
- A person records the outcome they want in Priorities or a Task Board.
- Orchestrator starts the relevant agent workflow.
- Nature Work or Agent Operator HQ shows the active terminal sessions.
- Ask My Agent requests a human decision at a controlled boundary.
- Final files go to File Drop or Project Base.
- The task record carries the result and the history behind it.
05Agent operations
Built for supervision, not for chat.
Longer agent jobs need execution, hand-offs, approvals and a record left behind.
These four tools deal with that, and they sit beside everything else in the account.
Orchestrator
Templated workflows
Repeatable work run across managed Codex and Claude sessions, so a process is defined once and started again on demand.
Nature Work
Terminals in a browser
Local terminal sessions connected to a browser-based viewer, so an operator can supervise a run away from the desk.
Agent Operator HQ
The control room
Several agent terminals in one full-screen command view, with keyboard controls and a live message queue.
Priorities
Where attention is needed
Work split into human, mixed and agent-owned tasks, so the operator can see what still requires a person.
06Extend
Two extension models. The difference is who owns the build.
Both sit beside the shared tools and both can reach the account's tasks, files,
contacts, documents and Automations. What changes is the runtime, the commercial
responsibility and the support model.
Custom Tool compared with Custom Module
| Attribute |
Route ACustom Tool |
Route BCustom Module |
| Who builds it |
You, or your coding agent. |
Raq.com and Vu. |
| Price |
Included with a Raq.com plan. |
£190 or $259 per month for each module, on top of a plan. |
| Runtime |
A sandboxed application in an isolated container, 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 |
You own the application work. |
We design, build, host, update and maintain it while you subscribe. |
| Access |
Draft tools stay with their creator; published tools can be shared with the account. |
Explicit access for your account, under 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. |
| Typical start |
Direct your agent and publish when it is ready. |
First mock-up normally within one working day; a working module within five working days or less after approval. |
One module covers one area of work, with its own screens and data.
A CRM and a quoting system would normally count as two modules, and a second module
carries a second monthly fee — although modules for the same account can share data.
Larger jobs are identified during the mock-up stage rather than discovered later.
The monthly fee covers design, development, hosting, maintenance and the changes you
ask for while subscribed. A module can connect to outside systems that provide an API.
Your data stays in your account and can be exported.
Describe the workflow→
07Plans
Every public tool, on every paid plan.
Per-user subscriptions. Plans differ by AI usage and service limits, not by which tools
you are allowed to open. Prices exclude VAT where applicable; annual billing currently
takes 5% off.
Starter
For a small team consolidating logins and trying the catalogue on real work.
£14
$19 rest of world
per user / month
Professional
Voice Calls starts here
For teams running daily AI work and client-facing processes across the account.
£45
$61 rest of world
per user / month
Business
For heavier AI production and higher monitoring and service limits.
£200
$272 rest of world
per user / month
Enterprise
For sustained agent operations and the highest allowances in the product.
£500
$680 rest of world
per user / month
How AI usage works
AI work draws on the account's monthly AI allowance, shown as usage rather than internal credit accounting. If it runs out, AI tools pause until renewal or a plan change. Non-AI tools carry on.
Why tools cost differently
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.
Changing the subscription
Upgrade immediately or schedule a downgrade for the next billing date. The total changes as users join or leave. Monitoring tools and FinUK have plan-specific quantity limits.
08Privacy & security
Zero Data Retention by default on core text AI.
Core text and chat requests use Zero Data Retention routes by default, so the model
provider cannot keep prompts or responses for training. You can change the AI Privacy
setting to reach models without that protection; live web search has its own setting,
because a current-information lookup may need a standard provider route.
- 01TLS 1.3 for data in transit.
- 02AES-256 full-disk encryption at rest on dedicated hardware.
- 03Role-based permissions and audit logging.
- 04Dedicated servers in Hetzner's German data centres for EU data residency.
- 05UK GDPR-aligned handling.
- 06Optional two-factor authentication for user accounts.
- 07Continuous monitoring and a defined incident-response process.
- 08We do not train models on customer content.
- 09Media and voice tools send only what the job needs, under each provider's own API terms.
Image and video tools send the prompt and the generation parameters to a specialist
provider; voice and transcription tools send the text or audio required. Completed media
is downloaded to our own storage. Those providers operate under their own retention
terms, so the text-AI Zero Data Retention statement should not be read as covering every
media tool.
Assessing Raq.com for regulated or sensitive data? Read the current Privacy Policy, the
AI Privacy & Security page and the subprocessors list, then map your own legal and
sector requirements onto the specific tools you plan to use.
Give your
agents
somewhere
to work.
Start a free trial with no card. It allows one use of each AI tool and limited
monitoring — enough to run a real job end to end and see where the record lands.