White paper xxvii · Salesforce

Salesforce Agentforce commercial scope.

Agentforce is the Salesforce platform for autonomous and semi-autonomous AI agents that act inside the Customer 360 estate. The commercial construct is a conversation-credit meter sat on top of a defined agent topology, with a hard dependency on the underlying Data Cloud substrate. The buyer-side procurement question is what an Agentforce conversation actually is, how the credit is consumed, how the agent topology is bounded and what the Data Cloud commitment must absorb to make the deployment viable. This 22-page paper sets out the credit metric, the agent topology, the Data Cloud dependency, the pilot discipline and the renewal posture inside the Salesforce contract cycle. Buyer-side. Independent. Gated.

FormatWhite paper, gated
Pages22
AudienceCIO, CRO, CMO, CFO, IT, Procurement
PublishedMarch 2026

A senior Admodum advisor will follow up to confirm receipt and offer a private read of the document if you would prefer a guided walkthrough. There is no obligation. The paper is the deliverable.

Contents

Inside the 22 pages.

i.
Why Agentforce exists
The Salesforce AI roadmap from Einstein 1 to Agentforce, the commercial pivot to platform-priced agents, and the buyer-side reading of the value-versus-price proposition.
ii.
The conversation-credit metric
Definition of a Salesforce conversation, the published credit schedule, the credit-pool construct, the over-consumption rate and the renewal-time re-set of the published schedule.
iii.
Agent topology
The Service Agent, Sales Agent, Marketing Agent, Commerce Agent, Personal Shopper, Health Agent and custom agents built on Agent Builder. Each agent’s scope, role-type alignment and credit-consumption profile.
iv.
Data Cloud dependency
Agentforce as a downstream consumer of Data Cloud. The data-substrate sizing, the profile and event ingestion question, the segmentation cost and the joint-commitment design.
v.
Included versus premium boundary
Where Einstein included entitlement ends and where Agentforce paid credit begins. The Einstein Copilot legacy, the Agentforce credit floor and the boundary the buyer-side methodology contests.
vi.
Sizing protocol
The buyer-side credit sizing methodology. Use-case enumeration, conversation-volume forecast, credit-per-conversation read, contingency band and committed-pool sizing.
vii.
Pilot to production discipline
The three-guardrail pilot discipline. Pilot pricing exposed at front, production sizing on methodology not enthusiasm, ramp design across the agent topology rather than flat commitment.
viii.
Renewal posture
Agentforce inside the Salesforce renewal cycle. Interaction with user-type reconciliation, MuleSoft and Tableau adjacencies, Data Cloud joint-commitment and the multi-year ramp design.
ix.
Reading list and references
Companion papers on Salesforce renewal defence, Data Cloud commitment, ServiceNow Now Assist scope, Workday Illuminate AI and the cross-vendor AI commercial reading.
Excerpt · Section II

The conversation is not the unit.

Agentforce prices on a conversation-credit construct, but the buyer-side reading of "conversation" is materially different from the publisher-side definition. A single end-to-end interaction with a customer may include several Salesforce conversations under the Agentforce counting; each handoff between agents, each context retrieval and each model invocation can register as a discrete event against the credit pool. The procurement question is not how many customer conversations the buyer anticipates per period but how many Salesforce credit events the deployment will generate against that customer-conversation count.

The customer has one conversation. The credit pool counts several. The procurement question is the multiplier.

The credit-per-conversation multiplier is the load-bearing input. Where Salesforce projections assume one credit per customer conversation, the deployed reality often runs at three, five or higher, particularly where multi-agent flows are designed against complex customer journeys. The Admodum methodology models the multiplier explicitly from a pilot read and sizes the committed credit pool to the trailing-twelve-month deployed evidence, not to the publisher forecast.

This paper sets out the nine-section Agentforce protocol Admodum applies inside the Salesforce commitment, with the credit metric, the agent topology, the Data Cloud joint-commitment and the renewal posture each carried through to the closing memorandum.

Request the white paper

Request the 22-page paper.

Corporate email only. The paper is sent by a senior Admodum advisor. No marketing list, no third-party distribution. Submission confirms you have read the independence statement at the foot of this page.

Please enter a corporate email address. Personal addresses (gmail, hotmail, outlook, yahoo, icloud and similar) are not accepted.
Corporate email required · No marketing list · Reply within one business day
Independence
Admodum is not a partner, reseller, or affiliate of Salesforce, or of any other software vendor. No reseller margin, no implementation-partner fee, no certified-consulting commission.
Software licensing white paper

Bring an advisor to the Agentforce decision.

The Admodum Salesforce practice sizes Agentforce commitments inside the Renewal Programme and the Benchmarking Programme. Engagements run as fixed fee, contingency or annual retainer.