Your next software renewal will likely carry two prices, not one. One line still counts the people who log in. The new line counts everything the agents they turned loose did while nobody was watching a screen. Salesforce already reports it publicly: Agentforce revenue up 205% year over year, with the seat line holding right beside it. This is a stacking model, not a swap. It changes three things at once: what you sell, what you buy, and how fast a software bill you thought was fixed can run away from you.
The bill already has two lines
For a year, the loud prediction has been that AI agents kill seat-based software. No humans logging in, no seats to sell, no business. It is a clean story. It is also already contradicted by the public numbers.
Salesforce put the split on record in its Q1 FY27 earnings. Agentforce reached $1.2B in annual recurring revenue, up 205% year over year. Combined with Data 360, the number is nearly $3.4B. The seat line did not vanish to make room. Agentforce for Sales still lists at $125 per user per month, sitting right next to consumption-priced credits for the agents those users switch on.
So the meter did not get replaced. It got a second dial. One counts people. The other counts machine work. The vendors reading this correctly are already outgrowing the ones still arguing about whether the seat dies.
The seat was never a headcount meter
The doom thesis treats a seat as a proxy for headcount, which is why it assumes the seat dies when headcount stalls. That is the wrong reading of what a seat actually does.
A seat is an identity and entitlement record. It says which data, which systems, and which actions belong to one named, accountable person. Strip a software product down to what the seat truly measures, and it is not "a human who clicks." It is "an authority that can be held responsible." Aaron Levie, Box's CEO, put the resulting shape plainly on the Platformer podcast in May: "You probably are going to have a stacking business model in software: humans still have seats, but agents will be a consumption pattern on top of that."
An agent cannot act with any authority it did not inherit. It needs a named human's identity to know what it is allowed to touch. No seat, no anchor for permission. That is why the seat is structurally different from a login count, and why it survives the arrival of agents that never log in at all. It is a governance record wearing a pricing costume.
That also explains why one meter cannot price both things. A human has a physical ceiling on how many actions they take in a day. An agent has none, and it runs at night. Bessemer has already started naming the new cost primitives that this creates: cost per thousand tokens, cost per resolved request, cost per agent minute. Not one of them maps onto "per seat." Seats meter identity. Consumption meters throughput. Trying to bill both on a single dial causes it to break in one direction or the other.
This is already the market, not a forecast
None of this rests on one CEO reading his own business favorably. The shift shows up across the category.
Roughly 40% of software companies now run hybrid pricing, a base fee plus a variable usage layer, and that is projected to exceed 60% by the end of 2026. Well over half now offer some form of usage-based billing, up from 27% in 2018. Credit-based pricing, the most agent-native flavor, jumped from 35 companies in the PricingSaaS 500 Index at the end of 2024 to 79 a year later.
The performance gap is the part worth pinning to the wall. In Chargebee's 2025 monetization survey, companies evolving their pricing alongside their AI were nearly twice as likely to expect high growth as those that left pricing untouched. Correlation, not proof. Yet the signal is hard to ignore: the vendors treating pricing as a live system are the ones expecting to pull ahead.
Which puts the same shift in front of two very different desks, and the answer looks different depending on which side of the software you sit.
If you build and sell software
The instinct will be to bolt a usage SKU onto the price sheet because everyone else is. Resist the reflex. The discipline is to deliberately decide which part of your product is identity and which part is throughput, and to price each for what it actually is.
Seat-price the parts that confer authority: access, governance, entitlements, and the record of who is allowed to do what. Consumption-price the parts that run unbounded: agent actions, resolved requests, and tokens burned against your platform on a customer's behalf. Get that line in the wrong place, and you either cap your own upside as usage explodes, or you hand customers a bill so volatile it makes them churn on principle. The second dial is only defensible when it meters something genuinely unbounded that customers agree is worth metering.
There is a quieter defensibility point underneath the pricing one. Levie noted that Box has not approved a single internal project to rebuild an existing software service from scratch with AI, because the workflow is the cheap part to clone. The governed identity, data, and permission layer beneath it is not. That layer is exactly what the seat prices are, and it is why "just have the agent rebuild it" is a worse idea than it sounds.
If you buy and run software
Here is where the meter change stops being interesting and starts touching your bottom line, fast.
Stop evaluating vendors on per-seat cost alone. That number is now the fixed, legible, well-behaved half of the bill. The other half is a variable line that can balloon in a quarter if a team wires an agent into a workflow and lets it run. A software cost you booked as fixed can behave like a cloud bill, and cloud bills are where finance teams have been ambushed for a decade.
Treat agent consumption the way a disciplined engineering org already treats cloud spend, before the first invoice surprises you, not after:
Put a real ceiling on it. Budget caps and rate limits per agent, per team, per workflow, so an unbounded meter cannot silently become an unbounded invoice.
Make the spend attributable. Issue a distinct API key per application, team, or use case, so every token charged by OpenAI, Anthropic, or your platform vendor is attributed to a named owner rather than a single anonymous pool. You cannot govern a number you cannot trace.
Instrument it. Dashboards, spend alerts, and anomaly triggers on the consumption line, reviewed at a significantly accelerated cadence than any other operating cost, not at renewal.
Assign the accountability. Showback or chargeback: the team turning the agent loose is the one that sees the bill.
And treat the seat itself as a governance control, not a checkbox for IT. Every agent identity should map to a named, accountable human with explicit entitlements. "Who authorized this agent to act as me, and against which data?" is now a real operating question with a real cost attached to getting it wrong.
The close
The doom thesis asked whether the seat survives. It was the wrong question. The seat was never the cost center. It is the accountability record for everything now running on top of it. The number that can hurt you is the one on the other line, and the discipline is deciding, on both sides of the software, what you are willing to let run through it.
Images source: ChatGPT Images / Claude Opus / Gérard Métrailler
Sources
Casey Newton, "The best argument I've heard for why AI won't take your job", Platformer, published 2026-05-13. https://www.platformer.news/ai-job-loss-box-ceo-aaron-levie/. Accessed 2026-07-14.
Salesforce, "Salesforce Delivers Record First Quarter Fiscal 2027 Results," press release, 2026-05-27. https://www.salesforce.com/news/press-releases/2026/05/27/fy27-q1-earnings/. Accessed 2026-07-14.
Salesforce, Agentforce pricing. https://www.salesforce.com/agentforce/pricing/. Accessed 2026-07-14.
Rob Litterst, "What actually works in SaaS pricing right now," Growth Unhinged, 2026-01-07. https://www.growthunhinged.com/p/2025-state-of-saas-pricing-changes. Accessed 2026-07-14.
Bessemer Venture Partners, "The AI pricing and monetization playbook". https://www.bvp.com/atlas/the-ai-pricing-and-monetization-playbook. Accessed 2026-07-14.
OpenView Partners, "The State of Usage-Based Pricing". https://openviewpartners.com/blog/state-of-usage-based-pricing/. Accessed 2026-07-14.
Chargebee, "2025 State of Recurring Revenue & Monetization Report". https://www.chargebee.com/resources/guides/2025-state-of-subscriptions-revenue-growth/. Accessed 2026-07-14.
