Agent&Capital  ·  The Pilot

Forty days, from access to evidence.

A 40-day diagnostic sprint that reads the contracts, invoices and identity data a business already holds and returns quantified, evidence-backed findings. Read-only throughout. Nothing changes in day-to-day operations. Every finding traces from the EBITDA impact down to the source document that produced it.

Read-only Day 15: early signal gate Day 40: go / no-go
The entry point

Why contracts
go first.

Of all the places agentic analysis can start, vendor contract optimisation offers the fastest path to quantified, auditable savings with the least operational disruption. The pilot asks a direct question: is the company paying more than it agreed, on terms it never chose?

Speed to evidence

Quantified findings by Day 15

The data already exists: invoices, purchase orders, vendor agreements. Nobody generates new data, nobody changes a process. The agents read what is already there.

Low disruption

Read-only, inside your perimeter

The platform is deployed as infrastructure inside your own cloud subscription or data centre, on Microsoft 365, Google Workspace or mixed estates, with scoped, read-only, time-boxed access your IT administrator sets up once. It never changes, moves or deletes anything. Operations continue untouched.

Direct P&L impact

Every finding lands on a line

A contract at £10 per unit invoiced at £10.40 is pure EBITDA leakage. Net-30 terms paid on day 12 without the early-payment discount is cash leaving faster than it needs to.

The one rule that survives everything

Your data never
leaves your perimeter.

The perimeter is the set of environments you control: your cloud subscriptions and, where required, your own data centre. The entire platform, including the AI models, is deployed inside that perimeter as infrastructure you own and can switch off at any time. Every other component is chosen on merit. This rule is not negotiable.

Everything inside

Processing, inference, storage, reporting

All of it runs in a dedicated subscription inside your own cloud organisation, or in your data centre. Nothing is sent to us or to anyone else.

The AI models too

Your cloud provider's own model service

Claude through Amazon Bedrock in your AWS account, Microsoft Foundry in your Azure tenant, or Vertex AI in your Google Cloud project. Procured on your bill, under your existing agreement. No new vendor in the data path.

Egress-locked

The compute cannot reach the internet

Default-deny outbound, verified by your network team before Day 1 and by flow logs every day after. The only thing that ever leaves is the report pack you choose to share.

You hold the kill switch

One command to remove everything

Delivered as infrastructure-as-code you can inspect. Decommissioning is a single command in your subscription, and it is yours to run. Access grants carry a pre-agreed expiry date.

How it runs

Two weeks of setup,
forty days of evidence.

A short Phase 0 with your IT security team, then a 40-day diagnostic sprint with decision gates at Day 15 and Day 40. No executive installs anything, grants anything or lends an account to anything.

Phase 0 · about ten working days before Day 1

Setup and consent

One conversation with IT security, using our pre-filled security pack. Deployment into your subscription by infrastructure-as-code, scoped read-only access with a pre-agreed expiry, egress-lock verification, a benchmark run of the AI model in your own region, DPIA sign-off. About three days of one IT administrator's time.

Days 1 to 15

Discovery and first findings

Full crawl of the agreed scope, extraction, validation against accounts-payable data, certification of early findings. Gate 1 at Day 15: £250K or more in quantified, evidence-backed findings, or an honest early exit.

Days 16 to 40

Deep validation and roadmap

Complete coverage, cross-department harmonisation, dependency and blast-radius scoring, renewal calendar, prioritised value recovery roadmap. Gate 2 at Day 40: £500K or more in recoverable annual EBITDA with at least five findings safe to act on now.

What we need from youHow much
IT administratorAbout three days in Phase 0, then about two hours a week on call during the sprint.
ERP accounts payableRead-only access to invoices, payments and purchase orders, by API or a periodic export.
Directory and documentsRead-only access to the company directory and scoped read access to the agreed document libraries, shared drives and mailbox groups.
A reviewerA procurement or finance lead for about four hours a week. Our specialists certify every finding first; your reviewer validates certified findings, and your CFO commits them at Day 40. Your team never sees an uncertified finding.
At the endYou keep the findings, the evidence, the roadmap and, if you continue, the running platform in your own subscription. If not, one command removes it, the grants expire, and a deletion certificate is issued. Source systems were never modified, so there is nothing to restore.