Outcome-based pricing charges the customer for a defined business result rather than for access, seats, or units consumed. A support platform billed per resolved ticket rather than per agent licence is outcome-based. So is a collections tool billed as a share of recovered debt, or a recruitment system billed per accepted offer.
The model is not new — agencies, law firms and BPO vendors have used variants for decades. What is new is the pressure pushing enterprise software toward it.
Why the seat stopped working
Per-seat pricing rests on a single assumption: that the number of humans with access approximates the value being extracted. That assumption held for thirty years of enterprise software, and it is now visibly eroding.
The market data shows the strain. Median growth among public software companies has slowed since the pandemic-era surge, and net revenue retention — expansion within the existing customer base — has fallen from roughly 116–117% in 2021 to around 108% in 2025. That is a maturing market rather than a collapsing one, but it removes the mechanism that made per-seat pricing self-expanding: you grew because your customers hired.
Agentic deployment removes the assumption entirely. If a workflow is executed by a system rather than a person, there is no seat to sell. Worse, a successful deployment reduces the seat count you were billing for, so your pricing model now penalises you for working.
This is the structural reason pricing is drifting toward consumption tied to workflows, tasks, or measurable outcomes.
The three models it sits between
Per-seat. Bills access. Predictable, easy to forecast, easy to procure. Decouples from value the moment the work stops being done by people.
Consumption. Bills units — API calls, tokens, runs, records processed. Reconnects price to usage, but transfers volatility to the customer and makes budgeting hostile. Procurement teams dislike it for good reason.
Outcome. Bills results. Aligns incentives most tightly. Also the hardest of the three to contract, measure, and audit.
Most vendors moving away from seats are landing on a hybrid: a platform fee for access, plus a consumption or outcome component on top. Pure outcome pricing remains rare.
Where outcome-based pricing breaks down
Four failure modes, in roughly the order they appear:
Attribution. If revenue rises 12%, how much of it belongs to the vendor? Every outcome-based contract is an argument about attribution wearing a pricing table. Without an agreed counterfactual — a control group, a baseline period, a holdout — the negotiation has no floor.
Definition drift. “Resolved ticket” sounds unambiguous until the vendor’s system closes tickets the customer considers unresolved. The definition of the outcome becomes the commercial battleground, and it usually favours whoever controls the measurement.
Customer dependency. The vendor’s revenue now depends on customer behaviour it cannot control. If the client’s own process is broken, the outcome does not land and the vendor is unpaid for work correctly performed.
Forecasting. Outcome revenue is lumpy, delayed, and hard to recognise cleanly. Public companies and venture-backed vendors both have strong reasons to prefer boring subscription revenue, whatever their pricing page says.
What to check before you sign one
If you are the buyer:
- Who owns the measurement system, and can you audit it?
- What is the agreed baseline, and how was it established?
- What happens when the outcome is achieved partly by your own changes?
- Is there a cap? Uncapped outcome pricing on a successful deployment can exceed a decade of licence fees.
If you are the vendor:
- Can you measure the outcome without the customer’s cooperation? If not, you have a collections problem, not a pricing model.
- What is your exposure if the customer’s adjacent process fails?
- Does your cost base flex with the outcome, or have you just added variance to revenue while holding cost fixed?
Related terms
Consumption pricing — bills units of usage rather than results. A halfway house, and where most agentic vendors are actually landing.
Value-based pricing — sets price by perceived customer value, but still bills as a subscription. Often confused with outcome-based pricing; the difference is whether the invoice varies with the result.
Net revenue retention (NRR) — expansion revenue within the existing base. The metric most directly disrupted when seats stop growing.
The vendors moving first are not the confident ones. They are the ones who can measure.