Claudeforce (Salesforce in Claude)

What it is

Claudeforce is the name Salesforce and Anthropic gave their expanded partnership on 26 August 2026, and in practice it means one product: Salesforce in Claude, a plugin that puts a seller’s accounts, opportunities and pipeline inside Claude under that seller’s existing Salesforce permissions. It ships 37 prebuilt sales skills — morning brief, call prep, deal review with a dated mutual close plan, post-meeting follow-up, pipeline dashboards, forecast narrative — plus bundled Salesforce and Slack connectors. It went to open beta on 15 September 2026, and as of 9 October 2026 it is still beta: it runs in Claude chat and Claude Cowork on web and desktop, not in Claude Code. Every capability claim on this page is dated to that beta and should be re-checked before you sign anything.

The partnership’s other two pieces — Claude as the default model in Slack and as a default reasoning model in Agentforce — change what powers products you may already own. They are not something you buy separately.

Why it shows up in ops stacks

The Reddit question is fair: Salesforce’s hosted MCP servers have been GA since 29 April 2026 for Enterprise Edition and above, and any admin can point a Claude custom connector at platform/sobject-reads in an afternoon. So what does the plugin add?

• The skills, not the connection. A raw connector gives Claude CRUD on records. The plugin gives it opinionated sales procedures — what to read before a call, how to score a deal, which fields a follow-up should update. A first-run setup skill builds a role-specific Artifact from the seller’s own book. That is weeks of prompt and skill engineering a RevOps team would otherwise own and maintain.
• One admin connection, per-user identity. The admin connects Salesforce once through an External Client App and assigns the plugin by Claude group; each rep then signs in with their own Salesforce login. Reads inherit object, field-level and sharing rules — Salesforce’s line is that if you can’t see the record, neither can the MCP server.
• Approval before writes. By default Claude proposes each change and the seller approves it before it lands in Salesforce, which remains the system of record.

Anthropic reports GitLab, Siemens and Legora as deployed customers and about 7,000 Salesforce sellers using it internally. Those are vendor figures.

Pricing reality

There is no Claudeforce price, and Salesforce’s Patrick Stokes acknowledged at launch you can’t buy it on one piece of paper. You pay two vendors:

• Anthropic — a paid Claude seat per user. Anthropic’s guide says all paid plans qualify; Team lists at $25/seat/mo ($20 annual) and heavy daily use pushes reps toward premium seats or Max, as on Claude Cowork.
• Salesforce — the beta requires the latest Sales Cloud Enterprise edition, which lists at $175/user/mo. Hosted MCP traffic draws on your org’s existing API request limits; Salesforce prints no per-call MCP price today, but “Headless Platform Interaction” already sits on its rate card unpriced, with 30 days’ notice promised before metering starts.

Real-world band for a rep who already has Sales Cloud Enterprise: $20–$125 per user per month of new spend, entirely on the Claude side, plus admin time. If you are on Pro Suite, the edition upgrade dwarfs everything else.

Best for

RevOps leaders at Salesforce Enterprise shops whose AEs already live in Claude, who want reps doing call prep, deal reviews and CRM updates from one surface without RevOps writing and maintaining the skills. The scoped case where it wins: a 20–200 seat AE team on Sales Cloud Enterprise with Claude Team or Enterprise already licensed, where the goal is fewer tab switches and better-kept opportunity fields, not autonomous selling.

Not for

Autonomous or customer-facing work — that is Agentforce, by Salesforce’s own framing. Bulk data jobs: hosted MCP creates one record per call, so “update 5,000 opportunities” belongs in a Flow or an n8n job. And teams below Enterprise Edition, or orgs that need a signed GA contract before rollout.

Versus the alternatives

• A free custom connector to Salesforce hosted MCP — the route Redditors are pointing at. Pick it when you have one technical RevOps owner, need only reads or a narrow write set, and want to choose exactly which server (sobject-reads versus sobject-mutations) is exposed. You give up the 37 skills and the managed setup.
• Salesforce Agentforce — the incumbent agent layer inside the CRM. Pick it for agents that run without a human in the loop or face customers, and when you want one Salesforce contract instead of two invoices.
• Microsoft 365 Copilot with the Sales agent — the other assistant-side incumbent. Pick it when sellers work in Outlook and Teams rather than Claude; note its Salesforce connector is read-only and write-back needs the separately licensed Sales agent.
• Day.ai — the entrant with the most momentum, an AI-native CRM that raised a $20M Sequoia-led Series A in February 2026. Pick it if you are under about 50 sellers and willing to replace the CRM rather than wrap an AI around it.

Watch-outs

• The two vendors’ documentation disagrees. As of mid-September 2026, Salesforce’s Winter ‘27 release note described the plugin as read-only and requiring Claude Enterprise, while Anthropic’s guides describe approved writes on all paid plans. Guard: run the pilot read-only in a sandbox, then confirm write support and plan eligibility in writing with your Salesforce account team before enabling it on production records.
• An approval prompt is not an informed approval. A prompt that shows only a generic dispatch call gives the rep nothing to check. Guard: keep pilot users off admin profiles, restrict the External Client App to a permission set with only the objects reps need, and have reps reject any write whose target record and new value are not shown.
• Audit trails don’t join up. Salesforce logs hosted MCP calls (API_CLIENT_CATEGORY = SALESFORCE_HOSTED_MCP) by user, but there is no shared correlation ID with Claude’s side, so the log proves which identity wrote, not who approved. Guard: on Claude Enterprise, retain Compliance API exports and sample-match them against Salesforce API logs monthly during the beta.