Brahim Bousnguar

Notes · Article

Tokenomics: don't count tokens, count what they bought

By · · 5 min read

Listen · 6:17 · read by an AI voice

Listen to this article0:00 / 6:17

Read by an AI voice · MP3

Tokenomics is AI economics: the discipline of turning energy and capital into AI, then using that AI well enough to show business value. It's not the crypto kind. Its first rule sounds odd for something named after tokens: don't count tokens. Count what they bought.

That's the pitch from J.R. Storment, executive director of the new Tokenomics Foundation at the Linux Foundation, in a five-minute keynote at AGNTCon + MCPCon on October 22. He opened with two questions for the room. How many of you know what your agents are costing you? A few hands. How many can tie that to value and ROI? One, at the back.

Energy in, value out

His slide gives the definition: take energy and capital, put them through chips to create intelligence, consume that intelligence efficiently, and drive measurable business value at the other end. His shorter version: energy creating intelligence driving value.

The definition is still a draft. The Linux Foundation launched the Tokenomics Foundation on August 4 to write open, vendor-neutral standards, benchmarks and best practices for the economics of AI, and it works closely with the FinOps Foundation.

Energy creating intelligence driving value

  1. Energy and capitalgo in
  2. Intelligenceis created
  3. Business valuemeasurable, at the other end

DraftVersion 0.5.2, dated September 1, 2026. It will move.

The definition from his slide as three steps. The marker walks them in order; the last one is the one the business cares about.

Cost per outcome beats cost per token

Token counts are not the important value metric, he said. Even cost per token isn't right. Cost per task is better, cost per outcome is better still, and what you finally need is business value from the total cost of AI, not just the cost of tokens.

A token count tells you how busy the models were. It can't tell you whether the work was worth doing. My TokenOps note has the other half of this problem: why the cost of one task can grow much faster than the number of turns it takes.

From counting tokens to business value

  1. SkipToken countNot the important value metric
  2. Not rightCost per tokenEven this is not the right one
  3. BetterCost per taskWhat one piece of work cost
  4. BetterCost per outcomeWhat one result cost
  5. The pointBusiness valueFrom the total cost of AI, not just tokens
Five metrics, the one to skip first and the goal last. The steps are his; the one-line glosses are mine.

The bill is more than the model

The total cost of AI includes everything under the models. He listed what agents quietly pull in: idle compute, storage, network, data, and often licensing and software. Then labor: your time, your colleagues' time and the company's time to manage all of it, plus what it does to hiring and staffing plans over time.

A token meter sees none of that below the line. My own Meterlex prices every model call from the session logs, which is exactly the visible slice. Useful, and only the top of the answer.

ModelsThe tokens. What a meter sees.

Above the line a meter sees it. Below, it does not.

  • Idle compute
  • Storage
  • Network
  • Data
  • Licensing and software
  • LaborYour time, your colleagues' time, the company's time to manage it, and the effect on hiring and staffing plans
Not to scale. The talk gave no proportions, only the list.

The business counts something else

The business, he said, does not care how many agents you have, how many tasks they finish, how many lines of code you write, how many PRs you ship or even how many features. It cares about revenue, outcomes, and how the organization changed. And that side is less cool than what you can ship with an agent this afternoon, which is why it's talked about less.

He sees a pattern from cloud coming back. There it went too expensive, so people pulled workloads back: repatriation. With AI the first signs are there already, in the stories moving from token maxing to how we realize value on the other end.

What we count

The shipping

Agents

Tasks accomplished

Lines of code

PRs shipped

Features shipped

vs

What the business counts

The change

Revenue

Outcomes

How the organization changed

Cloud, again?Too expensive, pull it back. He sees the first signs with AI.

His two lists, side by side. Nothing on the left is wrong; it's just not what gets the budget signed.

Three layers, and a gap at the end

The Foundation looks at the whole supply chain, in three layers. Production is the data center side: energy, chips, the AI factories and the models. Consumption is how well we use what comes out: the KV cache, prompt engineering, model selection, demand forecasting, even the cost of the harness. Value is not only cost per outcome or intelligence per watt but business impact, including pricing models and margins.

Their first survey, the State of Tokenomics, ran in September. Plenty of respondents were confident they could see their spending. Very few were confident they could show value on it to the person who signs off the AI budget, the CFO. He called that a real disconnect. The talk gave no figures and I haven't read the report, so I won't quote any.

  1. 1 · Production

    • Energy
    • Chips
    • Data centers
    • AI factories
    • Models
  2. 2 · Consumption

    • KV cache
    • Prompt engineering
    • Model selection
    • Demand forecasting
    • Cost of the harness
  3. 3 · Value

    • Cost per outcome
    • Intelligence per watt
    • Business impact
    • Pricing models
    • Margins

First survey: who is confident

Seeing the spendPlenty

Showing the CFO the valueVery few

Three layers, then the disconnect from the survey. Bar lengths are schematic: the talk gave no figures.

What the community is building

Work is going on across all three. He named caching optimization, model routing and gateways, and Big T, a riff on Big O for tokens. On the Foundation's site Big T writes token growth as T of n times k times a: n is requests or input size, k is model calls per request, a is agent depth. The page lists more levels between them; I've only checked the two ends and the default:

LevelWhat it is
T of 1A cache hit, no model call at all
T of nThe healthy default: one call per request
T of infinityUnbounded: a loop with no termination condition

The page's advice is to bound depth and add budgets. The launch announcement adds two more items of planned work: token cost telemetry in FOCUS, the FinOps cost-reporting format, and value measurement that starts with the share of work completed without human involvement.

All of it, he said, cascades into one job: take what your AI did and show the business in terms it recognizes. Revenue. Cost avoidance. Capacity gain. Labor augmentation. Speed to market, and not just code to market.

Work under way

  • Caching optimization
  • Big T: Big O for tokens
  • Model routing and gateways

What the business hears

  • Revenue
  • Cost avoidance
  • Capacity gain
  • Labor augmentation
  • Speed to marketnot just code to market

The jobShow the impact of your AI in terms the business already uses.

The technical work on the left only matters if it ends up in one of the five words on the right.

Try it

The Foundation's conference in San Diego, Tokenomicon with FinOps X, runs June 7 to 10, 2027. Before then:

Next time you open an AI bill, write one outcome next to it in the CFO's words. If you've managed a real cost per outcome, I'd like to hear how you defined the outcome.

Plain text: tokenomics-dont-count-tokens.md · Atom feed · All notes

Contact

Say hello.

b.bousnguar@gmail.com

SAP Commerce Cloud, MuleSoft and Salesforce integration · Nantes · EN / FR