Agentforce is priced by consumption, not by seat. Every conversation and action draws against a credit balance. That model can be efficient or it can run away. The difference is governance set before go live.
Salesforce Agentforce prices by consumption rather than by seat. This guide explains conversations, Flex Credits, the Data Cloud dependency, and the buyer side controls that cap cost.
Agentforce is priced by consumption. You pay for what the agents do, measured in conversations or actions, rather than for a fixed number of user seats.
The published Agentforce pricing has centered on a per conversation charge, historically around two dollars, alongside a credit model for finer grained actions. The exact units evolve, so treat the structure, not the number, as the thing to manage.
Seat pricing is predictable because it is capped by headcount. Consumption pricing is uncapped by design, so the cost follows usage wherever it goes.
Define precisely what triggers a billable conversation or action with Salesforce. Ambiguity in that definition is where consumption cost quietly inflates.
Flex Credits let you prepay a balance that agents draw down per action, giving finer control than whole conversations. They suit estates running many small automated actions.
Credits are bought in blocks and consumed as agents act. The Agentforce platform meters that draw, so monitoring the burn rate is essential from day one.
Seat pricing versus consumption pricing
| Dimension | Seat model | Agentforce consumption |
|---|---|---|
| Cost driver | Headcount | Conversations and actions |
| Predictability | High, capped by seats | Lower, follows usage |
| Scaling risk | Step changes at thresholds | Continuous growth with volume |
| Main control | User provisioning | Volume governance |
Agentforce relies on Data Cloud to ground agents in your data. Data Cloud is itself priced by consumption, so adopting Agentforce usually adds a second consumption meter to the bill.
Budget Data Cloud alongside Agentforce from the start. Treating it as a later add on is how the total cost outruns the original business case.
Data Cloud charges for ingesting and processing data. The more context your agents need, the more that meter runs.
The standard pitch is that consumption pricing is fairer because you only pay for what you use, so there is no need to worry about overbuying. We disagree. In the Agentforce and Data Cloud commitments we have advised, the open ended meter combined with optimistic volume forecasts produced bills well above the seat based tools they replaced, because usage rose faster than anyone projected. The buyer side move is to treat consumption pricing as a budget you must actively govern, pilot to measure true volume, and commit credits to a measured floor rather than a hopeful forecast. Pay as you go is only cheap when you control the go.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Consumption pricing is not cheaper or dearer than seats. It is less forgiving. The meter rewards governance and punishes optimism.
Three controls keep consumption in line.
Run a measured pilot to learn true conversation volume before buying a large credit block.
Size any credit commitment to measured volume, not to an optimistic forecast.
Agentforce is priced by consumption. You pay for what agents do, measured in conversations or actions, rather than for a fixed number of seats. A conversation has historically been priced around two dollars.
Flex Credits are a prepaid balance that agents draw down per action, giving finer control than whole conversations. They suit estates running many small automated actions.
Because consumption pricing is uncapped by design. Unlike a seat model bounded by headcount, the cost follows usage, so volume growth flows straight to the bill.
In practice yes. Agentforce relies on Data Cloud to ground agents in your data, and Data Cloud is itself priced by consumption, adding a second meter to the cost.
Run a measured pilot before committing. Early forecasts commonly undershoot real volume, so live pilot data is far more reliable than a planning estimate.
Volume governance. Limiting which agents run, on which channels, and monitoring credit burn with alerts does more than any rate negotiation.
Not before a pilot. Size any commitment to measured volume rather than an optimistic forecast, so you commit to a floor you will actually use.
Seat pricing is predictable and capped by headcount. Consumption pricing is less forgiving, growing continuously with usage, so it rewards governance and punishes optimism.
Consumption math, Flex Credit sizing, the Data Cloud dependency, governance controls, and the buyer side moves across the Salesforce estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Agentforce moves Salesforce from seats you can count to actions you must govern. The rate card is the easy part. The governance is the whole game.
