Token Maxxing Got Its Invoice
Pro Edition
This week’s free edition made the argument: Consumption is the wrong scoreboard, and the token bill is the raw material for a better one. This is how you build it, starting with the hard part: defining what output even means before you try to price it.
Define output before you measure it
“Output per token” is easy to say and hard to compute, and anyone selling you a clean, single number is … well … selling you something. Output shows up in different forms for different teams, it lags the spend that produced it, and attribution is messy. None of that is a reason to give up. It’s the same problem finance already solved for every other input it manages, where imperfect proxies beat no measurement at all, and the discipline is knowing exactly how each proxy lies to you.
Rank the proxies by how easily they’re gamed. The harder a measure is to fake, the more it’s worth … and usually the harder it is to collect.
Code artifacts. Merged pull requests, deployed changes, tests passing. Concrete and available today. The trap is that volume games it. One study found code churn, lines written then quickly deleted, rose more than 800% under heavy AI use, so a PR count can climb while durable work does not.
Knowledge artifacts. Drafts shipped, analyses delivered, models run, decks built. This is where finance, marketing, and operations actually show up, and it’s the layer most token dashboards ignore entirely. Same volume trap with fewer people watching for it.
Downstream outcomes. Cycle-time drops, ticket deflection, revenue per rep, faster close. Much harder to fake and much harder to attribute cleanly, which is the tradeoff that makes it valuable. This is the layer a board believes.
Judgment overlay. Was the work worth doing at all. No metric captures this, so a human has to. The productive, inefficient, or wasteful tag in the workbook is that judgment made routine, applied per session and rolled up.
Two data points explain the importance of that layering. Jellyfish found the heaviest token users were about twice as productive while spending 10x the tokens, so volume and value have already come apart in the data. And Gartner reports fewer than a third of decision-makers can identify specific financial outcomes from their AI investments. The gap isn’t a spending problem. It’s a measurement vacuum, and the proxy hierarchy is how you start filling it.
This section feeds the classifier tab. The tag is the judgment overlay; the roll-up is the productivity-of-spend read your provider dashboard will never hand you.
Tokens as COGS, worked
The reframe only pays off once it hits the P&L; and that starts with a split most teams haven’t made: Customer-facing inference is cost of goods. Internal productivity is operating expense. The same model lands in both depending on the job it’s doing. A support agent answering your customers is COGS. An engineer running Claude Code against your own repo is Opex … or capitalized development if it meets the bar. Sort every token line into one bucket or the other before you do anything else, because the two behave nothing alike on the way to the board.
But the split is important because tokens in COGS scale with usage, and if usage scales with revenue, your gross margin compresses as you grow unless cost-per-transaction falls faster than volume rises. That’s the number the board reads first, and a token line buried in a SaaS category will distort it without anyone noticing until the quarter closes. Tokens in Opex behave more like headcount, lumpy and forecastable, and they belong in the productivity conversation rather than the margin one.
For anything you sell with tokens riding inside it, the unit economics are the whole game. Cost per request has to clear comfortably below the contribution you earn per request, and that’s where routing stops being a hygiene tip and becomes margin defense. Sending a support classification to a frontier model isn’t a preference, it’s a gross-margin leak. Published cases show routing and caching together cutting 60 to 90% with no measurable quality loss, and the fattest single target is context, which runs about 62% of the agent bill when every step reloads the whole conversation. You aren’t trimming cost, you’re protecting margin.
This section feeds the routing decision table. Cost-per-task by tier is the input that tells you which requests are safe to keep on the expensive model.
Two runbooks, read as instruments
Uber is the runaway train here. The company gave roughly 5,000 engineers Claude Code and burned its entire 2026 AI budget in four months. And its own COO conceded the spend didn’t clearly track to features shipped. What did they measure? Adoption and volume. What they missed was whether the volume actually produced anything. The scoreboard was pointed at the meter the entire time, which is the failure the free edition described.
The turnaround is the mirror image. One team took an $87K April invoice down to $24K in May with routing, caching, and context pruning — and sprint velocity held flat. The difference was they classified the spend, found the waste, and cut it without touching output. The distance between those two invoices is the recoverable line, and it came entirely out of sessions that were never producing in the first place. Map your own situation onto one of these before you build the forecast, because the fix is different depending on which one you are.
Forecast it
Most token budgets are built through the path of least resistance: last month times a growth rate. And they break within a quarter because token demand doesn’t grow in a straight line. Build it driver-based instead.
Tokens = headcount by role x adoption rate x intensity per active user
This is phased along an adoption curve rather than a flat percentage. New hires ramp over a few months. Power users plateau. Agentic workloads step-change the day you deploy a new agent, and no smooth growth rate will ever catch that jump.
The commercial side follows from the same data. With real consumption history you can size a committed-spend tier instead of guessing, which carries weight now that pricing itself has moved. Anthropic split programmatic usage onto a separate metered credit pool in mid-June, and GitHub Copilot shifted to usage-based billing at the start of the month, so any budget set last fall is already stale. Finance leaders are responding by reforecasting quarterly and negotiating directly with the labs rather than defending an annual number nobody believes anymore.
This section feeds the savings estimator. The driver inputs are what turn a projected reduction into a defensible line in next quarter’s plan.
Budget the bots with the body
We need to reframe the way we think about AI spend. The fully-loaded cost of a hire used to be two lines: base comp + tax and benefits. It’s three lines now. Comp, benefits, and a token budget that travels with the person.
Model it per role. An engineer carries the largest token line by a wide margin, with Claude Code running $150 to $250 per developer each month for typical use and power users reaching $500 to $2,000. A financial analyst or a marketer carries a smaller line, though anyone living in these tools is not cheap either. The point for planning is that the moment you approve a rec, you have approved the bots that come with it, and your H2 headcount model should say so explicitly. Skip that and every hire sneaks in an unbudgeted variable cost.
The endpoint of this trend is already visible. Nvidia’s VP of applied deep learning told Fortune that for his team compute now costs more than the employees running it. Most finance teams are nowhere near that ratio today. The ones that model the token line per head now will not be surprised by it later.
Keep the scoreboard alive
An audit you run once decays by the next close. The cadence is what lasts. Instrument spend by team, model, and key daily. Give FP&A and a platform partner joint ownership of a weekly review. When a key spikes, notify and investigate rather than auto-capping, because the spike is often your most productive person mid-project. Monthly, take the productive-inefficient-wasteful mix to leadership as a standing KPI, so the scoreboard stays about output instead of drifting back to the total.
The durable control is enablement, not restriction. The 20x spread between two developers on the same tool closes with training, and organizations with mature AI-literacy programs report positive AI ROI at nearly double the rate of those without. A cap saves money once. A team that knows how to scope and route saves it every month, and produces more while doing it.
The prompt pack
Six prompts, structured Role / Action / Context / Format. Paste them straight into your workflow.
1. Session classifier. Role: FinOps analyst. Action: classify each AI session as productive, inefficient, or wasteful. Context: a usage log with task descriptions, token counts, and the model used per session. Format: a table with the tag, a one-line reason, and the recommended fix.
2. Model-downshift evaluator. Role: cost engineer. Action: decide whether a task can move to a cheaper model without losing quality. Context: the task description, the current model, and a sample of current output. Format: a verdict of downshift or hold, the target model, and one risk note.
3. Context-hygiene rewriter. Role: prompt engineer. Action: trim a bloated prompt and its context to essentials. Context: the full prompt, the system context, and the actual goal. Format: the rewritten prompt and an estimate of tokens removed.
4. COGS-versus-Opex sorter. Role: controller. Action: sort a list of AI workloads into cost of goods or operating expense. Context: a list of workloads with a short description of what each one does and who it serves. Format: each workload tagged COGS or Opex with a one-line rationale.
5. Weekly finance briefing. Role: FP&A partner. Action: turn raw token usage into a CFO-readable weekly brief. Context: this week’s usage by team and model, plus the prior week for the delta. Format: five bullets covering what changed, the driver, the COGS-versus-Opex split, a watch item, and an action.
6. Commit-tier sizer. Role: procurement analyst. Action: recommend a committed-spend tier from consumption history. Context: trailing three to six months of usage, the growth rate, and the provider tiers on offer. Format: a recommended commitment, the rationale, and the break-even against on-demand.
Run it this quarter
Download the Token-Efficiency Audit Workbook and the prompt pack below. Classify one team’s sessions against last month’s export, sort the workloads into COGS and Opex, and you’ll walk into your next forecast review with a recoverable number, a margin read, and a driver-based budget instead of a guess.
Glenn Hopper spent two decades as a CFO before turning to the question this newsletter keeps circling: what AI actually costs a business, and what it's worth. He writes Deep Finance Dispatch and, through RoboCFO, helps finance teams instrument, forecast, and govern their AI spend instead of guessing at it.