Outcome-based pricing
Paying when the AI does the job -- per outcome, not per token or seat -- has gone from a single live example to a documented pattern across the corpus. Twenty-four of 338 corpus companies (about 7%) now price on outcomes; the absolute count has roughly tripled as the corpus grew, yet it remains a minority model. It is a category standard in customer support, where Ada, Gorgias, Gladly, Kustomer, Lorikeet, Intercom Fin (at $0.99) and Parloa all bill per resolution, with Rox (per Agent Action in sales), Pixee (per code fix) and Digits (accounting outcomes) extending it beyond support.
What's happening — and why
What's happening: a growing set of products charge by the result the AI produces, not the work it does to get there. Twenty-four of the 338 corpus companies — about 7% — now meter on an outcome unit, up from a single live example when this trend was first logged; the absolute number has roughly tripled as the corpus expanded, but outcome pricing is still a minority model. In customer support it is now the default for new entrants — Intercom's Fin bills $0.99 per resolved conversation, and Ada, Gorgias, Gladly, Kustomer, Lorikeet and Parloa all meter on resolutions. Beyond support, Rox bills per Agent Action for sales tasks, Pixee per merged code fix, Digits on accounting outcomes, and the per-task unit has spread into pharma (Recursion milestones), AI training data (Mercor, Micro1) and contact-center QA (Observe.AI).
Why it works here: outcome pricing needs a result that's cleanly measurable and attributable to the AI. A resolved support ticket is about the cleanest such unit there is, which is why the support category converged on it first. Open-ended generation still doesn't qualify — but wherever an agent performs a discrete, checkable task, the outcome is becoming the meter.
How it works
Evidence over time
15 supporting · 4 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| Intercom | Mar 2024 | Fin AI agent priced per resolution ($0.99) — you pay only when the bot actually resolves a conversation, not per seat or per message. The first live outcome-priced product in the corpus. |
| Rox | Jun 2026 | AI sales-agent swarm metered in Agent Actions — each task (account research, meeting brief, pipeline generation) costs a defined number of actions scaled to complexity and model used. Tagged outcome-based in taxonomy. Free Starter (2k actions/mo), Core $50/mo (5k actions), custom Enterprise. |
| Gorgias | Jun 2026 | Published a transparent flat per-resolution AI Agent price alongside its tiers — outcome (resolution) billing made fully public in customer support. |
| Ada | Jun 2026 | Outcome/per-resolution model (third-party data ~$1–$3.50/resolution); the resolution unit is the core meter, now sales-gated. |
| Lorikeet | Jun 2026 | Repriced to channel-based per-resolution credits with a 2–3x list increase — resolution as the billable unit, now segmented by channel. |
| Kustomer | Jun 2026 | Hybrid seats + resolutions — per-resolution outcome billing layered onto seat-based CS pricing. |
| Parloa | Jun 2026 | Quote-only model metered on media-minutes and resolutions — voice CS agent billed on the resolved outcome. |
| Pixee | Feb 2026 | Pivoted to outcome-based, quote-only pricing in security — billed per fix/resolution (auto-remediated vulnerability) rather than per seat or scan. |
| Digits | Apr 2026 | Launched outcome-based Enterprise pricing for accounting firms — billing tied to delivered accounting outcomes, not seats. |
| Recursion | Jun 2026 | Pharma AI company billing on milestones and outcomes from drug-discovery partnerships — the most capital-intensive outcome-based billing in the corpus, where the 'outcome' is a clinical-trial milestone worth tens of millions of dollars. |
| Mercor | Jun 2026 | AI training marketplace billing per-task (sales-only) for AI data labeling and evaluation — outcome-based billing applied to human+AI annotation work. |
| Micro1 | Jun 2026 | AI labeling and tasks platform metered per-task (sales-only) — confirms the per-task unit extends into AI training data markets. |
| Observe.AI | Jun 2026 | Per-agent + per-interaction pricing for contact-center AI quality assurance — the interaction as a billable outcome unit in enterprise voice operations. |
| HubSpot | Jul 2026 | Moved Breeze Agents to outcome pricing: the Customer Agent bills $0.50 per RESOLVED conversation (50 HubSpot Credits, down from $1.00 per conversation) and the Prospecting Agent $1.00 per recommended lead (100 credits) — a 'you pay when it works' resolution unit on a horizontal CRM platform, explicitly positioned to undercut Salesforce Agentforce's per-conversation meter. |
| Gorgias | Jul 2026 | Raised its per-resolution economics: AI Agent overage past the bundled allotment went from $0.90 to $1.50 per automated interaction (+67%), with a modest included allotment (30 interactions on Basic) at ~$0.90 each. The per-resolution unit is settled; the dollar figure moved UP — the opposite direction to HubSpot's cut the same week. |
Counterexamples
- OpenAI · May 2026 — Prices inputs (per token) and seats, not resolved outcomes.
- Harvey · May 2026 — Per-seat enterprise pricing — value is billed by access, not by task completed.
- Anthropic · May 2026 — Pure per-token API + seat subscriptions; no outcome unit.
- 11x · Jun 2026 — Sells AI SDRs as 'digital workers' but prices on subscription seats, not per completed outcome — the agent framing without the outcome billing.
Trivia
-
Intercom's $0.99-per-resolution Fin pricing (March 2024) is the corpus's first live outcome-priced product, and its outcome definition — "no follow-up contact within 24 hours" — is the only published, time-bounded resolution standard in the corpus. That 24-hour window has become an informal reference point for the category: subsequent outcome-pricing discussions routinely invoke it when asking what "done" means for an AI agent in a support context.
-
Rox's "Agent Action" unit (June 2026) is the first outcome-pricing model in the corpus where cost scales explicitly with task complexity and model used — meaning two nominally identical Agent Actions can cost different amounts depending on which AI model handles them. This is a structural departure from Intercom's flat-rate resolution model and suggests outcome pricing will fragment into complexity-tiered outcome units as agent tasks become more heterogeneous.
-
11x is the corpus's sharpest illustration of the gap between agent framing and outcome billing: it sells AI SDRs as "digital workers" — the strongest possible outcome framing — but prices them on subscription seats, not per completed task. The contrast with Rox (same sales-automation use case, per-action billing) shows that outcome pricing is a deliberate structural choice, not an automatic consequence of positioning a product as an autonomous agent.
-
The 2026-06-08 re-test invalidated this trend's own "two adopters" framing in one stroke: per-resolution billing turned out to be the *default* in AI customer service, not a curiosity — Ada, Gorgias, Intercom, Kustomer, Lorikeet, Parloa, and Gladly all meter resolutions, meaning outcome pricing is simultaneously the rarest model corpus-wide and the category standard inside one vertical.
-
Outcome pricing and price gating move together: Ada, Parloa, Pixee, and Gladly all bill per resolved outcome AND hide the per-unit rate behind sales (Ada's ~$1–$3.50/resolution is only knowable from third-party data) — so the vendors most willing to tie price to delivered value are also the least willing to publish what that value costs, because the resolution rate is the negotiating lever.
-
Lorikeet (2026-06-07) is the first corpus vendor to *raise* outcome prices 2–3x while re-segmenting the unit by channel — evidence that as resolution billing matures it fragments (per-channel, per-complexity) rather than commoditizing toward a single flat rate, the opposite of what happened to per-token model pricing.
For buyers
Outcome pricing aligns spend with value — but scrutinise the definition: what counts as a 'resolution', who adjudicates it, and how the per-outcome price compares to your fully-loaded cost to do it another way. A loose definition can bill outcomes you wouldn't have paid a human for.
For vendors
Outcome pricing only works where the result is measurable, attributable and hard to game. You need event instrumentation, a defensible definition and dispute handling. Start with a narrow, checkable outcome (a resolved ticket, a completed task) before generalising.
Outlook — what to watch
Per-resolution is now the support default; the open question is whether the next agentic categories (sales, coding, finance, pharma) standardise on their own outcome unit the way support did. Watch the per-resolution price itself — as token deflation cuts the underlying cost, the $0.99 anchor has room to fall, and incumbents still on seat pricing will face pressure to add an outcome meter. The status would weaken if outcome adoption stalls as a share of the corpus, or if the support-resolution unit fragments so far (per-channel, per-complexity) that 'outcome' stops meaning a single comparable thing.
Bottom line
Outcome-based pricing has grown from a single live example to 24 of 338 corpus companies (about 7%) — roughly tripling in absolute adopters as the corpus expanded, while staying a minority model overall. Per-resolution billing is the de-facto standard for new customer-support AI, and the pattern holds wherever an agent performs a discrete, verifiable task.
FAQ
What is outcome-based pricing for AI?
Charging for the result the AI delivers -- a resolved support ticket, a completed sales task -- rather than for seats, messages or tokens. You pay when the job gets done.
How common is outcome-based pricing?
It's a minority model: 24 of the 338 corpus companies — about 7% — price on outcomes. That's up from a single live example when the pattern was first logged, so adoption has roughly tripled in absolute terms, but seat- and usage-based pricing remain far more common.
Who uses outcome-based pricing?
In customer support it's now standard — Ada, Gorgias, Gladly, Kustomer, Lorikeet, Intercom (Fin, $0.99/resolution) and Parloa all meter resolutions. Beyond support: Rox (per Agent Action in sales), Pixee (per merged code fix), Digits (accounting outcomes), Recursion (pharma milestones), and Mercor/Micro1 (per-task AI training data).
Where does outcome pricing work — and where doesn't it?
It needs an outcome that's measurable, attributable to the AI and hard to dispute. Support deflection (resolved or not) is the cleanest case, which is why support standardised on it first; open-ended generation doesn't qualify yet. Some agent vendors selling 'digital workers' (11x) still price on seats.