\
Salesforce today announced Headless 360, an API-based system designed to make its software easier for AI agents to use.
At a high level, Headless 360 allows agents to access data, workflows, and logic without relying on a traditional user interface. This allows AI agents to run tasks in the background, rather than requiring users to click through dashboards.
This shift reflects a broader shift in enterprise software, where automation is moving closer to the center of how work gets done. Instead of navigating tools, users increasingly rely on systems that act on their behalf.
Salesforce doesn’t build everything from scratch. The company layers this approach on existing products such as Customer 360, Data 360 and its Agentforce tools, making them accessible to agents through structured interfaces.
Shift to agent-driven workflows
The practical impact is the abandonment of on-screen interactions in favor of orchestration. Agents can call APIs, trigger workflows, and move data between systems without human intervention, changing the way processes are designed.
This change also changes the way developers think about building apps. Instead of focusing primarily on user experience, the emphasis is on creating systems that are composable, accessible and understandable to machines.
There are compromises. As AI systems take on more responsibility, outcomes become less predictable, introducing new challenges in testing, governance, and control.
At the same time, the flexibility of agent-driven workflows can make systems more adaptive, allowing organizations to respond more quickly to changing conditions.
A different model for enterprise software
Salesforce’s approach suggests a longer-term shift toward platforms functioning as infrastructure rather than interfaces. In this model, the user interface becomes optional, while APIs and automation layers become the primary means of getting work done.
This has implications for marketing and customer experience teams. If agents handle more interactions, the focus shifts to creating accessible data and workflows in a way that those agents can interpret and act on.
For developers, this change reinforces the importance of interoperability. Systems must work together seamlessly, with standardized ways to share data and trigger actions.





