Skip to content
Discuss your first workflow

One business.
One Twin.
Any AI.

Your team already uses Claude and ChatGPT. Your Twin connects them to the systems you run, so every answer, dashboard and workflow works from live records, not uploaded spreadsheets, and each person sees only what they are allowed to.

Your Twin’s app

Answers, with their sources

Read-only evidence path

Your TwinOne governed picture of the business, built from your records.

Connect the systems you useKeep your original records in the systems you use
Accounting · payments
Xero
SunSystems
Stripe
GoCardless
Documents · files
Microsoft 365
SharePoint
Google Drive
Knowledge · CRM
Google Docs
Google Sheets
Notion
HubSpot
Email · calendar
Gmail
Calendar
Outlook
Chat · meetings
Slack
Teams
Granola
Engineering · data
GitHub
Linear
Postgres
MySQL
SQL Server
Other connections agreed for your first workflow

Mercury Labs has delivered for

  • HM Government logo
  • Department for Education logo
  • Department for Work and Pensions logo
  • IfATE logo
  • HVM Catapult logo
  • MTC logo
  • Harrison Parrott logo
  • PrimaryBid logo
  • Augmentive logo
  • Forestreet logo
  • LVF Creative Studio logo

Client work by Mercury Labs, the team behind your Twin.

Spend less time assembling the picture.

Your Twin has its own app, and it also answers inside the AI tools you already use. On their own, those tools search one system at a time.

  1. 01Without your Twin

    Claude, with its own connector to Outlook, finds two of the three decisions due by Friday, and none of their dates, amounts or owners.

  2. 02With your Twin

    The same question to Claude with your Twin connected: all three decisions, with their dates, amounts, owners and the system each came from.

  3. 03A shared understanding

    Your Twin links the same customer across systems and connects their invoices, projects and commitments. The sources stay available to inspect.

  4. Twin chatShared context

    Where are we with Northstar?

    The website is delivered. The £8,400 invoice is overdue, and the client expects to pay Friday.

    Retrieved with

    Ask anything about this task…

    One Twin. Your tools. The same business knowledge.Example interfaces · External tools connect with your permission

    04A useful answer

    Ask the same question in Twin chat, ChatGPT, Claude, Gemini or Copilot, or from your own code through the CLI, SDK and API. Each uses the same connected records and definitions from your Twin. In Microsoft 365 Copilot and Teams, your Twin appears as an agent your team can ask.

Build on it with the AI you already use.

If your team is already building with Claude or ChatGPT, keep going. Your Twin gives those tools live records from your systems, joined and permissioned, so nobody exports or uploads the data first.

  1. 01In Claude and ChatGPT

    Connect your Twin once. Ask for a chart, a summary or a draft, and the assistant reads the figures from your records when you ask.

  2. 02In your own code

    The CLI, SDK and API give your scripts and internal tools the same records and the same definitions.

  3. 03In your Twin

    Save what works as a dashboard your team shares, or run it as a workflow on a schedule.

Connected records refresh on the schedule agreed for each source. Each person, and each tool they use, reads only what they are allowed to see.

Your Twin finds the match. You make the call.

When records in two systems look like the same customer, your Twin brings the match to your Inbox with the evidence side by side. Accept it, decline it or leave it for later. An accepted match can be undone.

An illustration of a proposal in the Inbox. Xero's contact Tarnwick University and HubSpot's company University of Tarnwick look like the same customer: their names are 84% alike and their website domains are identical, at 90% confidence. A person accepts the match, and the two records become one linked customer.

Agree the meaning. Reuse the understanding.

Which records describe the same customer? What counts as overdue? Your Twin connects identities, relationships and definitions, then checks the calculations against your data.

Your Twin’s app · Sample workspace

A sample run in a sample workspace: a services firm tests its weekly aged-receivables workflow. Each step runs in turn on the canvas: it reads the HubSpot companies and the Xero invoices, matches each customer across both, ages each invoice, ranks the customers by balance and checks that the totals reconcile. It ends on the results, each customer's balance by age.

Define it once. Ask it anywhere.

Ask three people what is overdue and you may get three numbers. Your Twin agrees each definition with you once, then uses it for checked answers wherever your team asks.

An illustration of a definition proposed in the Inbox. From the amount due, due date and status of Xero invoice INV-0027, your Twin proposes what counts as an overdue invoice: money is still owed, the due date has passed, and the invoice is not voided or deleted. On this workspace's data that is 7 of 16 open invoices. A person accepts it. The same thing is then asked in Twin chat and in ChatGPT, in different words, and both answers give £9,223.08 and name the definition and version they used.

  1. 01Drafted from your data

    Your Twin reads the systems you connect and drafts each definition in plain terms: what it counts, and what it leaves out.

  2. 02Accepted by you

    Each definition comes to your Inbox. Your Twin uses it for checked answers only once an admin has accepted it.

  3. 03Named in checked answers

    A checked answer shows the definition and version it used. A change is a new version, back in your Inbox for review.

An answer you can check.

See who owes what, using the same definition of outstanding debt. Inspect the invoices, ageing calculation and sources behind the answer.

Your Twin’s app · Sample workspace

The sample workspace with two pages open in tabs. The first is a finished session: a services firm asks for its aged receivables by customer, and the answer ranks each customer's balance by age, gives the total overdue and the two accounts to chase first, states the basis of the calculation and lists the sources it was retrieved with. The second is the Finance channel's sales invoices on their Receivables dashboard: the total outstanding and overdue, the number of open and overdue invoices, the outstanding amount by age, the overdue amount by customer, and the overdue invoices listed. The dashboard's figures are the answer's.

The figures are calculated. Never guessed.

AI models are good with words and unreliable with sums. So your Twin’s graph engine does the arithmetic: it holds your connected records and agreed definitions in memory and works out each figure. The model plans the question and writes the answer round it.

OverdueCalculated by the graph engine

£9,223.08

7 invoices, 4 customers

Definition
Overdue invoice v1
Counted from
Xero sales invoices
Read with
The access of the person asking
AI model used for the sum
None
Sample figure. Open it to see each invoice behind the total.
Same question, same number
The engine follows your definitions and uses no AI model, so the figure is the same in your Twin’s app, Claude and ChatGPT until the records change.
Answers in milliseconds
It is built in Rust and keeps your organisation’s records in memory, so a question across several systems does not wait on each of them.
Every figure traces back
Each result comes with what was counted and how, down to the invoices, bookings or tasks behind it.
Each person’s own view
It reads only the records the person asking is allowed to see, so a total never includes a row they could not open.

Your Twin. Your infrastructure.

A dedicated server for your business on the Core, Scale and Enterprise plans, with control over where it runs. The Team plan runs on a shared deployment.

  • European Union

    Available today

  • United States

    Available today

  • United Kingdom

    In development

The region is where your server runs. Model processing can take place elsewhere, depending on the provider you use.

Dedicated server
On Core, Scale and Enterprise, your Twin runs on a server dedicated to your organisation.
Read-only connections
It reads the systems you connect without changing the original records.
Your model provider
Requests go to the AI provider configured for your organisation.
Audit trail
Checked answers show the definition, version and sources they used.

Cyber security certifications

Mercury Labs, the company behind your Twin, holds both certifications through its legal entity, Mercury Digital Assets Limited. Scope: whole organisation.

Mercury Labs is a Crown Commercial Service supplier.

Legal & Security

Why keep AI in the UK

Your question never leaves the UK.

For many firms the hard question about AI isn’t what it can do. It’s where the data goes. A fully UK-hosted Twin keeps the whole path, from the question to the answer, inside the UK.

  1. 01Say yes to sensitive workClient files, contracts and personal data stay inside the line your policies draw, so AI can reach the work it was kept away from.
  2. 02No outside model providerPrompts and business context go to a private model on UK GPUs, not to a third-party AI service.
  3. 03One boundary to reviewServer, storage, model, logs and backups sit in one place, so your security review has one set of answers.
  4. 04The same checked answersSources, definitions and checks work as they do today, whatever model answers.

Runs on Project Venus, our private model: a draft model that predicts tokens ahead for speed, an adapter trained on real tasks, and no metering on token usage, subject to concurrency thresholds. Read the research

United KingdomIn development

ServerUK datacentre

StorageUK datacentre

Private modelUK GPUs

Logs and backupsIn the UK

Outside AI provider

Not on the route

Everything on the route, from the question to the answer, runs inside the UK.

Your choice of model

Or use the models you already know.

Your Twin can answer through Venus, our private model, or through OpenAI, Anthropic or Google. Whichever you choose, it works from the same records and definitions, and each checked answer shows its sources.

Requests go to the model configured for your organisation.

Your Twin’s app · Sample workspace

Model

Runs privately in the UK or EU

A finished session in a sample workspace: a services firm asks for its aged receivables by customer. The answer ranks each customer's balance by age, gives the total overdue and the two accounts to chase first, states the basis of the calculation and lists the sources it was retrieved with. The model menu is open over the answer, listing Venus, OpenAI, Anthropic and Google.

Forward-deployed engineering

Our engineers work alongside your team.

Reserve engineering time to connect your systems, check a first workflow or extend your Twin. We agree the work with you.

  1. 01Work with our engineersWork directly with engineers on your systems, business questions and the results you need.
  2. 02Faster path to live useConnect the systems for a useful workflow and check the results with your team.
  3. 03Expand where it helpsAgree additional connections and workflow improvements as your needs change.

£1,200 a day. Larger or dedicated teams are agreed separately. Add engineering days

Your Twin’s app · Sample workspace

The Finance channel's Feed in a sample workspace, over a fortnight with a Mercury Labs engineer. The engineer posts that Xero, HubSpot and Outlook are connected read-only and that nothing in those systems changes; that the Twin found three customers under two names and sent the matches to the Inbox to accept or decline; the firm's finance lead posts that overdue should start the day after the due date; and the engineer posts that aged receivables agrees with the customers checked by hand and is ready to switch on.

We connect the systems. You help define the result.

Start with one important workflow. In two focused weeks, we connect its systems and check the results with your team.

  1. Days 1–5

    Connect priority systems

    We agree the question, connect the systems it needs and start with read-only access.

  2. Days 6–10

    Build and check your Twin

    Your Twin connects the records, defines the calculations and tests them against your data. Work that fails the checks is left out.

  3. End of week 2

    Review the Twin, then switch it on

    Check the result against real business examples with your team. The release stays off until you switch it on.

Get started today on Team, from £75 a user a month on a shared deployment. Core from £3,000 a month with a dedicated, managed deployment and AI usage from £250 a month. Optional engineering at £1,200 a day. See pricing

The questions we hear 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.

More questions, including data and cost

Your first workflow

Start with the question your team keeps chasing.

Show us a recurring report, an awkward handover or a decision that takes too long to prepare. We agree a first workflow with you, then connect its systems and check the results with your team in two focused weeks.