Outcome Based Pricing: The Buyer's View
Outcome based pricing charges for a result rather than a seat, and from the buyer's view the whole negotiation lives in one place: the definition of the outcome. Agree what counts before you sign, or you inherit a meter the vendor controls.
Key takeaways
- Outcome based pricing charges per result, not per seat or per unit of consumption.
- Zendesk pioneered the model with pricing per automated resolution, charging when the software resolves a case.
- The definition of the outcome, for example what counts as resolved, must be agreed contractually before signing.
- Analysts project a large share of enterprise SaaS spend moving to usage, agent, or outcome models by 2030, by published market estimates.
- Counter by defining the outcome tightly, capping volume, and securing audit rights over the vendor's measurement.
What is outcome based pricing?
Outcome based pricing charges for a result the software produces rather than for a seat someone occupies or a unit of compute consumed. Zendesk pioneered the model in customer service with pricing per automated resolution, where the buyer pays each time the system resolves a case without a human agent rather than paying per agent seat. The appeal to the buyer is real: you pay when value is delivered, and an unused outcome costs nothing. The risk is equally real, because the vendor both defines and measures the outcome, so the meter that drives your bill sits inside the vendor's product. That is why outcome pricing is the most buyer favorable model in theory and the most dependent on contract language in practice.
This is the leading edge of the 2026 meter shift, where pricing moves from seats toward usage, agent, and outcome models. Analysts project that a large share of enterprise SaaS spend will run on usage, agent, or outcome meters by 2030, by published market estimates, so understanding the outcome model now is preparation for the contracts you will sign across the portfolio.
Why is the definition of the outcome everything?
The single most important term in an outcome based contract is the definition of the outcome, because it is the meter. For a per resolution model, what counts as resolved decides the bill. Does a case count as resolved if the customer returns with the same issue an hour later? Does a deflection to a help article count? What about a conversation the system handed back to a human after partial work? Each of these is a billing event or not depending on the definition, and a loose definition lets the count drift upward in ways you cannot easily audit. The buyer who agrees the definition tightly before signing controls the meter; the buyer who accepts the vendor's default inherits it. This is the contractual point the model's own pioneer makes plainly: the definition of resolved must be agreed before signing.
The same discipline applies to agent meters, which sit beside outcome pricing in the new pricing landscape. We cover the broader shift in agent meters, the new line on your invoice, and the gap between sticker and reality in list price versus what buyers actually pay.
How do the pricing models compare?
Seeing the three meters side by side clarifies where the buyer's leverage sits in each. The leverage moves with the meter: on seats you control headcount, on usage you control consumption, and on outcomes you control the definition.
| Pricing model | What you pay for | Where the buyer's leverage sits |
|---|---|---|
| Per seat | Each licensed user. | Right size the user count and the edition. |
| Usage based | Consumption, such as credits or calls. | Optimize consumption and size the commitment. |
| Outcome based | A defined result, such as a resolution. | Define the outcome tightly and audit the count. |
How should a buyer respond to an outcome based offer?
Respond with four moves. First, define the outcome tightly in the contract, with explicit inclusions, exclusions, and the handling of repeat or partial cases, so the meter cannot drift. Second, secure audit rights over the vendor's measurement, including access to the underlying logs, so you can verify the count rather than trust it. Third, cap volume or set a price schedule that protects you if outcomes spike, so a busy period does not become an uncapped bill. Fourth, model the total against your current seat cost before switching, because an outcome model is only a saving if your real outcome volume is lower than the seat equivalent. Treat the definition as the headline term and everything else as secondary.
Context sets expectations on what negotiation achieves. Across SaaS, negotiation cuts opening asks by roughly 55 percent on average, by published market estimates, and disciplined work typically lands 10 to 30 percent savings. On an outcome deal the saving is less about the unit price and more about the definition and the cap, because those decide how many units you are billed for in the first place.
What to do next
Before you sign an outcome based deal, define the outcome in writing, secure audit rights, cap the volume, and model the total against your seat baseline. Our full method for usage, agent, and outcome meters, including the definition language and the audit clause, is set out in the SaaS Benchmarks Guide. On an outcome meter, whoever defines the outcome controls the bill. Make sure that is you.
Get the full method
The SaaS Benchmarks Guide collects the model comparisons, the outcome definition language, and the audit clause for usage and outcome meters in one place. Free to download.
Download guide →Last reviewed January 2026