06-reference/research

agentforce flex credits consumption pricing

2026-06-17·research-brief·source: deep-research
agentforceconsumption-pricingflex-creditsnet-revenue-retentionsaas-death

Agentforce Flex Credits: The Per-Action Meter and What Seat-to-Consumption Does to NRR

The question

What exactly are Salesforce Agentforce "Flex Credits," how do per-conversation vs per-action vs token pricing tiers compare, and what does the seat-to-consumption transition do to Salesforce's net revenue retention math? Context: the Agentforce strategy brief (2026-06-14) flagged this as its #1 open follow-up — we had ~$540M ARR at 330% YoY and expansion-led bookings but zero depth on the actual pricing mechanics.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The mechanics resolve cleanly into a hierarchy, which matters for how sharply Ben can render the thesis. There are two mutually-exclusive consumption meters per org — the legacy $2/conversation flat rate and the current $0.10/action rate — and tokens are a multiplier inside the action meter (one action = 10K tokens; spill over and you're billed in additional action-units). Seats did not die; they were repackaged as credit-bundled licenses ($125–$550+/user/mo, the higher tier pre-loading 1M credits). So the honest picture is not "seats → consumption" as a clean swap. It is a seat floor with a consumption meter bolted on top — exactly Nadella's "subscription = entitlement to a consumption rate" ([[2026-06-04-stratechery-satya-nadella-microsoft-core-competencies]]). The move from $2-flat to $0.10-per-action is itself the tell-within-the-tell: Salesforce cut the headline price ~95% on simple interactions to drive adoption volume, betting that metered expansion on complex multi-action workloads more than recovers the per-unit cut. That is a classic consumption-economics wager — trade margin-per-event for event-volume — and it only pencils if usage compounds.

For NRR math, this is the crux of the "SaaS premium dies, workload lives" thesis rendered financially, and it cuts both ways in a way the founder should hold precisely. Seat-based NRR is mechanically sticky and predictable: contracted seats renew, expansion is a sales motion, and >100% NRR is the engine of the SaaS premium multiple. Consumption NRR is elastic and reflexive: it rises automatically when customers use the product more, but it can also fall without a churn event — a customer who simply runs fewer agent actions next quarter shrinks net revenue with no cancellation, no logo loss, nothing for a CRO to "save." That is the volatility analysts fear, and it is structurally why a usage business trades at a lower multiple than a seat business even at the same growth rate: the revenue is real but less forecastable, less contracted, more spot-priced. The seat-to-consumption transition doesn't just change the price — it re-rates the durability of the revenue, and the multiple compresses to match. The $540M-at-330% number looks like a seat-business growth rate, but it is run-rate-annualized consumption that can de-annualize as fast as it annualized ([[2026-06-04-mostly-metrics-consumption-based-arr]]).

That is precisely "the premium dies, the workload lives" on the income statement, and the Flex Credit gives Ben the unit to make it concrete and non-derivative. The premium multiple was the capitalized value of seat-revenue stickiness — you paid a premium because humans logging in was a contract you could underwrite. Re-pricing the same customer relationship as $0.10-per-action consumption keeps the workload (the CRM is still the system of record, the agent still runs on Salesforce data and permissions) while explicitly trading the premium (sticky contracted seats) for an elastic meter (spot-priced actions). The workload survives and even grows; the multiple that rewarded the old revenue shape does not. The Sanity Check angle sharpens to: watch the Flex Credit, not the ARR headline — the $0.10 action is the price of the workload, and the gap between that price and the old per-seat premium is the SaaS multiple being demolished one action at a time. RDCO's own positioning lands in the durable layer ([[2026-06-14-salesforce-agentforce-strategy]]): someone still has to wire the data, exceptions, and regulated last-20% so those actions fire correctly — that is FDE/data-platform work, priced like a workload, not app-config work priced like a seat.

Open follow-ups

Related

Sources