Is the real shift in SaaS “headless software” or AI embedded in workflows?
I’m trying to think through the product implications of Salesforce Headless 360 and the broader idea that “software is losing its head.” APIs have existed for years, so I’m trying to separate what is genuinely new from what is just new packaging.
My current understanding is: In the SaaS era, products were sticky because humans lived in the UI. A sales rep opened Salesforce, a support agent opened Zendesk, a recruiter opened Workday, etc. The interface was not just a screen. It encoded workflow, habits, fields, approvals, dashboards, admin rules, and tribal knowledge.
In the agentic era, that weakens because agents do not care about the UI. They can read/write through APIs, MCP tools, or other programmatic surfaces. So the product moat may shift from “users live in our app” to “agents can safely understand and execute our workflow.”
But I’m not fully convinced the future is just chat replacing SaaS UI.
My instinct is that the stronger product thesis is: Headless is the architecture. Embedded workflow AI is the experience. For example, the winning pattern may not be: “Ask a Slack bot to do everything Salesforce used to do.”
It may be: AI appears inside the renewal workflow, support escalation, discount approval, claims process, or sales forecast review, with context, valid next actions, approval buttons, audit trail, and rollback.
So my question for product folks: Do you think the real shift is toward headless SaaS, where agents operate systems mostly outside the UI? Or is the more durable pattern AI embedded inside existing workflows and decision points?
Also curious how people think this affects defensibility. If UI habits and training matter less, what becomes the new moat?