The Destination
CRM functions primarily as a capability layer — backend + APIs. Users interact through Slack, email, custom apps, agents. Logging into the CRM UI is rare and specialized.
Stage 1: Surface Key Capabilities
Expose the top 5 user workflows as APIs. ‘Create lead’, ‘update opportunity’, ‘query pipeline’, ‘draft follow-up email’, ‘escalate case’. Each becomes callable from non-CRM surfaces.
Stage 2: Build Surfaces
Slack integrations for the top workflows. Email/Outlook integrations. Mobile apps as needed. Agents (Agentforce, Copilot, custom) call the APIs. Users experience the capabilities, not the UI.
Stage 3: Rationalize
As non-UI usage grows, deprecate UI paths that nobody uses. Simplify the CRM UI for power users and admins. Full capability-layer architecture takes years; value flows throughout.