Outcome-based pricing charges the customer for a result the product delivers, not for a seat or a unit of usage. A support AI that bills $0.99 per resolved ticket, a collections tool that takes a cut of cash recovered, a sales agent priced per qualified lead: in each case the customer pays when the job gets done. It is the fastest-growing pricing model in AI software, and it is also the hardest to design, because your revenue and your gross margin now both hinge on how you define "the outcome." This guide covers how it works, the real examples, why it is rising, and how to price on outcomes without giving your margin away.
This page goes deep on outcome-based pricing specifically. If you are choosing between models, start with the SaaS pricing models guide; if you want the consumption model it is most often confused with, see usage-based pricing.
What is outcome-based pricing?
Outcome-based pricing (also called results-based or value-based-in-practice pricing) ties the price to a measurable result the customer cares about, rather than to access or consumption. The three common bases:
| Model | You pay for | Example |
|---|---|---|
| Per-seat | A license per user | $29 per user per month |
| Usage-based | A unit of consumption | $0.10 per 1,000 API calls |
| Outcome-based | A delivered result | $0.99 per resolved ticket |
The distinction from usage matters: a customer will happily pay for a job done, but resents paying per token or per API call for work an AI is doing on their behalf. Consumption stops being a good proxy for value once the software does the work rather than assisting a human who does it. That is exactly why outcome-based pricing took off alongside AI agents.
Real outcome-based pricing examples (2026)
Customer service is the cleanest case, because a resolution is objectively definable: the question was answered and the customer did not follow up, or it was not and they did. Binary, measurable, attributable. That is why the first wave of outcome pricing clustered there.
| Product | Billable outcome | Price |
|---|---|---|
| Intercom Fin | Resolved conversation | $0.99 per resolution (lead qualification $9.99), 50-outcome monthly minimum, on top of seats |
| HubSpot Customer Agent | Resolved conversation | $0.50 per resolution (cut to this in 2026) |
| Salesforce Agentforce | Conversation, then per action | Launched at $2.00 per conversation, then added per-action "Flex Credits" |
| Zendesk | Automated resolution | Resolution-based, on a committed plan |
Intercom Fin is the clearest live example. It counts an outcome when the customer confirms their issue is resolved, does not ask for more help after Fin responds, or Fin completes a workflow, and it charges once per conversation regardless of how many questions were answered. Failed attempts are not charged.
Salesforce Agentforce is the cautionary tale. Pricing per "conversation" at $2.00 proved awkward because a conversation could branch and linger without reflecting real value, so Salesforce added per-action credits as an alternative. The lesson is in the next section: the billable unit is the whole design problem.
Why outcome-based pricing is rising
Adoption jumped with the shift to AI agents. In ICONIQ's State of AI snapshot (January 2026, N=297 software companies), the pricing models in use were subscription/platform fees 58%, consumption 35%, per-seat 23%, and outcome-based 18%, up from just 2% a year earlier. Free-with-the-core-product fell from 34% to 17% over the same window. And 37% of companies planned to change their pricing within 12 months, so the mix is still moving.
The driver is structural. When an AI agent replaces work instead of assisting it, per-seat pricing breaks (the customer may cut seats as the agent does more), and per-token pricing feels like paying for the vendor's inefficiency. Charging for the result realigns price with value. It also passes a credibility test: a vendor confident enough to only get paid when it works is making a strong quality claim.
The hard part: defining the billable outcome
Everything difficult about outcome pricing lives in the definition of the outcome. Get it wrong and you either leave money on the table or bill for things the customer does not value.
- Attribution. If a human also touched the work, who gets credit? A "resolution" a customer reopens the next day was not really a resolution. You need rules for partial credit, reopens, and human handoff.
- Gaming and edge cases. Agentforce's "conversation" could branch and drift; a "resolution" can be declared prematurely. The tighter and more binary the outcome, the harder it is to dispute.
- Your margin now rides on efficiency. This is the one founders underestimate. If you charge $0.99 per resolution and each resolution costs you $0.60 in model inference, your gross margin on that outcome is about 39%. If your model gets less efficient, or a hard case takes ten calls to resolve, that outcome can cost more than you charge. Inference stops being an infrastructure line and becomes direct cost of goods sold against each billed result.
That last point is why outcome pricing and gross margin are inseparable. You are effectively promising a unit economic you do not fully control, because it depends on model cost and case difficulty. Model both before you commit to a price.
How to price on outcomes
- Define the outcome so it is binary and attributable. "Ticket resolved and not reopened within 24 hours" beats "conversation." If you cannot state it in one unambiguous sentence, you are not ready to bill on it.
- Cost the outcome first. Estimate the fully-loaded cost to deliver one result, including model inference at the p90 hard case, not the average. Your price has to clear that with margin to spare.
- Set a floor. A per-outcome minimum (Intercom's 50-outcome monthly minimum) or a small platform fee protects you from customers who get all the value at near-zero billed volume.
- Decide what is free. Not charging for failed attempts is good faith and good marketing, but it moves margin risk onto you. Price the successes to cover the failures.
- Model the blended margin. Run it as a distribution, not an average: some customers will have cheap outcomes, some expensive. If the expensive tail turns the blended margin negative, re-price or cap.
A hybrid is common and often safer: a base platform fee (predictable revenue, covers fixed cost) plus an outcome charge (aligns with value, scales with success). Pure outcome pricing maximizes alignment but also maximizes your exposure to model cost.
When outcome-based pricing fits, and when it does not
| Fits when | Avoid when |
|---|---|
| The outcome is binary and measurable (resolution, qualified lead, dollar recovered) | The result is fuzzy or subjective ("engagement," "insight") |
| Your software does the work, not just assist | A human does most of the work and the tool assists |
| You can attribute the result cleanly to your product | Attribution is contested across many tools and people |
| Your cost per outcome is well below the price, even on hard cases | Model or delivery cost per outcome is volatile or high |
What outcome pricing does to your model
Outcome-based revenue is harder to forecast than a subscription and behaves more like usage: it scales with the customer's success, not a fixed contract. Model it bottom-up from expected outcome volume per customer, and pair each revenue line with its inference-cost line so margin is visible per result, not buried in a blended COGS number. This is precisely the analysis flat-subscription models never had to do, and it is where founders get surprised. Adlega models outcome and usage revenue against their cost of delivery so you can see gross margin per outcome before you commit to a price, and its AI CFO explains which assumption is driving the number. For the wider picture, see the pricing models guide.
Outcome-based pricing FAQ
What is outcome-based pricing?
A pricing model where the customer pays for a measurable result the product delivers, such as a resolved support ticket or a qualified lead, rather than for a seat or a unit of usage. Price is tied to value delivered, not access.
What is an example of outcome-based pricing?
Intercom's Fin AI agent charges $0.99 per resolved conversation, HubSpot's Customer Agent charges around $0.50 per resolution, and Salesforce Agentforce launched at $2.00 per conversation before adding per-action pricing. Outside support, collections tools that take a percentage of cash recovered use the same principle.
What is the difference between usage-based and outcome-based pricing?
Usage-based pricing charges for consumption (API calls, tokens, seats used); outcome-based pricing charges for a result (a resolution, a conversion). Usage bills for effort, outcome bills for the job getting done. Outcome pricing puts more margin risk on the vendor, since cost to deliver can exceed the price on a hard case.
Does outcome-based pricing work for AI products?
It fits AI agents especially well, because they do work rather than assist, so consumption is a poor proxy for value. Adoption rose from about 2% to 18% of software companies in the year to early 2026 (ICONIQ). It works best where the outcome is binary and attributable, like customer-service resolutions.
How do you price an outcome?
Define the outcome so it is binary and attributable, cost the fully-loaded delivery of one result (including model inference on hard cases), set your price to clear that with margin, add a floor or minimum, and model the blended margin as a distribution rather than an average. A base fee plus an outcome charge (a hybrid) reduces your exposure.
What are the risks of outcome-based pricing?
Contested attribution, disputes over what counts as an outcome, unpredictable revenue, and the big one: your gross margin depends on how efficiently you deliver each result, so rising model cost or hard cases can turn an outcome unprofitable. Define the outcome tightly and model the margin before committing.
Related: usage-based pricing, SaaS pricing models, SaaS gross margin, and the AI CFO.