What an enterprise agreement actually is, when it fits, and the traps inside it. Three knowledge checks along the way, and 4 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real SAP negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back. Session twenty two, the SELA, the Salesforce Enterprise License Agreement. This is the instrument organisations reach for when the counting becomes exhausting, and it does solve that problem. It also creates a different one, which almost nobody sees until three years later. The short version: a SELA is a floor sold as a ceiling. So today: what it actually is, the five components and where each binds you, the four conditions under which it genuinely fits, the traps inside it, and the exit, which is the real negotiation and needs about eighteen months of preparation. Three knowledge checks. Let's begin.
Five objectives. First, say what a SELA actually is: a committed spend envelope with flexibility inside it, and not an unlimited licence. Second, judge whether it fits you, using four conditions, and if you fail two of them the answer is probably no. Third, name the traps: the scope that funds it, the floor that ratchets, and the measurement you do not hold. Fourth, manage it during the term, because the work that makes the exit survivable happens in years one and two. And fifth, prepare the exit, since a SELA ends in one of three ways and two of them need eighteen months of notice.
So, what it actually is: a commitment with flexibility inside it. A spend floor, because you commit to a number and using less does not reduce what you pay. Scope bounded, so freedom applies to named products and named entities rather than to everything. Term locked, usually three years, with limited ability to change direction inside it. And counting stops, which is the relief everybody wants and the reason the exit is so difficult. Let me explain why that word enterprise does so much damage internally.
Guest analyst clip.
The commercial trade is simple enough: you give up flexibility on spend to gain flexibility on deployment. Whether that is a good trade depends entirely on how much you are actually going to deploy, which is a forecast, and forecasts made to justify a commitment have a particular character to them.
Right, five components and where each one binds. The commitment: total spend across the term, often ramped, and it is a floor, so under-use is your loss rather than a saving. The scope: which products and which entities are covered, and anything outside is a separate purchase at standard rates. The flexibility: deploy freely within scope without counting, only within scope and only for the term. The term: usually three years, sometimes longer, and exit before the end is rarely available on reasonable terms. And the renewal basis: how the next agreement is priced, frequently on deployed volume, measured by them. That last row is where most of the risk sits, and it reliably gets the least attention during the original negotiation.
First knowledge check. What is a SELA best described as? A, an unlimited licence for Salesforce products. B, a committed spend floor with deployment flexibility inside a defined scope. C, a discount programme for large customers. D, a support and services agreement. Pause here and pick an answer before you continue.
B. Both halves matter: the floor means under-use returns nothing, and the scope means the freedom has edges that are very easy to forget once counting stops. A is how these agreements get described internally, and it causes real damage, because teams deploy products that were never in scope. C describes an effect rather than the instrument, and the discount is the compensation for the commitment. And D is a different agreement entirely, and support is usually priced on top of the SELA value, which we will come to next session.
So when does it genuinely fit. Four conditions, and you want most of them. You are genuinely growing into it, meaning a funded and dated deployment plan rather than an aspiration written for the business case. The scope matches your estate, so the products you will actually use are inside it, including the ones arriving later. Administrative drag is real, because if every small addition currently takes six weeks of procurement then freedom has genuine value and you should count that value. And you can measure yourself, because you will need your own deployment number at the end and nobody else is going to collect it for you. Now, the traps.
Guest analyst clip.
Scope funds the deal. That is the first and largest of them, and the rest follow from it. The floor ratchets, because next term is proposed from this term's deployment, so growth is permanent in a way it is not under standard licensing. Products drift out of scope, since new Salesforce products are new purchases unless the scope language anticipated them.
Nobody counts during the term, because counting was the thing you were escaping, and it is precisely what you need at the exit. And entities change, so an acquisition or a divestiture can sit entirely outside the named entities, which turns a corporate event into a licensing event nobody planned for.
Second knowledge check. You are in year one of a SELA. What is the most important thing to do? A, deploy as widely as possible to maximise the value. B, start recording your own deployment figures every quarter. C, wait until year three and let the vendor produce the numbers. D, renegotiate the commitment downward. Pause here before you continue.
B. The renewal is priced on deployment, so the only real question at the exit is whose measurement the room accepts, and a quarterly record you built yourself is the only thing that makes yours credible. A is the instinct the agreement encourages, and it directly raises the floor you will renew from. C is what most organisations do, and it hands the baseline to the other side entirely. And D is not usually available mid term, and it is the wrong problem anyway, because the commitment is already sunk while the exit is still open.
So, four habits that make the exit survivable. Count quarterly anyway: users by type, consumption by meter, capacity by environment, on one page, dated. Track what is genuinely used, because deployed and active are different numbers and only one of them justifies a renewal. Keep scope decisions written down, so when something new arrives you record whether it was in scope and who decided. And review adoption against the plan, meaning the plan that justified the commitment, because if it slipped you need to know early rather than at the exit. Let me say why the second of those is worth the effort.
Guest analyst clip.
Deployed and active are different numbers. And in a SELA that gap tends to be wider than anywhere else, precisely because nothing constrains deployment, so licences get handed out generously and nobody ever has a reason to take them back.
Now the exit, which is the real negotiation. Three ways out. Renew the SELA, which is simplest and is priced from deployment, so your own count decides how it goes. Return to standard licensing, which requires knowing exactly what you use and usually a reduction you can evidence. Or reduce scope and commitment, the middle path, which needs a story about what you no longer need told with data. Start eighteen months out, because two of those three take that long to prepare properly, and the first one does not, which is exactly why it is the one most organisations end up choosing. And know your walk away number, meaning what standard licensing would cost for what you actually use, because that is your ceiling.
Five failures. Sold as unlimited internally, so teams deploy freely including products that were never inside the scope. Sized on the ambition, with a commitment built on a three year plan that delivered half of what it promised. No internal counting, giving three years of freedom and then a renewal priced on a figure only they hold. The exit started too late, six months out with no data and no alternative, which is not a negotiation, it is a conversation about how much the increase will be. And entity changes ignored, where an acquired business gets plugged into the org while sitting outside the named entities.
Last knowledge check. What gives you the strongest position at a SELA renewal? A, a benchmark of what other customers pay. B, your own deployment and usage data, plus a costed standard licensing alternative. C, a credible threat to move to another CRM. D, waiting until close to the vendor's year end. Pause here and pick an answer before you continue.
B. Those two things together give you a number and an alternative, which is what a negotiating position is actually made of, and the alternative does not need to be attractive, only real and costed. A prices somebody else's scope and is easy to dismiss. C is not credible for most organisations at this depth of deployment, and everybody in the room knows it, so asserting it costs you standing. And D is genuine timing leverage that amplifies a position rather than creating one, so use it, and understand it is worth nothing on its own. Let me set out the programme.
Guest analyst clip.
Quarterly during the term, then the exit programme. The quarterly count: one page, users by type, consumption by meter, capacity, dated and stored somewhere that survives people leaving. The scope log: every new product, whether it was in scope, and who made that call. The adoption line: actual against the plan that justified the commitment, reviewed twice a year. At eighteen months out, cost the standard licensing alternative for what you genuinely use. And at twelve months out, decide the direction, renew, reduce or return, and then prepare that specific case properly rather than keeping all three open until the deadline.
Three sentences. A SELA is a committed spend floor with deployment flexibility inside a defined scope, so the word unlimited is wrong in two directions, because under-use returns nothing and anything outside the scope is still a purchase at standard rates. The agreement removes counting, which is the relief you are buying and the reason the exit is difficult, since the renewal is priced on deployed volume and whoever holds the only measurement holds the negotiation. And so count yourself quarterly from year one, keep a scope log, review adoption against the plan that justified the commitment, and start the exit eighteen months out with a costed alternative.
Homework before session twenty three, about two hours. One, establish whether you actually have one, because many organisations are unsure, so look for a committed total rather than per line quantities. Two, find the scope language: which products, which entities, and what happens when Salesforce releases something new. Three, find the renewal basis, which is the single sentence that matters most in the document. Four, start the quarterly count with today's deployment, dated, because even in year three one data point beats none. And five, cost the alternative roughly: what standard licensing would cost for current usage, where a rough figure is enough to start with.
Five guides, all on redresscompliance dot com. The Salesforce SELA, scope funds it, explains how the scope sizes the commitment and what that means for you. Cracking the Salesforce SELA takes the structure apart section by section. Managing a SELA during the term covers the work in years one and two that decides the exit. SELA renewal against exit covers building the baseline and costing the alternative. And Salesforce minimums and true ups covers how floors behave, inside a SELA and outside one.
That is session twenty two. The thing to take away is that a SELA buys you freedom from counting, and the price of that freedom is paid at the exit, so the discipline is to keep counting privately even when the contract says you no longer have to. Next time, support: Standard, Premier and Signature, what the percentage actually buys you, and whether you need the tier you are paying for. See you then.