Salesforce: the pricing arc

The SPP read

Salesforce is describing outcomes in the general sense, but bills for action related items that aren’t necessarily tied to client outcomes. Many vendors are jumping on the marketing bandwagon and charging for “outcomes.” But a resolved call and an updated customer record are two very different types of outcomes. One is a step in a workflow, the other is a business outcome.

The SPP read

The low end flipped to bundled-free while the top end went metered: Agentforce built into the entry Suites at no added cost, while enterprise editions carry credit meters and flat-fee agreements above them. Free at the bottom of a ladder is an acquisition instrument; the meter waits upstream.

The SPP read

Three purchase models for one product, available simultaneously with no forced migration: a consumption pool, per-profile SKUs, and the shared Flex Credit pool. Three meters for one product means the buyer, not the vendor, picks which unit the bill is denominated in.

The SPP read

The first modality-differentiated action rate to take effect: the same agent action costs fifty percent more when it is spoken. Cost-based rate differentiation inside a value-denominated currency tells you which way the meter is actually indexed.

The SPP read

The flat-fee agreement is the escape hatch from their own consumption model: when per-conversation and per-action pricing stalls enterprise commitment, a ceiling-priced multi-year restores it. The shared-risk framing does not answer the metering objection; it moves where the risk sits.

The SPP read

For the installed base the renewal-transition date is the real effective date. AI moved from a paid add-on into the higher editions, the standalone add-on was retired from sale, and the edition price rose twenty percent: a feature-level meter absorbed back into the edition, and the edition repriced for it.

The SPP read

A list action carrying an AI story, and the AI story is the one that matters. Six percent landed on the premium editions with AI named as the justification. Alongside it, a $125 per-user Agentforce add-on with UNMETERED employee agent usage, sold next to the per-action credit meter running elsewhere in the same catalog. Unmetered per-user agents beside per-action credits is a pricing surface admitting the metric question is not settled. The word doing the work is unmetered, and it is narrower than it sounds: the grant covers employee-facing workflows, and it is governed by fair use rather than by a meter: standard governor limits, API thresholds and platform performance guardrails still bound it. Unmetered here names a boundedness decision, not the absence of one. A seat price only holds when something bounds what the seat can consume, and here the bound moved from a counter the buyer can see to a policy the vendor administers.

The SPP read

Eight months after putting a price on the conversation, Salesforce put a price back on the seat. The Digital Labor add-ons and the Agentforce 1 edition introduce no new unit: they are per-user wrappers sold around the same meter, priced for buyers who could not underwrite a variable bill. The meter did not go away when the wrapper arrived. It moved behind a number the buyer could put in a budget.

The SPP read

Seven months after pricing the conversation, the meter moved down a level: actions at a dime, denominated in credits sold in hundred-thousand blocks, with licenses convertible into credits on demand. A finer unit gives the vendor pricing precision and gives the buyer a forecasting problem; the conversion bridge keeps both instruments live, licenses and credits, with a rate between them.

The SPP read

The arc opens with a price on conversation itself: agentic AI at $2 per conversation at general availability, volume discounts standard. A conversation is a surrogate for work the buyer cannot forecast, and every later Salesforce move on this ledger renegotiates what the meter counts: a conversation, an action, a credit, a resolution. The unit kept changing; what a customer is paying for never settled.