Six enterprise incumbents now run their own "agent meter," and Salesforce is booking $800M a quarter from it

Per-seat pricing is breaking everywhere at once. Not in one vertical, not as an experiment. Across CRM, ITSM, HR, and support simultaneously.

Salesforce booked roughly $800M in agent revenue last quarter, up from $540M the quarter before. That's not a pilot line item. ServiceNow, Workday, Zendesk, HubSpot, and Atlassian have each bolted a usage or outcome meter beside their per-seat pricing, under their own brand. Gartner forecasts 40% of enterprise SaaS spend will be usage, agent, or outcome-based by 2030. When six incumbents make the same monetization move in the same window, the per-seat assumption that built SaaS is the thing actually breaking.

The reason is simple and a little uncomfortable. A seat assumes a human clicking. Agents don't click, they consume. Billing a seat for a process that runs 1,000 transactions overnight either undercharges wildly or makes no sense. So the meter moves to what's actually consumed.

Deloitte frames the open question precisely: does an agent count as a seat? Four models are competing to answer it. Usage-based (compute, API calls). Outcome-based (leads, resolved tickets). Credit pools. And hybrid base-plus-surcharge. Nobody's won. The category hasn't converged.

That's the part builders need to internalize. This connects straight to the Copilot story and the Visa/Mastercard rails. Metered consumption is the model, settlement rails are getting built, and the pricing primitive is genuinely up for grabs. On the other side, indie hackers are running the play in reverse, gutting their SaaS stacks with agent swarms. One founder built five agents and cancelled $1,003/month in subscriptions. A 2026 solo stack runs $85 to $200/month against the $5K/month a small team paid in 2019.

What to do: if you're setting pricing right now, choose your meter deliberately, because these choices are hard to reverse at renewal. Outcome-based sounds great until you're on the hook for defining and attributing the outcome. Usage-based is honest but punishes your power users, the people who love you most. Credit pools hide the meter, which customers either appreciate or resent. I lean toward hybrid for most products: a predictable base so buyers can budget, a usage component so heavy agent workloads pay their way. Whatever you pick, instrument attribution from day one. You can't bill for what you can't measure, and retrofitting metering onto a live product is brutal.