outcome-based-ai-pricing

Outcome-Based AI Pricing

Overview

When AI replaces human work, the customer needs fewer seats — so seat pricing moves in the opposite direction from the value delivered. The more the product works, the less it earns. The charge unit has to move to a measure of value the customer recognizes: a usage unit close to the work, or the outcome itself.

Core mechanism: pick a charge unit that is measurable, attributable, and grows with value → add a floor and a cap to share risk → check gross margin against inference cost at the tail. The charge unit is a product decision, not a billing detail — the argument of Ramanujam & Tacke's Monetizing Innovation (2016): design the product around the price, not the other way round. Paying for measured results also has long precedent outside software: in U.S. federal Energy Savings Performance Contracts, the agency repays the contractor out of the energy-cost savings the project delivers.

Compose with pricing-strategy (the value-based pricing frame) · unit-economics-cac-ltv-payback (margin and payback) · principal-agent (attribution disputes) · goodharts-law (the metered unit gets gamed).

When to Use

• An AI agent or automation product replaces human workload
• Customers ask "why do we pay the same when we need fewer people?"
• Per-customer inference cost swings widely and a flat subscription leaves margin unstable

When NOT to use: the outcome cannot be measured or attributed · the customer's budget only accepts a fixed fee (offer fixed + usage add-on first) · value is unproven.

Coaching Novices (Adaptive Front Door)

Engine mode: user has a concrete product and cost data → run The Process directly. Coach mode: user is unfamiliar → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.