Skip to content
Discuss your first workflow

Your Twin / Food & consumer goods

Clear every
technical pack
before launch.

Your Twin connects launch critical paths in Google Sheets with technical specs and lab reports in Google Drive and supplier threads in Outlook, so missing allergen declarations and wrong-batch certificates surface before your launch gate.

For NPD, technical, operations and supply chain directors

The launch Twin · SKU, technical pack, supplier and owner

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
Google Docs
Google Sheets
CRM · projects
HubSpot
Notion
Productive
Asana
Linear
Email · calendar
Gmail
Calendar
Outlook
Chat · meetings
Slack
Teams
Granola
Engineering · data
GitHub
Postgres
Azure SQL
BigQuery
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.

What’s still missing before next month’s launch?

Ask across the critical path, technical packs and supplier emails. Catch missing allergen sheets, pending printer sign-offs and wrong-batch lab reports in seconds.

Your Twin’s app · Sample workspace

A replay of a session in a sample workspace: a tea company asks which products in next month's launch still have outstanding supplier documents, the Twin checks its launch products, the checklist in Google Sheets, the documents in Google Drive and Outlook, the answer streams in with each outstanding item and owner, then the first product's record opens.

Every launch gate, backed by its paperwork.

NPD and technical teams see what each supplier still owes — and who’s chasing it — before retailer deadlines hit.

  1. 01

    Spot missing certificates early.

    Match your launch checklist against actual allergen declarations, CoAs and packaging sign-offs.

  2. 02

    Check which batch and revision you’re reading.

    See the exact spec version and batch number behind every document.

  3. 03

    Know who’s chasing each supplier.

    Keep every open supplier query tied to a named owner — and flag anything unassigned.

Every upcoming SKU, with its technical pack.

NPD, technical and supply chain teams work from the same live launch list — each SKU tied to its launch date, missing documents, status and owner.

Your Twin’s app · Sample workspace

The Launches channel in a sample workspace, switching through its saved views of the launch products: a table sorted by the Target launch column, a board grouped by status, a calendar by target launch, and the Launch review dashboard, with what needs attention and the records by status, owner and date; then the channel's Overview, with what changed today. The replay above answers from these records.

Launch readiness, counted from the tracker.

How many SKUs launch next month with a supplier certificate still missing? Your Twin’s graph engine counts them from your critical path, so every team works from one list.

  • “How many SKUs launch in the next 30 days?”

    Counted fromLaunch products, by target launch

  • “How many still have a supplier certificate missing?”

    Counted fromLaunch products, by status

  • “Which owners are chasing the most open items?”

    Counted fromLaunch products, by owner and status

Same question, same number
The engine follows your definitions and uses no AI model, so the figure stays identical across Microsoft 365 Copilot, Teams, Slack, Claude, ChatGPT, the web app and Twin for Mac until the underlying records change.
Answers in milliseconds
It holds your connected records and agreed definitions in memory, so a question across several systems doesn’t have to wait on each of them.
Every figure traces back
Each result comes with what was counted and how, right 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 couldn’t open.

How you start.

Request Team access, from £75 a user a month (5-user minimum) on a shared deployment. Dedicated from £3,000 a month (up to 25 named users) and UK-hosted from £6,000 a month. Graph reads from Copilot, Claude, Teams and Slack use zero AI credits; add Twin Engineering Partner at £5,000 a month or Custom & Unlimited Development from £15,000 a month. See pricing

  1. 01 · First conversation

    Choose the review.

    Bring one launch critical path that’s always a scramble to finish.

  2. 02 · Week 1

    Agree the sources.

    Connect your launch tracker in Google Sheets, technical packs in Drive and supplier threads in Outlook — plus Xero if you want packaging and supplier bills alongside them.

  3. 03 · Week 2

    Check it with your team.

    Check the gaps against a launch your team already knows well. Expand from there.

A clear starting point.

  • No. It gathers and checks the paperwork for review — food safety and technical sign-off always stay with qualified people.

More questions

Your first workflow

Start with one launch checklist that’s never quite complete.

We look at it with you first. Then we agree which systems to connect and who can see the records, and check the result with your team in two focused weeks.