Per-Outcome Pricing
Also known as: outcome-based pricing · pay per outcome · pay per resolved · success-based pricing
A SaaS pricing model that charges the customer for each completed business-value event (ticket resolved, PR opened, invoice reconciled, return filed) rather than per user or per month.
In depth
Per-outcome pricing is the business-model pattern that agentic SaaS unlocks. For 20 years, software priced per seat — the user paid for the tool; they did the work. Agents invert this contract. The agent does the work; the customer pays for the outcome.
The economic consequences are large. A salesperson generates roughly $100,000 of annual value. Per-seat SaaS priced at $50 per month captures 0.5% of that value. Per-outcome pricing on a sales research agent priced at $20 per qualified lead, at 50 leads per rep per month, captures around $1,000 per rep per month — 20x more.
Per-outcome pricing works when the outcome is measurable, repeatable, and tied to the customer's own revenue or cost reduction. It does not work for subjective tasks (creative writing, judgment calls) or tasks where the customer cannot agree on what 'done' means.
Formula & example
Rules of thumb
- Anchor the price against the customer's value of the outcome, not the cost of tokens.
- Define 'outcome' crisply enough that both sides agree when one has occurred.
- Offer a baseline per-outcome price with volume discounts at enterprise tier.
- Publish your reliability score — enterprise buyers pay for measured outcomes, not hope.
Common mistakes
- Setting the outcome definition loosely — disputes on what counts destroy the relationship.
- Pricing against the agent's cost structure rather than customer value — leaves 5-15x upside.
- Refusing to offer a minimum contract — enterprise procurement departments need predictable spend.
Put it into practice
FAQ
Does per-outcome pricing work for consumer products?
Rarely. Consumers prefer predictable flat subscriptions and push back on pay-as-you-go variability. Per-outcome is primarily a B2B model, occasionally a prosumer model for power users.
What if the agent completes a task but the customer disputes the outcome?
Build a dispute flow into the product from day one. Customers flag disputed outcomes, the team reviews, and disputed-successful outcomes get a credit. Budget 2-5% of outcomes for dispute credits; anything higher signals the outcome definition is not crisp enough.
Related terms
USE THIS IN A REAL PLAN
Turn concepts into a real SaaS blueprint
PlanMySaaS runs Per-Outcome Pricing and every other SaaS metric for your idea — part of a full blueprint with architecture, feature specs, 21 docs, and Cursor-ready prompts.
Last reviewed 14 April 2026 by Abhi Verma.