This is Part 2 of the Budget Math column. Read Part 1: The Budget Math Behind Anthropic's Enterprise Push.
What Happened
On June 1, 2026, GitHub did something that looks like a billing footnote and reads like a warning. It retired the way it had always charged for Copilot. The old model billed in premium request units, a flat allotment that came bundled with your seat. The new model bills in GitHub AI Credits, a balance you draw down every time a model does work for you, priced against the actual tokens it reads and writes. GitHub's own language was blunt: the premium request model was "no longer sustainable."
Most coverage filed this under developer tools. That is the wrong drawer.
What It Actually Is
Here is the shift in one sentence. Your AI subscription is becoming a utility bill.
A CIO can budget 500 seats. It is much harder to budget for whatever an organization decides to consume. That is the shift hiding underneath the pricing change. The software budget that used to be fixed is slowly becoming a forecast.
A seat used to be a fixed cost. You paid your $19 per user per month, you budgeted it once, and a heavy user cost exactly what a light user did. Credits break that. Each seat now arrives with an included balance, and everything past it meters like electricity. The line item that used to sit still in your software budget now moves with how hard your team actually uses the thing.
GitHub is not hiding this. The release ships admin budget controls at three levels, enterprise, cost center, and user, and an enterprise has to explicitly switch on paid usage above the included balance before anyone gets charged a cent extra. Those are not the controls of a subscription. They are the controls of a meter. Companies do not build cost centers and per-user spending caps for a product that bills the same every month.
GitHub even softened the landing. Business and Enterprise plans receive additional included credits through August. That is the standard move that makes a meter feel generous before it starts behaving like a meter.
Get 10 AI workflows + the weekly briefing. Free.
Subscribe FreeWhy It Is Spreading
The reason this matters beyond GitHub is that the economics underneath are not specific to GitHub. Per-seat pricing assumes the cost to serve a user is roughly flat. Inference is not flat. A user running long agent tasks against a frontier model can cost a vendor many times what a casual user costs, and the flat seat quietly subsidizes the gap. Every AI vendor still selling a flat seat is sitting on the same problem GitHub just stopped pretending it did not have.
So watch the pattern, not the press release. When a vendor bolts "credits," "tokens," "AI units," or "budget controls" onto a product you already pay a seat price for, the per-seat era for that product is ending. It will not announce itself as a price increase. It will announce itself as flexibility.
The Tailwind
GitHub is not alone. Major AI vendors are increasingly building products around agents, automation, and long-running tasks that consume far more compute than traditional software. The direction matters more than any single pricing announcement. As usage grows, the pressure to align pricing with consumption grows with it.
The budgeting consequence arrives before the procurement consequence. Procurement teams negotiate contracts once or twice a year. Finance teams forecast spending every month. A tool that shifts from fixed cost to variable cost changes how budgets are built and defended long before it changes how contracts are signed.
What to Do in the Next 30 Days
You do not need a finance background for this. You need one spreadsheet.
List every AI tool your team pays for. Next to each, write two things: whether it still bills as a flat seat, and whether the vendor has shipped anything that sounds like credits, tokens, or usage tiers in the last six months. The tools in the second column are the ones to model now. Treat them the way you treat cloud: do not sign the renewal until you have a simple model for how the bill behaves when usage spikes. Pull last month's real usage, not your headcount, and ask what the bill looks like if that usage doubles. If the honest answer is "ask the vendor," you are not ready for that renewal. Whoever walks in owning that model sets the terms. The era of paying once and forgetting is closing; the era of budgeting for whatever your company actually consumes has already started.