The Number That Changes Your Renewal Math
Salesforce just posted some of the most concrete AI adoption metrics available from any enterprise vendor: 3.8 billion Agentic Work Units delivered, up 111% quarter-over-quarter, and 28.6 trillion tokens processed, up 152% QoQ. Slack AI alone grew 347% QoQ.
Those numbers aren't marketing. They're the signal that agent usage inside Salesforce is compounding — not plateauing — and that the pricing model underneath it has already shifted. Salesforce charges per AWU (Agentic Work Unit), not per seat. That distinction is going to matter on your next invoice in a way most operators haven't modeled yet.
Seat-Count Thinking Is the Wrong Frame Now
For the last decade, Salesforce costs were legible: headcount times license tier. You could forecast it in a spreadsheet. The move to consumption-based pricing breaks that model entirely.
Here's the trap: you reduce human seats as agents absorb repetitive tasks, you feel like you're saving money, and then AWU volume scales faster than you anticipated — because agents don't work 9-to-5 and they don't take PTO. The cost center shifts from HR headcount to compute and task volume. Finance isn't used to modeling it that way, and most RevOps leaders aren't either.
This isn't hypothetical. The 111% QoQ AWU growth tells you the task volume is real and accelerating. If your Salesforce footprint includes Agentforce or Slack AI today, you need a consumption estimate before your next QBR, not after.
What to Actually Do This Quarter
Three concrete moves:
Audit your current AWU exposure. Pull your Agentforce and Slack AI usage reports now. If you don't know where to find them, that's the first problem. Your AE knows — ask directly.
Model two scenarios for renewal. One where agent task volume stays flat (it won't), and one where it compounds at even half the rate Salesforce is seeing across its base. The delta between those scenarios is your budget risk.
Prioritize workflows by AWU efficiency, not just business impact. Not all agent tasks consume AWUs equally. Before you expand agent coverage, understand which workflows are cost-efficient at scale and which ones will eat your budget quietly.
The operators who win here aren't the ones who adopt Agentforce fastest. They're the ones who instrument it early enough to understand what they're actually spending — and make deliberate bets about where agent volume is worth the cost.