The Rebrand
Dreamforce 2025: Data Cloud becomes Data 360. Agentforce 360 as the ecosystem umbrella spanning Sales, Service, Marketing, Commerce, Slack, and Tableau. The vision: unified data, agentic AI, cross-cloud activation, and a single Trust Layer governing every model call. The naming change wasn’t cosmetic — it signaled architectural consolidation, with Atlas Reasoning, the Trust Layer, and Data 360 retrieval positioned as shared services rather than per-cloud features.
Six Months Later
2026 operational reality: the rebrand succeeded technically. Data 360 works at scale. Agentforce 360 coheres as a coherent story for buyers and analysts. Customer adoption of the full vision is uneven — 12,000+ Agentforce customers is real; most use narrow-scope deployments (one or two Topics, single channel, internal-facing). The “agents everywhere across every cloud” pitch overstated where most customers actually are. The “agents resolving repeatable tier-1 work” pitch holds up.
Aftermath snapshot (April 2026):
Agentforce customers (disclosed) 12,000+
Median Topics per deployment 1-3
Median Actions per agent 4-8
Most common channel Service Cloud chat
Common second channel Slack
Production-grade multi-agent orgs <500 (estimated)
Data 360 active customers 9,000+What Worked
Unified positioning helped enterprise buyers — the procurement story is now “Salesforce + agents” instead of “Salesforce plus a third-party AI stack.” The messaging “data and agents in one platform” resonates against fragmented competitors. Product integration (Data 360 grounding agents, Trust Layer governing model calls, Command Center observing them) delivers real functionality, not just a slide. Service Cloud deflection wins are the headline use case and are reproducible across customers.
What’s Maturing
Multi-agent coordination is nascent — Agent Fabric ships the discovery and policy plane in 2026, but compositional patterns (one agent calling another to complete a job) remain rare in production. MCP server distribution is in pilot with the 1,000-server milestone in early 2026. Command Center arrived mid-2026 and changed the operational picture decisively. The full Dreamforce 2025 vision needs 2026–2027 to land in production. Patience is warranted — and budgets should reflect a phased adoption curve, not a Big Bang.
What Changed in 2026
Three concrete shifts since Dreamforce 2025: Agentforce 360 opened to ISVs (was Salesforce-only), AgentExchange consolidated three marketplaces into one, and the Einstein Trust Layer added BYO-model governance with policy-based routing. Each materially raised the ceiling for what enterprises can build without leaving the platform.
Lessons for Buyers
Buy the slice you’ll actually use, not the umbrella. A Service Cloud deflection pilot with one Topic is a real ROI play; an “AI transformation” purchase scoping every cloud at once is a 2027 conversation. Stage Data 360 onboarding to match agent rollout — paying for unconsumed Data 360 storage is the most common waste line in disclosed budget reviews.
What to Do This Week
Audit your post-Dreamforce 2025 Agentforce roadmap against actual production usage. Cut the slides; keep the pilots that are showing measurable deflection or pipeline lift.
