On Tuesday, Marc Benioff stood on top of Salesforce Tower with Dario Amodei and announced that the #1 CRM now runs natively inside the #1 AI. Not a plugin buried in an app store. Not another copilot bolted onto a sidebar. The actual CRM – data, pipeline, workflows, permissions, actions – accessible entirely from inside Claude, with Salesforce's own president saying the quiet part out loud: the value "is not in our UI itself."

Wall Street's response: Salesforce stock closed up 22.6% the next day – its second-best day in company history, biggest single-day gain since August 2020.

The internet's response: everything from "this is how every business will run" to "so Salesforce is now a database with an expensive API?"

Both reactions are worth taking seriously. This guide covers what Claudeforce actually is, how it works under the hood, how to set it up, the highest-value use cases for sales and marketing teams, the limitations nobody puts in the launch video, and how B2B teams should actually reorganize the way they work.

TL;DR

• Claudeforce = Salesforce running natively inside Claude via a plugin with 37 prebuilt sales skills (meeting prep, deal health review, pipeline review), plus Claude becoming the default AI across Agentforce and Slack
• The killer feature isn't chat – it's governance: one admin connects the org once, every rep inherits their exact existing Salesforce permissions automatically. The permissions problem that killed self-serve MCP is gone
• Claude can generate live dashboards and mini-apps on the fly from your CRM data – "the UI is the AI"
• Rollout: select pilots now → open beta September 2026 → marketing/service/commerce skills late 2026
• Real limitations: beta software, sales-only at launch, two separate invoices with no disclosed pricing, dirty CRM data becomes confident wrong answers, and the whole thing was validated on Anthropic's young, clean org – not your 12-year-old instance with 40,000 zombie records
• The teams that win won't be the ones that "add AI." They'll be the ones that treat data hygiene, permissions, and prompts as revenue infrastructure – this guide ends with a 30-60-90 plan

What happened (and why Wall Street lost its mind)

On August 26, timed with Q2 earnings, Salesforce and Anthropic announced Claudeforce – the first time in 27 years Salesforce has ever attached its "force" suffix to another company's product.

The partnership has four pillars:

1. Salesforce inside Claude – the flagship "Salesforce in Claude" plugin for Claude CoWork
2. Claude inside Salesforce – Claude as a reasoning model across Agentforce (default for Agentforce Vibes and Coworker)
3. Slack – Claude is now the default model powering Slackbot, Claude Tag, and the new Slack Code
4. Mutual adoption – Anthropic runs on Salesforce; Salesforce gives Claude Code + Claude Enterprise to its entire workforce

Benioff's framing, verbatim: "Here, the UI is the AI… Probabilistic intelligence alone doesn't run a company, and deterministic systems don't reason. By fusing Claude's extraordinary reasoning with the trusted data, workflows, and governance every enterprise runs on, we're delivering a dynamic interface that thinks, reasons, and acts. This is how every business will run".

The money context matters for reading this correctly: Salesforce holds a stake in Anthropic reportedly valued around $5 billion and plans to spend roughly $300 million on Anthropic tokens this year. Anthropic hit a $65B annualized revenue run rate at end of July – 7x year over year – and leads enterprise AI spend share at 40% vs OpenAI's 27%. This is two market leaders locking arms against the "SaaSpocalypse" narrative – Benioff, on the earnings call: "This nonsense of the SaaSpocalypse, I think it's time for it to stop".

Worth noting for balance: the euphoric GAAP quarter leaned on a $2.6B investment gain tied partly to that Anthropic stake, and analysts cautioned the rally rests on "one report and one partnership". Retail euphoria and fundamentals are not the same thing.

What Claudeforce actually is (plain English, no keynote fog)

Strip the branding and it's this: Claude can now read from and write to your Salesforce org, under your exact permissions, using skills that encode how good sellers actually work.

The pieces, decoded:

• Salesforce in Claude – a plugin for Claude CoWork with 37 prebuilt sales skills built jointly by both companies: meeting prep, deal health review, pipeline review, and 34 more. Salesforce's pitch: every seller gets "an AI CRO"
• AIforce – Salesforce's "enterprise harness": the governance and security layer that brings business data and workflows to any agent through MCP servers, APIs, and CLI tools
• Headless 360 – the architecture (announced at TDX this spring) that exposes the full platform as APIs, MCP tools, and CLI commands so agents can use Salesforce with no UI at all. Salesforce co-founder Parker Harris introduced it by asking: "Why should you ever log into Salesforce again?"
• Data 360 – the "System of Context": unified, real-time business data that grounds every answer
• Tableau – trusted metrics, alerts, publish-back. Marked "Coming Soon"

The most underrated detail: the whole thing is productized from Anthropic's own internal setup. Salesforce's Patrick Stokes: "We sat down with Anthropic… and they said, 'Hey, this is actually how we're using Salesforce. We use Salesforce pretty much exclusively through Claude and a series of skills and MCP servers'". Anthropic's CRO Paul Smith: "I use Salesforce Claude every day".

That's real validation – with one honest caveat that The State of AI nailed: Anthropic's org is young and clean. It never survived a decade of migrations, acquisitions, and admin turnover. "The deployment that proved the concept has the least of what the concept depends on". Your 2014-vintage org with three generations of custom fields is the actual test. Keep that in mind through every use case below.

The architecture in 60 seconds (and why "isn't this just MCP?" misses the point)

The top skeptic question on r/ClaudeAI: "Isn't Claudeforce just Salesforce MCP set up within Claude?". Technically adjacent, practically wrong. Here's what's under the hood:

The Headless 360 Hosted MCP Server exposes just four tools: discover (semantic search over every Salesforce operation), describe (returns the operation's spec), dispatch (executes it), and dispatch_readonly (read-only version). Claude reasons over which skill applies, discovers the right operation, and executes – with every call running as you, inheriting your exact Salesforce permissions. Stokes: "If you don't own that record, if you don't have permission to see that record, the MCP server doesn't either".

Why the difference from DIY MCP matters commercially:

• Raw MCP is plumbing. This is a finished, governed product. Anyone who wired a custom Salesforce MCP server after TDX hit the same wall: every individual user had to configure it, and permission handling was on you. The plugin kills that – one admin connection, everyone inherits access
• The skills are the product. 37 encoded sales workflows tuned for Claude's reasoning and tool use – "not generic CRM prompts wrapped around an API"
• Writes are governed. Every action routes through Salesforce so validation rules, Flows, and Apex triggers all still fire. An agent write is ordinary DML – same guardrails, same audit trail
• Trust posture: Zero Data Retention – no Salesforce data retained inside Claude, no model training on it – and Claude runs inside the Salesforce Trust Boundary via Amazon Bedrock, the first LLM fully inside it

And the demo everyone's talking about: a Salesforce PM asked Claude to build a full sales "command center" dashboard – which Claude coded on the fly as a local HTML file from live Salesforce data, styled "like Miami Vice, like Tron" on request. Stokes: "This isn't like a product that we're shipping. This is Claude coding this on the fly using Salesforce data". Fair caveat from the practitioner press: the demo ran on fictional data, and "whether that survives contact with real users is an open question".

How to set it up

There are two different routes with two genuinely different security postures, and the marketing does not distinguish them. This is the distinction that will bite someone at your company if you don't catch it now.

Route 1 – Salesforce in Claude plugin (per-user, the Claudeforce flagship):

1. Get in line: select pilots now, open beta expected September 2026
2. One admin connects Salesforce in Claude a single time for the org – authentication and permissions managed centrally
3. Every seller gets access from day one. Each user authenticates via per-user OAuth (an External Client App with the mcp_api scope), so every single call runs as that person with their existing permissions – no per-user setup, no new permissions model, no re-auditing account by account
4. Admins set how much write autonomy Claude gets and when it updates Salesforce
5. First run: Claude reads the seller's enterprise context – Salesforce, Slack, other connectors – and stands up a personalized dashboard with their accounts and pipeline

Route 2 – Claude Tag in Slack (agent-owned credential):

1. In Salesforce: create a connected app with the OAuth 2.0 client-credentials flow and a dedicated integration user as run-as; grab Consumer Key, Secret, and your My Domain host
2. Scope that integration user with a Permission Set covering only what Claude should reach – the docs themselves recommend starting read-only
3. In Claude admin settings → Claude Tag → Access bundle → Credentials → connect Salesforce with the Client ID, secret, and token URL – and replace the example allowed-websites host with your real org host "or every request fails"
4. Verify: @Claude list the five most recently modified Opportunities in Salesforce, then check the integration user's login history

The critical difference: Route 1's credential belongs to each person; Route 2's credential belongs to the agent – one integration user acting for everyone in the bundle. Different blast radius, different audit story. Know which one you're rolling out.

Pricing reality check (woven in, because it belongs here): there is no unified price. Salesforce bills via headless consumption (API-call allotments scale with your edition), and you separately contract with Anthropic for Claude inference. Stokes, candidly: "You can't buy this on one piece of paper at the moment". No list pricing has been disclosed anywhere. Your CFO now has a token line item, and analysts are already calling token metering "a procurement trigger" for CIOs. Budget for both invoices before you scale the pilot.

The 12 use cases that matter for sales teams

Ranked roughly by value-to-effort, based on what's shipped, demoed, and documented:

1. The morning briefing that replaces pipeline archaeology. In the launch demo, a seller asks Claude to "schedule a daily briefing to tell me where should I focus my business." It returned a prioritized action plan, flagged six closing opportunities with no next steps, and surfaced a COO change at a key account pulled from the web. This is the "10,000 clicks → 30 seconds" claim in action – Stokes's words for what a rep's daily record-evaluation ritual costs today.

2. Meeting prep on autopilot. One of the 37 skills. Account history, open opps, recent activity, key contacts, talking points – assembled before you ask twice.

3. Deal health reviews that tell you what you don't want to hear. Amodei described his own chief commercial officer using it: "what are the biggest accounts that Anthropic is trying to close now?… Talk me through the risks of each one". When the CEO of the AI company runs his pipeline this way, that's the pattern to copy.

4. Pipeline hygiene as a conversation. "Summarize my open opportunities closing this quarter and flag any that are stalled" – an official example prompt. Follow-up: "update the next steps on all six." That's the write path, governed by your permissions.

5. Account 360 briefings. "Give me a briefing on the Acme Corp account: recent activity, open opportunities, and key contacts". Combine with web context (exec changes, funding, earnings) and you have genuine account intelligence, not a report snapshot.

6. CRM updates without the CRM. Log calls, update stages, create tasks, edit fields – by telling Claude what happened. The reason reps don't update Salesforce is friction; this removes the friction while validation rules still enforce data quality (caveat: your validation rules are now load-bearing – if they're weak, agent writes will find out).

7. Grounded email drafting. "Draft an update on the Acme renewal" pulls actual deal context – not generic AI slop. CNBC confirmed skills "compose emails, update records and take other relevant actions".

8. Vibe-coded command centers. At a Salesforce leadership summit, "every single one" of the sales execs presented a self-built command-center view made in CoWork. Every rep gets the dashboard they actually want, generated in minutes, without a BI ticket. Temper it with Stokes's own hedge: "This idea that people are going to vibe code their own CRM is probably not going to happen anytime soon."

9. Forecast narratives. Roll up pipeline movement, slipped deals, and coverage into the story your VP actually wants – with Tableau semantics and proactive alerts coming to make the numbers trusted.

10. Deal rooms in Slack. Tag u/Claude in a deal channel and it plans multi-step tasks, remembers channel context, and works asynchronously over hours or days. Admins can create a separate sales-scoped Claude identity that won't leak memories to other teams.

11. Handoffs and coverage. Rep leaves, territory changes, someone's on PTO: "brief me on everything active in this book of business" turns a two-week ramp into an afternoon. (This one's implied by the architecture, not demoed – treat as a fast-follow experiment.)

12. RevOps investigations. "Which Q4 deals have no activity in 14 days and champions who've gone dark?" – cross-object questions that used to mean building a report now run as one prompt through discover/dispatch_readonly.

The woven caveat for all twelve: an AI interface is only as good as the records underneath it. Duplicate accounts, stale stages, and fields filled in to please dashboards become confident wrong answers at conversation speed. One consultant put it perfectly: success "has absolutely nothing to do with the technology… It has everything to do with the state of the data in the adoptees' orgs". Data hygiene just became a revenue lever.

What marketing teams get (and what to do while you wait)

Straight talk: marketing skills are not live yet. Launch is sales-only; the marketing module ships with the late-2026 wave. But the roadmap is public and the prep work starts now.

What's coming, per the product page:

• Campaigns that auto-correct – grounded in live Data 360 context, adjusting against goals
• Content built for agents AND humans – an official acknowledgment that AI buyers' agents are now an audience (if you've been doing GEO, you're early)
• Personalization at every engagement – powered by the same unified customer context sellers use

And some of it leaks in early: the general Salesforce connector for Claude already lists "create campaigns" among its capabilities today.

The 90-day head start for marketing leaders:

1. Audit your data like an AI will read it – because it will. Campaign attribution, lead source hygiene, contact roles. Every gap becomes a confidently wrong answer in a CMO's chat window next quarter.
2. Get your team into Claude in Slack now. Claude Tag is in public beta for Claude Enterprise/Team customers – campaign war rooms, content reviews, competitive briefs in-channel. This is the same muscle Claudeforce will use; build it early.
3. Write your skills wishlist. The 37 sales skills encode seller workflows. Marketing skills will encode yours. Document your top 10 repetitive workflows (campaign brief → build → QA → report) now, so you can map them to skills – or pressure your AE for pilot access with a concrete case.
4. Rethink content for the agent audience. Salesforce itself now says content must serve "agents and humans." Structured, factual, citable content wins when the buyer is a Claude instance doing vendor research.
5. Watch the seat math. If sellers stop opening Salesforce, they stop seeing your embedded dashboards, banners, and enablement surfaces. In-CRM marketing real estate quietly evaporates. Plan for the conversation being the only surface left.

Claude in Slack: the other half of the story

The pillar most coverage skimmed is arguably the most immediately usable, because it's live and doesn't wait for the beta:

• Claude is now Slack's default intelligence layer – powering Slackbot, Claude Tag, and Slack Code
• Salesforce's own numbers: 83% of its workforce uses the Claude-powered Slackbot, with a claimed 8.1M hours of annualized productivity gains, up 2x quarter over quarter. Honest flag: that hours figure is Salesforce measuring Salesforce – the 83% adoption number is the more credible one
• Claude Tag is the interesting one for GTM teams: an AI teammate you tag in channels. It plans multi-stage tasks, remembers channel context (never reads private channels it isn't in), acts proactively, works async over days. Admins get per-function Claude identities, org- and channel-level token budgets, and a full action log
• Know the context limits: on a channel mention Claude reads the 20 most recent messages; in a thread, the 50 most recent replies. Slack conversations don't sync with Claude web. Structure important context accordingly – pin it, thread it, or feed it via connectors
• Requires a paid Claude plan (Pro/Max/Team/Enterprise); works on all Slack plans

The pattern to internalize: Slack is where the team reasons together; Salesforce is where governed action lands; Claude is the connective tissue between them. Salesforce's own positioning: teams "reason through complex decisions alongside Claude in Slack and instantly execute governed, high-value actions in Salesforce – all without ever leaving the flow of work".

The operating model shift: how B2B teams should actually work now

This is the inspirational part, so let's earn it with specifics. Stokes's comparison is the right mental model: "We think that what this can do is kind of be a version of what Claude Code did for developers… We think we're about to do the same thing for knowledge workers". Claude Code didn't make developers obsolete – it changed the unit of work from typing to directing. The same shift is now aimed at your revenue org:

• From navigating to directing. The rep's job stops being "operate the CRM" and becomes "direct an agent that operates the CRM." Time reallocates from admin work to actual selling. The reps who write clear, specific instructions win – prompt literacy is the new Salesforce certification.
• From dashboards to conversations. Static dashboards answer last quarter's questions. Generative UI means the interface is built per-question, per-person, on demand. BI backlogs shrink; curiosity compounds.
• RevOps becomes Agent Ops. Someone has to own skills, permissions, write-autonomy settings, token budgets, and the audit log. Forrester was already tracking the "Claude Cowboy in RevOps" archetype before this launch. That person just became one of the most leveraged hires in your company.
• Permissions become strategy. "Over-provisioned profiles that were harmless behind a slow UI become genuinely risky behind an agent". The agent moves at machine speed with exactly the access you granted. Least-privilege stops being a compliance checkbox and becomes an operating principle.
• Data quality becomes a P&L line. Every stale field is now a wrong answer delivered confidently to a decision-maker. The unglamorous cleanup project you've deferred for three years is suddenly the highest-ROI item on the roadmap.
• Keep an escape hatch. The lock-in concern is real – analysts called this a shift "away from model-agnostic flexibility toward deep, platform-level lock-in". Agent Builder still offers model choice; keep that optionality "genuinely exercised rather than theoretical".

The 30-60-90 playbook

Days 1–30 (now, before the beta):

• Permissions audit – before first-run onboarding, not after. The onboarding sweep touches everything the connection can reach
• Data hygiene sprint on the objects sellers will query first: opportunities, accounts, contacts, activities
• Roll out Claude in Slack; start with read-only Claude Tag + a scoped integration user
• Pick 5 pilot reps (your best, not your most junior – you want signal, not babysitting)
• Register interest for the September open beta; note it collides with the Winter '27 release window (production waves Sept 4, Oct 2, Oct 9) – stagger your pilot away from upgrade weekends

Days 31–60 (beta):

• Connect the plugin (Route 1), reads-first; keep write autonomy low
• Run the daily-briefing, meeting-prep, and deal-health skills against real pipeline; measure time saved and – more important – actions taken that wouldn't have happened
• Draft your token budget with actual consumption data; set org- and channel-level spend limits in Claude Tag
• Start the marketing skills wishlist and data prep

Days 61–90 (scale decisions):

• Expand write autonomy where validation rules proved solid
• Roll from 5 reps to a full team; publish internal prompt playbooks (the 10 prompts that worked)
• Decide your posture on custom skills vs. waiting for the late-2026 wave
• Board-level readout: productivity delta, data-quality delta, token cost per rep, risk register

And the one rule that overrides everything: beta means beta. Don't put a Q4 revenue process on this critical path. If your org's permissions and fields are in decent shape, "the September beta is a cheap test and worth running early". Run the cheap test. Don't bet the quarter.

What the smartest skeptics are saying (so you don't get blindsided)

The bear case, compressed – because you'll hear all of these in your exec meeting and should have answers ready:

• "A database with an expensive API." If Claude owns the interface, what's Salesforce's pricing power?. Counterpoint: "The real fight was never about whose model reasons best. It's about who already owns the data nobody wants to rebuild"
• Seat erosion. If agents become the primary consumers of SaaS, per-user licensing loses coherence; consumption pricing is the successor metric. Watch your own renewal math
• Launch-day validation was all in-house. Every public endorser on day one works at one of the two companies, and Hacker News – the most implementation-literate audience on the internet – gave the announcement 9 points and zero comments. Silence from builders is data
• r/salesforce's finest: "I'd love to see someone at Dreamforce try typing 'Delete org' at a booth" – funny, and also a legitimate question about write-autonomy defaults you should ask your rep
• And zerohedge's market-top jab for the road: "We are at the 'Claudeforce' on Cramer stage"

None of these kill the thesis. All of them sharpen the rollout.

Enterprise software just crossed a line it can't uncross.

The most important CRM company on earth conceded – on stage, at earnings, by name – that its UI is not the product, and rebuilt itself as infrastructure for someone else's AI. Amodei's summary is the one that will age best: "Salesforce has all the data… And Claude is a machine for interacting with that in a fluid and more flexible way".

For sales and marketing teams the takeaway isn't "AI is coming." It's that the winners of the next 18 months are being decided right now by unglamorous work: clean data, tight permissions, prompt playbooks, token budgets, and a team that practices directing agents instead of clicking through screens. The 10,000 clicks are going away either way. The only question is whether your team is the one that gets the 30 seconds.

See it live at Dreamforce next month – Benioff promised "a heavy dose of AIforce".

For the comments:

1. If the AI is the interface, what happens to the 40,000+ people whose job title is "Salesforce admin"?
2. Would you give an agent write access to your production CRM in 2026 – and at what autonomy level?
3. Marketers: is "content for agents and humans" the biggest strategy shift since mobile, or a slide-deck phrase?
4. Anyone in the pilot: what actually broke first?

Not affiliated with Salesforce or Anthropic. All numbers are from public reporting; vendor-reported figures are flagged as such.