At Dreamforce 2025, Salesforce positioned Agentforce 360 as the foundation for the agentic enterprise. The shift was from building a useful agent to coordinating a portfolio of agents, data, tools and human work.
That ambition needs architectural layers. Without them, every department creates its own identity assumptions, action interfaces, evaluation practice and version of customer truth.
Cloud Group point of view
Centralize the controls that protect the enterprise and federate the design that expresses domain expertise. A platform team should make the safe path easy without becoming a delivery bottleneck.
A practical playbook
The strongest next step is narrow enough to govern and useful enough to produce evidence. We would structure the work around these moves:
- Create shared identity, policy, model and tool gateways.
- Publish governed data products and action contracts by domain.
- Let business-aligned teams own agent jobs, knowledge and outcome measures.
- Standardize evaluation, traceability and incident response.
- Use an architecture council to resolve cross-agent ownership and reuse.
The architecture and operating implication
Organize the estate into experience, orchestration, context, action and control layers. Agents may vary by channel and job; controls and business capabilities should remain consistent. Data 360 and Salesforce metadata can anchor context while external services remain accessible through governed interfaces.
Measure what changes
Model activity is not a business result. Track a small set of indicators that connect behavior to accountable work:
- Shared capability adoption
- Time to launch a compliant use case
- Cross-agent conflicts and duplicated tools
- Portfolio outcomes, cost and risk concentration
The agentic enterprise is not a single product deployment. It is an operating architecture that lets many teams move quickly without fragmenting trust.
Primary sources
This field note is grounded in the product and market context available at the time of publication.
