Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-05-14 · source-backed
HubSpot moved to $0.50 per resolved conversation on April 14. Then Salesforce launched Flex Credits at $0.10 per action. Then Zendesk hit $1.50 per automated resolution. Three different categories. CRM, platform, support. All converging on pay-per-result within a single month.
This isn't experimentation anymore. When three companies that collectively serve millions of enterprise seats independently arrive at the same pricing model in 30 days, that's a market signal you can't ignore.
Salesforce actually went further than the other two. They're running three pricing models simultaneously: per-conversation, per-action, and per-seat. SaaStr argues this is the smartest move they've made, because the market hasn't converged on how customers want to buy agent work. Let them self-select. Result: 5,000 Agentforce deals in two quarters.
Bessemer's data shows hybrid pricing already at 41% adoption across the SaaS market. Combined with Blossom Street Ventures' analysis of 40 SaaS earnings calls this quarter, the picture is clear: AI-native SaaS products with outcome-based pricing are growing fast but retaining poorly (median 40% gross retention, 23% for sub-$50 products), while incumbents with proprietary data and enterprise lock-in are thriving by adding AI pricing on top of existing relationships.
For builders, the takeaway is straightforward. If you're launching any AI-powered product, design metered outcome pricing from day one. Don't retrofit it later. The per-seat model made sense when software was a tool humans operated. When agents do the work autonomously, customers will only pay for results. The three companies that just proved this serve a combined customer base larger than most countries' populations.
The pricing model IS the product strategy now.
Each link below shares sources, entities, or timing with this story.
SaaStr uses Agentforce / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (SaaStr uses Agentforce); both cover Agentforce, CRM, SaaS, SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Agentforce / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Agentforce); both cover Agentforce, Flex Credits, SaaS, SaaStr; reported by the same outlet (markets.financialcontent.com, saastr.com).
SaaStr uses Agentforce / Shared entities / Same source / Shared topic / What happened next / Tension
Linked by a graph relationship (SaaStr uses Agentforce); both cover Agentforce, Flex Credits, HubSpot, SaaS; cite the same source (Flex Credits at $0.10 per action).
SaaStr uses Salesforce / Shared entities / Shared topic / What happened next
Linked by a graph relationship (SaaStr uses Salesforce); both cover April, CRM, Days, SaaS; overlapping topics (agent, company, enterprise, incumbent, month).
SaaStr uses Monaco / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Monaco); both cover CRM, HubSpot, SaaS, SaaStr; reported by the same outlet (markets.financialcontent.com, saastr.com).
SaaStr uses Agentforce / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Agentforce); both cover Agentforce, April, CRM, HubSpot; reported by the same outlet (saastr.com).
Linked by a graph relationship (SaaStr uses Agentforce); both cover Agentforce, CRM, SaaS, SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Monaco / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (SaaStr uses Monaco); both cover CRM, HubSpot, SaaStr, Salesforce; reported by the same outlet (saastr.com).