Outcome-based pricing

Outcome-based pricing charges for the thing the customer wanted, not the thing that produced it. Not seats, not API calls — resolved support tickets, qualified leads, completed reconciliations, successful collections.

AI agents are what made this practical at scale. When software performs work that previously required a person, the natural unit of value shifts from “access for that person” to “the work itself”, and the vendor can plausibly take responsibility for the result.

The three hard problems

Attribution. Did your product cause the outcome, or did it happen anyway? A lead-qualification tool that charges per qualified lead has to define qualification in a way the customer accepts without arbitration.

Measurement. The outcome has to be countable, auditable and resistant to disagreement. This is metering with much higher stakes, because every disputed unit is a disputed invoice.

Revenue predictability. Outcome revenue is variable by construction, which makes forecasting harder and ARR reporting genuinely contentious. Most vendors mitigate with a minimum commitment or a platform fee underneath.

What it demands of your billing stack

Outcome pricing is metered pricing where the meter is a business event rather than a technical one, and where the customer will audit it. That means an event ledger with full history, mid-period visibility for the customer, and the ability to change the outcome definition on new contracts without repricing existing ones.

Very few pricing models expose the limits of a billing platform faster.