Salesforce Data 360 and Agentforce Readiness

Salesforce just reorganized the whole company around Agentforce and Data 360, with Agentforce past $1.2B ARR. The agents only work on a clean data foundation. Here is the readiness work that decides whether your rollout ships.

Salesforce just told the market what it thinks the next decade looks like, and it did it by rearranging its own income statement. In Q1 FY27 the company collapsed its product clouds into two reporting engines, Agentforce and Data 360, and the numbers behind the move are not subtle.

Agentforce passed $1.2 billion in annualized ARR, up 205 percent. Data 360 ingested 52 trillion records, up 136 percent. And the part most teams miss: more than half of that growth is existing customers expanding, not new logos. The platform is becoming agent-and-data-first, and the customers already on it are leaning in.

The reorg, and where the growth actually is

The detail that matters for planning: the Data 360 / Headless Platform segment, which now holds Data 360, MuleSoft, and Tableau, is growing almost three times faster than the app side. Salesforce is telling you the value has moved to the data and integration layer underneath the apps. That is not a CRM-admin story. It is a data-architecture story.

Agents are only as good as the data they read

This is the part the launch keynotes skip. Agentforce is impressive, but an agent acts on whatever data it is given. If identity is not resolved in Data 360, if the metric the agent uses is not certified, or if the feed it reads is stale, the agent acts confidently and wrong, and no human is in the loop to catch it.

That checklist is why the companies getting Agentforce into production are the ones that did the unglamorous work first: unified data, certified definitions, reliable integration, and governance. It is the same data foundation discipline that decides every AI outcome, applied to the Salesforce stack.

What "Headless 360" means for your team

Salesforce is moving toward an API, MCP, and agent-operable platform, where you interact with the ecosystem programmatically rather than through the Setup menu. The value of a Salesforce investment is shifting from configuration to architecture: the data model, the integration, the governance, and the agents. That is exactly the work that benefits from a data and AI partner alongside your Salesforce team, with the governance and managed operations to keep the agents safe after launch.

The move this quarter

If Agentforce or Data 360 is on your roadmap, the question is not "which agent" but "is our data ready for one." Inventory your Data 360 readiness, the certified metrics, and the integration paths before you scope the agents. The 30-day Analytics Truth Audit checks exactly that.

Frequently asked questions

What changed with Salesforce Data 360 and Agentforce in FY27?

Starting FY27, Salesforce reorganized its reporting into two engines: Agentforce Apps (Sales, Service, Marketing, Commerce, Slack) and Data 360 / Headless Platform (Data 360, MuleSoft, Tableau, Informatica). Agentforce passed $1.2 billion in annualized ARR, up 205 percent, and Data 360 ingested 52 trillion records, up 136 percent. The company is now organized around agents and data, not the old product clouds.

What is Salesforce Data 360?

Data 360 is Salesforce's renamed data layer (formerly Data Cloud): the unified, governed customer data that Agentforce, Sales Cloud, and the rest read from. It resolves identity across systems and is the foundation an agent grounds on. Getting Data 360 right is the prerequisite for everything agentic on the platform.

Why do Agentforce projects need a data foundation first?

An agent acts on the data it reads. If identity is not resolved, definitions are not certified, or feeds are stale, the agent acts confidently and wrong, with no human in the loop. More than half of Agentforce and Data 360 bookings are existing customers expanding, and the ones who succeed fixed the data layer before scaling the agents.

Where does MuleSoft fit in the new structure?

MuleSoft sits in the Data 360 / Headless Platform segment, the faster-growing one. It is how data from systems outside Salesforce arrives reliably for Data 360 and the agents. Integration is the bottleneck for agentic rollouts, not the model, which is why MuleSoft is now part of the data engine rather than a standalone product.

Is this a Salesforce admin job or a data and architecture job?

Increasingly the latter. Salesforce is moving toward an API, MCP, and agent-operable platform, so the value shifts from clicking in the UI to architecting the data, integration, governance, and agents. That is data and AI foundation work, which is the lane we operate in alongside your Salesforce team.

How do we get ready?

Unify and govern your data in Data 360, certify the metric definitions the agents will use, wire reliable integration through MuleSoft, and put governance, audit logging, and human review around the agents before they touch customers. A readiness assessment scopes which of those gaps is yours.