Salesforce replaced Enterprise, Unlimited and Agentforce 1 with three new editions on 3 September 2026: Core at $195, Advanced at $395 and Max at $550 per user per month. Most of the commentary so far compares the feature lists. For the people who actually build and run the org, the more useful question is a different one: who is going to watch the credits?
Every edition now ships with a Flex Credits balance. Core includes 500,000, Advanced 1 million and Max 2.75 million. That number reads like capacity. It is not. It is a starting balance, and how fast it drains depends on what you build, not on which edition you bought.
The full breakdown of the three editions, the pricing and what moved into the bundle is in our Salesforce Core, Advanced and Max editions guide. This post is about the part that lands on the admin and developer side.
Treat credits like API limits, not like licences
Licences are counted once a year. Credits are consumed every time an agent takes an action. That makes them behave much more like API call limits or storage than like seats, and they need the same kind of attention:
- A named owner. Someone on the platform team should be responsible for consumption, the same way someone already watches API usage.
- A baseline before go live. Run the agent workflows in a sandbox with realistic volumes and record what one case, one lead or one request actually costs.
- Alerts, not surprises. Set a threshold well below the included balance and review it monthly for the first quarter.
If you have not worked through how the credit model itself is priced, our explainer on Agentforce pricing and Flex Credits covers the mechanics.
Design decisions change the bill
Two orgs on the same edition can burn credits at very different rates. The drivers we see most often:
- How many actions an agent takes per request. An agent that looks up the account, checks the case history and then drafts a reply is three actions, not one.
- Whether automation re-triggers the agent. A record-triggered flow that calls an agent on every update will consume far more than one that fires on a status change only.
- How clean the grounding data is. Duplicate and stale records mean more retries and longer reasoning. Our Agentforce readiness checklist covers the data work that should happen first.
Outcome-based pricing is a different budget line
Help Agent, available in Advanced and Max, is priced on resolutions rather than per user. That means part of the service budget now moves with case volume. Finance should see that line separately, and the definition of a resolution should be agreed in writing before the contract is signed.
What to ask for before signing
- A consumption projection built from your own workflows and volumes, not an industry average.
- Written confirmation of what happens to legacy edition pricing at renewal. Salesforce has said existing pricing is unchanged, but renewal quotes follow the new structure.
- If you are on Agentforce 1, the no-cost upgrade to Max, requested now rather than at renewal.
- A separate budget for implementation. The licence line and the build line get approved by different people.
Where this leaves the build team
Agent configuration is no longer a separate phase that happens after the CRM is live. With Agentforce bundled into every tier, scoping agent actions, guardrails and credit monitoring becomes part of the core implementation plan. If you are choosing someone to help with that, these nine questions for an Agentforce implementation partner are a good filter, and our Salesforce cloud services page shows how we approach it.
Ashapura Softech is a certified Salesforce, Zoho, Microsoft and Odoo implementation partner.
Top comments (0)