Buyer side advisory. 500+ enterprise clients across 11 vendor practices. Schedule a Call →
Salesforce AI Playbook

Salesforce Data Cloud, Data 360, and Agentforce: A Buyer Playbook

How Salesforce Data Cloud, Data 360, and Agentforce are licensed, priced, and negotiated. Credits, profiles, segmentation, and what enterprise buyers should demand before signing.

Portrait of Fredrik Filipsson
Written byFredrik FilipssonCo Founder & Group CEO · ex Oracle, IBM, SAP
Read Time20 Minutes
Last UpdatedMay 2026

Now that you have the framework

Apply it to your Salesforce Agentforce situation.

25 minute call with our Salesforce Agentforce practice lead. We will walk through your specific renewal, audit, or contract and tell you what we would do next. No follow up sales pressure unless you ask for one.

Schedule a 25 Minute Review Contact Us
Home›Salesforce Hub›White Papers›Salesforce Data Cloud, Data 360, and Agentforce: A Buyer Playbook
The Short Version

If you read nothing else

Bottom Line

Salesforce Data Cloud, Data 360, and Agentforce shift Salesforce pricing from seats to consumption. Buyers without credit caps and consumption ramps will see runaway spend. The playbook is to model usage, cap consumption in writing, and refuse to sign without floors.

Key Takeaways

Five conclusions

Credits are the new seat. Data Cloud and Agentforce price by credits consumed. Without modeling, the meter runs faster than expected.
Profiles compound. Profile activations multiply across segments. Each one consumes credits. Watch the multiplier.
Agentforce is opaque. Conversation pricing is per outcome, but the metric is vendor defined. Confirm the meter before signing.
Data 360 overlaps. Data 360 features overlap CRM Cloud features. Avoid double licensing the same capability.
Ramps and caps win. Negotiate ramps for predictable growth. Negotiate hard caps for unexpected spikes. Both go in the order form.
Recommendations by Role

What to do this quarter

Chief Information Officer
  1. Model Data Cloud and Agentforce credit consumption monthly
  2. Set hard caps for AI consumption before signing
  3. Ensure Data 360 does not duplicate existing CRM capability
Procurement
  1. Negotiate ramps for predictable AI consumption growth
  2. Negotiate hard caps for spike protection
  3. Demand a credit pricing schedule in the order form, not the MSA
Salesforce Owner
  1. Track credit consumption weekly during the first quarter
  2. Identify high cost activations and optimize before scaling
  3. Document every segment, profile, and activation as a cost center
The Framework

Eight ideas

1. The Credit Currency

Credits are the unit of consumption across Data Cloud and Agentforce. The conversion of credits to dollars is contractual. Lock the rate before signing.

2. Profile Activation Math

Profile activations consume credits per segment. The math compounds as segments multiply. Model the worst case before signing.

3. Data Cloud Workloads

Data Cloud workloads (ingest, transform, segment, activate) each consume credits at different rates. Document the workload library.

4. Data 360 Positioning

Data 360 overlaps with CRM Cloud features. Confirm what Data 360 adds vs what is duplicated. Refuse to pay twice for the same capability.

5. Agentforce Consumption

Agentforce conversation pricing is per outcome. The meter is vendor defined. Demand a clear definition before signing. Demand a hard cap.

6. Ramp Pricing

Predictable AI growth deserves ramp pricing. Negotiate a 3 year ramp with the discount baked in. Document in the order form.

7. Hard Caps

Hard caps protect against runaway consumption. Without caps, a misconfiguration can cost 7 figures. The cap is non negotiable.

8. Renewal Posture

AI products renew on consumption history. Plan for the renegotiation 90 days before renewal. Do not let consumption set the next floor.

Reference

Acronyms

MSAMaster Subscription Agreement
OFOrder Form
SCVSingle Customer View
CDPCustomer Data Platform
ETLExtract Transform Load
APIApplication Programming Interface
Methodology & Sources

This white paper draws on Redress Compliance engagements, public vendor documentation, and the active Redress benchmark program.

Portrait of Fredrik Filipsson
About the Author

Fredrik Filipsson

Co Founder, Redress Compliance
Connect on LinkedIn →
Vendor relationship up for review?
Talk to an Advisor
Related

Continue

Oracle
Oracle ULA
Oracle flagship.
 Microsoft
Microsoft EA
Microsoft flagship.
 IBM
IBM Audit Defense
IBM flagship.
 SAP
SAP RISE
SAP flagship.
 AWS
AWS EDP
AWS flagship.
 Index
All Papers
Browse the library.
Skyscraper
Ready?

Stop overpaying. Start negotiating.

We work for the buyer. Always. There is no other side of our table.

Contact UsView Case StudiesGet Monthly Briefings

Monthly Licensing Intelligence

Once a month. Vendor moves, audit patterns, renewal alerts. For IT and procurement leaders.