Agentforce licenses a usage entitlement, not a seat. Action types, the conversation meter, the Einstein 1 bundle, and the Data Cloud overlay all move the cost. This guide maps the model and the clauses that protect the run rate.
Agentforce licenses a usage entitlement, metered by conversation, with Data Cloud behind it. This guide maps what the license includes, how action types and the meter work, how the Einstein 1 bundle changes the math, and the clauses that protect the run rate.
Agentforce changes how Salesforce licensing works. The platform you know prices per user. Agentforce prices the work the agent does, so the licensing conversation moves from named users to metered consumption.
That has two consequences. You license an entitlement to run agents, and you separately commit to a consumption volume. Confusing the two is the most common and most expensive error.
An Agentforce license is an entitlement to run agents, plus a metered consumption allowance.
The license covers the agent runtime and the topics and actions you build. Salesforce documents the model on its Agentforce product page. The build is yours, the runtime is licensed.
Consumption is metered by conversation, and Salesforce publishes the rate on its Agentforce pricing page. The allowance you commit to is the volume number in your order, and overage bills at a rate you should fix in advance.
Grounded agents need Data Cloud, which carries its own license and credit meter. The Agentforce entitlement does not include Data Cloud consumption.
Actions are the unit of work. The conversation is the unit of billing. The two are not the same.
A single conversation can chain several actions. The conversation count stays at one, but the data and model consumption rise with each action. Heavy action chains are where the cost to serve grows.
The Einstein 1 edition bundles platform, data, and AI entitlements. Whether it lowers or raises your Agentforce cost depends on what else you need.
Agentforce buying paths compared
| Path | Best when | Cost risk | Buyer move |
|---|---|---|---|
| Agentforce add on | Existing edition fits | Data Cloud overlay | Right size the credit pool |
| Einstein 1 bundle | You need platform and data too | Paying for unused parts | Map use of every component |
| Flex Credits pool | Volume is uncertain | Pool expiry shelfware | Negotiate rollover |
| Committed volume | Volume is high and steady | Over forecast lock in | Commit conservative, Flex the upside |
The bundle wins when you genuinely need the platform and data entitlements it carries. Then the marginal cost of reaching Agentforce is low.
The bundle loses when you buy it only to reach Agentforce and leave the rest idle. That is paying for shelfware to unlock one feature.
The common advice is to standardize on the Einstein 1 bundle because it future proofs the estate and simplifies the order. We disagree. In about half the deals we advised on, the bundle was bought purely to reach Agentforce, and the platform and data entitlements it carried sat unused while the buyer still paid for them.
The buyer side move is to license the edition on what the business actually uses, then add Agentforce as a metered line with its own forecast. Simplicity on the order form is not the same as value, and a tidy bundle can hide real shelfware.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
License the edition on what the business uses. Commit the conversation volume on what a pilot proves. Keep the two decisions apart and the bill stops drifting.
Four clauses decide whether the run rate you modeled is the run rate you pay.
Cap the rate uplift across the term. Without it, the conversation rate can rise each year and erase the discount you negotiated up front.
Secure the right to reduce the committed volume at renewal. An over forecast should not become a permanent floor.
Fix the overage rate in advance. Unpriced overage is where consumption growth turns into an open ended bill.
Lock the Data Cloud credit rate for the term. The overlay grows with grounded volume, so an unlocked credit rate compounds the exposure.
Three moves carry most of the leverage.
Bring a measured pilot to the table. A defensible volume number is the strongest counter to the vendor consumption model.
Negotiate Agentforce inside the wider Salesforce renewal where the account team values the upside and will trade rate and clauses to land it.
An Agentforce license includes the agent runtime, the topics and actions you configure, and a consumption allowance metered by conversation. Grounding data is supplied through Data Cloud, which is licensed and metered separately. The license is a usage entitlement, not a per seat right.
Agentforce is priced per conversation, not per seat. The standard rate is near two dollars per conversation. This breaks from the per user model that governs Sales Cloud and Service Cloud, so it needs a usage forecast rather than a headcount count.
Action types are the units of work an agent performs inside a conversation, such as answering from knowledge, retrieving a record, or writing back an update. A single conversation can chain several actions. Heavier action chains consume more data and model time even though the conversation count stays at one.
The Einstein 1 bundle folds platform, data, and AI entitlements into one edition, which can lower the effective Agentforce cost when you already need the other components. It raises cost when you buy the bundle only to reach Agentforce and leave the rest unused.
Yes. Data Cloud is licensed and metered on its own credit model, and grounded agents draw on it. Treat the Data Cloud entitlement as part of the Agentforce licensing decision, because the agent cannot ground answers without it.
The clauses that matter are a mid term uplift cap, a true down right at renewal, an overage rate fixed in advance, and a credit rate locked for the term. Without them, consumption growth and uncapped overage can move the bill faster than the platform line.
Rollover is not standard and must be negotiated. Prepaid pools that expire at period end create shelfware risk if your forecast is high. Push for rollover or a true down so an over forecast does not become sunk cost.
Base the forecast on a measured pilot, not on the vendor model. Take the resolved conversation volume per topic from the pilot, project it to steady state, and add a contingency band. Commit to the conservative number and use Flex Credits for the upside.
Separate the entitlement from the consumption before you negotiate. Most buyers conflate the edition they need with the conversation volume they will use. Price the edition on what the business genuinely needs, then negotiate the conversation rate and the Data Cloud credits against a measured forecast.
The conversation meter, the bundle math, the Data Cloud overlay, and the renewal clauses that protect the run rate across the Salesforce estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The most expensive Agentforce mistake is not the rate. It is committing to a conversation volume from a vendor model instead of a measured pilot, then living with the over forecast for three years.
