Agentforce Pricing in 2026: What a Team Really Pays, and When Claude on Salesforce Is Cheaper

Salesforce now sells Agentforce four ways, and since Dreamforce there is a fifth option on the table: Salesforce inside Claude. Here are the published prices, the math for a 20-person sales team, and how to tell which route fits your org.

Oct 16, 2026

A CRM cloud fed on one side by a meter tower dropping coins through a turnstile, and on the other by a single cable to a small server with an assistant plugged in

Agentforce pricing, as Salesforce publishes it on 16 October 2026: $2 per conversation, or $0.10 per action through Flex Credits, or $125 per user per month for the Sales, Service, Field Service and Operations add-ons, with Agentforce Max Editions from $550 per user per month. Building agents is free with Salesforce Foundations. What you actually pay depends on which of those meters you pick and how much your agents do. Since Dreamforce there is another route on the table: Salesforce inside Claude, in a gated beta, and more generally any assistant reaching your org through an MCP server. Below: the published prices, worked math for a 20-person sales team, and how to tell which route fits.


The published prices

From Salesforce's Agentforce pricing page, read on 16 October 2026. Salesforce says the page is "for information purposes only and is subject to change".

OptionPriceNotes
Salesforce Foundations$0Agentforce Builder, Prompt Builder, Agent Script, Agentforce Coworker
Conversations$2 per conversationCannot be combined with Flex Credits in the same org
Flex Credits$500 per 100,000 credits20 credits per action ($0.10), 30 per voice action ($0.15). No rollover
Agentforce User License$5 per user per monthRequires Flex Credits
Add-ons (Sales, Service, Field Service, Operations)$125 per user per monthIndustries add-ons $150
Agentforce Max Editionsfrom $550 per user per monthIncludes the add-on and 2.75M Flex Credits per org per year

Salesforce also announced Core, Advanced and Max editions on 3 September at $195, $395 and $550 per user per month, and no new pricing at Dreamforce itself, according to Aptivus's recap. Industry cloud pricing was promised for later in the fall.

You can pay up front (Pre-Purchase), against a monthly baseline with a true-up (Pre-Commit, "widely available later this year"), or pay as you go, billed monthly in arrears.

What a 20-person sales team pays

Illustrative math, at list prices, before any negotiated discount.

Per user, with the Sales add-on: 20 × $125 = $2,500 a month, $30,000 a year, on top of your existing Salesforce licences. Predictable, and the same whether a rep uses it twice or two hundred times a day.

Per action, with Flex Credits: say each rep triggers 30 agent actions a working day (look up an account, summarize a call, draft a follow-up, update an opportunity). That is 20 × 30 × 21 days = 12,600 actions, or 252,000 credits, or about $1,260 a month, plus 20 × $5 user licences: about $1,360 a month. Cheaper here, but it scales with usage. Triple the actions and it is about $3,880.

Per conversation: at $2 each, the same team holding 10 agent conversations per rep per day is 4,200 conversations, $8,400 a month. This meter suits customer-facing service agents with a few long conversations, not internal assistants used all day.

The lesson is not that one meter is right. It is that you should model your own volume before you sign, and that the cheapest option at pilot volume is often not the cheapest at full adoption.

The other route: your assistant, your Salesforce

Agentforce puts the agent inside Salesforce. The other approach puts Salesforce inside the assistant your people already use.

  • Salesforce in Claude is Salesforce's own version, announced on 26 August and opened as a gated beta at Dreamforce. As of late September, there was no published price. We cover what it includes and what it doesn't yet in Claudeforce explained.
  • An MCP server is the general version. It exposes your org to Claude, ChatGPT or your own agents as a set of typed tools, running inside your Salesforce permission model. Salesforce also offers its own hosted MCP server, and Claude can be connected to it as a custom connector.

The cost structure is different. You pay for the assistant seats you probably already have, the model usage, and the server, built once and run monthly. Nothing is metered per action on the Salesforce side.

Which route fits

Agentforce fits when:

  • the agent faces your customers, on your site or in Service Cloud;
  • your Salesforce admins will configure and own it;
  • everything the agent needs is in the org;
  • you want one vendor and one contract.

Claude or ChatGPT over MCP fits when:

  • your people already work in Claude or ChatGPT and won't open another tool;
  • the job crosses systems: Salesforce plus your ERP, your inbox, a spreadsheet;
  • your org is heavily customized, with custom objects, record types and Flows a generic connector ignores;
  • per-action pricing would grow faster than your team.

Many companies will end up with both: Agentforce for customer-facing service, an assistant over MCP for the internal work.

What we build

We design, build and run Salesforce MCP servers. Each action, such as finding an account or updating an opportunity, becomes a typed tool with validated inputs. Every call runs inside the acting user's Salesforce permissions, so the assistant never sees more than that user could. Writes to revenue-critical records can require a person to confirm. And the same server composes with your other systems, so one assistant can work across Salesforce and the rest of your stack. Our AI work starts at $2,300 to $4,700 to scope one workflow, and from $17,500 for a first one in production, priced here.

Related: Salesforce MCP server, Claude connectors explained, and WhatsApp to Salesforce, a reference architecture.

Read next: Microsoft 365 Copilot pricing after July 2026, AI agent security after SalesBleed.