Managing a Salesforce SELA during the term. How to use what you prepaid and protect the renewal.

A SELA fixes the price at signature and leaves the value to the term. Consumption you track, products you gate and interpretations you write down decide both what you get for the fee and what the renewal costs.

A Salesforce Enterprise License Agreement (SELA) gives you broad rights to a defined set of Salesforce products for a fixed fee. The price is settled at signature. Whether it was good value depends on what you deploy over the next three years, what you leave unused and what gets switched on without anyone deciding to buy it.

This guide covers the term itself: how to measure consumption, how to govern new products, what to get in writing and when to start the renewal case. What to negotiate at signing sits in our SELA scope guide.

What are you actually buying with a Salesforce SELA?

You are buying a bet on consumption. You prepay for broad usage rights, and every entitlement you do not use hands that value back to Salesforce. The editions and per user list prices a SELA is sized against are on the Salesforce pricing overview. The value case, though, only exists after the signature.

Treat a SELA as a prepaid budget with an expiry date. Unused entitlements are spend you have already committed. They are not savings, and finance teams that book them as underspend let the gap run for the whole term.

Where do the limits sit inside an unlimited agreement?

They sit in the order form. Enterprise license agreements carry thresholds sized to your needs at signature, and in the agreements we have seen, usage above them ran at 2 to 3 times your contracted rate. The first job of the term is to find those numbers and separate proven demand from speculative demand.

We cover that distinction in the briefing Unlimited Is Still a Number, part of our SELA video series.

What does a SELA consumption plan need to contain?

• An entitlement map. Every product, edition and quantity or threshold in the agreement, with current deployment recorded against each line.
• A named owner per product. A business owner who is accountable either for adoption or for formally rejecting the product.
• A quarterly review. Consumption measured against the plan, with reallocation decisions minuted so the record survives staff changes.

How do you measure SELA consumption during the term?

Start in your own org, before you ask Salesforce for anything. Seat based products report their counts in Setup, and consumption based products report in a separate console. Pull both into one sheet that matches the product lines on your order form.

• Setup, Company Information. Lists User Licenses, Permission Set Licenses and Feature Licenses, each with Total, Used and Remaining counts.
• User list with Last Login. Shows assigned users who have not logged in for months. Those seats count as deployed at renewal unless you deactivate or reassign them.
• Digital Wallet. Salesforce's console for consumption products such as Data Cloud and Agentforce credits, showing usage against what you bought.
• Login History and the Lightning Usage App. Separate people who hold a license from people who actually open the product.

Our license usage calculator turns those counts into a value figure per product. The shelfware guide covers what to do with assigned seats that sit idle.

A worked example: what the consumption gap costs

Say your SELA costs $1,800,000 a year over three years, $5,400,000 in total. You split the fee across the products in scope by their share of list value, then compare deployment at the end of year two with the user counts the fee was sized on. The table assumes deployment holds at that level for the rest of the term.

In this example $2,011,500 of prepaid value will expire. The two smallest lines each lose more than half their value. Lines like these rarely have an owner, which is why a year two decision to reallocate or reject them pays.

What goes wrong during a Salesforce SELA term?

Two structural problems pull in opposite directions. Under consumption wastes money you have already spent. Ungoverned adoption raises a renewal price you have not negotiated yet.

Why is casual adoption more expensive than shelfware?

Shelfware is visible in a license report. Casual adoption is not, because nothing is bought and no invoice arrives. A product that feels free during the term is a dependency by the renewal, and Salesforce prices dependencies from deployed usage.

Say a sales operations team enables a bundled add on for 600 users in year two because it costs nothing extra. By month 30 their process runs on it. At renewal, those 600 users are measured usage, and removing the product now means rework rather than a line deleted from a quote.

Why we advise against deploying everything you have paid for

The usual advice is to push adoption of every product in the SELA so you get your money's worth. We disagree. A low value deployment returns little during the term, yet it adds to the usage the renewal is priced from for the next three years.

Deploy where the business case is proven. Formally reject the rest, record each rejection with its reason, and use that record to cut the product at renewal.

What have we seen in recent Salesforce SELA reviews?

We reviewed roughly 15 to 25 Salesforce enterprise agreements between 2024 and 2025. Across them, the gap between contracted value and consumed value was the number that shaped the renewal. Three patterns came up repeatedly.

• Consumption stayed well below the fee. Organizations used 55 to 75 percent of contracted value across the term, and the remainder expired as margin for Salesforce.
• Casual adoption was repriced. Bundled products switched on without governance became part of the renewal baseline, and 1 in 3 organizations faced repricing on products adopted because they felt free at the time.
• Reviews created room. Buyers who ran quarterly consumption reviews reached renewal with 20 to 30 percent more negotiating room than buyers who found out their position at the renewal meeting.

Every product switched on casually during the term became deployed usage that the renewal could measure and price.

The third pattern is the cheapest to act on. The review takes about an hour a quarter, and it replaces a renewal where Salesforce presents the usage data with one where you do.

What governance should run through a SELA term?

You need a gate on new products and a dashboard on existing ones. Both are cheap to run. Most organizations have neither, because the SELA was sold as removing exactly this kind of friction.

The gate matters more. A bundled product switched on because it costs nothing today becomes a line item at renewal, and the person who enabled it never made a purchasing decision.

What should the new product gate ask?

1. Which order form line covers this product, and is it inside a threshold or outside it?
2. Who owns adoption, and what does the business gain in the first 12 months?
3. How will Salesforce count this usage at renewal, and is that written down?
4. What would it cost to remove the product if the renewal price for it is unacceptable?

Write the interpretations down while the seller still agrees with you

Entitlement interpretations agreed during a sales cycle disappear unless they are in the order form. The account executive and solution engineer who gave them move on, and the document is what remains at renewal. Email confirmations help, but an amendment is what binds.

What will the Salesforce account team say during the term?

Expect the conversation to push adoption early and repricing late. These lines come up in most SELA terms, with the replies that hold up.

• "It is unlimited, so switch on whatever helps." Ask for the counting method at renewal in writing before anything new goes live.
• "Your usage has grown past what the agreement was sized on." Ask for the count by product and by date, then separate proven production use from pilots and inactive users.
• "Add Data Cloud now and we will fold it into the next agreement." Refuse anything folded in without a priced order form and a statement that it does not raise the baseline.
• "We can only hold this price if you renew early." Answer with your consumption record and your alternative case, and renew early only if the terms improve on both.

When does SELA renewal preparation actually start?

It starts in year one. A credible alternative case takes about two years to build, so a case started in the final year looks like theater, and an experienced account team can tell. The renewal mechanics are in our renewal pillar and the renewal negotiation guide.

Year three behavior sets year four cost

The SELA reprices at term end from deployed usage. Everything your teams enable in year three is the starting point for the year four price, which makes the term itself the negotiation. Put that sentence in front of whoever owns adoption.

Timing adds pressure from the other side. Salesforce's fiscal year ends on January 31, so its fourth quarter runs from November to January and that is where account team targets bite hardest. Our fiscal year end timing guide explains how that interacts with your renewal date.

The floor under the agreement is covered in our guide to minimums and true ups. The product lines themselves are listed on the Salesforce product range page.

For the full sequence across a cycle, see the 12 part Salesforce negotiation series. It runs from the January 31 year end to a signed order form in briefings of about five minutes each, with a printable checklist at the end.

What to do next

1. This month. Build the entitlement map from your order form and assign a named owner to every product, accountable for adoption or for rejecting it.
2. This quarter. Pull counts from Company Information, the user list and Digital Wallet, and hold the first consumption review with decisions minuted.
3. Before the next enablement. Put the new product gate in place so nothing bundled goes live without an owner and a written counting method.
4. At the next amendment. Write every entitlement interpretation from the sales cycle into the order form, along with the measurement date and pilot exclusion.
5. In year one. Start the alternative case, since it needs about two years to become credible.
6. Before year three. Ask the Salesforce practice to build the renewal case from your consumption record, so the negotiation starts from your data rather than from a threat.

Frequently asked questions