The seat price is the easy number

Salesforce's post of September 3, 2026 gives three list prices for the new Agentforce Sales and Service editions. Core is $195 per user per month, Advanced is $395, and Max is $550. Those numbers will sit on a budget line by month end, and they are the least useful ones in the post. What an organisation pays over a year is decided by what sits around the seat, and the announcement says much less about that.

We read it as a simplification of the quote, which anyone who has assembled a Salesforce order form from a dozen SKUs will welcome. The cost model got more complicated. A seat that carries a credit pool, a collaboration tool, an analytics product, and a support plan has more moving parts than the old per-user licence, and each part has a cost the headline price does not show.

A credit pool with no unit price on it

Every edition ships with Flex Credits. Core includes 500,000, Advanced includes 1 million, and Max includes 2.75 million. Salesforce's announcement does not say what one credit buys, what an agent conversation costs in credits, or what happens in the month the pool runs out. A pool with no rate card is a number nobody can forecast.

At Max, the Service Rep Assistant comes with unmetered Coworker access. Our reading is that below Max the same access is metered, so a busy service floor on Core or Advanced spends credits every time a rep asks the assistant for help. The post does not say what that spend looks like across a quarter. Our piece on the tier as an architecture call argues for an allow list of workloads that may draw on the pool, and each line on that list needs a consumption estimate beside it.

Bundled and already paid for are different things

All three editions include Slack and Slackbot, embedded agentic analytics through Tableau Next, data security features, and a Premier Success Plan. Salesforce says Core offers 70% more value than the legacy Enterprise Edition, Advanced more than 50% more than legacy Unlimited, and Max 60% more than Agentforce 1. Those are Salesforce's figures, built on list prices for components you may never have wanted.

The cost that matters is the one on your side of the table. An estate that already runs Slack or Tableau under a separate agreement, or bought a Premier Success Plan two renewals ago, pays for the same thing twice until those contracts co-terminate. An estate that runs Teams and Power BI instead finds the bundled tools cost nothing to own and something to adopt, and that something includes admin hours, training, and a recorded decision in the retirement list about which tool stays. Either way the model needs an overlap line and an adoption line, and neither appears on the price list.

A free upgrade still costs somebody a quarter

Salesforce says existing Agentforce 1 Edition customers can move to Max at no extra cost, with up to $500 in added value. For everyone else the post frames the comparison against legacy Enterprise and Unlimited, which tells us the move is a renewal conversation. Either path carries labour that no spreadsheet lists. Someone checks feature parity against what the org uses, reviews permission sets and feature licences, refreshes a sandbox, and runs the regression pack. We'd budget a quarter of a platform owner's attention for a mid-sized org and treat anything lower as optimism.

Industries customers have a further gap. Salesforce says new pricing for the Industry Editions goes into effect later this fall, so a healthcare team building its 2027 budget this month is working against a price that does not exist yet. Our licensing change checklist asks the right question here. On what date does the number become firm, and who revisits the model on that date.

Seats go down and the meter goes up

The unit of cost is moving. Sales and Service seats are still priced per user, but the Agentforce capabilities inside each tier are the reason to buy them. When an agent deflects a share of cases or drafts the account research a rep used to do by hand, the seat count stops being the number that grows with the business. The credit consumption is. A finance team that forecasts Salesforce spend from headcount will be right about the seats and wrong about the total.

Our piece on why packaging changes the governance conversation covers the ownership side of that meter. On the cost side it needs a monthly read, a threshold, and a named person who decides what gets switched off when the threshold is hit. The post says nothing about Data Cloud, where the volume-based charges on most estates already live, so we'd keep it on its own line until Salesforce says otherwise.

Build the twelve-month model before the quote arrives

The practical step is a single sheet with five lines per tier. Seat cost at list. Estimated credit consumption per workload, with the assumption written next to it. Overlap with existing Slack, Tableau, and support contracts. Adoption labour for anything bundled that will actually be switched on. Migration labour for the edition move itself. Fill it for Core and Advanced side by side, because the gap between $195 and $395 is only real once you know how much of it the credit pool difference explains.

Then take the sheet into the account meeting and ask for the credit rate card and the overage terms in writing. If the demo can run one of your scenarios with the meter visible, as we describe in running a vendor demo on your terms, the consumption line stops being a guess. If it cannot, that is the number to leave blank on the renewal paperwork, and the reason to say so out loud.