Fetching from the wire…
Top 5 · 2026-04-07 · source-backed
Here's the paradox nobody in SaaS wants to talk about. Salesforce deployed its own Agentforce across customer support. 380,000+ interactions. 84% fully resolved without a human. Only 2% escalated. By any product metric, that's a success.
The stock dropped 26%.
Investors see the math clearly. The better Agentforce gets, the fewer Service Cloud seats customers need. A tool that replaces 84% of support interactions doesn't sell more seats. It eliminates them. Salesforce is eating its own revenue with its own product.
Their answer is the Agentic Work Unit (AWU), a new pricing metric where one AWU equals one discrete task accomplished by an AI agent: a processed prompt, a completed reasoning chain, or an invoked tool. Salesforce processed 2.4 billion AWUs total through Q4, with 771 million in Q4 alone. Agentforce reached $800 million in revenue. CIO magazine called AWU "a shiny new metric that tells CIOs little of value."
I think the CIO criticism is right. An AWU measures activity, not outcomes. A support agent that loops through five reasoning chains to answer a simple question generates 5 AWUs. A support agent that resolves it in one generates 1 AWU. The incentive structure rewards verbosity, not efficiency.
But the bigger story isn't Salesforce's pricing problem. It's the pattern. Every SaaS company building AI agents will hit this same wall. Your agent gets good enough to replace the humans using your per-seat product. Your product succeeds and your revenue model fails simultaneously. I don't think anyone has a clean answer yet.
What builders should do: if you're building SaaS, start designing your pricing model around outcomes or consumption now, not seats. If you're buying SaaS, pay attention to which vendors are still charging per-seat while shipping agents that reduce the number of seats you need. That gap is where leverage lives.
Each link below shares sources, entities, or timing with this story.
Salesforce acquired Intercom / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Salesforce acquired Intercom); both cover Agentforce, AWU, AWUs, CIO; cite the same source (CIO magazine called AWU).
Salesforce competes with HubSpot / Shared entities / Shared topic / What happened next / Tension
Linked by a graph relationship (Salesforce competes with HubSpot); both cover Agentforce, SaaS, Salesforce; overlapping topics (agent, agentforce, customer, model, pricing).
Salesforce released AWU / Shared entities / Shared topic / Earlier coverage
Linked by a graph relationship (Salesforce released AWU); both cover Agentforce, AWU, AWUs, SaaS; overlapping topics (awus, pricing, product, salesforce).
Agentforce built by Salesforce / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Agentforce built by Salesforce); both cover Agentforce, SaaS, Salesforce; overlapping topics (agent, agentforce, model, pricing, product).
SaaStr uses Salesforce / Shared entities / Shared topic / What happened next
Linked by a graph relationship (SaaStr uses Salesforce); both cover Agentforce, SaaS, Salesforce; overlapping topics (agent, agentforce, customer, model, pricing).
Salesforce competes with HubSpot / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Salesforce competes with HubSpot); both cover Agentforce, SaaS, Salesforce; overlapping topics (agent, customer, model, pricing, product).
SaaStr uses Salesforce / Shared entities / Shared topic / What happened next
Linked by a graph relationship (SaaStr uses Salesforce); both cover Agentforce, SaaS, Salesforce; overlapping topics (agent, model, pricing, product, saas).
Agentforce built by Salesforce / Shared entities / Shared topic / What happened next
Linked by a graph relationship (Agentforce built by Salesforce); both cover Agentforce, SaaS, Salesforce; overlapping topics (agentforce, answer, revenue, salesforce, seat).