Salesforce and Anthropic have launched Claudeforce, an expanded partnership whose first product is Salesforce in Claude: a Claude plugin with 37 prebuilt sales skills. Salesforce says the product is available to select pilot customers now, with an open beta planned for September 2026.
The number matters because these are not just prompts for writing emails. Salesforce publicly shows skills for daily briefing, pipeline review, forecast narrative, meeting preparation, deal-health review, win/loss analysis, activity logging, and Salesforce hygiene. The company says those skills can reason over live revenue context and route actions back through Salesforce.
For B2B sales and RevOps teams, that changes the operating question. When we covered Salesforce’s 2026 State of Sales, the story was whether sales teams were moving from AI assistance to agent use. Claudeforce moves the question downstream: which sales skills should be allowed to read, recommend, or write to the CRM, and who governs each level of autonomy?
Direct answer — what does Salesforce in Claude change for RevOps?
Salesforce in Claude packages 37 common sales workflows as prebuilt Claude skills connected to live Salesforce context. The practical shift for RevOps is from building one-off AI integrations to governing a catalog of repeatable capabilities. Salesforce remains the system enforcing permissions and business rules, while teams decide how much write-side autonomy Claude gets.
Key Takeaways
- Claudeforce launches with Salesforce in Claude, a plugin containing 37 prebuilt sales skills.
- Named examples include pipeline review, forecast narrative, meeting prep, deal-health review, activity logging, and Salesforce hygiene checks.
- Salesforce says actions are routed through Salesforce so existing permissions and business rules still apply.
- The product is in select pilot access now, with an open beta planned for September 2026.
What Salesforce Actually Launched
Claudeforce is the partnership. Salesforce in Claude is the first product under it. That distinction matters because the current release is narrower than the partnership headline: it starts with sellers and 37 sales skills, while Salesforce says additional skills for Service, Marketing, and Commerce are coming later.
The product is built on the same architecture IVRIS covered in Salesforce Headless 360. Salesforce says Claude connects through Headless 360 using a secure Model Context Protocol connection, so Salesforce data, workflows, permissions, and business logic can be exposed without rebuilding them inside Claude.
The public Claudeforce page also says onboarding can read a seller’s Salesforce context, Slack context, and other Claude connectors to surface accounts, pipeline, and live data in generated views. Salesforce and Anthropic say they first assembled similar workflows internally with MCP servers, skills, and authentication, then productized that setup for customers.
Why the 37 Sales Skills Change the RevOps Job
Our read: the 37 is not important because it is a large number. It is important because Salesforce is packaging sales work into named capabilities. That gives RevOps something more concrete to govern than an open-ended chatbot.
A pipeline-review skill mostly reads and analyzes. A meeting-prep skill assembles context. Activity logging and pipeline updates can change the system of record. Those are different risk classes even if they all appear in the same Claude interface. The useful control model is therefore skill by skill: what data can it read, what action can it propose, what can it write, and when must a human approve?
That is a more operational version of the copilot-versus-autopilot decision in our AI agents for RevOps guide. Instead of deciding whether “Claude” is trusted in general, teams can decide whether specific sales capabilities are trusted for specific records and actions.
The Hidden Catch: Read Access Is Not Write Authority
Salesforce’s own documentation makes the governance boundary unusually explicit. It says actions run through Salesforce so company business rules are enforced, and its Claudeforce FAQ says customers control how much autonomy Claude has on the write side and when updates are made inside Salesforce. That is the part RevOps should treat as the product, not a setup detail.
It also means a clean demo can hide a messy operating model. A rep may be happy to let Claude summarize a deal, but an automated next-step update, forecast change, or activity log can affect downstream reporting, compensation, routing, and manager inspection. The same interface does not make those actions equally reversible.
Salesforce has not published independent performance data showing how the 37 skills affect conversion, forecast accuracy, or seller productivity. The current evidence establishes availability, architecture, and intended workflows. It does not establish business impact.
What Sales and RevOps Teams Should Do Before September
- Classify the skills by authority. Separate read-only analysis, draft/recommendation work, and CRM write actions. Do not apply one approval rule to all 37.
- Pilot against three workflows, not the whole catalog. Pipeline review, meeting prep, and activity logging give you three different risk levels to test without turning the pilot into an organization-wide rollout.
- Audit the Salesforce side first. Check role hierarchy, permission sets, required fields, validation rules, and automation that can fire after a record change. Claude can only be as safe as the rules it is inheriting.
- Measure correction, not just speed. Track how often reps accept, edit, or reverse Claude’s suggestions and writes. A faster workflow that creates more cleanup is not an operational win.
Claudeforce is a meaningful step because it makes agentic CRM work easier to deploy, but easier deployment raises the value of tighter governance. For RevOps, the September beta should be treated less like a chatbot rollout and more like the arrival of 37 new callable business capabilities.
Frequently Asked Questions
Claudeforce is Salesforce and Anthropic’s expanded partnership for bringing Salesforce data, workflows, business logic, and governed actions into Claude. Its first product is Salesforce in Claude, a seller-focused plugin with 37 prebuilt sales skills. Salesforce says the partnership will expand to additional business functions over time.
Salesforce has highlighted skills including daily briefings, pipeline reviews, forecast narratives, meeting preparation, deal-health reviews, win/loss analysis, activity logging, and Salesforce hygiene checks. The broader point is that the plugin packages recurring seller workflows as named capabilities rather than leaving every rep to build custom prompts and integrations.
Salesforce says Salesforce in Claude is available to select pilot customers now and is planned for open beta in September 2026. The initial release focuses on Sales. Skills for Service, Marketing, and Commerce are planned later, so teams should not treat the current seller plugin as a generally available cross-cloud release.
