Salesforce Says Users Will Never Log Into Your App Again
The MCP server decision carries retention consequences most product teams have not modeled yet
Salesforce turned Slack into a Model Context Protocol client that routes AI agent workflows across rival vendors’ enterprise software, and co founder Parker Harris told the audience that users may never need to log into Salesforce again. That statement is not a product roadmap aspiration. It is an architectural declaration that the AI interface is separating from the AI engine, and whoever controls the conversation layer captures the user relationship, the workflow data, and the switching costs that used to belong to the application itself. For every vertical SaaS company, the decision to publish or withhold an MCP server now carries measurable consequences for usage data visibility, net revenue retention, and the cost of being displaced. Salesforce reported $800 million in Agentforce annual recurring revenue for fiscal year 2026, 300% growth in custom AI agents on Slack since early 2026, and $2.9 billion in combined AI ARR, while the broader MCP ecosystem has reached 97 million monthly SDK downloads and over 10,000 active servers under Linux Foundation governance.
Companies mentioned: Salesforce, Slack, Microsoft, NVIDIA, Anthropic, Snowflake, Pure Storage, Dropbox, GitLab, Workday, ServiceNow, Cursor, Linear, DocuSign, Vercel, Notion, Google, Perplexity
Today’s Deep Dive covers:
What happens to a SaaS company’s retention economics when its workflows move from its own UI to Slack?
Where do the lock in points actually sit across the three competing orchestration layers, and which one captures your data?
How should SaaS operators evaluate the MCP server decision when both publishing and not publishing carry quantifiable risk?
