Journal / Technology

Technology

The End of the Seat: What Usage Pricing Does to Your Bill

Software pricing is moving from per-seat to per-use and per-outcome. Almost every article about it is written for the people setting prices. This one is for the people paying them.

11 min readResolution

For two decades, buying software was easy to forecast: a price per person, per month. You knew the year's cost before you signed.

That is being dismantled, and not out of pricing ideology. It is a direct consequence of AI agents. When the work is done by software rather than by people, charging per person stops making sense for the seller — because the customer can shrink the team and consume just as much.

OpenView tracked adoption of usage-based pricing among software companies: 34% in 2020, 45% in 2021, 61% in 2022.1 And Gartner, in a release dated 1 July 2026, put a number on what is in play: $234 billion of enterprise application software spend at risk from agentic AI, describing the shift as an existential threat to vendors defending seat-based models.2

per seat flat, predictable per use scales with consumption per outcome scales with success the risk moves from the vendor to you
fig. 01 — three models, and where the risk sits in each

What "per outcome" means in practice

The clearest verifiable example is Fin, Intercom's support agent: $0.99 per resolution, charged at most once per conversation, with a fifty-resolution monthly minimum.

The promise is appealing — you pay when it works. The small print less so: a "qualification" is billed separately at $9.99; inside Intercom you still need at least one paid seat; and the definition of what counts as a resolution belongs to the vendor.

In June 2026 Salesforce announced it was acquiring the company for roughly $3.6 billion. In the same month it launched its own support agent charging per resolution at about $2 — double the price of the product it was buying. That says something about the maturity of this market: nobody yet knows what an outcome is worth.

The counter-trend almost nobody reports

Here is the information that changes how to read this subject, and which is missing from nearly all coverage of it.

In December 2025, The Register reported the opposite movement: Salesforce, after experimenting with consumption and per-conversation pricing, moved back toward treating seat-based licensing — with adjustments — as the norm for AI agents. The stated reason was simple: customers wanted predictability.3

So "the death of the seat" is a contested thesis, including among those who announced it loudest. Anyone writing about it as settled fact is selling something.

Meanwhile, the price goes up

Whatever the model, aggregate cost has risen. Vertice, which measures software inflation across a base of 16,000 vendors — and sells spend optimisation, which should be said — recorded 8.7% in 2023 and 11.4% in January 2025, against 2.7% average G7 inflation over the same period.4

Software spend per employee moved from about $7,900 in 2023 to $9,100 at the end of 2025. And there is the phenomenon Vertice calls shrinkflation: 28% of renewals in the final quarter of 2025 delivered less for the same price.

The figure that matters most for you: companies of 100 to 500 employees spend around $6,700 per employee on software, against $4,700 at large enterprises. Less volume, worse per-head price.

pays less pays more idle seats you were paying forseasonal or light usesmall teams, large licence count heavy, growing usagetools that work wellanyone who needs a fixed budget the better it works, the more it costs
fig. 02 — who pays less and who pays more when the model changes

Who wins and who loses

Wins: anyone carrying idle seats, anyone with light or seasonal use. Here usage pricing corrects a genuine unfairness in the old model.

Loses: heavy users. This is the counter-intuitive point — under outcome pricing, the better the tool works, the more you pay. A support team that resolves well pays more than one that resolves badly.

And everyone loses predictability. Recurring revenue becomes an estimate, the annual budget becomes a range, and the month-end bill becomes a surprise.

Six clauses worth having

  1. A written definition of the billed unit. Exactly what counts as a resolution, a conversation, an execution. Without it, the metric is defined by whoever is charging.
  2. A consumption cap. A ceiling above which nothing is billed without your approval.
  3. A commit-to-consume discount. If you can forecast usage, that forecast is worth money.
  4. A grandfathering clause. Locks your current terms for a period even if the vendor changes policy — especially relevant after an acquisition.
  5. A notice window for price changes. Without it, you find out in the invoice.
  6. A re-evaluation clause in any multi-year deal. This market is moving too fast to sign three years without an exit.

The general rule

Usage pricing is not a synonym for cheaper. It is a transfer of risk: away from the vendor, who previously had predictable revenue, and onto you.

Whether that is good or bad depends entirely on your consumption pattern. The calculation that decides it is simple and almost nobody does it: take the last twelve months of actual usage and re-price it under the new model. If you cannot run that calculation because you do not measure usage, that is the problem to solve before negotiating any price.

Further reading

Books that shaped this article, including the ones we disagree with. Where a work is popular rather than peer-reviewed, we say so.

Madhavan Ramanujam & Georg Tacke — 2016
Written for people setting prices, which is exactly why it is useful to a buyer: it shows you the reasoning on the other side of the table.
Clayton Christensen — 1997
Why the cheaper, less capable option keeps winning — and why vendors restructure pricing rather than lose to it.

Resolution is a participant in the Amazon Services LLC Associates Program. As an Amazon Associate we earn from qualifying purchases — at no additional cost to you. Affiliate links never determine what appears on these lists: several of these books are here specifically because we think they are wrong in an instructive way.

References & notes

  1. OpenView, State of Usage-Based Pricing, first and second editions. Definitions are elastic; the figure counts anything tied to product consumption.
  2. Gartner press releases, 26 August 2025 and 1 July 2026. These are analyst forecasts, not outcomes.
  3. The Register, 12 December 2025, on the return to seat-based licensing for AI agents.
  4. Vertice, SaaS Inflation Index — base of 16,000 vendors; vendor with a commercial interest in the subject.
  5. Published pricing pages for the products named, consulted August 2026. Pricing changes frequently; check the current pages.

Corrections are published inline and dated. Write to us if something here is wrong.

// weekly dispatch

One email. Every Tuesday.

The week's analysis, one tool we actually tested, and one behavioural pattern worth practising. Unsubscribe in one click.

// no spam · no resale · ~4 emails a month