The purchase path just became a design decision

Salesforce published its new editions on September 3, 2026, and the shape of the bundle matters more than the headline. Core, Advanced, and Max now cover Agentforce Sales, Agentforce Service, and Agentforce Industries, and every tier ships with Agentforce, Slack and Slackbot, embedded analytics through Tableau Next, data security, a Premier Success Plan, and an allocation of Flex Credits. Salesforce calls this a single purchase path. We'd call it a single architecture decision that procurement is being asked to sign.

Until now, each of those pieces crossed the boundary between architecture and procurement on its own. Someone made the case for Slack, someone else priced the analytics add-on, and the support plan came up at renewal. The tier folds those separate conversations into one choice, and the choice carries commitments that most buying processes were never built to catch.

What Salesforce put inside each tier

Salesforce's announcement lists Core at $195 per user per month, Advanced at $395, and Max at $550, with Max priced the same as the Agentforce 1 Edition. Flex Credits scale with the tier: 500,000 for Core, 1 million for Advanced, and 2.75 million for Max. Max alone includes unmetered Agentforce Service Rep Assistant, Agentforce Workforce Engagement, Agentforce IT Service, and a future allocation of Headless 360 capacity. Salesforce says existing Agentforce 1 customers can move to Max at no extra cost.

Three lines in the post set the timing. Existing customer pricing on legacy editions remains unchanged. Pricing for the Industry Editions goes into effect later this fall, so Industries customers are reading a partial price list today. And availability varies by region and is governed by customer agreements, so the list in the press release and the list your account team can quote may not match.

Owned is not the same as switched on

When a capability arrives inside the seat, procurement will reasonably record it as owned. The architecture team then inherits a question it never asked: which of the owned components will actually be turned on, and what do they replace. A Salesforce estate inside a Microsoft 365 shop now holds a Slack entitlement for every Agentforce Sales user. A reporting team that standardised on Power BI two years ago now has Tableau Next embedded in seats it never chose.

The problem is a tier decision that lands without a written answer for each bundled component. We'd expect the awkward version to surface at the first renewal review in 2027, when a finance partner asks why the company pays for collaboration and analytics it does not use, and nobody in the room owns the answer. A retirement list that names what the bundle displaces, or a recorded decision that a component stays off, closes that gap before anyone asks.

Flex Credits move a meter into the seat

The credit allocation is the part of this packaging that changes the commercial shape rather than the price point. A per-user licence with a consumption pool inside it behaves differently from the flat seat most Salesforce estates have modelled for years. Beyond the size of each pool, the post does not say what one credit buys, how consumption is metered, or what happens in the month a pool runs dry.

For an architect, the pool is a design constraint before it is a budget line. An agent that fires on every case update draws on it very differently from one that runs once a night, and someone has to decide which workloads may draw on it at all. Our companion piece on the total-cost questions inside a simplified edition covers the finance side. The architecture side is the allow list of workloads.

Max carries capability, not only capacity

The Max-only items are where the buying line moves furthest. Agentforce IT Service and Agentforce Workforce Engagement are product decisions that would once have had their own evaluation and their own integration plan. In the new packaging they arrive because a sales or service leader chose the top tier for the unmetered Service Rep Assistant. A ServiceNow shop can find itself holding an IT service agent nobody evaluated, and a contact centre with an existing workforce management tool can find a second one in the licence.

The future allocation for Headless 360 capacity is capacity for something the post does not describe, included in a tier that customers are choosing now. We'd want the account team to put in writing what it will cover and when.

Data Cloud is the line the post does not draw

The announcement does not mention Data Cloud. Both Agentforce and embedded analytics read from the data layer, and on most Salesforce estates that is where the capacity questions already live. We'd want a plain statement of what Data Cloud entitlement comes with each tier, if any, and whether Flex Credits are the mechanism that pays for it.

Until that statement exists, scope the edition as covering the agent and analytics surfaces and keep Data Cloud as a separate decision with its own owner. That keeps ingestion volume and retention rules with the people who understand them.

Put the tier on the architecture review before the order form

The practical change is small. The tier choice goes through the architecture review board before it reaches procurement, and the paper that leaves the meeting answers three things: which bundled components will be switched on, which stay off and why, and which workloads may draw on the credit pool. Our licensing change checklist is a fair frame for that hour, and the questions in our piece on why packaging changes the governance conversation belong on the same agenda.

Then ask the account team for the two documents the post leaves out: the credit consumption rules and the Data Cloud entitlement per tier. If either arrives as a slide rather than contract language, you have found the first item for the renewal negotiation.