Agentforce Core, Advanced and Max: What $195, $395 and $550 Actually Buy

Agentforce Core costs $195 per user per month and ships with 500,000 Flex Credits. That sounds like a lot until you divide it out. At Salesforce's published rate of 20 credits per standard action, the pool buys about 25,000 agent actions a year, and it belongs to the whole org, not to each seat. Agentforce pricing in 2026 is a seat price with a fixed experiment budget attached.

The three Agentforce editions and their list prices

Salesforce announced the new editions on 3 September 2026. They cover Agentforce Sales, Agentforce Service and Agentforce Industries, with Industries pricing due "later this fall". The announcement lists Core at $195, Advanced at $395 and Max at $550 per user per month.

The Sales pricing page confirms all three figures in US dollars and marks each one "Billed annually". So the reported $195, $395 and $550 numbers check out against Salesforce's own pages. You do not need a third-party estimate for any of them.

Each edition maps onto an older one. Core replaces Enterprise, Advanced replaces Unlimited, and Max replaces the Agentforce 1 Edition. Salesforce says existing customers on legacy editions keep their current pricing, and Agentforce 1 customers can move to Max at no extra cost.

Prices and allocations from Salesforce's Sales pricing page and the 3 September 2026 announcement. The pricing page shows the three credit values in a comparison row. Only the Max figure is printed on its own edition card, so the Core and Advanced mapping rests on the announcement text, which states it directly.

What else sits inside each edition

The announcement says every tier includes Agentforce capabilities, Slack and Slackbot, embedded analytics, data security tooling and a Premier Success Plan. Max adds the most. The Service pricing page lists Tableau Next, Slack Enterprise+ and unmetered Agentforce Coworker on the Max card, against Slack Business+ on Core.

Salesforce frames the change as value. It claims Core offers "70% more value" than Enterprise, Advanced "more than 50%" over Unlimited and Max "nearly 60%" over Agentforce 1. Those are bundle contents measured at list, not outcomes measured in a customer org. I would treat them as a description of the box, not of what you will use.

The meter underneath every edition

A Flex Credit is Salesforce's unit of agent consumption. The Agentforce pricing page sells them at $500 per 100,000, which is half a cent each. A standard Agentforce action costs 20 credits and an Agentforce Voice action costs 30.

The same page states three rules that shape everything below. Unused credits "do not roll over into subsequent subscription terms". There is no overage penalty, and usage above the entitlement is billed at the contracted rate monthly in arrears. And Flex Credits and per-conversation billing "will not be supported in the same org".

How many Agentforce actions the bundled credits buy

The arithmetic is short. Divide each pool by 20 for standard actions, or by 30 for voice. Multiply by $0.005 for the list value of the pool.

Zan Digital calculation. Daily figures divide the annual count by 365. They assume every credit goes to one action type, which no real org does.

Put those numbers next to Salesforce's own worked example. The Agentforce pricing page prices a workflow at 40 credits per request, 20 requests a day, for 30 days, and gets $120 a month. That one modest workflow burns 24,000 credits a month.

Run that single workflow on Core and the pool lasts about 21 months. Run five of them and it lasts about four months. This is the clearest way to see what the bundle is. It funds a pilot, not a deployment.

The Agentforce 1 figure that keeps getting misquoted

Several pricing guides describe Agentforce 1 as carrying 2.5 million Flex Credits. Salesforce's June 2025 pricing update says something else. It lists "1 million Flex Credits per org per year" and, separately, "Data Cloud with 2.5 million Data Services Credits per org per year".

The 2.5 million number belongs to a different meter. Mixing the two makes Max look like a 10% bump over Agentforce 1 rather than 2.75 times the allocation. If a vendor deck or partner proposal quotes 2.5 million Flex Credits for your current edition, ask which credit type they mean.

The Agentforce credit pool is per org, so it shrinks per seat

Every allocation above is stated "per org per year". That one phrase matters more than the size of the pool. The seat price scales with headcount. The credit pool does not.

So the bundle is generous for a 10-seat team and close to symbolic for a 1,000-seat sales floor. A seat at Core costs $2,340 a year at list. The credits attached to that seat depend entirely on how many colleagues share the pool.

Zan Digital calculation at US list prices with no discount. Licence spend is seats times monthly price times 12. Credit value is the pool at $0.005 per credit.

Why Salesforce would design it this way

A per-org pool is the right design for the vendor, and it is not cynical. It gives every customer enough capacity to build and test agents without a separate purchase order. It also guarantees that any org running agents in production will buy more credits.

That second effect is the business model. The seat price funds the platform. The pool seeds the habit. Consumption above the pool is where Agentforce revenue grows, and the edition structure is built to get you there. The wider pattern, seats shrinking while metered charges rise, is the subject of the analysis of seat compression in SaaS pricing.

At 1,000 seats on Core, the pool gives each user about two standard actions a month. Nobody will notice those credits in a production rollout. If you are that size, budget your agent consumption as a separate line from day one and treat the bundle as a rounding error.

Agentforce editions against the older pricing models

None of the earlier Agentforce pricing models has gone away. The Agentforce pricing page still lists four ways to pay, and the editions sit on top of them rather than replacing them.

The $2 conversation

The per-conversation price is still listed at $2 and is scoped to customer-facing agents. At that rate the list value of the Core pool, $2,500, would buy 1,250 conversations. But you cannot spend it that way. Bundled credits are Flex Credits, and Salesforce does not support Flex Credits and Conversations in the same org.

That rule turns the edition choice into a meter choice. Buying an edition with bundled Flex Credits effectively commits the org to the per-action meter. The break-even between the two meters for a service desk is worked through in the $2 conversation math, which this post does not repeat.

The $125 add-on

Salesforce still sells Agentforce add-ons from $125 per user per month for Sales, Service and Field Service, and $150 for Industries. The pricing page describes the add-on as "Unmetered Agentforce usage for employees". The Max card on the same page says "Agentforce add-on included".

So Max is, in part, Advanced plus the add-on plus a bigger pool. That is the comparison worth running, and it is the one Salesforce's own value claims skip.

The Agentforce User License lists at $5 per user per month and "Requires Flex Credits". It grants access to limited CRM objects with metered agent usage. For staff who only touch agents occasionally, it is a cheaper path than a full edition seat, and every action it triggers draws from the same pool.

The upgrade math: are the extra credits worth the step up

Each step up the edition ladder adds credits. The question for a budget owner is whether the extra credits alone pay for the extra seat cost. They rarely do.

Zan Digital calculation at US list prices. Credit value assumes every credit is used inside the subscription term, because unused credits do not roll over. Enterprise and Unlimited prices are from secondary reporting, see the next section.

The Core to Advanced move is not a credit decision at all. The extra 500,000 credits cover the upgrade for one seat. If you move, you are buying the Advanced feature set, such as the Help Agent and the security and backup tooling, and the credits are incidental.

The add-on row is the interesting one. An org that would otherwise run Advanced with the $125 add-on pays $30 more per user per month for Max. Below about 24 seats, the extra 1.75 million credits are worth more than that premium, if you use them. Above it, the premium outgrows the credits, and Max has to justify itself on Tableau Next, Slack Enterprise+ and unmetered Coworker.

My read is that small teams already planning to buy the add-on should price Max first. Large orgs should ignore the credit line and decide on features.

What the editions replace, and the real price rise

Salesforce raised Enterprise and Unlimited list prices by "an average of 6%" on 1 August 2025, according to its June 2025 announcement. That page gives the percentage but not the new list prices. Salesforce's current pricing pages no longer show Enterprise or Unlimited at all.

The post-increase figures come from secondary reporting. SalesforceDevops.net put Enterprise at $175 and Unlimited at $350 per user per month. On those numbers, Core is about 11% above Enterprise and Advanced about 13% above Unlimited.

Legacy customers keep their current pricing, per the announcement. That protects you only until renewal terms say otherwise. The editions have no Enterprise or Unlimited list to anchor against, so expect renewal conversations to steer toward Core and Advanced.

The bundled credits soften the rise for small orgs. A 10-seat Enterprise customer moving to Core pays $2,400 more a year and gains $2,500 of credits. A 200-seat customer pays $48,000 more and gains the same $2,500. How renewal pressure tends to play out in practice is covered in the piece on grandfathered pricing at renewal.

What stays unconfirmed in Agentforce pricing

The brief for this post was to label anything that could not be confirmed. Four items fall into that bucket after checking Salesforce's own pages.

Data 360 credits per edition. Agentforce 1 shipped with 2.5 million Data Services Credits. None of the edition pages I read states a Data 360 allocation for Core, Advanced or Max. The Agentforce pricing page notes its examples exclude "Data 360 credits or other consumption services". Ask your account team for the number in writing.

Whether Core and Advanced employee usage burns credits. Max is described as including unmetered Coworker access. The Service page shows Coworker as "Available for purchase" on lower editions. Neither page says whether employee-facing agent use on Core or Advanced draws down the bundled pool.

Rate card multipliers. Salesforce says credits are fungible across actions, prompts, translations and voice actions, and points to a rate card PDF for multipliers. I could not extract the rate card text, so every count here assumes standard 20-credit actions.

The Headless 360 allocation. The announcement says Max editions will "in the future" include Headless 360 capacity. It gives no size and no date.

Where this argument is weakest

The analysis above treats credits as the thing being bought. That is the narrowest possible reading of an edition, and it has three real problems.

The bundle contents may matter more than the credits

The Sales pricing page lists the Premier Success Plan at 30% of net licence fees. If Core genuinely includes Premier, as the announcement says every edition does, then a customer who paid for Premier on Enterprise was spending about $227.50 per user per month at the reported $175 list. Core at $195 would be cheaper for that customer, before counting a single credit. The Service page wording is less clear and places Premier on the Advanced card, so verify which plan tier your quote includes.

Nobody large pays list

Every figure here is a US list price. Enterprise Salesforce contracts are negotiated, and the discount on seats and on credits need not be the same. A deep seat discount with credits at near list would change every break-even in the upgrade table. The direction holds. The precise seat counts will not.

Even division across seats is a fiction

The per-seat table spreads the pool evenly. Real agent usage concentrates in a handful of high-volume workflows, such as case triage or lead research. A 1,000-seat org with one busy service agent might burn the whole Core pool in a quarter while 990 sales reps never touch it. That makes the per-seat view a framing device, not a forecast.

Frequently asked questions

How to price your Agentforce renewal

Start with one spreadsheet column: actions per month for every agent workflow you plan to run in the next 12 months. Multiply by 20 credits and compare the annual total against your edition's pool. If you exceed the pool, the overage is your real Agentforce budget, and it belongs in the business case now.

Then send your account team four written questions. What is the Data 360 allocation in this edition? Does employee agent usage on Core or Advanced draw from the pool? What discount applies to credits, separately from seats? And which success plan tier is included? The answers decide the edition more than the list price does. For a wider view of how credit units obscure real cost, see the guide to AI billing in credits and tokens.

Related reading