One place to see everything. One place to control it.

The AI Control Centre gives you what you don't have today: a single, honest record of every AI tool touching your business, what it's touched, and who said yes to it.

Three questions worth being able to answer

  • Can you show which AI tools are actually touching your systems right now?
  • Can you show what customer or business data has passed through them?
  • If a supplier questionnaire landed tomorrow asking exactly this, what would you actually send them?

Most businesses can't answer all three. That's not a judgement — it's roughly where AI adoption inside most mid-sized businesses currently sits. It's exactly what the Control Centre is for.

ToolUsed byTouchesApproved byStatus
ChatGPT (Team plan) Sales Customer emails Unapproved
Claude Finance Invoice data James O. Approved
Copilot Operations Sage 200 records James O. Approved
Personal ChatGPT account Unknown Unknown Unapproved

Illustrative — what you can see once your AI tools are actually joined up, not a real business's records.

This is the screen the three questions above are actually about — the ledger below is what happens once something on it moves.

TimeSystemActionStatus
09:15 Sage 200 Read Logged
14:02 AI Drafted a follow-up for Aldata Ltd Awaiting approval
14:07 James O. approved the draft Approved
14:07 HubSpot Write Logged

Illustrative — a real ledger, not a reconstruction from memory.

Where we actually are right now

You'd be among our first customers — which is exactly why the entry point costs you nothing while you weigh it up. If that matters to your decision, ask us directly during the free snapshot; we'd rather you know exactly where we are than guess.

We're not here to stop your team using AI. We're here to make sure it's visible.

Every AI action sits as a draft until someone in your business approves it — nothing changes without a named person saying yes. Not a policy nobody follows. A record nobody can argue with.

You set what needs approval and what doesn't. Routine, low-risk actions can run on their own; anything touching customer data, money, or an external message waits for a named person to say yes. You decide where that line sits — this isn't an extra job, it's a switch you control.

The approval gate: proposed, held, routed, decided, then logged A five-stage flow. AI drafts a follow-up for Aldata Ltd. It is held as a draft, nothing sent. It is routed to James O. He approves or declines. Either way the outcome is written to the ledger. AI proposes Follow-up for Aldata Held Nothing sent yet Routed To James O. Approved Declined LOGGED EITHER WAY

Illustrative — the critical beat is the pause: nothing happens until a named person says so

Never boxed into one AI provider.

Behind the scenes, we always use whichever AI genuinely fits the task — so you're never stuck paying inflated prices for a tool that's fallen behind. Worth knowing, not worth leading with.

Questions about the ledger

Does every AI action need approval before it changes anything?

Reading data doesn't need approval — nothing changes. Writing back to your systems does, by default: an AI-drafted action sits as a draft until a named person approves it, and that approval is itself part of the record.

Is a logged action the same as a certified-secure one?

No. The ledger describes how the system is designed to work — it isn't a certification, and we don't imply it is one. See Security and Data Handling for what's actually in place today.

Can I show the ledger to an auditor or in a supplier questionnaire?

It's designed to give you something concrete to point to when you're asked what your AI actually touched — a real record, not a reconstruction from memory.

Get your AI Exposure snapshot