Week of June 6, 2026
Tokens are the receipt. Not the result.
As AI adoption grows, the question is shifting from how much are we using to what work is actually getting done.
The bill is visible. The value is not.
When organisations start tracking AI, they usually begin with the easy things to count: licences, token spend, cloud cost, and tool usage. The harder question is what completed work or business value those signals actually point to.
Tokens prove the machine ran. Not that work got done.
Most AI dashboards blur three separate things: what went in, what happened, and what work was actually completed.
Input
Tokens, API calls, compute, licences
Activity
Prompts, agents launched, documents generated
Outcome
Work completed, risk cut, time saved, value captured
Most dashboards stop after the first two rows.
Measure usage, manufacture fake transformation.
When usage becomes the target, people maximise usage, not value. That is AI theatre: visible activity, no redesigned work.
Usage is climbing
Tokens consumed
+340%AI sessions per week
+210%Leaderboard rank
+4 positionsDocuments generated
+180%Everything looks great.
Outcomes are missing
Customer problem solved?
Cycle time reduced?
Quality improved?
Cost per outcome?
Nothing answered.
Reported examples at Amazon and Microsoft, and more tentatively Meta, point to the same risk: visible AI activity can look like progress even when the underlying work has not changed.
Service-as-a-Software: the recommended solution.
Once AI can complete parts of a workflow, the old software question becomes less useful. The better question is not who needs a seat, but what work should be completed, to what standard, and at what cost.
This is the strategic move behind Service-as-a-Software: AI makes it possible to sell the finished work, not just the interface people use to get there.
Define the unit before you claim the value.
A token count does not tell you whether the work improved. A completed unit does. That is how hidden AI value becomes something finance and operations can inspect.
Per resolved ticket
Customer support handled end to end, with verification and escalation only when needed.
Per reviewed contract
Standard contracts reviewed against approved playbooks, with deviations flagged and escalated.
Per reconciled invoice
Invoices ingested, classified, reconciled, and prepared for approval.
Per qualified lead
Leads researched, scored, and prepared with verified contact and intent data.
These units are the bridge from activity to value: they turn AI from something the organisation consumes into work the organisation can verify.
The question is no longer how much AI are we using
It is what work did AI complete, and did it create measurable business value?