Every SaaS vendor just had its head chopped off, and Salesforce went first. It voluntarily stepped up to the guillotine and let its own head go. Yes, that sounds a bit savage, but don’t worry. It’s wonderful. The entire SaaS industry is about to go headless, and I couldn’t be more excited.
For thirty years, the interface has masqueraded as the product. That disguise just came off. The UI was always just the delivery mechanism, and it has quietly become one of the most expensive parts of enterprise software ownership.
Think about what a typical knowledge worker actually does in a day. They log into an ERP system to check a budget, then into a CRM to update an opportunity, then into an expense tool to file a report, then into an HR system to approve a request. Each application has its own navigation logic, its own field names, its own permissions quirks, and its own learning curve. Most of these systems are also loaded with three or four times the functionality any single user needs, which means the interface is optimized for the vendor’s full customer base, not for the person actually sitting in front of it. The result is a tax on productivity that has compounded for years. Time is lost to switching, time is lost to relearning, and time is lost to hunting for the right screen inside the right app. This was never a minor annoyance. It was one of the largest hidden costs in enterprise software.
The UI was never the product
Oracle was among the first major vendors to say this out loud in a meaningful way. With its agentic applications announced earlier this year (one of the first live market examples of cross-application agents as explained in IDC’s Agentic Evolution of Applications framework), Oracle began dynamically assembling the interface itself, pulling the data, functionality, workflows, and logic a user needed from across whichever applications were relevant, rather than forcing the user to go find them. That was among the first real cracks in the old model. It correctly suggested that the fixed screen was a legacy constraint, not a design requirement.
Salesforce has now taken that idea and extended it a step further. At Dreamforce 2026, held September 15 through 17 in San Francisco, Salesforce unveiled AIforce, which it is calling a live interface layer. AIforce does what Agentforce already does inside Salesforce (dynamically composing the data, workflows, and business logic a user needs on the fly), but it goes a step further. It extends that same capability outside of Salesforce entirely, into whatever interface a person already happens to be working in. Salesforce launched this with three surfaces at once: Claudeforce, Slackforce, and Agentforce Coworker, meaning the same trusted enterprise data and governance can now show up inside Claude, inside Slack, or inside a dedicated coworker agent, not just inside Salesforce’s own screens.
Meeting users wherever theyare
This is precisely why AIforce matters more than another feature release. The goal is to help customers break free of a shared user interface, so that every individual gets an intelligent, dynamic interface that comes to them, wherever they are, instead of forcing everyone into the same fixed screens. That is not a UI update. It is an admission that the UI was the obstacle all along.
What this means for the rest of the market
Oracle and Salesforce arrived at the same conclusion from opposite ends of the market, and that convergence is the real signal, not either company’s product name. When two competitors this large independently decide that the fixed screen is disposable, the SaaS UI is not being tweaked. It is being retired.
Buyers should not mourn it. The interface was never where the value lived. The value lived in the data, the workflows, and the logic sitting underneath it, and buyers have been paying a productivity tax for thirty years just to reach that value through a screen. That tax is now optional.
For vendors across ERP, HR, finance, SCM, and every other enterprise application category, the imperative is not subtle:
- Stop pricing and marketing the interface as the differentiator. It never was.
- Open the data, workflows, and business logic underneath the UI to whatever surface the customer already lives in, whether that is Claude, Slack, Teams, ChatGPT, Outlook, Office, or any other work environment.
- Build the governance and permissions layer first. A composable interface without composable trust is a liability, not a feature.
- Assume the next RFP will not ask what your UI looks like. It will ask whether your platform can show up anywhere.
The UI is not being replaced by a better UI. It is being replaced by the absence of one. That is not a loss. It is the correction the market has needed for thirty years. I never thought I’d see the day when I applaud a beheading, but that day has arrived, and I hope it continues.