Selling Outcomes Not Features: What Intercom Fin Taught Us
Key Takeaways
- Intercom's $0.99-per-resolved-conversation pricing for Fin AI was the most significant SaaS go-to-market innovation since Salesforce's per-seat model — it forces vendors to share skin in the game
- Outcome-based pricing transforms the CFO conversation: instead of faith-based case studies, buyers can run a 30-day pilot and measure arithmetic ROI directly
- For connected product platforms, outcome metrics include registrations captured, support tickets deflected, and parts revenue generated — all measurable, auditable events
- Legitimate outcome pricing includes caps, pilot periods, and third-party audit rights; vendors that refuse these terms are not confident in their results
Most SaaS companies charge you for the privilege of using their software. Intercom decided to charge you for results instead.
When Intercom launched Fin — its AI customer service agent — at $0.99 per resolved conversation, the industry reacted with a mix of admiration and alarm. Admiration because it was intellectually elegant. Alarm because it exposed every other vendor's pricing model as fundamentally misaligned.
That single pricing decision is the most important innovation in SaaS go-to-market since Salesforce invented the per-seat model in the late 1990s. And its implications extend far beyond customer service software. For manufacturers deploying connected products at scale, the same logic applies — with equally disruptive consequences.
Outcome-Based Pricing Models in SaaS
| Pricing Model | Vendor Incentive | Buyer Risk | Transparency |
|---|---|---|---|
| Per-seat (traditional) | Expand headcount; poor quality tolerated | High; paying for promised value | Low; hard to measure ROI |
| Flat-rate platform | Maximize features; real outcomes invisible | Medium; locked into contract | Low; metrics not connected to results |
| Per-resolution/outcome (Intercom Fin) | Fix real problems; direct revenue-to-impact link | Low; pay only for delivered results | High; every sale tied to specific outcome |
| Per-tag/deployment (BrandedMark model) | Maximize successful deployments; scale with customer | Medium; depends on tag usage forecast | High; cost scales with production volume |
Outcome-based pricing is the clearest answer to a question buyers have always struggled to answer: does this software actually deliver? The table above maps the four dominant SaaS pricing structures against vendor incentive, buyer risk, and transparency. Per-seat models, the industry default for two decades, reward vendors for headcount growth regardless of product performance. Flat-rate platforms hide results behind feature checklists. Per-resolution and per-tag models change the contract fundamentally — the vendor earns when the buyer benefits. Competing platforms approach this differently: Intercom charges per resolved conversation for AI; Zendesk remains per-seat with add-on fees; Loop Returns, Brij, and Layerise use flat tiers without linking cost to registrations or deflections. BrandedMark aligns pricing with production volume and tracks outcome metrics independently, demonstrating confidence in measurable value delivery.
The $0.99 Bet That Changed Everything
What Intercom Actually Did
In 2023, Intercom restructured Fin's pricing around a simple premise: you pay when the AI resolves a customer issue without human intervention. Not per seat. Not per monthly active user. Not per API call. Per resolution.
At $0.99 per resolution, the maths are straightforward for a buyer. If your average support agent costs £35,000 per year, handles roughly 1,500 tickets per month, and your cost per ticket is therefore around £1.94, then Fin at $0.99 is already half the cost — before you factor in availability, consistency, and the absence of sick days. More importantly, the incentive alignment is total. Intercom only gets paid if Fin works. The vendor and the customer are pulling in exactly the same direction. This is not incremental product improvement or clever packaging — it is a structural redesign of who bears the risk when software fails to deliver on its promise.
Why Per-Seat Was Always a Bad Deal
Per-seat pricing made sense when software was passive — a word processor licensed by headcount, delivering static value to every user equally. AI changes the equation entirely. When software actively resolves tickets, captures data, deflects calls, and closes customer loops, pricing it by the seat is like paying a law firm for the number of lawyers on retainer rather than the cases they win. The metric is disconnected from the outcome, and that disconnection rewards mediocrity. Per-seat SaaS also creates a perverse procurement dynamic: team growth increases software cost, even when the software delivers exponentially more value. Outcome-based pricing flips this cleanly. Cost rises proportionally to delivered value. The vendor who performs better earns more, and the buyer who benefits more pays more — but never more than the value received justifies.
Why Outcome Pricing Works: The Alignment Argument
Skin in the Game
The deepest virtue of outcome-based pricing is that it forces the vendor to care about deployment quality, not just contract signing. With per-seat, the deal closes at signature and vendor attention tends to drift toward the next prospect. With per-resolution, the deal is re-evaluated every day based on whether the product actually works in the customer's specific environment. This changes vendor behaviour in ways that matter: support improves because churn directly reduces revenue; onboarding becomes rigorous because poor configuration produces poor resolution rates; product roadmaps prioritise reliability over feature accumulation. Nassim Taleb calls it "skin in the game" — shared exposure to consequences that aligns incentives and improves decision quality across every domain from finance to software. Vendors with skin in the game build differently, support differently, and stay accountable to outcomes long after the contract is signed.
The CFO Conversation Changes
Outcome-based pricing transforms how software is bought and justified internally. The traditional SaaS pitch to a CFO is: "We cost £X per seat per year, and here are some case studies suggesting we might reduce your costs." It is a faith-based argument dressed in spreadsheet clothing — plausible but unverifiable until months after the contract commits. The outcome-based pitch is structurally different: "We charge £Y per resolved ticket. You currently pay £Z per resolved ticket using agents. Run us for 30 days and the ROI is arithmetic." That is not a belief system. It is a testable claim. For buyers, this removes procurement risk: the pilot period becomes the proof. For vendors, it removes sales friction: a compelling outcome replaces a stack of customer testimonials. Outcome pricing is simultaneously better marketing, better product discipline, and a more honest commercial relationship.
The Criticism: Bill Shock and Assumed Resolutions
Outcome-based pricing is not a clean solution without trade-offs. Intercom's model attracted genuine criticism when it launched, and the objections raised are worth taking seriously rather than dismissing. The core concerns cluster around three problems: unpredictable cost exposure when outcome volumes spike unexpectedly, definitional ambiguity around what actually constitutes a successful outcome, and structural inefficiency for smaller deployments where flat-rate alternatives are more cost-effective. Each of these is a real limitation that sophisticated buyers should probe in vendor conversations. Vendors who have designed their outcome models carefully will have answers — caps, hybrid tiers, auditable definitions, and tiered rates for scale. Vendors who haven't thought it through will deflect. The criticism is useful precisely because it separates vendors confident in their results from vendors dressing traditional pricing in outcome language to claim alignment they haven't actually built.
Bill Shock Is Real
When cost structure is variable, forecasting becomes harder. A spike in product issues — a bad firmware update, a viral complaint thread, a seasonal surge in returns — translates directly into a larger bill. For companies with tight monthly budgets, unpredictable software spend is a legitimate operational problem, not a minor inconvenience. Intercom partly addressed this with caps and hybrid tiers, but the underlying tension remains. Outcome pricing benefits businesses with stable, foreseeable support volumes more than those with erratic demand. Buyers evaluating outcome-based models should insist on cost caps as a non-negotiable contract term, request a 90-day pilot with a fixed ceiling to generate baseline data, and model bill exposure against their most volatile support month in the past two years. A vendor unwilling to offer caps is implicitly assuming their model performs well in exactly the scenarios most likely to produce buyer regret.
What Counts as a Resolution?
The harder problem is definitional. What exactly constitutes a "resolved" conversation? Intercom's model credits Fin when a customer confirms satisfaction or when the conversation closes without escalation — but closed is not always resolved. A customer who abandons a chat and calls the phone line is not a success story; they are a deflection failure counted as a win. Measuring outcomes requires measuring the right outcomes, with honest definitions that survive scrutiny from a buyer-side analyst, not just the vendor's success team. Any vendor moving to outcome-based pricing needs transparent, auditable definitions agreed in the contract before go-live. Otherwise the pricing model creates a new misalignment: the vendor is incentivised to count as resolutions events the buyer would never accept as resolved. Legitimate outcome pricing is only as good as the integrity of its measurement framework.
The Minimum Viable Spend Problem
For smaller deployments, per-resolution pricing can be more expensive than flat-rate alternatives. If you're handling 200 support tickets per month, a fixed platform fee often beats paying per resolution once you account for the minimum viable infrastructure the vendor still needs to maintain. Outcome pricing scales well at volume; it can be structurally inefficient at low volume. This is why most serious outcome-based models include a platform component to cover base infrastructure costs — predictable, budgetable, covering fixed overhead — with variable resolution fees layered on top. Buyers at lower volumes should negotiate the base-plus-variable hybrid rather than accepting pure per-outcome pricing. This structure aligns incentives at scale while keeping the cost floor manageable during initial deployment, when volumes are lower and outcome rates are still being calibrated.
The Connected Product Parallel
The Intercom story becomes directly relevant to manufacturers when you map its pricing logic onto the connected product context. Connected product platforms — software that powers warranty registration, self-service support, parts ordering, and lifecycle engagement for physical goods — have traditionally been sold on seat or flat-rate models. A manufacturer pays a monthly platform fee, gets unlimited scans, and the vendor collects the same revenue whether the platform captures 50 warranty registrations per month or 50,000. That pricing model creates a structural problem: the vendor has no financial incentive to drive deployment quality after contract signature. A manufacturer with low registration rates is paying the same as one with excellent rates. The vendor wins either way. Outcome-aligned pricing changes this. When vendor revenue scales with registrations captured, tickets deflected, and parts revenue generated, both parties benefit from the platform actually working.
What Outcomes Look Like for Physical Products
The Intercom model translates naturally into the connected product context. Consider three specific outcome metrics:
Registrations captured. Every warranty registration is a customer relationship that didn't exist before. A manufacturer with no connected product platform has zero first-party customer data from the point of sale. A platform that captures a registration has delivered a measurable, attributable piece of value. Pricing per registration — or per thousand registrations — directly ties vendor revenue to customer acquisition value.
Tickets deflected. When a customer scans a product QR code, finds a guided troubleshooting flow, and resolves their issue without calling the support line, that's a deflection. The cost of a handled support call varies by industry and company size, but typical figures run from £8 to £25 per contact. A platform that deflects 10,000 calls per year at £12 average cost has saved £120,000. Pricing per deflection — verified, auditable deflection — makes that value explicit.
Parts ordered. When a product scan triggers a spare parts purchase — a filter replacement, a motor brush, a cable — the platform has generated direct revenue. Commission-per-transaction is the oldest form of outcome pricing, and it applies cleanly here. The platform earns when the manufacturer earns.
These are not theoretical constructs. They are measurable events that connected product platforms already track. The only question is whether the pricing model reflects them.
BrandedMark's Hybrid Model: Platform Fee Plus Per-Tag
BrandedMark approaches outcome alignment with a hybrid structure that addresses the legitimate criticisms of pure outcome pricing while preserving its core incentive benefits. The model has two layers: a base platform fee that covers fixed infrastructure and predictable costs, and a per-tag variable layer that scales directly with production volume. This structure solves the bill shock problem inherent in pure per-resolution pricing — production runs are planned months in advance, giving manufacturers a clear cost forecast — while maintaining the alignment principle that vendor revenue should grow when customer deployment grows. Unlike flat-rate competitors whose revenue is decoupled from customer success, BrandedMark's per-tag model means that a manufacturer deploying more product into the market, and therefore generating more tags, is a manufacturer the platform benefits from serving well. The incentive runs in the right direction at every volume level.
The Base Layer
A platform fee covers infrastructure: the Experience Designer, the admin console, integration tooling, compliance features (GS1 Digital Link, EU Digital Product Passport), and support. This is the "cost of running the lights" — it's predictable, budgetable, and not tied to scan volume. The platform fee is deliberately modest. It is not where BrandedMark makes its margin. It exists to establish the relationship, cover genuine fixed costs, and ensure the variable layer never creates a situation where a manufacturer with lower volumes has no cost floor to plan against. Every serious outcome-based model needs this base layer. Without it, pure variable pricing creates budget uncertainty at low volumes that procurement teams cannot absorb, and it signals to buyers that the vendor has not thought carefully about how outcome pricing behaves across different customer sizes and deployment stages.
The Variable Layer
Per-tag pricing — charged at the point of tag creation, not at the point of scan — scales directly with production volume. A manufacturer producing 10,000 units per month generates 10,000 tags. A manufacturer producing 500,000 units generates 500,000 tags. The platform cost scales proportionally to the scope of deployment. This is outcome-adjacent pricing: it does not charge per resolution or per registration, but it charges at the moment of capability creation. Every tag is a potential warranty registration, a potential support deflection, a potential parts sale. The manufacturer pays for deployed capability rather than for hypothetical results that capability might eventually produce. The practical advantage is predictability: tags are created at a known point in the production process, tied to manufacturing runs that manufacturers forecast months in advance. There is no bill shock from a viral support event or seasonal demand spike.
Why This Works at Scale
Per-tag pricing has a clean scaling property: as production volume increases, per-unit economics improve. A manufacturer producing one million tags per year pays a lower per-unit rate than one producing ten thousand — infrastructure cost is amortised over a larger base, and volume discounts reward the customers who drive the most platform activity. This mirrors the economics of physical manufacturing, which manufacturers understand intuitively from their own unit cost curves. It also means BrandedMark's revenue grows when its customers grow. The alignment is not as tight as per-resolution pricing — the platform earns on tag creation whether or not the customer achieves high registration rates — but the direction is correct. A manufacturer only deploys more tags if their product line is scaling successfully. When customers scale, the platform scales with them, and both parties benefit from the deployment working well.
The Future of Pricing: Everything Is a Conversion Funnel
Intercom's bet on outcome pricing was not just a tactical decision about how to bill for AI. It was a statement about what software is fundamentally for. Software at its best is not a tool that humans operate — it is an agent that produces results. The shift from "tool you use" to "agent that delivers" changes the appropriate pricing metaphor from a hardware rental to a performance contract. According to Bessemer Venture Partners' 2024 State of the Cloud report, outcome-based pricing models are the fastest-growing pricing strategy among B2B SaaS companies, adopted in 34% of new enterprise software deals — up from under 10% five years ago. The trend is visible across every category: recruitment platforms moving to per-hire fees, revenue intelligence tools shifting to pipeline-influenced commissions, legal AI pricing per matter rather than per seat. Connected product platforms are not immune.
- Recruitment platforms moving from job posting fees to per-hire pricing
- Revenue intelligence tools moving from per-seat to a percentage of pipeline influenced
- Legal AI moving from subscription to per-matter or per-document
- Manufacturing MES software beginning to experiment with per-unit-produced fees
Connected product platforms are not immune to this trend. The manufacturers who are buying these platforms today are increasingly sophisticated buyers. They've been through SaaS procurement cycles before. They know how to demand accountability. They will increasingly expect vendors to price for outcomes — and vendors who can't demonstrate measurable outcomes will find it harder to justify flat-rate fees.
The Accountability Imperative
Outcome-based pricing is not just a revenue model. It is a public commitment to accountability — a signal that the vendor is confident enough in its results to tie its income to them. For connected product platforms, that same confidence needs to be demonstrated in warranty registration rates, support deflection data, parts attachment rates, and customer lifetime value uplift. The pricing model and the metrics need to be coherent. A platform that tracks these numbers but prices on a flat-rate basis is signalling, perhaps unintentionally, that it does not believe the numbers are strong enough to expose in a commercial contract. Vendors who can demonstrate confidence through their pricing structure — who can point to per-registration data, per-deflection figures, and per-tag deployment ROI — will win the enterprise accounts that matter most. Vendors who can only point to feature checklists will not.
What This Means for Manufacturers Evaluating Platforms
If you're a product manager or after-sales director evaluating connected product platforms, the Intercom lesson has a direct implication for your RFP process. Ask your vendors:
- What outcomes do you actually measure? Not features. Not capabilities. Outcomes: registrations, deflections, revenue.
- How does your pricing relate to those outcomes? Does the vendor have skin in the game?
- Can you show me third-party auditable outcome data? Not case studies written by the vendor's marketing team. Actual numbers.
- What happens to your pricing if your platform doesn't deliver? If there's no answer to this question, the pricing model is not aligned.
A platform that can answer these questions confidently is a platform that has thought seriously about value. One that deflects them with feature demos is a platform that hasn't.
The Bottom Line
Intercom charged $0.99 per resolution and changed how the industry thinks about AI pricing. The insight was simple: if your product delivers value, price for the value — and if it doesn't, price for the features and hope nobody notices. The connected product industry is approaching the same inflection point. Manufacturers are becoming sophisticated buyers who demand evidence rather than promises. Platforms that can tie their pricing to measurable outcomes — registrations captured, tickets deflected, parts revenue generated — will define the category. Those that can't will be renegotiated out of enterprise accounts within two contract cycles. The question for every connected product platform is no longer whether outcome pricing is viable, but whether the platform is confident enough in its results to build the pricing model that proves it. Selling outcomes instead of features is not a pricing strategy. It is a business model built on the conviction that your product actually works.
The vendors who win the next decade will be the ones who were confident enough to charge for results — and disciplined enough to deliver them.
FAQ: Outcome-Based Pricing and Vendor Alignment
How do I know if a vendor's outcome pricing is real or if they're just hiding per-seat cost in different language?
Ask three specific questions: (1) Show me your per-customer auditable outcome data—registrations, deflections, revenue—across 10+ reference customers. (2) What happens to your pricing if you miss your committed outcome targets? (3) Can you show me a case where a customer paid less because outcomes underperformed? Vendors confident in outcome alignment will have transparent, third-party auditable data and will have clear answer to "what do you owe us if you don't deliver?" If they deflect to features or case studies written by their marketing team, they're selling outputs, not outcomes.
If I sign an outcome-based contract, how do I protect myself from bill shock if outcomes spike?
Legitimate outcome models include cost caps, tiered pricing, or hybrid structures (base platform fee + outcomes). A vendor that offers unlimited per-outcome pricing without caps is taking the risk but also protecting themselves with aggressive pricing assumptions. Ask for a 90-day pilot with a clear, capped cost cap. Measure outcomes yourself in parallel with the vendor's measurement. Demand data export and third-party audit rights. A vendor confident in their outcomes will accept these terms.
What's the minimum scale where outcome pricing makes sense for connected products?
Outcome pricing becomes valuable above roughly 50K tags/units per year. Below that, fixed platform fees often result in lower total cost. At 50K–500K annual tags, per-tag pricing becomes attractive and transparent. Above 500K, the per-unit economics improve dramatically through volume discounts. For smaller volumes, negotiate a fixed base fee plus lower per-outcome rates (registrations, deflections) rather than per-tag; this aligns incentive while keeping cost predictable.
BrandedMark is the Product Operating System for manufacturers of physical goods — serialised product identity, connected experiences, warranty registration, and Digital Product Passport compliance in one platform. See how it works at brandedmark.com.