Zendesk, Intercom, Sierra, and others have publicly committed to outcome-based pricing in the past year. Gartner forecasts that by 2027, a majority of enterprise AI agreements will include outcome components. But the companies making the move are struggling to operationalize it. This post is for the VP Sales, CRO, or Head of Pricing who has been asked to make the shift and doesn't know where to start.
Why outcome pricing stalls
Outcome pricing fails in specific, predictable places. The deal is not structured precisely enough — outcome definitions are vague, measurement methodology is unspecified, exclusions and edge cases are left to future negotiation. The data is messy or disputed. The workflow still needs human judgment the vendor doesn't control. Finance cannot turn approved outcomes into invoices and records.
Each of these is solvable — but only if you name it explicitly and design for it. Most companies trying to shift to outcome pricing fail because they treat the pricing change as a sales and marketing problem. It's an operational problem. And it requires operational infrastructure.
The four-phase structure
Every durable outcome-based deal has four phases: structuring (before signing), execution (during the engagement), verification (after outcomes are claimed), and settlement (when money moves). Most companies collapse these phases mentally, which is why their deals break.
Treating them as distinct — with distinct tooling, distinct ownership, and distinct checkpoints — is the first operational insight that separates companies that make outcome pricing work from companies that can't get past the pilot stage.
The measurement question
Who measures the outcome? If the vendor measures, they have an incentive to count high. If the buyer measures, they have an incentive to count low. If either party operates the measurement system, the other party cannot fully trust the output.
The resolution is a measurement methodology and source systems that both parties agreed to before the deal started — documented in the deal specification, executed against agreed sources, and reviewable by an independent CPA when disputes arise. Both parties operate against the same defined process. That process becomes the basis for payment.
Structuring the deal
The first document you need is a signed deal specification. Not a term sheet. A structured document that defines the outcome being sold, the measurement methodology, the baselines, the exclusions, the fallback pricing, the evidence requirements, and the dispute resolution process. This becomes the operating rules for everything downstream.
The deal specification is not a legal document. It's an operational document that happens to be signed. Its purpose is to give both parties a shared reference point when anything is ambiguous — which will happen.
Common mistakes in the first deal
- Baselines defined after the deal is live. Too late. The baseline must be established from agreed source data before the engagement begins, or the "improvement" you're claiming has no reference point.
- Outcome definitions that rely on the vendor's internal dashboards. Not independent. Measurement sources must be jointly agreed and defined in the deal specification before measurement begins.
- Pricing formulas that don't account for reversal windows. Creates unlimited exposure. Define the window during which outcomes can be reversed or clawed back.
- No agreed dispute resolution path. Every disagreement escalates to legal. A defined escalation path — counter-evidence submission, adjudication, appeal — prevents escalation by giving both parties a process to follow.
What to ship first
Most companies try to transition their entire book to outcomes in one move. Wrong approach. Pick one deal — ideally a lighthouse customer who already wants outcome pricing — and use it to build your infrastructure. The first deal is your pilot, not your growth engine.
The first deal will be harder than it needs to be. That's expected. The second deal will be easier because you'll have a specification template, a baseline methodology, and measurement infrastructure that's already proven. By the fifth deal, the infrastructure is compounding.
Outcome pricing is becoming table stakes
Companies that build the infrastructure — measurement, verification, settlement — before they need it will outcompete companies that don't. The window to be ahead of this shift is closing.