Define the Outcome Before You Price on Outcomes

Outcome pricing is the most appealing idea in software pricing right now. Charge for the result rather than the tool, and your price rises with the value you deliver instead of with the number of people who log in.

The appeal is real. The difficulty is that an outcome is a definition, and definitions are contractual. Before you can bill for a result you need both sides to agree on what counts as one, who decides, and what happens when the answer is disputed.

Two public moves in 2026 show companies working through exactly this.

Charging only for the ones that worked

On 14 April 2026, HubSpot moved its Breeze Customer Agent from $1.00 per conversation to $0.50 per resolved conversation, as documented in the 2026 SaaS pricing guide from SaaSRise.

Both halves of that change matter. The price per unit halved, and the unit changed from something the software does to something the software achieves. A conversation happens whether or not it helps. A resolution, by definition, helped.

Under the old structure the customer paid for every attempt. Under the new one the vendor absorbs the cost of the failures. That is a real transfer of risk, and it is only possible if the vendor is confident enough in the resolution rate to price around it.

Tiers priced by the value delivered

On 18 May 2026, Zendesk introduced resolution tiers priced by value delivered, drawn from a dollar-based allowance pool, also documented in the SaaSRise guide.

The structure is worth separating into two ideas. First, not all resolutions are worth the same, so they are priced in tiers rather than at a flat rate. Second, the customer buys a pool of dollars rather than a count of units, and different resolution types draw down that pool at different rates.

That handles a problem flat per-resolution pricing does not. A simple password reset and a complex billing dispute are both resolutions. Charging the same for both either overcharges for the easy ones or undercharges for the hard ones.

In text: 1. HubSpot: $1.00 per conversation 2. HubSpot: $0.50 per resolved conversation, April 2026 3. Zendesk: resolution tiers priced by value, May 2026 4. Zendesk: drawn from a dollar-based allowance pool

The questions the definition has to answer

Before you can write this into a contract, four things need answers.

What counts as the outcome. Resolved is not self-evident. Does a conversation count as resolved if the customer stops replying? If they reopen it two days later? If the agent gave an answer that was correct but the customer was unsatisfied? Every one of these has to resolve to a yes or no that a billing system can evaluate.

Who verifies it. The vendor's system knows what it did. The customer knows whether it helped. If the vendor is the only judge, the customer will not trust the invoice. If the customer is the only judge, the vendor carries unbounded revenue risk. Most workable answers put the vendor's system in charge of the measurement and give the customer a defined route to dispute.

What happens to the revenue when it is disputed. Credits, clawbacks or a monthly true-up. This has to be decided in advance because it directly changes what finance can recognise.

What the customer does to help. Outcome rates depend on the customer's own setup: their knowledge base, their data quality, their escalation rules. If the vendor is paid only on results, the contract needs to say what the customer is responsible for providing.

The exposure sits with the vendor

The structural consequence of outcome pricing is that the vendor takes on risk that previously sat with the customer.

Under seat pricing, a customer who deploys the product badly still pays. Under resolution pricing, they do not, and the vendor absorbs the inference cost of every failed attempt with no revenue against it.

That is the real reason to care about the definition. It is not legal hygiene. It determines your gross margin, because the gap between attempts and successful outcomes is a cost you are now carrying.

Start narrower than you think

The practical route is to begin with the outcome that is easiest to define and measure, even if it is not the most valuable one. A narrow, unambiguous unit that both sides can verify builds the operational muscle and the data you need before you attempt the harder ones.

It is also worth running the proposed definition against historical data before it goes into a contract. Take last quarter's activity, apply the definition, and see what you would have billed. That exercise tends to surface the ambiguous cases faster than any amount of discussion.

If you are considering pricing on outcomes, our pricing and packaging work starts with defining the unit.

Related reading: Seat Pricing When AI Means Customers Need Fewer Seats and How to Set AI Credit Rates and Allowances Customers Can Predict.