Outcome Pricing Sounds Right and Usually Is Not

Outcome-based pricing is having a moment. Charge for tickets resolved, deals booked, or spend recovered rather than for access. It aligns incentives perfectly, it is easy to justify to a buyer, and it sounds like the obviously correct answer to the per-seat problem.

It is also the model that quietly kills more small software businesses than any other, and the reasons are worth understanding before adopting it.

The attribution problem

Outcome pricing requires agreement on what happened and why. That agreement is far harder to reach than it appears in a pricing discussion.

If your tool identifies $186,000 of overpaid freight and the customer renegotiates and recovers $140,000, what did you cause? The customer's procurement lead will argue their negotiation produced the recovery. They are not being dishonest. They genuinely did the negotiating. But your fee now depends on a number that is disputed every quarter, with your customer on the other side of the dispute.

Any pricing model that puts you in recurring negotiation with your own customer about how much value you created is structurally hostile to the relationship, regardless of how fair it is in principle.

The measurement burden

“Any model that puts you in recurring negotiation with your own customer about how much value you created is structurally hostile to the relationship.”

Outcome pricing requires a baseline. Establishing a credible baseline means measuring the customer's performance before your product existed, which means either trusting their historical data or running a measurement period before you can charge anything.

For a small company that measurement period is unfunded work, and it extends the sales cycle by exactly as long as the baseline takes to establish. A three-month baseline turns a six-week sale into a five-month one, which most early ventures cannot survive.

The volatility problem

Any model that puts you in recurring negotiation with your own customer about how much value you created is structurally hostile to the relationship.

Outcome-linked revenue is not recurring revenue in any meaningful sense. It moves with the customer's business, their market, their staffing, and events entirely outside your control.

A freight benchmarking tool priced on recovered spend earns beautifully in a volatile rate market and poorly in a stable one, for reasons that have nothing to do with product quality. That volatility makes hiring, forecasting, and any kind of financing considerably harder.

Where it does work

Outcome pricing works when three conditions hold together. The outcome is unambiguously measurable by a system neither party controls. The attribution is not seriously contestable. And the customer would otherwise refuse to buy at all, meaning outcome pricing is a risk-transfer mechanism rather than a value-capture one.

That third condition is the one people forget. Outcome pricing is a good way to sell to a sceptical buyer who will not commit. It is a poor way to maximise revenue from a convinced one.

The model that actually dominates

Hybrid pricing, a base subscription combined with usage or outcome components, is used by around 43% of SaaS companies and is the most common primary structure in recent monetisation surveys. It is the pragmatic answer and it gets far less attention than pure outcome pricing because it is less interesting to write about.

A base fee that covers your cost to serve, plus a component that scales with the customer's use or success, gives you predictable revenue and aligned upside without putting attribution at the centre of every renewal.

The next post covers how hybrid pricing is structured in practice.