Claudeforce Explained: What Salesforce in Claude Means for Your Org (2026)
Salesforce in Claude puts your live CRM inside Claude with 37 sales skills. We cover setup, permissions, Flex Credit costs, and who should pilot it.
TLDR: Salesforce in Claude (the centerpiece of Claudeforce) puts your live Salesforce data inside Claude through 37 prebuilt sales skills, and the open beta is live now on all paid Claude plans. Permissions mirror each user’s Salesforce profile and every write waits for approval by default, so the security model is sounder than most admins expected. But every agent call will consume Salesforce Flex Credits under a new metering model whose per-call multiplier still hasn’t been published — so run a scoped one-team pilot in read-only mode first, audit your data hygiene, and don’t sign any consumption commitment until Salesforce puts the rate in writing.
Why This Matters Now
On August 26, 2026, Salesforce told the world its customers may never need to open Salesforce again. Marc Benioff and Anthropic CEO Dario Amodei announced Claudeforce on stage together the same afternoon Salesforce reported earnings: a partnership that embeds the entire CRM inside Claude as a plugin called Salesforce in Claude.
Here’s why you can’t file this as just another AI announcement. The beta opened September 15 to all paid Claude plans, and Salesforce confirmed it at Dreamforce as part of its AIforce launch. Your sellers can request access this week. And days before the beta opened, Salesforce revealed that agentic MCP and API calls will consume Flex Credits under a brand-new Agentic Identity metering model — with the actual per-call rate still unpublished. That means the cost question your CFO will ask has no answer yet, and your pilot is how you generate one.
Claudeforce vs. Agentforce vs. Einstein: Which Is Which
The naming is doing real damage. Three different things share one press cycle, so here’s the map before anything else. Get this wrong and you’ll buy the wrong license.
| Salesforce in Claude (Claudeforce) | Agentforce | Einstein / Copilot | |
|---|---|---|---|
| What it is | Claude plugin with 37 sales skills that reads and writes your CRM | Salesforce’s own agent platform for customer-facing and workflow agents | Embedded AI inside Salesforce UI (summaries, scoring, predictions) |
| Where you work | Inside Claude (chat interface) | Inside Salesforce, portals, Slack | Inside Lightning pages and records |
| Who it’s for | Sellers and managers doing pipeline work | Service teams, customers, ops workflows | Reps working records one at a time |
| Reasoning model | Claude (served via Bedrock inside the Trust Boundary) | Your choice in Agent Builder; Claude now default for Vibes and Coworker | Salesforce models + partner models |
| Pricing | Two invoices: Salesforce headless consumption + Claude contract | Flex Credits consumption | Bundled in most editions |
| Status | Open beta since Sep 15, 2026 | Generally available | Generally available |
| Best for | Daily briefings, call prep, pipeline review without opening Salesforce | Autonomous customer-facing resolution | In-record assistance |
But here’s the part most coverage skips: these aren’t rivals. Salesforce’s own framing is that Claudeforce complements Agentforce — knowledge-worker productivity on one side, autonomous customer workflows on the other. The r/salesforce thread asking “what actually happens to Agentforce now” got the right answer from the community: Salesforce becomes the backend enterprise layer, Claude becomes one interface among several. Agentforce isn’t going anywhere. Your Agentforce investment is safe.
What the 37 Sales Skills Actually Do
The plugin exposes your org to Claude through skills — structured, prebuilt workflows, not free-form prompting. You describe the task and Claude picks the skill. Anthropic groups them into eight areas:
| Skill area | Example request | What you get |
|---|---|---|
| Daily briefing | ”What do I need to handle today?” | Meetings, at-risk deals, pending threads from Salesforce and Slack |
| Call preparation | ”Prep me for the 2 pm with Acme” | Account history, open opportunities, recent Slack and email context |
| Deal scoring | ”Score this deal against our methodology” | Gaps against your process plus a draft close plan |
| Follow-up | ”Update the opportunity from my notes” | Summary and proposed record changes, held for your approval |
| Pipeline dashboard | ”Show pipeline by stage with risk” | Interactive view generated in the conversation |
| Forecast | ”Draft my forecast narrative” | Commentary written from live pipeline data |
| Account research | ”Catch me up on this account” | History, stakeholders, open threads |
| CRM hygiene | ”Clean up my stale opportunities” | Proposed stage and close-date updates, approval-gated |
What’s missing matters as much as what’s here. These are sales-productivity skills only. Service, marketing, commerce, and field service packs are announced but not shipped. Revenue and quoting skills — the ones your CPQ team actually wants, described as quoting “with context and governed logic” — carry a “coming soon” label with late 2026 as the horizon. Quote-to-cash inside Claude is a roadmap promise, not a feature.
Earned insight: The launch testimonials Salesforce and Anthropic cite — GitLab, Siemens, Legora, Deloitte — are vendor-published, and Legora’s “briefings in seconds instead of hours” line tells you nothing about data quality underneath. In every Salesforce org I’ve worked with, pipeline hygiene is the binding constraint on any AI summary tool: duplicate accounts and stale stages produce confident, wrong briefings. The approval gate catches bad writes, not bad reads. Clean your pipeline before the pilot or you’ll benchmark the tool against your own dirty data.
Setup: What Your Admin Actually Has to Do
The setup story is better than most enterprise AI launches. One admin connection covers the whole org — no per-user MCP tokens, no homegrown prompts to maintain. The steps:
- Request access through AgentExchange. The plugin is distributed via Salesforce’s marketplace, so the admin starts there, not inside Claude.
- Connect Salesforce once for the organization. One admin-managed connection centralizes authentication.
- Scope it to groups. Assign the plugin to one sales team for the pilot. Don’t turn it on org-wide on day one.
- Optionally connect Slack. Deal-channel context improves briefing quality substantially. But it widens what Claude can read, so add it deliberately — not by default.
- Sellers sign in with their own Salesforce credentials. They install nothing. Skills appear in Claude once their group is enabled.
The beta runs on all paid Claude plans, but note the catch from Anthropic’s own docs: there’s no self-service route for an individual on a Pro plan. A solo seller’s only path is asking their admin. This is an organizational tool wearing a chat interface.
Earned insight: Run the first three days read-only. Use briefings, call prep, and account research — and decline every proposed write. You learn what Claude gets right about your data before letting it touch anything. Day three, test deal scoring: it’s the fastest check of whether the skills understand your methodology, because a generic answer is obvious immediately. Only on days four and five should one experienced rep approve writes, comparing records against what they’d have entered by hand. Teams that pool their working prompts in a shared doc outpace teams that start from scratch every session.
The Permissions Model (Better Than Expected)
Three defaults govern what Claude can do with your CRM, and all three favor the admin:
- Permissions mirror Salesforce exactly. A user can’t see or change through Claude what they couldn’t see or change in Salesforce. They authenticate as themselves. “If you don’t own that record, the MCP server doesn’t either.”
- Writes wait for approval. Claude drafts record changes but asks the seller to approve each one before writing. Companies can widen that autonomy later; the default is the conservative setting.
- No training on business data. Anthropic states it does not train on Team and Enterprise data by default.
Permissions Model Strengths:
- Inheritance means no parallel access system to audit — your existing sharing rules are the policy
- Approval-gated writes prevent the nightmare scenario of an agent bulk-updating your pipeline overnight
- Single admin connection replaces per-user tokens, which is how shadow AI access usually spreads
- Sandboxes and scratch orgs are excluded from agentic metering, so pilots cost nothing on the Salesforce side
Permissions Model Weaknesses:
- Inheritance also inherits your mess: over-permissioned profiles give Claude the same over-broad access your users already have
- Approval fatigue is real — reps who click “approve” on everything recreate the risk the gate was built to stop
- The upcoming Agentic Identity framework will give agents their own credentials instead of riding user identity, which means this model is transitional, not final
- Slack connector scope is a separate decision with its own read surface, and it’s easy to enable carelessly
Pricing Reality: Two Invoices and an Unpublished Multiplier
This is the section none of the launch-week explainers could write, because the pricing story changed in September. Here’s the full picture as of September 25, 2026.
Invoice one: Anthropic. You need a paid Claude plan. Standard Claude Team or Enterprise per-seat pricing applies. No per-seat add-on exists for the Salesforce plugin itself — it rides on the CoWork license.
Invoice two: Salesforce. Headless consumption is metered through Flex Credits. And here’s what shifted: Salesforce confirmed (via updated help documentation and Salesforce Ben’s September 23 coverage) that every successful MCP or agentic API call made by a registered agent counts as a “Headless Platform Interaction” consuming Flex Credits — tracked through Digital Wallet. Traditional integrations keep their existing pricing; only registered agentic traffic moves to the new model.
Three facts your CFO needs:
- The per-call multiplier is unpublished. Salesforce has not said how many Flex Credits one Headless Platform Interaction costs. You cannot model this. Salesforce promises 30 days’ notice before metering begins — and metering hasn’t started yet — but “30 days’ notice” on an unknown rate is cold comfort for budget planning.
- Consumption varies by agent behavior. Salesforce’s own statement: “the number of interactions charged depends entirely on the third-party agent’s behavior.” A verbose agent that re-queries your pipeline five times per briefing costs five times what an efficient one does. Your bill depends on prompt implementation you don’t control.
- Context: Core edition is now $195/user/month. Salesforce restructured editions September 3 (Core/Plus/Premium replacing Enterprise/Unlimited), with Core at $195 including bundled Flex Credits. Headless consumption for Claudeforce sits on top of whatever your edition includes.
| Cost component | What we know (verified Sep 25, 2026) | What’s unknown |
|---|---|---|
| Claude license | Standard paid-plan per-seat pricing | Whether a bundled Salesforce+Claude SKU appears |
| Salesforce headless consumption | Flex Credits per Headless Platform Interaction | The per-call multiplier — unpublished |
| Edition baseline | Core $195/user/mo with bundled credits | How many bundled credits each edition carries |
| Implementation | Admin setup is hours, not weeks | Cost of data-hygiene cleanup the pilot will surface |
| Metering start | 30 days’ notice promised; not yet billing | The actual start date |
Sources: Salesforce Flex Credits rate card (Aug 18, 2026); Salesforce Ben agentic metering coverage (Sep 23, 2026); Salesforce editions announcement (Sep 3, 2026); Salesforce help docs on Headless 360 architecture (Jul 29, 2026).
Warning: Do not sign any consumption commitment or Flex Credit true-up tied to Claudeforce until the Headless Platform Interaction multiplier is published in writing. Right now you’d be agreeing to a meter with no rate. Pilot in sandbox (excluded from metering), measure your interaction volume through Digital Wallet, and bring that data to your AE when the rate card lands.
Claudeforce Strengths:
- Genuinely eliminates the “10,000 clicks” daily workflow for sellers living in pipeline review and call prep
- Security model inherits your existing RBAC instead of inventing a parallel one — the single biggest enterprise adoption blocker, handled
- One admin connection for the whole team beats the per-user MCP token sprawl admins were already fighting
- Claude inside Agentforce and Slack is live today, so the partnership has shipped product on both sides, not just press releases
Claudeforce Weaknesses:
- Two-vendor billing with an unpublished consumption rate makes cost modeling impossible right now
- Sales-only skills at launch; service, marketing, and quoting teams get roadmap slides, not software
- Beta status means breaking changes are likely — piloting on production data without guardrails is reckless
- If the interface commoditizes, Anthropic holds the pricing leverage long-term, not Salesforce
Who Should Pilot Now, and Who Should Wait
Good fit — pilot this month:
- Sales orgs already on Claude Team or Enterprise, where the license cost is sunk and the incremental ask is only the Salesforce-side setup
- Teams drowning in pipeline review overhead — managers running Monday forecast calls off stale dashboards are the ideal first users
- Orgs with clean sharing rules and recent data-hygiene work, where permission inheritance is a feature rather than an exposure
- Salesforce admins who already experimented with DIY Claude-to-Salesforce MCP connections — this replaces fragile per-user tokens with a governed path
Not a good fit — wait for GA:
- Service, marketing, or CPQ teams: your skills haven’t shipped, and the revenue pack timeline (late 2026) will slip like every enterprise AI roadmap
- Orgs without Claude contracts: don’t buy two new vendor relationships to test a beta
- Companies in regulated industries needing data-residency answers: “served via Bedrock inside the Trust Boundary with zero data retention” is a claim to verify with your security review, not a checkbox to trust from a press release
- Anyone whose Salesforce profiles are over-permissioned: Claude inherits the mess, and the beta is the wrong moment to discover your sharing model is broken
Bottom Line
Claudeforce is the most consequential Salesforce announcement since Agentforce itself — not because the technology is exotic (it’s MCP packaging done well), but because Salesforce just blessed the idea that its own UI is optional. The permissions model is genuinely enterprise-grade, the setup burden is light, and the beta is open now.
But the pricing is a blank check until the Flex Credit multiplier publishes, the skills cover one department, and Anthropic’s long-term leverage over the interface should make every CIO slightly uneasy. Gartner’s warning stands: 40% of agentic AI projects won’t survive to 2028 on cost and ROI grounds, and an unmetered consumption pilot is exactly how you end up in that statistic.
Pilot with one sales team, read-only for three days, in a sandbox-adjacent scope with Digital Wallet tracking every interaction. Bring the volume data to your account executive and get the rate in writing before you expand. In the next 30 days, assign one admin to run the AgentExchange setup for a single team and deliver a measured interaction count your finance team can actually budget against.
Frequently Asked Questions
Does Claudeforce replace Agentforce?
No. They do different jobs. Agentforce runs autonomous customer-facing and workflow agents inside Salesforce; Salesforce in Claude is a knowledge-worker productivity tool for sellers inside Claude. Salesforce positions them as complementary, and Claude is now the default reasoning model for Agentforce Vibes and Coworker — the two products are converging technically, not competing.
Does Claudeforce require Claude Enterprise?
The beta runs on all paid Claude plans, but it’s an organizational tool: your admin connects it once and scopes it to groups. Anthropic’s docs describe no self-service route for an individual Pro user — a solo seller has to go through their admin. Whether Enterprise versus Team matters for your rollout is a scoping question for your Anthropic rep, not a technical gate.
Can Claude change records in Salesforce?
Yes. Follow-up and CRM-update skills draft changes to opportunities and records. By default every write waits for the seller’s approval, and Claude can only touch records the seller’s own Salesforce permissions allow. Companies can widen that autonomy, but the conservative default is the right starting point.
What does Salesforce in Claude cost?
Two bills, one unknown rate. You need a paid Claude plan plus a Salesforce contract, with headless API consumption metered in Flex Credits. Salesforce hasn’t published the per-interaction multiplier or the metering start date — only a promise of 30 days’ notice. Until the rate card lands, treat every cost estimate as provisional.
How is this different from connecting Claude to Salesforce with MCP myself?
Plenty of admins already wired up DIY MCP connections. The honest difference is packaging and governance: one admin-managed connection for the whole team, co-built skills instead of homegrown prompts, centrally enforced permissions instead of per-user tokens. The DIY route still works, but it won’t get the Agentic Identity tracking, revocation, or cost-optimization tooling Salesforce is building into the official path.
Does it work with HubSpot or Dynamics 365?
No. The 37 skills are Salesforce-specific. Claude has connectors to many tools, but neither company has announced equivalent skill packs for other CRMs. If you’re not on Salesforce, this announcement doesn’t change your tooling.
Is my Salesforce data used to train Claude?
Anthropic states it does not train on Team and Enterprise data by default. Claude models serving the Salesforce integration run through Amazon Bedrock inside the Salesforce Trust Boundary with zero data retention on the model family, with additional enterprise safeguards phasing in through fall 2026. Verify these claims in your own security review before connecting production data.
What happens to my DIY MCP setup when Agentic Identity launches?
Salesforce’s Agentic Identity framework will require agents to register with their own credentials rather than riding user identity, and MCP/API clients will need reconfiguring to OAuth credentials tied to the registered identity. Traditional integrations are explicitly excluded. Expect a migration notice with the 30-day metering warning — another reason to keep DIY setups in sandbox until the framework lands.
Related Articles
Discussion