Asked, answered.
How your Twin fits into your work, where your data goes, what it costs and what you control.
- Where does our data go?
Your Twin reads the systems you connect without changing the original records. On Core, Scale and Enterprise it runs on a dedicated server for your organisation; Team runs on a shared deployment. Keep managing the original records in your existing systems.
When you use an external AI provider, the business information needed for that request is sent to the provider configured for your organisation. We agree the connections, access and model provider before setup.
- Do we need to migrate our legacy systems first?
Keep your existing systems. We agree a first workflow and connect the systems it needs, starting with read-only access.
Mercury Labs engineers work with your team to connect the relevant records, agree business definitions and test the calculations against your data. You review the result before switching it on.
- Can we choose models and control their cost?
Yes. Use stronger models for demanding work and lower-cost models for routine tasks. Your Twin keeps the same business records and definitions when you change AI providers.
Each provider needs to be configured for your organisation. Important changes are tested before they go live.
- What does this cost?
Subscription: Team is £75 a user a month, on a shared deployment. Core starts at £2,000 a month, Scale at £5,000 and Enterprise at £15,000, and each of those includes a dedicated, managed deployment.
AI usage: Team includes a usage allowance, with top-ups available. On Core, Scale and Enterprise, model credit packs start at £250 a month.
Optional engineering: Mercury Labs engineers can help with setup and integrations at £1,200 a day.
See the pricing page for what each plan includes. We agree the work and costs for your teams and systems before starting.
- Why not just use ChatGPT or Copilot?
You can use them with the Twin. It connects your business records and agreed definitions, so your AI tools can work from the same company knowledge. Answers from the checked Twin show the sources and calculations used.
Keep your business knowledge in the Twin as your choice of AI tools changes. Each external connection needs the right setup and permissions.
- How does our Twin stay useful over time?
Connected records refresh on the schedule agreed for each source. When a business definition changes, it is checked and released for review, with version history. Your team and approved AI tools keep using the same shared understanding.
Your subscription covers the managed deployment and support included in your plan. We agree setup, additional connections and engineering work with you. Expanding the Twin starts with the next useful question, rather than rebuilding it for each AI tool.
- Where do we work through the results?
Channels bring related records, saved views, files and conversations together. Organise them around areas such as Commercials, Delivery or Finance, then work through a review or follow-up with the supporting records close by.
Your Inbox is where you review incoming updates and suggested actions, with the context behind them. Start an agent session from an item when it needs more work. What you can see and do depends on your access.
- We're regulated. Can we actually use this?
We need to check your requirements with you. Your Twin starts with read-only connections and access limited to your organisation. You can review each tested version of the Twin before it is switched on.
The standard checked query path does not include browser, terminal or write access. Your team still needs to approve where data and model requests go, how long evidence is kept and how the deployment is operated.
- What do the AI agents actually see?
While building the Twin: the AI agents use descriptions and measurements, not raw records. Software converts sensitive values into protected fingerprints before comparing them to find connections.
When you use it: agents can use the checked Twin or explore connected records within your organisation’s permissions. Exploratory work is kept distinct from answers produced through the checked Twin.
- Which systems can you connect?
Accounting and payments: Xero, SunSystems, Stripe and GoCardless.
Documents, email and collaboration: Microsoft 365, SharePoint, Outlook, Teams, Google Drive, Docs, Sheets, Gmail, Google Calendar, Slack, Granola and Notion.
CRM and delivery: HubSpot, Linear and GitHub.
You can keep legacy ledgers such as SunSystems. We confirm which records and connections your first workflow needs before setup.
- What happens when the Twin cannot support a question?
It tells you when the checked Twin cannot answer. This path (called a governed answer) identifies the published definition, version and source freshness it used. If the question or evidence is unsupported, it returns “not supported”.
An agent can still explore the underlying records within its permissions. That exploratory work is not labelled a governed answer and needs to be reviewed accordingly.