What is the difference between an input, an output, and an outcome in AI pricing?

In Woody's essay, an input is a cost, like a token. An outcome is a business result for the customer, such as more revenue, more pipeline, or less churn. An output is an objective, verifiable metric, like a generated image, a sent email, or a resolved support conversation.

What went wrong with pricing per resolved ticket?

The definition was the vendor's reading, not the customer's. Resolved meant no escalation within 48 hours. Customers who came back after 60 to 72 hours with a related follow-up considered it the same issue and contested the charge. At scale that was more than 200 contested cases a week, and the dispute team grew from 4 analysts to 14.

Rewriting the unit at month 20 to require no follow-up in 7 days. It cost some revenue and cut disputes by 60%. Before launch, the cheaper fix is to test the definition at 10x the projected dispute volume and to staff dispute analysts to 5x the projection.

What does the contract need before the meter?

The unit definition, a dispute window, an arbitration mechanism, a committed minimum, and a price ceiling, each in writing.

Is Outcome-Based Pricing a Myth? Outputs Get Disputed Too

Is outcome-based pricing a myth?

THE SHORT ANSWER

No, and output-based pricing is not the escape from it. Scott Woody argues on the Stripe blog (2026-10-01) that outcome pricing is a myth outside monopoly power or very large contracts, and that vendors should price an objective output like a resolved support ticket. When I priced per resolved ticket, the definition (no escalation within 48 hours) held for 98% of cases, and the remaining 2% produced more than 200 contested cases a week and 600 disputes a month against 50 projected. Outcome and output sit on one line: outcomes draw few, large attribution disputes, and outputs draw many small definition disputes. Price the unit whose disputes you can afford, and put the definition, the dispute window, and the arbitration path in the contract before the meter.

Scott Woody's essay on the Stripe blog makes two arguments. The first, that a token invoice defines your value as a markup on someone else's cost, holds. The second, that outcome pricing is a myth and an objective output is the way out, is the one The Output Gets Disputed Too takes apart, using his own example of a resolved support ticket.

The numbers come from Field Report: What Broke When We Killed Our Per-Seat Tier: a definition that held for 98% of cases, 200-plus contested cases a week from the rest, 600 disputes a month against 50 projected, and a 60% drop after the definition moved to seven days. The three redesigns in Per-Outcome Pricing: What Gets Clearer and What Gets Terrifying show the same trade at $1.75 per resolved ticket, $40 per qualified meeting, and $1.20 per accepted suggestion. All of it belongs to the SaaS to AI Business Models argument.

Last reviewed 2026-10-02 · 1 min read

Is outcome-based pricing a myth?

SOURCES

THE LONG VERSION

RELATED ANSWERS