Advisory Service · AI Sprawl Audit
You're paying for AI that nobody uses
Two years of pilots, agents, copilot licences and vibe-coded internal tools have accumulated across your estate. Most of it has no owner. Some of it still holds production credentials. All of it is on a bill somewhere. We find it, cost it, and give each one an owner or a shutdown date.
Request a sprawl audit
Tell us where to look and we'll come back with scope, timing, and what the first week would cover.
No obligation, no sales sequence. One reply from a human. Protected by reCAPTCHA.
The problem
Nobody set out to build an unmanaged estate
It happened one sensible decision at a time. The tooling got good enough that anyone could ship something, and nothing in your process says who turns it off.
Agents with no owner
Built for a project that ended, or by someone who has since left. Still running, still calling APIs, still on the invoice.
Seats nobody opens
Copilot and assistant licences bought per-seat and rolled out department-wide, with a third of them never used twice.
Vibe-coded internal tools
Apps prompted into existence by people who don't write code, now load-bearing for a team — and unmaintainable by anyone else.
Credentials nobody tracks
Each of the above holds an API key, a service account, or a data connection that was never inventoried and is never rotated.
How it works
Four weeks, from inventory to shutdown
Discover
We inventory what exists: SSO and OAuth grants, expense and procurement records, cloud and model-provider billing, browser-extension installs, and the internal app catalogues nobody has opened in a year.
Cost
Every item gets a real annual number — licence, inference, infrastructure, and the support time it quietly consumes. This is the column that funds the rest of the work.
Triage
Keep, consolidate, or kill. Each surviving item gets a named owner and a review date; each duplicate gets folded into the tool you're standardising on.
Retire
A decommissioning runbook per item: who to tell, what to migrate, which credentials to revoke, and what to keep for audit. Executed with your teams, not handed over as a PDF.
Deliverables
What you walk away with
The register
Every agent, assistant, and AI app in one list, with owner, cost, data reach, and status.
The spend picture
Annualised cost per item and the total you can recover by retiring the dead weight.
Decommissioning runbooks
A step-by-step retirement plan per item, including credential revocation and data retention.
The risk shortlist
The handful with production credentials or customer data that need attention this month, not next quarter.
Honest scope
An audit is a snapshot. Four weeks after we finish, someone will have shipped something new — that is the point of the tooling, and stopping it is not the goal. The audit is worth doing because it resets the baseline and tells you what it is costing you; keeping the register current afterwards is what stops you buying a second audit next year.
That ongoing half is what the AI Use-Case Registry and Atlas AI are for. You do not need either to get value from the audit, and we will tell you if you do not need them at all.
Related
Once you know what you're keeping
Find out what it's costing you
Most estates carry more unused AI than their owners expect. Four weeks is usually enough to find it, price it, and start switching it off.