The 48% NRR Floor: Why AI-Native SaaS Is Leaving Expansion Revenue on the Table
Three of the most-deployed support AI products now charge $0.99–$2.00 per resolved ticket, not per agent seat. Here's the economics, the vendor risk, and what it forces product managers to build — whether they're buying or shipping AI.
The Ticket That Cost $0.99
Sometime in 2025, Intercom made a decision that should have received more attention in SaaS pricing circles than it did. The company published a price card for Fin, its AI support agent: $0.99 per resolved conversation.
Not per seat. Not per month. Per resolution.
Zendesk followed with $1.50 to $2.00 per automated resolution for its AI Agents product, plus a $50 per-human-agent add-on for the AI capabilities. Salesforce launched Agentforce at $2.00 per conversation (a slight variation — per conversation, not per confirmed resolution, but in the same paradigm).
In the span of roughly 12 months, three of the most widely deployed customer service platforms in enterprise software converged on a fundamentally different way to bill for AI. The pricing unit shifted from the human to the outcome. The implicit contract between vendor and customer changed: instead of "here is a tool, use it however you want," the deal became "here is a result — pay when you get one."
This shift matters far beyond customer service. Per-resolution pricing is the first large-scale deployment of outcome-based pricing for enterprise AI, and the patterns it establishes — the product design requirements, the measurement standards, the risk allocation between buyer and seller — will shape how AI pricing works across every category over the next three years. Product managers in industries far outside support automation need to understand what is happening here.
How Per-Resolution Works — and How It Differs
The traditional enterprise SaaS pricing model has a clean logic: count the users, multiply by the monthly rate, invoice. The unit of value is access. Per-resolution pricing changes the unit of value to outcome.
A resolution is a support interaction that completes without human handoff. The AI understands the customer's issue, locates or generates a response, delivers it, and the customer closes the interaction satisfied. No human agent touches the ticket. The vendor collects the per-resolution fee. Conversations that escalate — where the AI cannot handle the issue, or where the customer explicitly requests a human — are not billed as resolutions.
This sounds simple. In practice, three definitional problems immediately appear.
The classification problem. Who decides whether an interaction was resolved? Vendors currently self-classify: their system identifies when a conversation closed without escalation and charges accordingly. But "closed without escalation" is not the same as "issue resolved." A customer who gives up in frustration and closes the chat without escalating is classified as a resolution. A customer who says "thanks" and then files a new ticket 20 minutes later is classified as two interactions — the first one a resolution. Enterprise buyers need contract language that defines resolution quality, not just resolution mechanics, and audit rights to verify that automated classification matches their customer satisfaction data.
The scope problem. Per-resolution pricing works well when the issue type is well-defined: reset a password, track a package, cancel a subscription. It becomes complex when the AI handles nuanced, multi-step, or subjective requests. Is a resolution where the AI provided technically accurate information that the customer didn't understand really a resolution? Vendors are currently resolving this by scoping their per-resolution billing to specific issue categories — the simple, high-volume, well-defined requests that their AI handles with high confidence. This creates a hybrid model where simple tickets are AI-handled and per-resolution-billed, while complex tickets remain human-handled and bundled into the base seat price. That hybrid is practical but introduces complexity that buyers need to map carefully.
The margin problem. At $0.99 per resolution, Intercom needs its cost per resolution to be well below $0.99 — including the inference cost of running the AI model, the infrastructure cost of serving the conversation, and the amortized cost of the fine-tuning and training that makes the model accurate for support tasks. Deloitte's June 2026 accounting spotlight on outcome-based pricing notes that this cost structure is harder to manage than fixed subscription margin because it varies with conversation complexity, model version changes, and input token volume. A complex support request may require 10,000 tokens of reasoning to resolve at $0.99 — the same price as a one-sentence password reset.
The Three Vendors Setting the Standard
The comparison across the three primary per-resolution vendors reveals meaningful differences in model design.
| Vendor | Unit | Price | Definition | Human seat add-on |
|---|---|---|---|---|
| Intercom Fin | Per resolution | $0.99 | Closed without escalation, not reopened in 24h | Included in base plan |
| Zendesk AI Agents | Per automated resolution | $1.50–$2.00 | AI fully handled ticket, no human touch | $50/agent/month add-on |
| Salesforce Agentforce | Per conversation | $2.00 | Any AI-handled conversation started | Standard license required |
| Freshworks Freddy AI | Per automated ticket | $1.00–$1.50 | Ticket closed by AI without human intervention | Included in Pro tier |
| Quickchat AI | Per resolved session | $0.75–$1.50 | Customer rated interaction complete | Base subscription required |
Salesforce's model is the most aggressive: billing per conversation rather than per resolution means that interactions where the AI fails to help still generate revenue for Salesforce. Buyers in negotiations should note this distinction — Agentforce's $2.00 per-conversation rate has a different economic profile than Intercom Fin's $0.99 per-resolution rate, even though they are priced similarly.
Zendesk's model is the most conservative: the combination of per-resolution billing plus a per-agent add-on means enterprises pay for both human agent access and AI resolution outcomes, rather than substituting one for the other. This is partly a function of Zendesk's positioning as a platform — they need seat revenue from the enterprise agreements that predated AI — and partly a function of the reality that most enterprises still need human agents for complex cases.
Intercom Fin is the most straightforward: $0.99 per resolution, resolution clearly defined, human agents included in the base plan. This clarity is a deliberate positioning decision. Intercom has committed more fully to AI-first support than Zendesk or Salesforce, and the simple price card reflects that commitment.
Why Seat-Based Pricing Cannot Survive AI Agents
The shift from seat-based to per-resolution pricing is not primarily a strategic choice by vendors — it is a structural inevitability. RSM's 2026 analysis of SaaS pricing models documents the underlying economics: seat-based pricing ties revenue to human headcount. AI agents reduce the human headcount needed to do a job. Vendors who price on seats are therefore pricing against their own value proposition.
The math is simple. A company with 100 human support agents at $80 per agent per month pays $8,000 per month for the SaaS platform. If they deploy an AI that handles 60% of their volume, they can reduce to 40 human agents. Their seat-based SaaS bill drops to $3,200 per month. The vendor's revenue fell by 60% precisely because the vendor's product worked.
This is what happened to several contact center SaaS vendors in 2025 and early 2026. They sold AI add-ons to their seat-based customers, the AI worked, the customers reduced headcount, and the vendor's seat revenue collapsed. The companies that recognized this dynamic early and restructured toward per-resolution billing preserved their revenue while delivering value. The ones that didn't face an uncomfortable conversation: "we bought your AI and now we don't need as many seats."
Per-resolution pricing solves this misalignment by decoupling revenue from headcount entirely. The vendor earns based on AI output. If the AI handles more tickets, the vendor earns more — even as the customer needs fewer human agents. The incentive structure is no longer in tension.
The Economic Case for Enterprise Buyers
For buyers, the per-resolution model is straightforward to evaluate against the status quo. The average cost of a human-handled support ticket varies by industry and complexity, but industry benchmarks consistently place it at $8 to $15 for straightforward inquiries and $25 to $50 for complex technical support. Against that baseline, a $0.99 to $2.00 per-resolution rate is a compelling offer — assuming the resolution rate is real.
The buyer evaluation framework has three components.
Resolution rate auditing. What percentage of inbound volume will the AI actually resolve, and how does that compare to vendor claims? The vendor number is typically generated on a curated data set. Buyers should run a 30-day pilot with full audit logging before committing to volume pricing. A vendor claiming 70% resolution rate on your ticket mix is a very different economic proposition from a vendor delivering 40%.
Cost-per-resolution vs. cost-per-ticket comparison. Build a simple model: current cost-per-ticket (fully loaded, including agent salary, tooling, management overhead) × number of tickets per month = current total cost. AI resolution rate × total ticket volume × per-resolution price = AI cost. Human-handled rate × remaining tickets × human cost = residual human cost. The sum tells you whether per-resolution pricing is actually cheaper than your current model.
Blend-and-switch risk. Buyers who move from pure seat-based to per-resolution models are betting that AI resolution rates stay high. If a product update changes the ticket mix toward more complex queries, or if the vendor changes their resolution definition to exclude a category previously included, the per-resolution cost can spike. Contracts should include resolution rate guarantees, category definitions, and notification requirements for any change in classification methodology.
The Economic Case (and Risk) for Vendors
For vendors, per-resolution pricing has attractive economics when it works and dangerous exposure when it doesn't. The 2026 guide to agentic pricing models notes that the model creates three specific vendor risks.
Inference cost volatility. The cost of running an LLM to resolve a support ticket is not fixed. It depends on the ticket's complexity (more reasoning steps = more tokens = higher cost), the current pricing of the underlying model API, and the length of the conversation required to reach resolution. A vendor selling at $0.99 per resolution can achieve 60-70% gross margins on simple tickets and negative margins on complex ones. Without careful routing — sending complex tickets to humans or lower-cost models — the per-resolution unit economics can deteriorate rapidly.
Definition inflation pressure. When vendors need to show high resolution rates to justify per-resolution pricing, there is an incentive to classify borderline cases as resolved. This is the same pressure that creates inflated customer satisfaction scores in human-run contact centers — agents learn to handle interactions in ways that score well on the metric, not necessarily in ways that solve problems. AI systems are no different: resolution rate is an optimizable metric, and optimizing it without corresponding customer satisfaction metrics can produce high-billing, low-value outcomes.
Customer concentration. Per-resolution billing with enterprise customers creates revenue concentration: a single large customer whose AI deployment is working well can represent a significant percentage of the vendor's per-resolution revenue. If that customer's inbound volume decreases — because their product got better, because they changed support workflows, because of seasonal variation — the vendor's revenue drops with it. Seat-based billing smooths this out. Per-resolution amplifies it.
What This Forces Product Managers to Build
The shift to per-resolution pricing is not primarily a finance story — it is a product story. Building a product that can charge per resolution requires specific product investments that most SaaS teams have not fully reckoned with.
1. Resolution detection infrastructure. You need a system that can accurately classify whether an interaction was successfully resolved. This requires intent analysis (what was the customer trying to accomplish), completion detection (did the response address the intent), and quality filtering (did the customer signal satisfaction or frustration). Without accurate classification, your billing is wrong and your contract disputes multiply.
2. Escalation routing. When the AI's confidence drops below a threshold that suggests resolution is unlikely, the handoff to a human agent must be clean, fast, and contextualized. A poorly designed escalation is a failed resolution and a customer experience failure simultaneously. The product needs confidence scoring, threshold management, and handoff protocols that preserve conversation context across channels.
3. Quality monitoring dashboards. Both vendors and buyers need dashboards that surface resolution quality signals beyond just the binary resolved/not-resolved classification: repeat contact rate (customers who reopened within 48 hours), CSAT correlation (resolution classification vs. satisfaction score), and category-level resolution rates. These dashboards are the audit infrastructure that makes per-resolution billing trustworthy.
4. Billing transparency portals. Enterprise buyers under per-resolution contracts need to see every billable event, its classification, and the reason for classification. This is a product requirement, not an accounting requirement. The billing portal is part of the product.
5. Gaming prevention. When buyers know they are charged per resolution, some will route only their easy tickets to the AI. This looks like high resolution rates but actually represents cherry-picking — the AI is handling 40% of volume but only the 40% that would have resolved quickly regardless. Vendors need usage analytics that can detect this pattern and have contract provisions that address it.
What the Market Looks Like in 2027
The enterprise AI infrastructure shift documented in recent coverage is accelerating the adoption of per-resolution pricing beyond customer service. Legal AI (Harvey, Legora) is experimenting with per-document and per-matter billing. Sales AI is exploring per-meeting-booked or per-qualified-opportunity models. HR automation is testing per-workflow-completed pricing.
The common thread is the same logic that drove per-resolution in support: when AI does discrete, measurable units of work, billing per unit of work aligns incentives between vendor and buyer far better than billing per seat of access.
Product managers building AI products in 2026 need to start with the question that per-resolution pricing forces: what is the discrete, measurable outcome my product delivers? If you cannot answer that question clearly enough to write a billing definition, you cannot charge outcome-based prices — and you probably also cannot articulate the value your product delivers to procurement teams in the post-chasm enterprise market.
The companies that answer that question clearly, build the product infrastructure to measure and verify outcomes at scale, and price accordingly are the ones that will escape the per-seat pricing trap. The ones that don't will face the same choice their predecessors in contact-center SaaS faced: watch their seat count shrink as their AI works, or rebuild their pricing model while the market is still forming.
Takeaway: Per-resolution pricing at $0.99–$2.00 per ticket is not an Intercom-specific pricing experiment. It is the product-market structure of enterprise AI support taking shape in real time. For buyers, the evaluation is straightforward: audit the resolution rate, model the cost comparison, and build definition protections into the contract. For vendors and product managers building AI products, the harder question is whether your product has a clearly defined outcome that can be priced the same way — and whether your product infrastructure can actually measure, classify, and bill for that outcome at enterprise scale. The shift from per-seat to per-resolution is already happening. The question is whether you are designing for it or reacting to it.
Frequently Asked Questions
What is per-resolution pricing for AI customer service agents?
Per-resolution pricing is a billing model where a company pays an AI vendor only when the AI agent successfully resolves a customer interaction end-to-end, without human handoff. Each resolved conversation triggers a fixed fee — typically $0.99 to $2.00 for enterprise support AI — while conversations that escalate to a human agent, fail to reach resolution, or are abandoned by the customer are not billed. The model emerged as a natural fit for AI-powered customer service because the business outcome — a resolved support ticket — is clearly defined, measurable, and attributable. Per-resolution pricing differs from the traditional per-seat model (a fixed monthly fee per support agent regardless of output) and from per-conversation or per-interaction pricing (which bills for every exchange, successful or not). The defining characteristic of per-resolution is that payment is contingent on outcome: the vendor only earns when the AI actually does the job. This aligns vendor incentives with customer success in a way that seat-based pricing structurally cannot, but it also creates new risks around resolution definition, gaming, and cost predictability for enterprise buyers.
How does Intercom Fin's $0.99 per-resolution model work in practice?
Intercom Fin, Intercom's AI-first support agent, publishes a rate of $0.99 per resolved conversation. A resolution is defined as a support interaction that ends without being escalated to a human Intercom agent and where the customer either explicitly closes the conversation or does not reopen it within a defined window (typically 24 hours). Intercom's definition deliberately excludes conversations where the customer writes back saying their issue was not solved — these route to human agents and are not billed as resolutions. In practice, this means enterprise buyers need to define 'resolution' clearly in their contract and verify that Intercom's automated classification of resolutions matches their internal quality standards. A conversation where a customer says 'thanks' and closes the chat without their actual problem being solved would typically still count as a resolution under an automated classification — which is a known loophole in per-resolution billing that buyers need to audit. For most enterprises, the practical experience is that per-resolution pricing reduces support costs significantly: a resolution at $0.99 is far cheaper than the $8-12 average cost per human-handled ticket, and the AI handles 40-60% of total volume at scale.
What is the difference between per-seat and per-resolution pricing for enterprise AI buyers?
Per-seat pricing charges a fixed monthly fee per human support agent who uses the software, regardless of how many tickets they handle or how effective the AI assistance is. Per-resolution pricing charges per successful AI-handled outcome, regardless of how many human agents are also using the platform. For enterprise buyers, the key differences are predictability, risk allocation, and alignment with value. Per-seat is highly predictable — you know your monthly cost based on headcount — but it decouples cost from value: you pay the same whether the AI resolves 10% or 70% of your inbound volume. Per-resolution creates a direct cost-to-outcome relationship: your bill scales with AI effectiveness. If the AI handles more tickets at lower cost than humans, you save money. If the AI resolution rate is low, your savings are minimal and you may still be paying for human seats on top. The risk allocation also shifts: under per-seat, the buyer bears the risk of low AI adoption; under per-resolution, the vendor bears more of the risk that the AI will actually perform. This alignment is why per-resolution has become the preferred model for enterprise buyers who have been burned by AI investments that underperformed.
What product design changes does per-resolution pricing require for SaaS product managers?
Per-resolution pricing forces product managers to redesign the product around outcome verification rather than engagement volume. Five specific changes become necessary. First, resolution detection logic: the product must be able to classify whether an interaction was successfully resolved, which requires intent detection, sentiment analysis on the closing message, and a reopening-window policy. Second, resolution quality monitoring: PM teams need dashboards that show the percentage of interactions classified as resolved but followed by a repeat contact within 48 hours — a key signal that resolution classification is inflated. Third, escalation path optimization: the product needs to route gracefully when confidence is below threshold, since a failed handoff under per-resolution billing is worse than a clean escalation (you lose the resolution fee and damage trust). Fourth, billing transparency: enterprise buyers need a billing portal that shows every interaction, its classification, and the reason for classification, so they can audit and dispute individual line items. Fifth, quality floors: building confidence-threshold gates that route to humans when the AI's likelihood of resolution drops below a set threshold — this protects the resolution rate that defines the vendor's revenue and the buyer's trust simultaneously.
What are the risks of outcome-based pricing for SaaS vendors in 2026?
Outcome-based pricing creates five structural risks for SaaS vendors. First, revenue unpredictability: if the vendor's AI performs below expectations for a month — due to a model update, a new product category the customer launched, or unusual inbound patterns — revenue drops in a way that seat-based billing never would. Second, gaming risk: customers may optimize their workflows to inflate the resolution metric (e.g., routing only simple cases to the AI) while handling complex cases with humans. This technically improves the vendor's resolution rate while reducing the genuine value the AI delivers. Third, definition disputes: resolution definitions are interpreted differently by vendors and buyers, leading to billing disputes that damage the relationship and consume customer success resources. Fourth, margin volatility: the cost of generating each resolution (compute, API calls, reasoning loops) can fluctuate significantly with model updates, while the contracted per-resolution price is fixed. Vendors can find themselves earning $0.99 per resolution while spending $1.20 in inference costs. Fifth, competitive pressure: once per-resolution pricing is established as the category norm, price competition moves to the unit cost, and the vendor who can achieve the lowest cost-per-resolution while maintaining quality wins. This creates a race-to-the-bottom dynamic that is harder to escape from than the stable margin structure of seat-based SaaS.