Between October 6 and October 8, Microsoft, Google and SAP each described the same change in where work begins. A worker no longer opens the business application to find the record and act on it. The worker asks an assistant, and the application answers from behind it. Microsoft’s Jeff Teper put the reversal in one sentence, and Google and SAP described the same direction the same day.
This feature goes through what each vendor said, what the sources show and do not show, and what a revenue team should decide before the next renewal. The short version of our read: the system of record is not going anywhere, but the screen where sellers spend the day, the meter that bills for it and the console that governs it are all moving to whoever owns the assistant.
What the three vendors announced
Microsoft: CRM goes to where the rep already works
Teper, executive vice president of Microsoft Apps and Agents, wrote on the Microsoft Copilot blog that people used to go to their CRM to find customer context, take action and move work forward. “AI is inverting that model,” he wrote. Microsoft’s label for the result is “agentic, headless CRM,” which it defines as keeping the CRM as the trusted foundation for customer data and business processes while bringing expertise, insights and actions into the places people already work.
Advertisement
The announcement has three concrete parts. First, 30 new pre-built skills across Dynamics 365 Sales, Customer Service and Customer Insights. Sellers can use them to surface at-risk deals, develop account engagement plans and propose CRM record updates for review. Microsoft says the skills are generally available in Cowork, in private preview in Autopilot and available through the Frontier Program in Code, and that they run on Dynamics 365 model context protocol servers.
Second, Dynamics 365 CRM in the flow of Teams, now in public preview. Once a Teams channel is connected to a customer account, agents can deliver updates such as pre-meeting briefs, case notifications and account developments. Third, the Sales Development Agent, in public preview, which Microsoft says is managed in Teams, sends email from its own Exchange account and connects to leading CRM platforms. It starts consuming Copilot credits on November 16, 2026.
Christian Lewis, Managing Director and Commercial Hub Co-Lead at BNY, described the Teams use case this way: “By surfacing account insights, service updates, and important client developments in real-time, our teams can stay aligned, make informed decisions, and take action without switching applications.” Prabhath Yeluri, Senior Manager of Sales Strategy at Adobe, reported that the Sales Development Agent “has already unlocked new opportunities, driving meetings with 10+ customers we wouldn’t have otherwise reached” in three weeks from a limited-scale launch.
Google: work starts in the prompt window
On the same day, Google Cloud CEO Thomas Kurian introduced the Gemini agent in a post on the Google Cloud Blog adapted from his Gemini at Work keynote. His framing is blunt: “Work now starts in the prompt window.” The agent takes objectives, and Kurian says “You give it objectives, not instructions.”
For a sales organization, the relevant details are about connection and identity. Google says the agent can connect to enterprise platforms like Salesforce and ServiceNow, and that its lakehouse can read directly from Salesforce Data 360, SAP and Workday without copying data. It can run as a headless agent that does not need a dedicated user interface, and Google says it can be reached from Google Workspace, Microsoft 365 and Slack. Its coworker agents get dedicated identities, including their own @agents.company.com email addresses. Google also reports that nearly 90% of the Fortune 100 use Gemini Enterprise.
That email detail connects to something we covered earlier. We covered Zoho’s version of this in AI Sales Reps Now Get Their Own Email Address, where a sales agent got its own address and audit trail as a product feature. Microsoft’s Sales Development Agent and Google’s coworker agents now do the same inside platforms that most large companies already run.
SAP: Joule Work reaches every customer this month
Brenda Bown, chief marketing officer for SAP Business AI Platform and Joule, wrote on SAP News Center that all SAP customers will get Joule Work when it rolls out later this month. SAP’s example comes from Reinhausen, a maker of grid equipment. Peter Wied, director of Complexity Management there, said: “What once required up to an hour of manual effort across our SAP S/4HANA environment is now accessible in seconds through natural language, fundamentally changing how our teams interact with business data.”
Two other items in the SAP post matter more to a revenue team than the headline rollout. SAP Reltio is now generally available in SAP Business Data Cloud, which SAP says helps organizations eliminate fragmented records with a single trusted view of customers, suppliers, products and employees across SAP and non-SAP systems. And SAP AI Agent Hub, also generally available, is described as helping organizations govern every agent, LLM and MCP server across SAP and non-SAP environments.
Salesforce makes the same argument from the chat window
Salesforce is making the case from a different surface. In a September 22 interview with Alex Heath of the Sources podcast, posted on Salesforce’s news site, CEO Marc Benioff said Salesforce bought Slack because it saw agents coming. “Our premise was that it was going to be the agent for business,” he told Heath. The same page says Claude is now the default model in Slack, including Slackbot, and that the Claudeforce partnership brings Salesforce sales workflows directly into Claude.
Benioff also described where he expects the interface to go. He told Heath that static screens will not stay static, and that software will feel “live or living.” Read next to Teper’s “inverting that model,” the two CEOs are describing the same destination from opposite directions. One is putting CRM into the collaboration app. The other is putting the collaboration app in front of CRM.
Where the announcements agree, and where they split
All four sources agree on three points. The record stays in the application: Microsoft says the CRM remains the trusted foundation, Google connects to Salesforce and SAP as systems of record, and SAP grounds Joule Work in its own platform. The assistant is the place requests begin. And agents act, rather than only answer: proposing record updates, sending email, running multi-step plans.
They split on who runs the assistant. Microsoft routes through Copilot and Teams, SAP through Joule Work, Google through its own agent that reaches into Microsoft 365 and Slack, and Salesforce through Slack. Google’s agent connects to Salesforce and Microsoft’s Sales Development Agent connects to what it calls leading CRM platforms. Our reading is that a company on one vendor’s CRM can end up taking its daily interface from another vendor. They also split on governance. Microsoft points to Agent 365, SAP to AI Agent Hub, and Google lists identity and policy management, authorization and permission controls among the ways it secures and governs agents. SAP’s description is the most explicit about reach: it says AI Agent Hub covers agents, LLMs and MCP servers across SAP and non-SAP environments.
The interpretation that follows is ours, not any vendor’s. A seller who starts in an assistant generates fewer logins to the CRM, and the vendors that own the assistant gain the view of what that seller does. The system of record keeps the data. The assistant layer keeps the behavior: which questions get asked, which deals get flagged, which emails get drafted.
The strongest objection: most of this is preview
A skeptical reader will point out that most of the Microsoft announcement is not generally available. The Teams experience and the Sales Development Agent are in public preview, Autopilot is in private preview, and Code is available through a program for early access. Service Agent in Microsoft 365 is a private preview for a select group of Frontier customers. A skeptic will also say that announcing an assistant is easier than changing how a sales team runs its pipeline review.
That objection is fair on timing and weak on direction. The 30 Dynamics 365 skills are generally available in Cowork today. SAP says Joule Work reaches every customer this month. Google announced the Gemini agent on October 8, with its financial services and legal versions in preview. More important, the commercial terms are already being set: Microsoft has put a date, November 16, on when its Sales Development Agent starts drawing Copilot credits. A billing date is a sign Microsoft expects the agent to move past preview, though the post does not say when. The conclusion is that the direction is settled and the pace is not, and that a revenue team’s planning horizon should be this fiscal year, not three years out.
What it means for the sales leader
Four consequences follow for anyone who owns a sales stack.
The seat count stops describing usage. If a seller works through Teams or a Slack thread, a per-seat CRM license counts logins that happen less often, while a credit meter counts work the agent does. In Stop Signing Token-Metered AI Sales-Tech Contracts we argued that token-based pricing hands vendor cost swings to your forecast. Microsoft’s November 16 date makes that concrete for one vendor, and the other vendors’ pricing for these agents is not in the sources we fetched.
Record quality becomes a ceiling on agent quality. An assistant that proposes record updates or drafts outreach from CRM context reads whatever the CRM holds. SAP put Reltio in the same post as Joule Work, and our reading is that record unification and the assistant are being sold as a pair. We made the same point about agents and bad data in Duplicate CRM Records Are Now an AI Agent Problem.
Governance splits across consoles. A company running Dynamics, Salesforce data in Slack and a Google agent will have agents in three places, each with its own permissions and audit trail. In Sales AI Vendors Now Pitch a Rules Layer Between Agent and Action we looked at one vendor’s split between reasoning and rules. With three vendors, someone in the company needs a view across all of them.
Outcome claims are still vendor claims. Adobe’s three-week result, Reinhausen’s hour-to-seconds result and Google’s customer figures are each reported by the vendor, with a customer name attached. None of the three posts says how the figure was measured. Revenue Software Vendors Now Pitch Outcomes as the Product set out the questions to ask about any such number, and they apply to all of these.
What to do before the next renewal
Start with an inventory of where your sellers actually begin the day. Pull a month of CRM logins against activity in Teams, Slack and the email client, by role, and see whether the CRM screen already holds a minority of the working time. The answer decides which assistant surface deserves a pilot.
Then write down three questions for each vendor whose agent will touch your pipeline data. Where does the audit trail for an agent action live, and can your RevOps team export it? How is agent work billed, and what stops a runaway task from spending the quarter’s budget? Which other vendors’ CRMs does the agent connect to, and under what permissions?
Finally, schedule the record cleanup before the agent pilot, not after. Duplicate accounts, stale contacts and unowned opportunities are the cheapest problems to fix and the most expensive to discover through an agent that acts on them. A pilot with a baseline, a cap on spend and one named owner for the audit trail will tell you more in a quarter than any vendor keynote.
Source: Microsoft Copilot Blog
