Per-seat pricing worked because seats and value moved together. More people using the software meant more work getting done, so charging per person was a rough but honest proxy.
AI agents break the proxy. An agent does the work and never logs in.
The arithmetic that panicked the industry
Take a support team of fifty on a CRM at $150 a seat. Deploy agents that handle most of the ticket volume, keep fifteen people for escalations, and the work still gets done. The vendor’s revenue from that account falls by seventy percent while the customer’s outcome is unchanged or better.
Nobody churned. Nobody complained about price. The unit the contract was denominated in simply stopped correlating with the value delivered.
That is the whole story, and it explains behaviour across the industry in 2026 that otherwise looks like ordinary greed.
What vendors are doing instead
Four responses, and most large vendors are running more than one.
Metering the agent. The seat survives, wrapped in a consumption meter for delegated work. Salesforce, Microsoft, ServiceNow, Workday, Zendesk, HubSpot and Atlassian have all added a version of this. Reporting puts Salesforce’s agent revenue at around $800 million in a single recent quarter, and Microsoft has added a separate per-user charge for agent governance in the region of $15.
Licensing the agent as a user. Agents get identities, authenticate, and appear in the billing system much as employees do. Conceptually tidy, and it makes the seat count go back up.
Outcome pricing. Charging per resolved ticket, reviewed contract or qualified lead. Goldman Sachs has taken to calling this Results-as-a-Service. Attractive in a demo, hard to write, since it requires both sides to agree what counts as a result and who adjudicates when they disagree.
The flat agentic bundle. Salesforce’s Agentic Enterprise License Agreement replaces per-seat and consumption billing with a flat unlimited-use fee across a multi-year term. Predictability in exchange for commitment and lock-in, which is a genuine trade rather than a trick.
How fast this is moving
Seat-based arrangements are reported to have fallen from roughly 21% to 15% of enterprise software contracts in about a year. IDC expects 70% of vendors off pure per-seat models by 2028. Hybrid structures, a base fee plus a variable component, are said to be running around 43% of SaaS companies and heading toward 61%.
Numbers like these come from analyst and vendor research with an interest in the narrative, so hold them loosely. The trend is corroborated by the thing that is hardest to spin, which is what vendors actually shipped: nearly every major platform changed how it charges within the same eighteen months.
What it means if you are buying
The comfortable assumption to abandon is that headcount reductions produce software savings. Under the new models they may not, and under a flat agentic bundle they explicitly do not.
Practical consequences:
- Your renewal maths changes. Cutting seats used to be the reliable lever. If the value has moved into a meter, cutting seats saves less than you expect and may trigger an audit. See what triggers a software audit.
- Two vendors are no longer comparable. One prices per seat, one per outcome, one per credit. Comparing them requires modelling your own workload, not reading a pricing page.
- Agents multiply, employees do not. Headcount is bounded by hiring. Agent count is bounded by whoever can deploy one, which is a much looser constraint and a much faster-moving cost.
- Term length is the real negotiation. Flat bundles buy predictability with lock-in, at exactly the moment the market is repricing. Two years is a long time to be certain about this.
The one thing to do now
Find out, for your largest contracts, whether the metric has already changed. Not the price. The metric.
A per-seat agreement that quietly became per-seat-plus-consumption is a different contract from the one you signed, and it usually arrives as a product announcement rather than as a commercial notice. Most organisations discover it on an invoice.
Tracking those changes is what CopperFeed is built for. The credit mechanics are in AI Credits Explained, and forecasting against them in How to Budget for Usage-Based Pricing.
Figures here come from published analyst and press reporting rather than vendor disclosure, and are indicative. General guidance, not procurement advice.