The Bill Nobody Modelled For
Two large, AI-forward engineering organisations just hit a budget failure mode that no finance team modelled. That is the part worth a CXO's attention. The tools did not break. They worked well enough that engineers would not stop using them, and consumption-based pricing converts "loved by the team" into "the line item that blew up the Q2 forecast."
Agentic Coding Tools Don't Bill Like Software
Agentic coding tools like Claude Code are not priced like the software most procurement teams know. A traditional seat licence is a fixed number. You buy a thousand seats, you know the annual cost, and usage above or below the plan changes nothing.
Token-based billing inverts that. The bill tracks how much the model is used — every prompt, every long agent session, every large context window. For a tool that engineers genuinely love, adoption velocity and cost exposure become a single number.
The Uber Case: When Adoption Incentives Backfire
Uber did not stumble into this passively. The company encouraged adoption and ran internal leaderboards ranking engineers by Claude Code activity. Every incentive pointed toward more usage, and on token pricing, more usage is more cost.
The leaderboard worked. The budget did not survive it.
The Mechanism Is Consistent Across All Teams
Flat licences kept token spend invisible because the price did not move with usage. The moment a tool is billed by consumption, every prompt, every long agent session and every large context window shows up on an itemised invoice, and the total becomes surprisingly material.
The companies that scaled agentic coding without a Q2 surprise will be the ones that treated this spend as a metered utility rather than a software subscription — and built controls accordingly.
Microsoft's Exit: Own the Stack
Microsoft's chosen exit is GitHub Copilot CLI, a tool it owns outright. Owning the vendor lets Microsoft negotiate internal economics, retire duplicate tools and standardise controls in ways an external supplier would never allow. There is a real saving available there, and it has little to do with Copilot's raw capability.
The Fix: Treat It Like a Utility
The fix is not slower adoption. Engineers who lean this heavily on AI are not giving it up, and a CFO who tries to claw it back is fighting productivity.
A mature control model includes:
- Team-level soft alerts: Catch budget drift before it becomes an overrun, without hard cutoffs that interrupt critical work
- Anomaly detection: Flag when a single session consumes unusually high tokens
- ROI metrics alongside cost: Cost per merged change, cost per accepted suggestion, cost per resolved ticket
- Contract renegotiation: Volume commitments in exchange for predictable pricing caps
The Cultural Lesson for Engineering Leaders
Blunt per-engineer ceilings are a starting point but a poor finish. The companies that scale agentic coding without a Q2 surprise will be the ones that understood adoption velocity and cost exposure are now a single number — and stopped treating one without monitoring the other.
A engineering culture optimised purely for AI usage is also optimising for an unbounded bill. The board needs to know that.