Full narration of the briefing. Click a section heading to jump the player to that moment.
When Salesforce proposes a SELA, the word you will hear most is flexibility. Broad product access, one commitment, freedom to grow. A well built SELA genuinely delivers that, and we have seen it. But in roughly seven of the ten agreements we reviewed, the unlimited framing hid two specific things: metered consumption that carried on being metered, and a structure that only ever trued forward.
Both are ordinary contract mechanics. Neither is hidden in the sense of being concealed. They are simply not what the word unlimited suggests to the person reading the summary slide, and the summary slide is what most executive teams see.
So separate the agreement into the parts that are genuinely broad and the parts that are not. User access is usually broad, within the named clouds you bought, and that is the part the word unlimited describes fairly. Consumption is a different animal. API calls, data storage and sandboxes are frequently still metered above a cap, governed by the per product limits Salesforce publishes.
And new products, the ones released during your term, are usually excluded from the bundle altogether, which matters more than it sounds in a portfolio that ships new SKUs every year. Three questions, then, on every draft: which resources are unlimited, which carry a cap, and what happens to a product that does not exist yet.
Then the structural half, and it is the one that costs real money. True forward only means growth gets billed up and decline gets nothing back. Add people and the agreement notices immediately. Lose a division, outsource a function, shrink a channel, and the fee does not move.
In most first drafts we see, there is no true down clause at all. Not a weak one. None. So an unlimited agreement that still meters consumption and only trues forward is, in plain terms, a fixed bet that your own growth forecast is right, placed for three years, with the vendor holding the other side.
That is a legitimate bet to make. It is not what predictability means, and the two get used interchangeably in the room.
Which brings us to the arithmetic, and the first error is choosing what to compare against. Do not compare the SELA fee to list price. List is a number designed to make any bundle look generous. Compare it against your projected per user cost across the whole term, built from your real growth forecast.
That comparison has an answer, and the answer is a user count: the break even, the point where the fixed fee equals what you would have paid per seat. Above it the SELA saves you money. Below it you are paying for headroom you never use. Model three scenarios before you sign, base, growth and decline, and be honest about which one your board actually believes.
Run those three scenarios and the pattern is consistent. Flat headcount: the per user path wins, because you pay for actual seats instead of a fixed ceiling. Fast growth: the SELA wins, because the fixed fee absorbs the growth you would otherwise buy at rising prices. Decline: the per user path wins decisively, because your cost falls with your seats while the SELA does not move at all.
Heavy consumption is its own case, and the answer there is not a scenario, it is a reading exercise: check the caps carefully, because that is where a flat fee stops being flat. Sign a SELA when you have genuine fast growth and the flexibility clauses to match it. Decline it when headcount is flat or uncertain.
And forecasts do miss, which is why we can put a number on this. Where the growth forecast underpinning a SELA did not come true, the median overpay across our engagement file was fifteen percent. That is not a catastrophe, and it is worth seeing clearly: fifteen percent of a large fixed fee, every year, for the whole term, in exchange for predictability the organisation had already priced as free. The buyer side move is not to refuse the instrument.
It is to model the break even against a forecast you would defend to your own CFO, insist on true down rights, and get every consumption cap written into the order before you trade flexibility for a flat fee.
So the ask, and it is short enough to send in an email. One, a true down right, so the fee follows a genuine decline in headcount rather than only a rise. Two, every metered consumption item listed in the order with its cap stated, not referenced to a page that can change. Three, a written answer on new product treatment, because an unlimited deal that excludes everything new leaves you buying point products on top of a flat fee.
The fee gets the attention in every SELA conversation we have ever sat in. These three clauses decide whether it ever pays off. Next part, we go and look at what this carrier was actually using, because that is where the leverage came from.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Salesforce negotiator