Your CRM is turning into a back end. Plan for the users who never open it
Microsoft shipped 30 Dynamics 365 CRM skills for Copilot and Salesforce launched AIforce. Both bet that people will reach the CRM from chat and AI tools, which makes your data model and business rules matter more than your page layouts.
For most of my career, a CRM project ended with screens: page layouts, list views, a Lightning app for each team, a dashboard for the VP. We measured adoption by logins. Over the last few weeks, the two biggest CRM vendors have both said, fairly openly, that the screen won't be the main way people use the CRM anymore.
Two vendors, one bet
On 8 October Microsoft announced 30 pre-built CRM skills for Copilot Cowork, now generally available. The skills draw on more than 180 generally available tools across Dynamics 365 Sales, Customer Service and Customer Insights. Microsoft's own wording is that customer intelligence "should move with the business—not remain locked inside" the CRM. Its post describes a stack of three layers. Dynamics 365 holds the data and business logic. Model Context Protocol (MCP) tools expose that context and approved actions. Skills add task guidance on top: what evidence to weigh and what a useful answer looks like.
Salesforce got there first, at Dreamforce on 16 September, with AIforce, which it calls "a live interface layer". The press release is blunt about it: "people don't have to come to Salesforce to get work done. Salesforce comes to them – in Claude, Slack, Lightning, or wherever they want to work." It launched with Claudeforce, Slackforce and Agentforce Coworker. Salesforce says every request runs on existing permissions and business rules, so an agent only sees what the person asking can see.
Then on 12 October Salesforce signed a definitive agreement to acquire Loops, an AI analytics platform that monitors metrics and explains why they change. Salesforce says Loops can be triggered from Slack and email. The theme is the same again: insight delivered where people already work, not in a separate tool they have to open.
Microsoft's tool vs skill line is the useful part
I found one passage in Microsoft's post more useful than any of the launch headlines. It separates a tool from a skill. Retrieving an opportunity record is a tool action. Working out why a deal has stalled is a skill, because it has to interpret context and structure a recommendation.
That's a good way to think about your own org. Your objects, fields, validation rules and Flows are the tools. The judgement your best rep or best support lead applies is the skill. Vendors now ship generic skills like "deal rescue" and "case triage". Those skills can only be as good as the records they read.
Microsoft also draws a clear line between what AI recommends, what a user approves and what actually changes. "A proposed update should not appear as a saved change, and a draft should not appear as a sent message." I'd make that a test case on any project that puts an AI front end over a CRM.
What this changes for an architect
I've built portals, LWC tools and plenty of integrations, so I'm not saying UI work is over. But if more people reach the CRM through Slack, Teams, Claude or Copilot, a few things move up my list.
- The data model is the product. An AI layer reads field names, descriptions, picklist values and relationships to work out what things mean. A field called
Status_2__cwith no description was always annoying. Now it actively confuses the model reading it. Clear names and filled-in descriptions are cheap and pay off quickly. - Business rules have to live in the platform. Both vendors stress that actions go back through the system's own permissions and logic. If an important rule only exists in a page layout, or in a rep's head, a chat interface will skip right past it. Put it in validation rules, Flows or Apex where every route has to obey it.
- Permissions decide who sees what. Salesforce says an agent sees only what the person asking can see. That's a strong promise, but it means your sharing model now decides what every conversational surface shows. Get it right before you turn these tools on.
- Logins stop measuring adoption. If a manager asks Slack about pipeline and never opens Salesforce, a login report says nobody uses it. RevOps teams will need to measure actions and outcomes instead.
The takeaway for CRM and RevOps teams
I don't think the CRM is going away. Both announcements say the opposite. Microsoft calls Dynamics 365 the "system of action", and Salesforce's whole pitch is that its data and rules matter more once they can be reached from anywhere. What's changing is where the value sits. Less of it is in the screens and more is in clean data, clear definitions and rules the platform enforces.
So in your next planning cycle, take some budget from new layouts and put it toward three things. Field hygiene and descriptions. Moving business rules out of people's heads and into the platform. A sharing model you'd be happy to have read aloud in a Slack channel. Those are what make the new interfaces useful instead of risky, whichever vendor you're on.