Map the 37 Claude sales skills to your sales stage, then stop custom-building what Salesforce can govern
Treat the new prebuilt sales skills as a stage-based execution layer, and build custom only when the CRM cannot enforce the action.
The sales-agent debate has a new default. Salesforce and Anthropic announced Claudeforce on August 26, 2026, with a Salesforce plugin inside Claude that includes 37 prebuilt sales skills for select pilot customers before a September 2026 open beta.
For RevOps, sales ops, and AI agent leads, the new tool changes the build-versus-buy decision. If an action can route through the CRM, the CRM should own it. If it cannot, build a narrow agent workflow. The 37 prebuilt sales skills include meeting preparation, deal health review, and pipeline review as examples.
The control-plane test
The core claim is simple. Salesforce says actions taken through the plugin are routed back through Salesforce so business rules are enforced at the point of execution.
For CRM automation, that changes the default. Salesforce says the routing keeps business rules enforced at the point of execution.
Stage mapping: where the skills fit
Map each skill to a sales stage before you assign it to a team. The stage determines the risk. The control plane determines the permission. The build cost determines the urgency.
- Prospecting and outreach. Use skills that prepare context, rank accounts, and draft next actions. Keep send, suppression, and consent rules in the CRM. If the skill cannot respect those rules, do not let it touch the send path.
- Qualification and opportunity creation. Use skills that summarize meetings, extract requirements, and flag missing fields. Let the CRM own opportunity creation, stage entry, and required fields. If the agent can create an opportunity without validation, the pipeline will drift.
- Deal health and pipeline checks. Use skills that surface risk, stale activity, and next-best action. Keep forecast changes, discount approvals, and owner reassignment behind CRM permissions. A pipeline check is only as good as the audit trail behind it.
- Close and handoff. Use skills that prepare close checklists, renewal notes, and handoff summaries. Keep contract terms, pricing, and customer data access governed by the CRM. If a handoff cannot be traced, it is not a handoff; it is a leak.
Build only what cannot be governed
Salesforce describes AIforce as a trusted enterprise harness that exposes business data and workflows to agents through MCP servers, APIs, and command line tools, without what the company characterises as complicated and costly custom integrations.
Administrative setup for the plugin is described as a single connection performed once by an administrator, with authentication and permissions managed centrally.
Use this rule for every skill:
- Score stage fit. Does the skill match a stage where the action is repeatable and high-volume? If not, keep it manual or experimental.
- Score execution control. Can the CRM enforce permissions, required fields, audit logs, and business rules at the point of execution? If not, do not automate the action yet.
- Score build cost. Can you adapt the prebuilt skill with data mapping, field labels, and stage rules? If yes, adapt. If the workflow cannot route through the control plane, build a narrow custom agent.
The build decision should be conservative. Prebuilt skills are useful when they reduce manual work without creating a parallel system. Custom agents are useful when the workflow is outside the CRM, such as a source system, a compliance check, or a non-CRM workflow. The moment a custom agent can write back to the CRM, it should route through the same permissions and audit path as the prebuilt skill.
Do not let the agent become a parallel source of truth. If the CRM does not know the action happened, the action did not happen for RevOps. If the user cannot see why the action happened, the action is not auditable. If the business rule can be bypassed, the automation is a liability.
The next step is a stage-by-stage inventory. List the skills you will use. Map each to a stage, a CRM object, a permission set, and an audit event. Then decide: use, adapt, or build. The goal is not to deploy every skill. The goal is to deploy the skills that make the sales process faster without weakening the control plane.