Your largest software vendors are changing the thing they sell you. Quietly, at renewal, one SKU at a time. The seat license that anchored every enterprise software deal for twenty years is being replaced by a charge per result: per resolved ticket, per booked meeting, per completed workflow.
This is not a pricing tweak. It is a repricing of risk. And the function you have pointed at it, procurement, was engineered for a world that is disappearing.
The unit of value moved and nobody told procurement
Per-seat pricing worked because one seat meant one human doing one unit of work. It breaks the moment the point is autonomy: an agent that processes 10,000 cases a month is not a seat, and seat counts do not move when the work does. The math is not subtle. Per-seat pricing is structurally broken for AI agents: the better the agent works, the fewer seats a buyer needs, so the vendor is paid to under-deliver.
So vendors are moving. Three main alternatives to the classic seat-based model have emerged: usage-based pricing, outcome-based pricing, and some hybrid of all of the above. The market is validating it: Sierra, the AI customer service company founded by former Salesforce CEO Bret Taylor, hit $100 million in annual recurring revenue in less than two years using an outcome-based pricing approach. Salesforce priced Agentforce resolutions at two dollars a conversation. This is the arrival of what analysts now call service-as-software: in the old model, software was a tool and humans did the work using the software. In service-as-software, AI agents perform the work. The software and the service merge into one product.
Here is the operator problem. Your procurement team knows how to count users, benchmark a per-user rate, and grind out a discount on a three-year term. Ask that same team to evaluate a per-outcome contract and the tooling collapses. There is no seat count to true up. There is a definition to litigate, and the vendor wrote it first.
The mismatch is where the money leaks
The value leak is not the headline rate. It is the process. The immediate risk is not merely a higher invoice. It is a renewal process that evaluates each contract separately while the work moves across contracts. Consider a single support workflow: a human support representative may hold a help-desk seat, a CRM seat, a knowledge-management seat, a collaboration seat, and a premium AI copilot entitlement. When an agent absorbs that workflow, you are now negotiating five contracts against a piece of work none of them can see. Procurement scores the SKU. The value lives in the workflow.
It compounds. Zylo’s 2026 SaaS Management Index reported that organizations leave an average of 36 percent of SaaS licenses unused when measured against recommended utilization levels. You are layering variable outcome charges on top of a seat estate you already overbought.
And the single most expensive word in the entire category is “resolution.” Outcome-based pricing charges per verified business result, per resolved support ticket, per closed deal, per completed workflow. Costs tie to value delivered, not activity. The catch: you need a contractual Outcome Measurement Agreement defining what counts as a valid outcome before you sign. A deflected chat is not a resolved issue. An output is not an outcome. HubSpot learned this from the buy side: the company saw clients initially getting outputs from its tools, but that these outputs would not always translate into outcomes.
What survives a business case, and what to fund
Do not romanticize this. Pure outcome pricing is not where the market is landing, and neither should you. The dominant transition state is hybrid: fixed base plus variable consumption is the dominant transition state, and most enterprise renewals in 2025 to 2026 will land here. That is the right posture for a board. Predictable floor, variable upside, and a hard consumption ceiling while adoption is early.
Three institutional moves. First, retire per-contract scoring. Score the workflow and its cost per completed decision, not the license. Second, never sign an outcome term you cannot meter yourself. If the vendor owns the meter, the vendor owns the invoice. Third, make the Outcome Measurement Agreement a gating document, not an appendix: what counts, who verifies, what happens in dispute.
The window is closing. The transition window for these conversations is 2025 to 2026. After that, the vendors will have set the terms, and you will be inheriting them rather than shaping them. The structural direction is not in doubt: Gartner predicts at least 40 percent of enterprise SaaS spend will shift to usage, agent, or outcome-based models by 2030, with seat-based revenue share declining from 21 percent to 15 percent.
The Cost of Doing Nothing here is not one bad renewal. It is a decade of structurally overpaying because you scored seats while the vendor sold outcomes, and letting the meter, the definition, and the margin all sit on the other side of the table. Fix the buying model before the next renewal, or inherit the one your vendor already wrote.