Committed minimums ran 10 to 25 percent above the seats the buyer could actually deploy in year one

The committed minimum is agreed once, at the point of least information, against a deployment plan that has not survived contact with the business. It then prices every year of the term.

Prepared by Redress Compliance · August 17, 2026 · Salesforce advisory. 36 Salesforce contracts reviewed, 2024 to 2025.

A committed minimum is a floor rather than a budget, and its relationship to actual deployment is one directional.

Across the 36 Salesforce contracts reviewed, the committed minimum was set above realistic demand more often than not, running 10 to 25 percent above the seats the buyer could actually deploy in year one. The reason is structural rather than careless. The minimum is fixed at signature, which is the moment the buyer knows least about how quickly the rollout will proceed, how many of the identified users will genuinely need licences, and how the business will absorb the change. It is then paid for the full term regardless of what any of those answers turn out to be.

What makes this different from ordinary over-forecasting is that the error only moves in one direction. Deploy below the minimum and you pay the minimum. Deploy above it and you true up. Delay the rollout and the minimum does not wait. Cancel it and the minimum survives. There is no configuration in which an over-set commitment corrects itself, which means the number agreed in that low information moment is effectively permanent for the term.

The move that works is structural rather than a matter of negotiating harder on the figure. Buyers who tied the commitment to a low baseline plus a priced option cut first year overcommit by 15 to 30 percent. That works because it separates two genuinely different things: the demand you can evidence today, which belongs in a commitment and should attract the discount, and the demand you expect from a rollout that has not happened yet, which should be priced now and bought when it materialises. Merging them into one number charges you for both and refunds neither.

The option costs something, and that cost is the point. It converts an irreversible commitment into a reversible one at a known price, which is a favourable trade whenever the rollout carries any delivery risk at all. Negotiate the option rate at the same time as the baseline, because an option whose price is agreed later is not protection. The wider estate discipline sits in hidden costs, the renewal sequence in the CIO negotiation playbook, and the library in the Salesforce practice.

• Set the minimum against demand you can evidence today, not against the rollout plan, since the plan is the least reliable input available at signature.
• Buy the expected growth as a priced option, which cut first year overcommit 15 to 30 percent in the contracts reviewed.
• Negotiate the option rate at the same time as the baseline, because an option priced later is not protection.
• Treat the minimum as a floor you will pay in the worst case, and ask whether the number still makes sense if the rollout stalls entirely.
• Check for any reduction right, since without one the commitment survives a cancelled rollout intact.
• Model the true up rate alongside the minimum, because the two together determine what growth costs and only one of them is usually discussed.

Across roughly 36 Salesforce contracts reviewed, the committed minimum was set above realistic demand more often than not:

The minimum is a floor rather than a forecast. Deployment below it still costs the full amount, delay does not pause it, and cancellation does not release it unless a reduction right was negotiated in.

It is agreed at signature, which is precisely the point at which year one demand is least knowable, and it then prices every year of the term.

Watch the briefing · 4:44Shrinking a Salesforce EstateWhat can and cannot be reduced once a commitment is in place.

How far above reality are Salesforce minimums typically set?

Between 10 and 25 percent above the seats the buyer could actually deploy in year one, across the 36 contracts reviewed. The minimum was set above realistic demand more often than not.

Why does that keep happening?

Because the minimum is fixed at signature, which is the moment the buyer knows least about rollout pace, genuine user need, and how the business will absorb the change. It is then paid for the whole term regardless.

Does under-deployment produce any refund?

No. Deploy below the minimum and you pay the minimum. The error only moves in one direction, which is what makes the number agreed at signature effectively permanent for the term.

What happens if the rollout is delayed?

The minimum does not wait. It applies from the contracted start whether or not the deployment has begun, which is why delivery risk in the rollout is really commercial risk in the contract.

What is the baseline plus option structure?

Committing to the demand you can evidence today and buying expected growth as a separately priced option. It cut first year overcommit by 15 to 30 percent in the contracts reviewed.

Why does the option work?

Because it separates two genuinely different things: evidenced demand, which belongs in a commitment and should attract discount, and hoped for demand, which should be priced now and bought when it arrives. One number charges for both.

When should the option be priced?

At the same time as the baseline. An option whose rate is agreed later is not protection, because the price will be set at a moment when you have already committed and lost the leverage that would have shaped it.

What is the right test for the number?

Whether it still makes sense if the rollout stalls entirely. The minimum is a floor you will pay in the worst case, so the worst case is the correct scenario to size it against.

Should the true up rate be negotiated too?

Yes, alongside the minimum. Together they determine what growth costs, and typically only the minimum gets attention, which leaves the price of every seat above it unexamined.

Is a reduction right available?

Only if you ask. Without one the commitment survives a cancelled or descoped rollout intact, which is the scenario where an over-set minimum is most painful and least defensible.