Somewhere on your laptop is a spreadsheet with names in it. Two hundred rows, a column of checkboxes, and a running total at the bottom that you keep looking at. You’re deciding who gets an AI seat. Marketing wants twelve. The regional VP wants one for every director because it looks bad if he doesn’t ask. Finance wants the total to stop moving.
You’ll spend two weeks on that spreadsheet. It’s the wrong two weeks, because the number in the bottom right stopped being the bill.
The seat question had a real answer in 2024, when a seat cost two hundred dollars a month and rationing was the whole job. That answer went obsolete this spring, and most of the advice you’ll find still assumes the old math.
The thing you’re rationing costs twenty dollars now
Here’s what changed. Flat per-seat enterprise pricing is gone across the serious vendors. The replacement is a low seat fee plus consumption billed at usage rates, against a commit you negotiate up front.1 Anthropic’s is twenty dollars plus what you use. OpenAI’s Workspace Agents is credit-based on the same logic. Google is consumption-priced. Microsoft was the last flat-seat holdout and gave it up in June.
Run that through the spreadsheet. Under the old model, a seat you handed to someone who never opened it cost you two hundred dollars a month, twenty-four hundred a year, times however many rows you were too polite to uncheck. Rationing was correct. Every checkbox was a real, recurring, wasted expense, and the discipline of saying no to the regional VP paid for itself.
Under the meter, that same idle seat costs twenty dollars and consumes nothing. The person who opens it twice and drifts away costs you twenty dollars and a rounding error. The person who turns out to be your next power user, the one you would never have predicted from an org chart, costs you twenty dollars plus a consumption line that scales with the work they’re producing.
The cost of a wrong “yes” fell by an order of magnitude. The cost of a wrong “no” didn’t move at all.
That asymmetry is the whole answer, and it inverts the advice you’ve been given. When being wrong in one direction costs twenty dollars and being wrong in the other costs you a power user you never found, the guessing isn’t worth the two weeks. You hand out the cheap thing broadly and you manage the expensive thing closely.
Eighty dollars per employee is the number that holds up
For a knowledge-work organization, total AI spend should land between forty and a hundred and twenty dollars per employee per month, with the average closer to eighty. Below forty, you’re underfunding the people producing leverage. Above a hundred and twenty, you’re usually paying flat rates for seats nobody opens. Evaluating Spend has the full allocation model.
Notice that the benchmark is per employee, not per seat. That’s deliberate now. Divide your AI spend by your headcount and you get a number you can defend. Divide it by your seat count and you get a number that means nothing, because seats no longer have a stable relationship to cost.
So the seat rule is boring. On metered plans, give a seat to anyone who might plausibly open it, which in most knowledge-work orgs is most of the company. Don’t run an approval process for a twenty-dollar line item. You don’t hold a committee meeting about who gets a phone.
Then give the fifteen percent who use it hard everything they ask for: the better plan, API access, the consumption budget. The top decile of any role should usually have both a seat and API access, and the cost of that is small compared to what happens when you force a builder through a chat window. Recognizing Leverage is how you find those people, and the honest news is that you can’t find them from the spreadsheet. They identify themselves once they have access, which is the argument for handing it out.
The flat-priced seats are where the audit still belongs
The old math holds completely in one place, and it’s probably your biggest line item.
Workspace AI is still sold the old way. A Copilot seat bundled into your E5 at thirty dollars, flat, whether the seat is opened or not. That’s a real recurring cost with no consumption signal attached, so an idle one is pure waste in the way an idle metered seat no longer is. If you have a hundred and fifty of them and a third are dead, you’re burning about eighteen thousand dollars a year on nothing, and the rep will tell you it’s already paid for.
This is where the quarterly audit still earns its keep, and it’s why killing the bottom thirty percent of seats is still the right advice. That advice is scoped to the flat-priced workspace SKUs. On a Copilot seat, a dead row costs you thirty dollars a month forever, so cutting it is free money. On a metered seat, the same cut saves twenty dollars and forecloses the chance that the person turns into a power user in Q4. Same audit, applied where the flat price makes the waste real. The five-minute version in Evaluating Spend is the whole procedure; run it against your Copilot roster and leave the metered plans alone.
Consumption is what you manage now
The seat count was only ever a proxy for consumption, and it was a decent one back when you had no way to see consumption directly. Now you can look at the thing itself.
Your bill is a usage report, so read it like one. Set per-team and per-user spend limits. Watch consumption by workspace rather than by headcount. Put one person on the dashboard monthly who can answer “why did this double” before your CFO asks it, and understand that the answer is often good: the Q3 briefing is blunt about the fact that a successful rollout produces a bigger invoice by design. The instinct to throttle the thing that’s working is the expensive mistake here, and most of the real savings live in plumbing your engineers already know about anyway.
The consumption that goes wrong is usually mechanical. An uncached script running ten thousand times against a workflow nobody profiled, burning tokens at the rate of a whole department. A heavy seat attached to a named person and a named output is leverage. A heavy seat attached to a job no one owns is an invoice. Both show up as consumption, and only the dashboard tells you which is which.
When the CFO asks how many seats you bought, you’ll have the number, and it won’t be what carries the meeting. The paragraph that works is the one in Defensible AI Spend: spend is up because the tools are metered and our use is up, it’s concentrated on people whose workflows we can name, and we audit it quarterly. That paragraph gets through a budget review without a seat count in it, because the seat count wasn’t answering the CFO’s question in the first place.
Something to carry
Go back to the spreadsheet. Find every row you unchecked on a metered plan and check it. That’s the whole decision, and it costs twenty dollars a head to be wrong about.
Then take the two weeks you were going to spend defending those checkboxes and spend them on the harder question, which is who in your organization is already producing something with the access they have. Those people are why the line item exists, and they’re the reason adoption stalls in the broad middle when you ration access to them. The org chart won’t tell you who they are. The usage report will.
Footnotes
-
Across the major enterprise vendors, flat per-seat AI pricing has been replaced by a low seat fee plus consumption billed at usage rates, committed against an annual spend or token volume negotiated up front (typically a 50-seat minimum). Usage billing generally cannot be disabled. Terms current as of mid-2026 and change frequently. ↩