Salesforce Data 360 and Agentforce: The Consumption Pricing Playbook
Data 360 and Agentforce price by the credit, not the seat. At $500 per 100,000 credits, an unmodeled estate can run 30 to 60 percent over budget in year one. The defense is a credit rate lock and a hard cap in the order form.
Prepared by Redress Compliance · June 2026 · Representative Salesforce estate scenario (benchmark scenario, not a quote)
Executive Summary
Salesforce renamed Data Cloud to Data 360 in October 2025 and finished the shift it began years earlier. Pricing moved from a seat you buy once to credits you burn continuously. The list rate is roughly $500 per 100,000 Flex Credits, about $0.005 per credit, and the meter never stops while data flows.
The trap is invisible at signature. A single operation, identity resolution, consumes about 100,000 credits per million rows processed, and it runs automatically on ingestion. Buyers who size the deal on a demo, not on modeled row volumes, discover the gap on the first true up, not the first invoice.
Agentforce adds a second meter. You choose Conversations at $2 each or Flex Credits at about 20 credits per action, and the two cannot coexist in one org. The wrong meter for your interaction profile doubles the bill, and the choice is hard to reverse mid term.
Three controls decide the outcome, and all three live in the order form, not the master agreement. Lock the credit to dollar rate, ramp the commitment to modeled growth, and cap consumption with a hard ceiling. Without the cap, the meter sets your next renewal floor.
How Does Credit Consumption Work Across Data 360 and Agentforce?
Everything converts to one currency. Data 360 ingestion, segmentation, activation, queries, and Agentforce actions all draw down Flex Credits, priced at roughly $500 per 100,000, about $0.005 each. Credits are fungible, poolable across Data 360, Agentforce, and Slack.
Consumption follows a published formula: credits equal rows processed divided by one million, times an operation multiplier. The multiplier is where the spread hides. A simple query costs almost nothing per million rows; identity resolution costs a fortune.
| Operation | Multiplier per million rows | Credits per 100M rows | Cost at $0.005 |
|---|---|---|---|
| Data query, SQL | About 2 | 200 | $1 |
| Profile activation | Moderate | 1,600,000 | $8,000 |
| Segmentation | Higher | 2,400,000 | $12,000 |
| Identity resolution | About 100,000 | 10,000,000 | $50,000 |
Read the spread. The same 100 million rows cost $1 as a query and about $50,000 as identity resolution. Sizing on the cheap operation and running the expensive one is the most common way a Data 360 budget breaks.
The first non obvious mechanic: Flex Credits expire annually and do not roll over. Buy a generous ramp to feel safe, underuse it, and the unused balance is simply lost. Over buying is as costly as under capping.
What Do Profile Activations Cost, and Where Are the Silent Line Items?
Salesforce now sells two ways to pay. You take the profile SKU at $240 per 1,000 profiles baseline, or $420 premium, billed annually, or you stay on pure Flex Credits. The profile SKU promises predictability, and it bundles one flex credit per profile per year.
That bundle is the second non obvious mechanic. Buyers who hold both a profile SKU and a separate Flex Credit pack often pay twice for credits already included. Read the entitlement before you add a credit line.
The silent line items
The profile count is the visible number. The charges below are the ones that arrive later and were never in the demo.
| Silent line item | How it bills | Why it surprises buyers |
|---|---|---|
| Identity resolution | About 100,000 credits per million rows, run automatically on ingestion. | It is not a feature you switch on. It runs to build the profile, and it is the single most expensive operation. |
| Data storage | About $23 per TB per month for the Data Storage card. | Unified profiles plus engagement history grow storage quietly, outside the credit meter. |
| Reprocessing | Each refresh reprocesses rows and consumes credits again. | Frequent refresh schedules multiply credit draw against the same underlying data. |
| Activation targets | Each activation to an external platform consumes credits per run. | More destinations means more runs, and the count scales with the marketing calendar, not the contract. |
The third non obvious mechanic sits in the free tier. Salesforce Foundations includes 200,000 Flex Credits and 250,000 Data 360 credits at no cost. That looks like generosity. It is a metered on ramp designed to seed usage that converts to a paid commitment once the team builds on it.
Of the first proposal we typically remove.
Across Data 360 and Agentforce deals reviewed in 2024 to 2025, cutting CRM overlap and right sizing profile counts removed 25 to 45 percent of the opening proposal value before any rate negotiation.
Year one overage without a hard cap.
Estates that signed without a written consumption cap ran 30 to 60 percent above their modeled credit budget in the first year, most of it from identity resolution and reprocessing.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. Confirmed against your estate during delivery.
How Does Data 360 Overlap With the CRM You Already Own?
Data 360 is positioned as the layer that unifies every source into one profile. Much of what it does, your Sales Cloud and Service Cloud estate already does in part. The risk is paying a second time for a capability you licensed years ago.
| Capability | Already in core CRM | What Data 360 genuinely adds |
|---|---|---|
| Customer record | Accounts, Contacts, and the standard data model. | Cross system identity resolution into one profile across non Salesforce sources. |
| Segmentation | Reports, list views, and campaign member logic. | Large scale segmentation across unified data, beyond CRM object limits. |
| Activation | Flows, journeys, and native marketing sends. | Activation to external advertising and data platforms in near real time. |
| Analytics | Reports, dashboards, and CRM Analytics. | Querying high volume engagement data the core objects cannot hold. |
The buyer move is a capability audit before signature. Map each Data 360 line to a question: does this replace, extend, or duplicate something we already pay for? Pay only for replace and extend.
How Is Agentforce Metered, and Where Is the Overage Risk?
Agentforce gives you two meters and makes you pick one. Conversations bill $2 for any interaction inside a 24 hour window. Flex Credits bill about 20 credits per action, roughly $0.10. You cannot run both in the same org.
The crossover is arithmetic. At 20 actions per conversation the two meters tie at $2.00. Below 20 actions, Flex Credits win. Above 20, Conversations win, because the flat fee caps the action count.
Two mechanics raise the audit and overage risk. First, the 24 hour window quietly bundles repeat contacts. A customer who returns the next day starts a second billable conversation, even on the same issue. High repeat traffic inflates the count.
Second, agents call actions you did not forecast. Each tool call, record update, and prompt is an action that draws credits. A misconfigured agent that loops or over retrieves can burn a year of credits in weeks, with no cap to stop it.
How Do You Negotiate Ramps, Floors, and Caps on Consumption Products?
Three terms decide whether consumption pricing works for you or against you, and all three belong in the order form. The master agreement sets the relationship. The order form sets the price, the rate, and the ceiling.
The worked estate
Take Meridian Retail Group, a representative enterprise with three million unified profiles and an active Agentforce support deployment. Its modeled annual budget is 120 million credits, about $600,000 at list. Without a cap, year one ran toward $960,000.
| Workload | Annual credits | Cost at $0.005 |
|---|---|---|
| Identity resolution | 60,000,000 | $300,000 |
| Segmentation | 24,000,000 | $120,000 |
| Activation | 16,000,000 | $80,000 |
| Agentforce actions | 12,000,000 | $60,000 |
| Data queries and SQL | 8,000,000 | $40,000 |
| Modeled total | 120,000,000 | $600,000 |
The fourth non obvious mechanic is the rate. The credit to dollar conversion lives in the order form, not the MSA, and it resets at renewal unless you fix it. Lock the rate for the full term, and lock the renewal uplift cap in the same clause.
The three terms to win
- Ramp: stage the commitment to modeled growth, so you pay for year two volume in year two, not at signature.
- Rate lock: fix the credit to dollar rate and the renewal uplift cap for the full term, in the order form.
- Hard cap: set a written ceiling on monthly and annual consumption, with notice and approval before any overage bills.
The fifth non obvious mechanic protects the downside. Insist on a true forward, not a true up: overage converts to added commitment at the locked rate, never at an undiscounted on demand rate. That single clause turns a billing shock into a planned expansion.
The 90 Day Negotiation Sequence
Size the real estate
Model row volumes, refresh schedules, profile counts, and agent action profiles. Convert each to credits at $0.005. Separate identity resolution out, because it carries the largest share of the bill.
Cut the overlap
Run the capability audit against your Sales and Service Cloud entitlements. Remove duplicated lines, choose the Agentforce meter from measured actions, and right size profiles before any rate talk.
Win the three terms
Put the ramp, the rate lock, and the hard cap in the order form. Add the true forward clause and the renewal uplift cap. Time the close to Salesforce quarter end pressure.
Recommendation
Treat Data 360 and Agentforce as a metered utility, and contract for it like one. The list rate of $0.005 per credit is not the risk. The risk is unmodeled volume, duplicated capability, and the wrong Agentforce meter, all compounding without a cap to stop them.
- Model before you sign. Size identity resolution, segmentation, and agent actions in credits, and cut every Data 360 line that duplicates your existing CRM entitlement.
- Lock the order form. Win the rate lock, the ramp, and the hard cap, and add a true forward so overage expands commitment at the locked rate, never at on demand.
Redress Compliance runs this playbook on the buyer side only: model the estate, scope out the overlap, and hold the rate and the cap in writing. We are glad to tie a meaningful part of the fee to delivered value.