Salesforce Renewal Decision: Make the Credit Pool a Yes/No
Log the Salesforce renewal as a choice with a usage trigger, so the new org-level credit pool becomes a clear yes/no before the invoice.
The price gap is the entry fee
The renewal email may look like a routine price bump. The harder part is structural: the included usage pool may now belong to the organization instead of scaling with each added seat. Compare only the per-user price, and you can miss the trigger that decides whether the new tier is a yes or a no.
Salesforce announced Core, Advanced, and Max on September 3, 2026, with list rates of US$195, US$395, and US$550 per user per month, billed annually. Existing customers on legacy editions keep their current pricing. That creates a fork: hold the old price or move to a new edition whose included usage is allocated differently.
For a 10-user team, the list gap is the entry fee. Each Core organization receives 500,000 Flex Credits annually, and the new editions allocate those credits to the organization rather than adding them for each seat. The renewal question is whether that gap buys enough headroom in the shared action pool for the coming year.
A short chat can miss the allocation change. The renewal file needs a record that a new reader can understand without asking anyone.
The credit pool is a shared budget
The included figure is a pool, not a per-seat entitlement. The team can spend it faster than the seat count suggests, so the renewal math needs a ceiling, not a forecast.
Salesforce's rate card sets a standard agent action at 20 Flex Credits, so the 500,000-credit pool equals 25,000 standard agent actions per year. At list, those included credits are worth US$2,500 per organization per year. The action count is the number that turns the pool into a budget a single owner can watch.
Divide the annual action pool by the number of people who will consume it, and you get a monthly ceiling that tells you when the included value is being spent. Because the pool is shared, a heavy workflow can consume value that another team expected to use. The per-person number is the test. The owner should be able to answer the renewal questions: what we chose, what we rejected, and what will make us look again.
Write the decision before the invoice
A decision log keeps the renewal from becoming a seat-price argument. Each line is short enough to check in a minute, and each line forces the team to say what it is buying, what it is giving up, and when it will look again.
The entry should be written before the invoice, not after the first surprise. The owner can be the ops lead, the founder, or the person who already knows where the usage report lives. The log should be short enough to paste into the renewal file and long enough to survive a challenge.
Attach the log to the renewal meeting, not a chat thread. The owner can bring the usage report, the invoice draft, and the lines. If the team changes the plan, the log changes with it, and the next review starts from the same page.
Before the meeting, the owner should pull the usage report and mark the month where standard agent actions cross the trigger. If the number is close, the team should decide whether to change the plan, adjust the workflow, or revisit the edition. If the number is far, the log still records the reason for the choice.
- Choice: renew Core at list, or hold legacy Enterprise at US$175 per user per month; for a 10-user team, the list gap is US$2,400 more per year.
- Rejected option: the other path, with the reason it fails the usage trigger.
- Per-person action math: 2,500 actions per user per year for a 10-person team.
- Review trigger: if monthly standard agent actions pass 2,084, revisit the renewal.
Put the log in the renewal file, set the calendar reminder, and let the next invoice test the choice.