Agentic Transformation for Organisations
In development. Taking enquiries.
- ·It is not a programme, it is not a platform, and nothing runs on our infrastructure. The work happens inside systems the organisation already owns.
- ·One process is chosen, its current cost is measured, the agent version is measured against it, and the result is reported whichever way it comes out.
- ·There is no roster of transformed organisations on this page, because there is not one yet.
| Becomes live when | A local experiment on one real process is finished and its evidence pack is published, including at least one result that came out red and at least one claim that could not be verified. This is the thinnest delivering system on the list: the process analysis specialist the plan wants has not been built, so today it is assembled from general strategy and engineering members. |
| Delivered by | chief-of-staff · · ai-engineer |
| Skills used | spec-it · eval-suite |
What this involves
Start with what this is not, because the phrase attracts the opposite. It is not a programme. It is not a platform. Nothing runs on our infrastructure, no data leaves systems the organisation already owns, and there is no licence attached to the result. If the engagement ends and the organisation keeps nothing, it was sold wrong.
The unit is one process. Its current cost is measured first, in the plainest terms available: how long it takes, how often it is redone, and how often it is wrong. Then the agent version is measured the same way against the same tasks. Then the comparison is reported to the people who asked for it, including the parts that came out worse.
The reason for that shape is uncomfortable and worth stating on a page trying to sell the work. The published failure rates for large AI transformation programmes sit high enough that the phrase itself is now a warning label in the market's own data, and the failures are consistently programme-shaped: broad, top-down, and measured by activity rather than outcome. A single measured process is the smallest thing that can honestly be called a result.
There is no roster of transformed organisations on this page, because there is not one yet. The condition for that changing is stated above the fold and includes publishing a red result, which is the part most vendors' first case study is missing.
How the work runs
1. Discovery
We agree what the project has to achieve, what it must not break, and how we will both know it worked, before any code is written.
2. Build
The work is built with an AI agent as the working partner and a human reviewing every change before it lands. You get commits you can read rather than a status update.
3. Review
You review running software at each milestone, not a screenshot of it, and the next milestone absorbs what you send back.
4. Launch
We deploy to production with checks in the pipeline and alerting that reaches a human, and you hold the repository and the infrastructure accounts.
Questions people actually ask
Is this an AI transformation programme?
No, and the distinction is the point rather than a quibble. A programme is bought at the organisation level, runs for quarters, and is measured by activity. This is bought one process at a time, is measured against how that process ran before, and is designed so that stopping after the first one leaves the organisation better off rather than half-migrated.
Where does our data go?
Into systems the organisation already owns and already governs. There is no platform to sign up to here, and if a step genuinely requires sending data to an external model, that step is named in the scope with the alternative next to it before anything is built.
What if the agent version is worse?
Then that is the reported result and the process is handed back unchanged. This is the reason the measurement is agreed before the build rather than after it: a comparison designed once the results are in will find something to be pleased about.
What is honestly missing from this service today?
Two things, both stated rather than hidden. There is no published experiment yet, so there is nothing here to check. And the delivering system is the thinnest on this site: the process analysis specialist this work wants has not been built, so it is currently assembled from general strategy and engineering members who were designed for other jobs.