Skip to main content
Headless 360 horseman image

‘Twas a dark and stormy sprint cycle in the hollow of legacy CRM, where poor Ichabod Crane, a mild-mannered Salesforce admin, spent his days clicking, tabbing, navigating, and logging in. Every case status updated by hand. Every workflow, one more mouse click away from madness.

Then came the Horseman . . . Headless 360.

No browser. No face. No patience for dropdown menus. Just API calls, MCP tools, and CLI commands, galloping through the enterprise at full speed. The horseman doesn’t navigate Salesforce. He is Salesforce, operating directly from within the platform’s core.

His weapon of choice? Sixty-plus MCP tools and thirty-plus coding skills, compatible with Claude Code, Cursor, and Codex out of the box.

The three haunts of Headless 360:

  • Build Any Way You Want: Coding agents get live access to data, logic, and workflows from whatever environment they already occupy. Dev cycles reportedly cut by up to 40%.
  • Ride Across Every Surface: The Experience Layer renders agent interactions natively across Slack, Voice, WhatsApp, ChatGPT, and Teams. Build once, deploy anywhere. Though “renders everywhere” and “renders well everywhere” are two different promises.
  • Trust the Ghost: New testing, scoring evaluations, session tracing, and A/B tools help teams monitor agent behavior and catch drift before it reaches production. Useful guardrails, though not a guarantee when agents are handling refunds, approvals, and compliance-sensitive workflows.

The horseman is impressive. The fine print is worth reading:

  • Deep Roots & High Walls: The more your agents are built on Salesforce’s logic and permissions, the more expensive it becomes to leave. Trading a UI dependency for a platform dependency is still a dependency.
  • An Open Gate is an Open Gate: Exposing the entire platform programmatically means a compromised or misconfigured agent can move through your business faster than any human ever could. Speed cuts both ways.
  • The Moat May Not Hold: MCP is an open standard, which means any vendor can play the same game. Salesforce’s real bet is that decades of accumulated business data and logic are hard to replicate. That may be true today. It is less obvious tomorrow.

The Moral of the Story: Ichabod logged in. The horseman called an API. Only one made it across the bridge. The difference between a triumphant ride and a disaster is not the horse. It is who is holding the reins.

Welcome to the Agentic Enterprise. Ride carefully.