Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-05-04 · source-backed
Outcome-based pricing crossed from experimental to mainstream this quarter. The data is now unambiguous.
Zendesk charges $1.50 per automated resolution on committed plans, $2.00 pay-as-you-go. Intercom's Fin charges $0.99 per resolved conversation with no charge if unresolved. 43% of all SaaS companies now use hybrid pricing models, projected to hit 61% by end of 2026. Companies using hybrid models report 38% higher revenue growth and 38% higher net revenue retention.
Gartner projects 40%+ of enterprise SaaS spend shifts to usage/agent/outcome-based pricing by 2030. That's four years away.
The connection to agentic engineering is direct: if agents do the work, you charge per outcome, not per seat. A customer support agent that resolves tickets doesn't need a human "seat" to bill against. The entire per-seat model assumes humans use the software. When AI agents use the software, you need a different economic primitive.
The SaaS repricing is already brutal. JP Morgan called it the "largest non-recessionary software repricing in three decades." Wix dropped 66% in one year. Monday.com crashed 60% in six months. Calcalist's tech division reports that SaaS-only startups won't even get pitch meetings with VCs anymore.
Here's what caught me off guard: customer support hiring has fallen 65% in two years according to Pave data (386,500 new hires tracked). From 8.3% of all new hires in Q4 2023 to 2.88% in Q3 2025. SaaStr calls this the first category AI has "almost destroyed."
If you're building a SaaS product and still charging per seat, start planning your migration this quarter. Not next quarter. This quarter. The companies that moved early (Zendesk, Intercom) are capturing the growth. The companies that waited are getting repriced by the market.
Sources: SaaS Mag, SaaStr, SaaS Capital
Each link below shares sources, entities, or timing with this story.
SaaStr uses Replit / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Replit); both cover Intercom, Outcome, SaaS, SaaStr; reported by the same outlet (saastr.com).
SaaStr uses OpenAI / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (SaaStr uses OpenAI); both cover Monday, SaaS, SaaStr; reported by the same outlet (saastr.com).
Zendesk uses SaaS / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Zendesk uses SaaS); both cover Gartner, Intercom, SaaS, Zendesk; overlapping topics (agent, customer, human, model, pricing).
SaaStr uses Agentforce / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Agentforce); both cover Intercom, Outcome, SaaS, Zendesk; reported by the same outlet (saastr.com).
SaaStr uses Salesforce / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Salesforce); both cover Gartner, Intercom, Outcome, SaaS; overlapping topics (data, model, pricing).
Linked by a graph relationship (SaaStr uses Salesforce); both cover Intercom, Outcome, SaaS, Zendesk; overlapping topics (agent, human, model, pricing, seat).
Intercom uses SaaS / Shared entities / Same source / Shared topic / What happened next
Linked by a graph relationship (Intercom uses SaaS); both cover Intercom, SaaS, SaaStr; cite the same source ($1.50 per automated resolution).
SaaStr uses Agentforce / Shared entities / Same source domain / Shared topic / What happened next / Tension
Linked by a graph relationship (SaaStr uses Agentforce); both cover SaaS, Zendesk; reported by the same outlet (saastr.com).