Economy & Market December 10, 2024 sierra.ai

From Seat-Based to Outcome-Based Pricing for AI Agents

Sierra blog post (December 10, 2024, Elliot Greenwald) that lays out the founding text of outcome-based pricing for AI agents. Pivotal thesis: AI agents that execute processes autonomously make possible an entirely new pricing model — "you pay only when the software achieves specific, valuable outcomes: outcome-based pricing." The article traces a four-age genealogy of software pricing: (1) shrink-wrapped software (1980s-90s, floppy disk/CD-ROM box at Fry's Electronics — "Whether you actually used it or not, you paid for it") → (2) SaaS / seat-based (pioneered by Salesforce, followed by Google/Microsoft/Adobe — the Internet makes it possible to sell software as a service) → (3) consumption-based (Amazon/AWS and Snowflake — "charged only for what you used") → (4) outcome-based (AI agents). Canonical definition: *"outcome-based pricing is tied to tangible business impacts—such as a resolved support conversation, a saved cancellation, an upsell, a cross-sell, or any number of valuable outcomes.

By **Elliot Greenwald** — Sierra / December 10, 2024 / Source sierra.ai ↗ / Reading 2 min / .md / / Auto-verified translation

#outcome-based pricing#results-based pricing#AI agents#autonomous AI agents#Sierra#seat-based pricing#shelfware#consumption-based pricing

On December 10, 2024, Elliot Greenwald (Sierra) published the founding text of outcome-based pricing for AI agents. Pivotal thesis: AI agents executing processes autonomously make possible an unprecedented pricing model — "you pay only when the software achieves specific, valuable outcomes: outcome-based pricing."

The article unfolds a four-age genealogy. (1) Shrink-wrapped software (1980s-90s): the floppy disk/CD-ROM box at Fry's Electronics — "Whether you actually used it or not, you paid for it." (2) SaaS / seat-based: Salesforce pioneered it, followed by Google/Microsoft/Adobe; its major flaw = shelfware ("Unused seats sit idly on a proverbial store shelf"). (3) Consumption-based: AWS and Snowflake — "charged only for what you used." (4) Outcome-based: AI agents.

Canonical definition: "outcome-based pricing is tied to tangible business impacts—such as a resolved support conversation, a saved cancellation, an upsell, a cross-sell, or any number of valuable outcomes. If the conversation is unresolved, in most cases, there's no charge."

Alignment principle: "With outcome-based pricing, Sierra gets paid only when we complete a task for you. Our incentives are aligned." Greenwald highlights the structural conflict facing legacy CX vendors: their revenue depends on seat-based pricing, yet "the more effective their AI becomes, the fewer contact center seats their clients need—undermining the provider's own revenue model." An effective AI agent cannibalizes a revenue model built on seats; a pure-play vendor paid on outcome has no such conflict.

The model is granular: a distinction is drawn between simple resolutions (a single question) and complex ones (a case requiring a 20-minute L2 call); escalations generally incur no charge; a blended pricing model is possible (consumption-based for routing/greeting interactions). On the vendor side, there is a commitment to continuous optimization: "we continue to deploy concerted, directed optimizations to refine the agent's performance over time."

Scope: posed in late 2024, this post precedes and grounds the 2026 debate on the agentic economy. It supplies the vocabulary of the billing unit (the completed outcome, not the seat/usage/token) later taken up by Gupta (cost of a completed outcome, buyer-side view), Bain (outcome-based pricing shifts revenue from fixed seats to labor/operations economics, with Sierra cited as an example) and Ng (pricing anchored to the replaced salary). ⚠️ The article contains no figures (no ROI, no named client): it is a conceptual manifesto. To be used for the Cost Optimization slot (vendor-side view of cost per outcome) and the value-based positioning of agentic delivery.

Key takeaways

Date / source. December 10, 2024, Sierra blog, Elliot Greenwald. Founding text of outcome-based pricing — roughly 18 months ahead of the 2026 debate (Gupta, Bain).
Pivotal thesis. autonomous AI agents make possible a 4th era of pricing — "you pay only when the software achieves specific, valuable outcomes." ### The four-age genealogy | Age | Model | Unit | Example | Waste | |-----|--------|-------|---------|-----------| | 1980-90s | Shrink-wrapped | the box | Fry's Electronics (floppy disks/CD-ROM) | total (paid whether used or not) | | Internet | SaaS / seat-based | the seat (license) | Salesforce, Google, Microsoft, Adobe | high (shelfware) | | Cloud | Consumption-based | usage | AWS, Snowflake | medium | | AI agents | Outcome-based | the completed outcome | Sierra | low | ### The definition to remember > "outcome-based pricing is tied to tangible business impacts—such as a resolved support conversation, a saved cancellation, an upsell, a cross-sell, or any number of valuable outcomes. If the conversation is unresolved, in most cases, there's no charge." ### The structural conflict facing legacy CX vendors
Legacy revenue = seat-based (thousands of $/year per license).
Yet "the more effective their AI becomes, the fewer contact center seats their clients need" → a good AI agent cannibalizes the vendor's revenue model.
Sierra (a pure-play vendor) has no such conflict: paid on outcome, it benefits from reducing the need for seats. ### The model's granularity (fairness)
Simple resolution. (answering a question) vs complex resolution (a case requiring a 20-minute L2 call) → priced differently.
Escalations. "typically incur no charges."
Blended pricing. is possible: e.g. consumption-based for routing/greeting interactions, outcome-based for resolutions.
Continuous optimization. "we continue to deploy concerted, directed optimizations to refine the agent's performance over time" — durable alignment. ### ⚠️ What the article does NOT contain
No figures. no ROI, no client metrics, no client names (not even Klarna), no precise pricing. It is a conceptual manifesto, not a case study. ### To be used for
"Cost Optimization" slot (Claude Code morning session). the vendor-side view of cost per completed outcome — a perfect complement to Gupta's cost of a completed outcome (buyer-side view). Useful to explain why the KPI becomes the outcome, not the token/seat.
Agentic-delivery pricing positioning (firm). a canonical reference for proposing value-based / outcome-based models on engagements, vs. staff-augmentation/day-rate billing.
CX decision-maker messaging. the concept of shelfware + incentive alignment ("we get paid only when we complete a task") = simple, memorable arguments. ### Connections within the watch dossier
Gupta — Token Budget Wars. (2026-05-28): the exact buyer-side counterpart — "what is the cost of a completed outcome?", token-to-outcome attribution. Sierra (2024) lays out the billing model, Gupta (2026) lays out the measurement problem that makes it operable. Gupta also cites "which replace BPO" — Sierra is that type of vendor.
Bain — cross-system labor. (2026-05) & Rule of 40 (2026-04): Bain cites Sierra as a reference example and describes outcome-based pricing as shifting revenue from fixed seats to labor/operations economics — Greenwald is the primary source of this shift.
Ng — No AI jobpocalypse. (2026-05-08): pricing power (vendors anchor pricing to the salary of the replaced employee) — Sierra's outcome-based pricing is precisely this anchoring (a resolution = a unit comparable to the cost of a human agent/BPO).
VoxComm / MediaPost — billable hours are dead. (2026-03): the same value-based / performance-based shift in knowledge services (agencies) — a cross-cutting convergence.
Hezarkhani — Paying Engineers like Salespeople. (2025-11): compensation-to-outcome alignment, another variation on skin in the game.
Sierra (dossier). Bret Taylor AI-native interview (2026-04-20) + Iyengar/Asemanfar/Wang (2026-04-22) — this post completes the Sierra portrait from the business-model side.

Attributed claims

"If the conversation is unresolved, in most cases, there's no charge"
— Sierra
escalations generally do not result in any billing
— Sierra

Reading note — the source

Profile: Corporate-pedagogical blog post aimed at CX buyers / decision-makers (VP Customer Experience, COO, CFO) and the product community. An assumed "we" (Sierra) perspective, clear and didactic register, low technical level — the argument is economic, not technical. Short format (pricing manifesto, ~5 min).

Style: Storytelling through historical genealogy (the floppy-disk box at Fry's → SaaS → consumption → outcome) — a classic device for making outcome-based pricing appear as the natural culmination of an evolution, rather than a self-interested commercial argument. Polished marketing prose: each pricing age is summed up in a memorable image-phrase ("shelfware," "the meter is running" for the usage version). Prescriptive and self-positioning tone: the article implicitly sells the Sierra model while presenting it as the client's aligned interest ("Our incentives are aligned"). Tactical honesty: it acknowledges granularity (simple vs. complex resolutions, unbilled escalations, blended pricing) to lend credibility to the model's fairness.

Key aphorisms: - "you pay only when the software achieves specific, valuable outcomes: outcome-based pricing." (pivotal definition). - "With outcome-based pricing, Sierra gets paid only when we complete a task for you. Our incentives are aligned." (alignment principle). - "If the conversation is unresolved, in most cases, there's no charge." (the shared-risk promise). - "Unused seats sit idly on a proverbial store shelf, hence the derisive moniker 'shelfware.'" (critique of seat-based pricing). - "the more effective their AI becomes, the fewer contact center seats their clients need—undermining the provider's own revenue model." (the structural conflict facing legacy vendors).

Worked metaphors: - Shelfware — unused seats "sitting idly on a proverbial store shelf": an image that turns unused fixed cost into visible waste, set against the outcome-based model. - The floppy-disk box at Fry's — a nostalgic anchor that makes tangible the idea of "paying whether you use it or not," the starting point of a trajectory toward strictly value-based payment. - Incentives aligned — the rhetorical pivot: outcome-based pricing is not presented as a pricing grid but as a structural alignment between vendor and client (the vendor only wins if the client gets the outcome).

Epistemic stance: a business-model manifesto positing a pricing category (outcome-based) as the culmination of a genealogy. A normative argument (this is the right model) served by a historical narrative (this is the inevitable model).

Authority: built through (a) Sierra's position as a pure-play CX AI-agent vendor (Bret Taylor), (b) the genealogical narrative that places the proposal in continuity with Salesforce/AWS/Snowflake, (c) the consistency of the "skin in the game" logic (we only get paid when you get the outcome), (d) the granularity (simple/complex resolutions, escalations, blended pricing) that defuses the unfairness objection.

The knowledge graph extracted from this fiche — 8 entities, 14 relations.

In this graph : Elliot Greenwald · Sierra · Outcome-based pricing · Shelfware · Généalogie tarification logicielle · Conflit fournisseurs CX legacy · Blended pricing · Alignement des incitations

Outcome-based pricing — definition →

READ THE ORIGINAL ARTICLE ↗ .MD VERSION FOR AGENTS

From Seat-Based to Outcome-Based Pricing for AI Agents

Summary

Key takeaways

Attributed claims