Case Study: Putting a Defensible Number on AI Adoption

"The team really likes it" is the sentence that kills AI budgets¹. Not because it is false — because it is unpriceable, and it always loses to a line item that isn't.1A composite case, anonymised from several Fellow engagements. Numbers are representative of the pattern, not one client's audited results.

The situation

A 600-person services organisation had run AI licences and training for a year. Usage was genuinely healthy: daily activity, enthusiastic champions, anecdotes everywhere. Then the CFO asked the reasonable question — what did we get for it? — and the programme discovered it had no answer. No baseline existed for any workflow the tools had changed. The renewal went into review with sentiment as its only defence.

Their readiness profile showed the signature: solid Applied use, near-zero on impact measurement^◦.By the numbers0 of 14AI-touched workflows with any before-measurement, at the point the budget question arrived

Why value goes unmeasured

Nobody plans to skip measurement; it is skipped by default. In the excitement phase, measuring feels like bureaucracy slowing the fun down. Later, the before-state is gone — nobody recorded how long a report took in the era before the tools, so the improvement became unprovable the moment it succeeded^◦.DefinitionBaseline The before-measurement — time, quality, adoption — taken prior to a change, without which no after-number means anything

The cost is not hypothetical. Unmeasured programmes lose budget reviews to measured ones regardless of relative merit, and the people who quietly gained hours a week lose them back when the licences go.

What we did

We did not build a measurement programme. We baselined exactly two workflows — proposal drafting and client-meeting summaries — chosen for volume, repeatability, and how visibly they mattered to the business.

For each: two weeks of honest before-numbers (time per unit, revision counts, who used AI at which step), one named owner of the number, and a one-page monthly delta report designed in the CFO's own format. Nothing else was measured on purpose — two credible numbers beat ten estimates^◦.FigureOne person owning one honest number is a measurement system; a committee with a dashboard is usually not

What changed

One quarter later, proposal first-draft time was down by roughly half against its baseline, with revision rounds flat — quality had held^◦. The renewal conversation took ten minutes: the programme survived the cut that year, and the same evidence format earned an expansion into two more workflows the next.By the numbers≈50%reduction in proposal first-draft time against a two-week baseline, quality flat

The deeper change was cultural: with a delta report on the table, adoption stopped being a belief and became a managed quantity — which also exposed one workflow where AI genuinely was not helping, and it was retired without drama. Proof cuts both ways, and that is the point.

What to steal

1. This month: pick two workflows — high-volume, repeatable, visible — and baseline them before your next change: time, quality proxy, adoption.
2. Name one owner per number. A committee owns nothing.
3. Report the delta monthly, one page, in the budget-holder's format — before they ask.
4. Let the number kill weak use cases. A programme that can retire failures is one that gets believed about successes.

If your readiness report flagged unproven value, your programme is currently one budget review away from resetting to zero — the two-workflow baseline is the cheapest insurance that exists^◦.RelatedWhy measurement is what keeps a rollout alive