AIforce vs Agentforce vs Claudeforce: Salesforce AI Terminology Cheat Sheet (2026)
Confused by AIforce, Agentforce, Claudeforce and Einstein? This cheat sheet explains what each Salesforce AI actually does, who it's for, and what it costs.
TLDR: Four names, four different things. AIforce is the plumbing — governance, context, and model routing — that everything else runs on. Agentforce is the agent platform doing customer-facing work. Claudeforce puts Salesforce inside Claude for your sellers. Einstein is the AI already bundled inside Lightning.
Why This Matters Now
Salesforce renamed the portfolio mid-flight. The Dreamforce 2026 Main Keynote (Tuesday, Sept 15, 10 a.m. PT) is built around “AIforce and Claudeforce coming to life.” It looks like there’s a dedicated AIforce keynote on Sept 16.
The trap is treating them as interchangeable. One is infrastructure, one is agents, one is a plugin, and one is something you’ve probably already paid for. I’ll post updates live from Dreamforce.
Last updated: Sept 12, 2026. AIforce keynote lands Sept 16 — pricing and packaging rows hope to be revised based on announcements same-day.
The Four Names in 60 Seconds
| AIforce | Agentforce | Claudeforce | Einstein | |
|---|---|---|---|---|
| What it is | Trusted enterprise harness | Autonomous agent platform | Salesforce-in-Claude plugin | Embedded in-app AI |
| Who uses it | Everyone (platform layer) | Customers + ops via agents | Internal sellers and reps | End users in Lightning |
| Where you touch it | Any interface (Claude, Slack, CLI, portals) | Service flows, portals, Slack, Coworker | Claude CoWork | Inside Salesforce UI |
| Pricing | TBD (keynote Sept 16) | Flex Credits (~$0.10+/action) or $2/conversation legacy tier | Two invoices: headless + CoWork | Bundled by edition |
| Status Sept 2026 | Launching at Dreamforce | GA, scaling ($800M ARR) | Open beta (Sept 2026) | GA, mature |
AIforce: The Harness Everything Rides On
Salesforce’s own press release defines it plainly: “Salesforce in Claude is made possible by AIforce — Salesforce’s trusted enterprise harness that brings all your business data and workflows to any agent through MCP servers, APIs, and CLI tools, without complicated and costly integrations.”
Nobody logs into AIforce. It sits underneath everything else.
The harness story (published by Salesforce on Sept 10) breaks it into six trusted capabilities plus a new AI Control Plane:
- Trusted Context — customer context, metadata, semantics, memory, real-time signals
- Trusted Agency — reasoning, planning, orchestration with deterministic controls where certainty matters
- Trusted Action — secure connections to apps, APIs, workflows
- Trusted Governance — lineage, quality, guardrails
- Trusted Security — identity, permissions, privacy, runtime security
- Trusted Models — route the right model per job by accuracy, performance, cost
The AI Control Plane is the operational payoff: one place to discover and register agents, set identity and policy, manage lifecycle, evaluate performance, observe behavior, and control cost — across Salesforce and third-party AI.
Under the hood for developers: the Headless 360 hosted MCP server exposes four tools — Discover, Describe, Dispatch, and Dispatch Read-Only. The July beta opened with roughly 100 skills expanding to thousands.
None of this answers the packaging question though. No pricing, no SKU boundaries, no GA scope yet with hopes of this being clarified during the Sept 16 keynote.
Warning: If your renewal quote already lists AIforce as a line item, push back. Salesforce hasn’t published packaging. You’re looking at a placeholder, not a price.
Agentforce: The Autonomous Agents
Of the four names, this is the grown-up. Launched Oct 2024, now past $800M ARR with 29,000+ deals (FY2026 Q4). When Salesforce says “agentic enterprise,” this is what they’ve referred to in the past.
Agentforce agents do customer-facing and operational work: resolve service cases, qualify pipeline, run back-office flows. This year’s Dreamforce keynote theme says it all: “From Fast Start to Real ROI” — out-of-box agents, customized against your data, grounded in customer context.
Claude already lives inside Agentforce as a reasoning model for the Atlas Reasoning Engine, powering Agentforce Vibes and Agentforce Coworker by default, and available in Agent Builder. Through Amazon Bedrock, Claude runs within the Salesforce Trust Boundary for regulated-industry deployments.
Where it gets murky is cost. The current model is Flex Credits: 20–30 credits per action, which lands around $0.10+ each at $500 per 100k credits. (The older $2-per-conversation tier still exists for Service Agent–style use, but treat it as legacy.) Either way the headline rate sounds simple until you watch a multi-step run chain Discover into Describe into Dispatch before it even reads a record. Every hop burns credits.
Earned insight: In every consumption-priced agent rollout I’ve reviewed, the invoice surprise never comes from the headline per-action rate. It comes from retry loops and grounding calls nobody modeled. Budget 3x your happy-path estimate for the first quarter, then tune down.
Agentforce Strengths:
- GA and proven at scale — 29,000 deals is real deployment data
- Out-of-box agents get you started fast; customization path is clear
- Claude reasoning + Trust Boundary via Bedrock covers regulated use cases
Agentforce Weaknesses:
- Consumption metering punishes complex multi-step runs
- Flex Credit framing hides grounding and retry costs (legacy $2/conversation tier hides them too)
- Still requires Data 360 maturity — bad data in, confident wrong answers out
Claudeforce: Salesforce Inside Claude
Announced Aug 26 alongside Q2 FY27 earnings by Benioff and Amodei on stage together. The headline: “Salesforce in Claude,” a CoWork plugin shipping with 37 prebuilt sales skills — meeting prep, deal health review, pipeline review. Salesforce publishes the skills openly in the salesforce-skills repo on GitHub (see salesforce-for-sales), so you can read exactly what each skill does before you let it touch your pipeline.
Your sellers can stop opening Lightning. They instead can ask Claude for a daily briefing and get a prioritized action plan. Salesforce president Patrick Stokes framed it in clicks: synthesizing a book of records is “like 10,000 clicks inside of Salesforce. Now you just go to Claude and it’s going to execute all of that for you… in like 30 seconds.”
The branding hides some complexity: Claudeforce is three things sharing one name. Claude as the reasoning model inside Agentforce (already live). Claude as the default model in Slack (already live). And the new piece, Salesforce in Claude, the plugin. Only the plugin is in pilot now, with open beta expected in September 2026.
The part I actually like is the security model. An admin connects once, authentication and permissions are managed centrally, and every seller gets access day one. Claude sees what the user is authorized to see, nothing more. No per-user MCP setup, no new permissions model to build.
Every write goes through Salesforce, so your business rules still fire. When it updates a record, it changes only the field it said it would. Humans direct, agents execute, Salesforce governs.
But the pricing is two invoices from what we now so far. Salesforce charges headless consumption tied to your license edition. Anthropic bills Claude inference on a separate contract. Stokes said it out loud: “You can’t buy this on one piece of paper at the moment.” The official announcement’s only pricing language is “pricing and packaging are subject to change.”
That asymmetry is what will bite you in budgeting. Salesforce’s meter throttles: MCP tool calls count against your org’s daily API allocation (Enterprise: 1,000 calls per license per 24 hours; Unlimited: 5,000; enforced in aggregate, not per user). Hit the ceiling and your integrations fail, not just your agents. Anthropic’s meter just bills. No cap, no throttle, just an invoice.
One thing practitioner write-ups keep getting wrong, so here’s the precise version: the “Trust Boundary-via-Bedrock” sentence in the announcement sits in the “Claude inside Salesforce” section, which describes the Agentforce path. No primary source puts the plugin’s inference inside that boundary. Salesforce data isn’t retained in Claude and isn’t used for training (per TechTarget’s reporting), but the plugin runs on a separate Anthropic contract.
What’s coming: Service, Marketing, Commerce, Revenue, Field Service, Tableau, MuleSoft, Informatica, Data 360, and industry skills are all listed as “coming soon” on the Claudeforce page. Sales ships first. Everything else starts late 2026.
Tip: Pilot this in a full-copy sandbox with API usage alerting turned on before you touch production. A Discover → Describe → Dispatch loop burns several API calls per seller question. You’ll want the consumption baseline before the whole sales floor joins.
Claudeforce Strengths:
- Zero workflow change for sellers — they stay in Claude
- Permission inheritance means no re-audit, no new security model
- 37 sales skills out of the box, built by Salesforce + Anthropic jointly
- Salesforce is customer zero — their own AEs piloted it on real pipeline
Claudeforce Weaknesses:
- Two-invoice pricing with no published price and no single contract
- Beta, not GA — pilot in sandbox, not production
- API allocation risk: MCP traffic shares the bucket with your ETL and integrations
- Only sales skills at launch; every other function waits
Einstein: Still There, Still Bundled
Don’t sleep on Einstein just because it’s the oldest name here. It’s the AI embedded in the apps you already pay for: lead scoring, conversation insights, Trust Layer enforcement.
The positioning after this cheat sheet:
- Einstein = AI embedded in the UI you’re already in
- Agentforce = agents doing work on your behalf outside the UI
- Claudeforce = your data and rules surfaced inside Claude
- AIforce = the harness making all three trustworthy
If you’re renewing Sales or Service Cloud, Einstein capabilities ride along by edition. That’s your baseline. Everything else is incremental spend that needs its own ROI case.
How They Fit Together
Stop thinking of these as separate items on a menu and start thinking of them as a stack:
Data 360 (context) → Trust Layer + AIforce harness (governance, routing, control) → Agentforce / Claudeforce / Einstein (surfaces) → you, wherever you work.
Salesforce’s bet, in Stokes’s words: “The value of Salesforce is not in our UI itself… It’s in the data and the metadata, the years worth of encoded workflows and business practices.” The UI is the AI now. The moat is the 27 years of business logic underneath.
It’s also multi-model now. Salesforce fronts Anthropic, OpenAI (Altman shares the Dreamforce stage Sept 15), and Google, and the harness story explicitly supports third-party models with intelligent routing by accuracy, performance, and cost. That’s either de-risked lock-in or three vendors to manage, depending on how your procurement team sees the world.
Pricing Reality
| Surface | Model | What we know | What we don’t |
|---|---|---|---|
| AIforce | TBD | Harness + Control Plane announced; no SKU | Everything commercial — wait for Sept 16 |
| Agentforce | Flex Credits | ~$0.10+/action (20–30 credits); $2/conversation legacy tier; $800M ARR proves willingness to pay | True TCO with retries, grounding, Data 360 uplift |
| Claudeforce | Two invoices | Headless consumption by edition + CoWork license (min 20 seats Enterprise, ~$20/user/mo floor) | Headless 360 usage rates; API overage behavior at scale |
| Einstein | Bundled | Included by Sales/Service edition; Conversation Insights expanded to Starter/Pro in Summer ‘26 | Which Einstein features migrate to consumption over time |
No published Claudeforce price exists. Anyone quoting you a number is guessing. Budget the CoWork seats you know, meter the headless consumption you can observe in pilot, and refuse to annualize either until GA terms land.
Who Should Care About Which
Salesforce admins: Claudeforce changes your week. One-time connect, permission audit, sandbox pilot, API alerting. Start there. AIforce Control Plane becomes your job once it GAs.
Architects: AIforce is your layer. Six capabilities, model routing, MCP surfaces. Map every agent — Salesforce or third-party — to the harness before Dreamforce ends.
CIOs: The question isn’t which AI. It’s how many invoices. Agentforce consumption + Claudeforce two-invoice + Einstein bundled + AIforce TBD. Demand a single cost model from your AE before you expand. Forrester’s already asking if you have headless pricing dialed in. Most orgs don’t.
RevOps: Claudeforce pilot, scoped to one sales team, sandbox first. Measure briefing time saved against API consumption burned. That’s your ROI input for the GA decision.
Bottom Line
Four names, one stack. AIforce governs. Agentforce acts. Claudeforce meets sellers where they work. Einstein stays bundled where you already are.
The single biggest trap is signing consumption contracts against demo math. A 30-second pipeline review looks free until you multiply Discover → Dispatch loops by 200 sellers by 20 selling days.
Your 30-day action: map every AI line item in your current Salesforce order form to one of these four names, flag the overlaps, and ask your AE which ones the Sept 16 AIforce keynote will supersede — in writing, before you sign anything else.
FAQ
Is AIforce replacing Agentforce?
No. AIforce is the harness underneath Agentforce, not a successor. Agentforce is GA with $800M in ARR and 29,000 deals; AIforce is a partially built platform whose rollout starts February 2027 at the earliest. Think foundation versus house. Nothing you bought gets replaced, and nothing about AIforce is purchasable yet — so don’t let any 2026 order form reference AIforce SKUs that don’t exist.
Is Claudeforce replacing Agentforce?
No — this is the most common confusion in the r/salesforce threads. They run in opposite directions: Agentforce agents live inside Salesforce and reach your customers there, while Claudeforce puts Salesforce data inside Claude for your internal sellers. Same foundation (Headless 360 MCP servers, Data 360, Trust Layer), opposite user. Most orgs will run both: Agentforce for customer-facing automation, Claudeforce for seller productivity. Complementary budgets, not either-or.
Do I need both a Salesforce and an Anthropic contract for Claudeforce?
Yes, as of the September 2026 open beta. Salesforce provides the hosted MCP infrastructure and meters tool calls against your org’s daily API allocation; Anthropic bills Claude inference on a separate contract. Salesforce’s Stokes said it plainly: “You can’t buy this on one piece of paper at the moment.” Ask both vendors for a combined TCO worksheet — neither publishes one, and neither side’s quote tells the full story alone.
How does Claudeforce pricing actually work?
There is no published standalone price. Usage draws down two resources: your org’s shared daily API allocation (every Discover-Describe-Dispatch call counts against the same budget your ETL and integrations use) and Anthropic inference on your Claude contract. That makes Claudeforce the only one of the four where heavy adoption can throttle unrelated systems before it shows up on an invoice. Pilot with a capped group in a full-copy sandbox, watch the API dashboard daily, and don’t commit org-wide until Salesforce publishes meter rates.
When will AIforce be generally available?
Rollout begins in “early FY28” — February 2027 at the earliest, since Salesforce’s fiscal year starts February 1. The September 16 Dreamforce AIforce keynote should clarify GA scope and possibly packaging, but platform chief Rohan Kumar declined to discuss pricing on September 10. This article will be revised as those details land. Treat AIforce as a roadmap commitment until then, not a capability you can buy.
Do I still need Einstein if I buy Agentforce or Claudeforce?
Yes — different jobs. Einstein is embedded AI inside the Salesforce UI, bundled with your edition at no marginal cost. Agentforce and Claudeforce are agentic layers that act across systems. Dropping Einstein to fund agents is like canceling electricity to pay for appliances. With Conversation Insights expanding into Starter and Pro suites in Summer ‘26, the bundled value actually went up. Keep it, and evaluate the agentic layers on top of it.
Related Articles
Discussion