Skip to content

5 minute read

AI Economics in 5 Minutes

AI cost is measured far better than AI outcomes, and the gap widens with embedded SaaS AI, agents and human review. The whole argument in five minutes: why the gap exists, the one number to lead with, and how to get from spend to a decision.

Five stages from left to right: cost, use, value, proof and allocation. Cost and use are increasingly well measured; value and proof are where the gap opens.
From AI spend to a decision. Cost and use are increasingly well measured; value and proof are where the gap opens.
PwC, 29th Global CEO Survey

56%

of CEOs report no significant financial benefit from AI so far

Source: PwC, 29th Global CEO Survey, 2026

State of Tokenomics

39%

are not confident they can connect AI spend to an outcome their CFO would accept

Source: State of Tokenomics, 2026

Bain & Company

44%

are funding their next AI wave from prior automation savings that came in below target

Source: Bain & Company, 2026

Surveys describe their respondents, not the whole market. Sources and caveats.

The problem in one sentence

There is a gap between what organisations spend on AI and the share of that spend they can connect to a measured outcome. That difference is the AI Value Gap. Cost data tends to be automatic and timely. Value data tends to be manual, delayed and contested. Many leaders can say what they spent last month far more confidently than what they gained.

Bar chart contrasting AI cost that is tracked precisely with the much smaller share of value that can be proven.
Cost is tracked to the token. Value proof lags far behind.
Bar chart contrasting AI cost that is tracked precisely with the much smaller share of value that can be proven.

Cost is tracked to the token. Value proof lags far behind.

PwC’s 2026 survey of 4,454 chief executives found 56% reporting no significant financial benefit from AI so far, and 12% reporting both cost and revenue gains. Bain’s 2026 survey of 951 companies found that nearly 40% of those measuring AI cost savings landed at 0 to 10%, although 37% had targeted 11 to 20%. See the key numbers for sources and caveats.

Why cheaper AI does not close the gap

As generating work gets cheaper, the limit on value moves from the model to people: the capacity to review, correct and absorb what AI produces. AI output that looks finished but is not costs someone hours to fix, and that cost rarely appears in the business case. A case that prices the tokens but not the review capacity overstates value.

Three bars: generate scales almost freely, verify needs people and process, absorb needs decisions and change. Value is capped by the narrowest stage.
Output is cheap. Review and absorption set the ceiling.
Three bars: generate scales almost freely, verify needs people and process, absorb needs decisions and change. Value is capped by the narrowest stage.

Output is cheap. Review and absorption set the ceiling.

This is the site’s most distinctive argument, set out in The AI Abundance Paradox and priced in The Cost of Verification.

The one number to lead with

Illustrative line from a measured starting level of attribution coverage to the owner's target four quarters later.
Illustrative, not a benchmark. Work out your own starting figure with the attribution coverage calculator.
Illustrative line from a measured starting level of attribution coverage to the owner's target four quarters later.

Illustrative, not a benchmark. Work out your own starting figure with the attribution coverage calculator.

From spend to decision: four phases, eight steps

The AI Economics System turns the argument into a working routine. Each phase answers one question and hands its output to the next.

  1. Phase 1MeasureWhat does AI fully cost, where is it consumed, and who owns it?01See the costEvery AI cost line, including seats, embedded SaaS tiers and platform.02Name the workloadAttach the cost to a piece of work with an owner.
  2. Phase 2ProveWhat changed because AI was used, and how strong is the evidence?03Measure the outcomeAgainst a baseline, counting only outputs that clear the quality floor.04Net out the cost createdReview, rework, escalation and harm.05Judge the evidenceAnecdote, before-and-after, matched comparison or controlled trial.
  3. Phase 3DecideGiven the economics and the evidence, what should be scaled, held, redesigned or stopped?06Compare full cost with valueIncluding verification and the platform the workload relies on.07DecideScale, hold, redesign or stop, with an owner and a date.
  4. Phase 4OperateWho owns each part, how often is it reviewed, and what reaches the board?08Check the decisionAt the next review, was it right? Adjust the rules if not.
Five evidence levels from E0, anecdote, to E4, controlled and independently validated, with the decisions each is good for.
More money needs stronger proof.
Five evidence levels from E0, anecdote, to E4, controlled and independently validated, with the decisions each is good for.

More money needs stronger proof.

A two by two grid of expected value against bottleneck load: scale, redesign, opportunistic and stop. Hold applies when evidence is below the level the commitment needs.
Evidence and load on people drive the decision.
A two by two grid of expected value against bottleneck load: scale, redesign, opportunistic and stop. Hold applies when evidence is below the level the commitment needs.

Evidence and load on people drive the decision.

Where this site sits

Cost and value measurement are being standardised by bodies such as the FinOps Foundation and the Tokenomics Foundation, whose value classification sets out how to build a value claim. This site focuses on the management layer above that evidence: how leaders compare claims, account for scarce human capacity, and decide what to fund, redesign or stop. The standards map shows where each body’s work ends and this site’s proposals begin.

Five stacked layers: cost structure, cost and usage data, operating model and value claims, each covered by an external standard, with the decision layer on top labelled as a hub proposal.
The standards measure cost and value claims. The decision layer says what to do with them.
Five stacked layers: cost structure, cost and usage data, operating model and value claims, each covered by an external standard, with the decision layer on top labelled as a hub proposal.

The standards measure cost and value claims. The decision layer says what to do with them.

Our position, stated plainly

We read the gap as mainly a governance problem rather than a measurement impossibility. Organisations already measure hard things, including marketing attribution and cyber risk. AI has not yet been given the same discipline.

Waiting for prices to fall is not a budget plan. Per-token prices are falling, but agentic systems multiply the tokens used per task, and new uses appear as access gets cheaper. Our expectation is that total AI bills keep rising for some time even as unit prices drop. How to budget for AI shows how to plan for that.

Unit price falls over time while volume rises faster, so the total bill keeps climbing after the lines cross.
The scissors: unit price falls, volume rises faster, the total bill climbs. Schematic.
Unit price falls over time while volume rises faster, so the total bill keeps climbing after the lines cross.

The scissors: unit price falls, volume rises faster, the total bill climbs. Schematic.

Time saved is not the same as financial value. Some saved time is absorbed by review and rework, some is too fragmented to redeploy, and some becomes extra output rather than lower cost. A credible value claim shows what happened to the released capacity instead of multiplying saved hours by salary.

What to do first

You can start with finance extracts, vendor portals and a spreadsheet. In the first 30 days:

  1. Name one owner accountable for AI economics, with a mandate from the CFO or CIO.
  2. Build one spend inventory in four categories: direct consumption, licensed seats, embedded tiers inside SaaS contracts, and infrastructure.
  3. Capture baselines for the top three use cases by spend, before that history ages out of your systems.
  4. Define one unit cost per major use case, fully loaded - for example, cost per resolved ticket or per accepted code change.
  5. Hold a first value review with finance in the room, publish the pack, and make three decisions: one tool to consolidate, one use case to baseline properly, one contract to renegotiate.

The toolkit has working templates for these steps, each with a worked example:

To see the system applied, the decision cases follow 4 illustrative workloads to a scale, hold, redesign or stop call, with the cost, claimed value and evidence level behind each.

Where to go next

The four questions a leader should be able to answer

01

What are we really spending on AI, in full?

02

Who owns the economic result?

03

What proof standard governs the next tranche of scale?

04

Which initiatives deserve more capital, less, or a redesign?

Organisations that can answer these are not just measuring AI better. They are governing it better.

Read next