A Salesforce Enterprise License Agreement folds the estate — clouds, products, add-ons — into one multi-year committed spend with agreed usage envelopes; per-product contracts keep each purchase a separate, visible, droppable line. The decision rule is blunt: a SELA pays when growth is certain, broad and near-term, because the commitment gets consumed; it costs when growth is hoped-for or needs might shrink, because the commitment is irreversible, the unit economics go opaque, and the exit is repriced from your peak. Salesforce is signing more of these than ever — which tells you who the structure usually favours.
Published 16 December 2025 · Last reviewed 16 December 2025
The per-product contract is the Salesforce default: an order form per product, priced per user (or per consumption unit), each with its own quantities, discount and co-termed or separate renewal. The estate’s cost structure is the sum of its visible parts — which makes it auditable by you, and makes every line a lever at every renewal.
A SELA replaces that with a custom-negotiated frame: a committed spend over a multi-year term covering a defined product set, with usage envelopes generous enough that teams deploy covered products without raising a purchase order. The pitch is real — one agreement, one renewal date, headroom for growth, no procurement friction per rollout. What it costs is structural: the line items dissolve into a single number, the commitment cannot shrink mid-term, and usage beyond the envelope triggers true-up at rates the base number no longer explains.
Note what a SELA is not: it is not an edition. Enterprise vs Unlimited decides what each user’s subscription contains; the SELA question decides how the whole estate is bought and committed. The two decisions compound — an edition upgrade inside a SELA raises the committed baseline the rest of this page is about.
This guide compares contract structures as the vendor offers them; it is general information, not legal or licensing advice for your situation, and it names no firms. SELA terms are individually negotiated — your agreement is what its paper says, not what this page says. The firm directory lists Salesforce-capable advisors with balanced pros and cons, listed, not ranked.
| DIMENSION | PER-PRODUCT CONTRACTS | SELA |
|---|---|---|
| Unit economics | Visible per line; effective rates auditable by you | Folded into one committed number; per-product rates implied, not stated |
| Growth | Each expansion is a purchase event — friction, but also a negotiation | Deploy inside the envelope without new paper |
| Shrinkage | No mid-term true-down either — but each line can drop at its renewal | Committed spend runs to term end regardless of need |
| Overage | Buying more is a standard purchase at negotiated rates | True-up beyond the envelope, at premium rates unless capped at signature |
| M&A / divestiture | Affected lines adjusted at their renewals | Commitment survives the org chart unless carve-out clauses were negotiated |
| Administration | Many order forms, many renewal dates to calendar | One agreement, one date, one negotiation |
| Renewal leverage | Many small levers; underused lines drop quietly | One large cliff; the proposal is built from peak deployment |
The shrinkage and renewal rows carry the weight. Salesforce paper never allows mid-term reduction — that is true on both sides of the table — but per-product structures let need and spend re-converge line by line at each renewal. A SELA defers every adjustment to one event, years out, negotiated against a vendor holding your complete deployment history and a baseline built from your widest year.
The per-product structure fits most estates most of the time — stable or moderately growing deployments, single-cloud or loosely coupled multi-cloud use, any organisation whose three-year Salesforce roadmap contains the word “maybe.” The friction of purchase events is also the discipline of purchase events: every expansion gets priced, every line gets re-examined at its renewal, and optionality stays on your side of the table.
A SELA fits the estate whose growth is already decided: committed multi-cloud rollouts to known populations, integration of acquired businesses onto the platform, expansion plans with budget attached rather than aspiration attached. For that buyer the envelope genuinely gets consumed, procurement friction was a real cost, and a well-negotiated commitment can land below the accumulated uplifts of buying the same growth piecemeal.
The test: write the three-year deployment plan you would defend to your own CFO — products, populations, dates. If the SELA envelope is materially larger than that plan, the difference is headroom you are paying for and calling flexibility. The vendor’s enthusiasm for the structure is itself data: committed spend, locked baseline and an opaque rate card serve the seller’s renewal position before they serve yours.
The rate card is the whole game. Insist on stated effective unit rates per product inside the commitment — not just the single number — and on those rates governing true-up and post-term pricing. An envelope without a rate card prices your renewal for the vendor in advance; the renewal proposal will start from the committed total, and without per-product rates you cannot even decompose it.
Negotiate the exits at the entrance. True-up rates and caps, envelope rollover, divestiture carve-outs, the right to rebalance spend between products mid-term, renewal uplift caps, and what happens to pricing if you step back to per-product paper at term end. Every one of these is negotiable while the vendor wants the signature and rarely negotiable afterwards. The same applies to consumption-metered AI — if Agentforce credits ride inside the envelope, their overage terms belong in the same negotiation, and the Agentforce 1 vs Unlimited guide maps that meter.
Compliance inverts: the risk is overcommitment, not under-licensing. Salesforce exposure is contractual rather than audit-shaped, and a SELA concentrates it — the envelope must be measured against actual deployment continuously, because drifting over it triggers premium true-up while drifting under it is money committed and gone. Standing usage measurement of exactly this shape is Salesforce licensing advisory work between events; turning the term-end cliff into leverage is what renewal negotiation does at them. Start that work a year out — the when-to-engage guide maps the clock.
Buying headroom as if it were free. The envelope sized for the optimistic roadmap is paid for whether or not the roadmap happens. Size the commitment to the defensible plan and let genuine surprises be purchase events — they were going to be negotiations anyway.
Signing without a rate card. One number covering everything feels simple until true-up, rebalancing or renewal requires knowing what anything costs. Implied rates reconstructed from a total are the vendor’s arithmetic, not yours.
Assuming the org chart is stable. Divestitures, shutdowns and strategy changes do not reduce a committed spend. The carve-out clause costs negotiating capital at signature and is unobtainable mid-term.
Letting peak deployment write the renewal. The term-end proposal will be built from your widest usage year. Continuous measurement, documented decommissioning and an early start are what keep the next baseline honest.
Taking the structure’s valuation from the parties paid by it. Account teams are increasingly compensated to land SELAs, and implementation partners benefit from the deployment headroom. Apply the independence test to every adviser in the room, and put the twenty questions to whoever helps you price it.
A Salesforce Enterprise License Agreement is a multi-year, custom-negotiated agreement that consolidates an organisation’s Salesforce estate — typically several clouds and products — under a single committed spend with agreed usage envelopes, in place of separate per-product, per-user order forms. It trades line-item visibility for deployment headroom: teams can adopt covered products inside the envelope without new purchase events.
No. Unlimited is an edition — a feature tier priced per user. A SELA is a contract structure that can cover any mix of editions and products. The two answer different questions: the edition decides what each user’s subscription includes; the SELA decides how the whole estate is bought, committed and renewed. An estate can run Unlimited on per-product paper, or Enterprise inside a SELA.
Effectively no. The committed spend is the contract; headcount reductions, divested business units and abandoned products do not reduce it. The commitment runs to the end of the term, and the renewal proposal will be built from your peak deployment, not your current need. This one-way flexibility — easy to grow into, impossible to shrink — is the central structural feature to price before signing.
Usage beyond the agreed thresholds triggers a true-up, and true-up rates in SELA structures are typically priced well above the effective unit rate implied by the base commitment unless overage terms were negotiated into the agreement. Measuring deployment against the envelope continuously — not at the vendor’s true-up letter — is the operating discipline a SELA demands.
When growth across multiple Salesforce products is certain, broad and near-term: planned rollouts to known populations, a multi-cloud adoption roadmap with budget attached, and M&A integration that will add users. In that estate the envelope gets consumed, the simplification is real and the unit economics can beat accumulating per-product uplifts. Where growth is hoped-for rather than committed, the per-product structure keeps the optionality the SELA sells back to you.
No. This is a directory, not a ranking. Firms are listed alphabetically with balanced pros and cons. Independence is shown as a pro and reseller, Big-Four or vendor-side-audit ties as a con, both stated as factual trade-offs for you to weigh.
Building the defensible deployment plan, decomposing the vendor’s single number into rates you can hold at true-up, and negotiating the exits before the entrance — that is precisely the work of a Salesforce license negotiation engagement when the SELA is new paper, and of renewal negotiation when the cliff approaches. The Salesforce hub maps the vendor’s wider licensing world, and the directory lists every firm covering Salesforce — with balanced pros and cons, listed, not ranked. Choosing between them? Start with how to choose a Salesforce licensing partner.
The edition decision inside the contract →
The AI bundle and its meter →
Every firm for this work →
The criteria, questions and red flags →
Fixed, day-rate, gain-share →
Every field guide on the site →
Tell us the vendor, the service you need and where things stand, and we will route your brief to firms that genuinely cover that combination. The directory and matching are free for buyers, no vendor ever sees your brief, and we add no markup.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.