Salesforce Per-Seat Renewal Playbook: Prepare, Trade and Win

This article covers the practical mechanics of a per-seat Salesforce renewal — the kind most organisations are familiar with from Sales Cloud, Service Cloud, and other traditionally licensed products. If you haven't read Part 1 yet, it's worth four minutes — it covers the foundations that apply regardless of contract type.

If your contract also includes Data Cloud or other consumption-based products, Part 4 covers those separately. The mechanics are different enough to warrant their own treatment.

1. The utilisation audit

The single most important thing you can do before any renewal conversation is understand what you're actually using. Not what you contracted for. Not what was deployed at go-live three years ago. What is genuinely being used today, by whom, and how often.

This information is in your Salesforce org. Your administrators can pull it without any special access or request to Salesforce.

Step 1 — Get the headline numbers

Start at Setup → Company Information. This shows you, for each licence type in your contract:

• Total licences contracted
• Licences currently assigned
• Remaining (unallocated) licences

This is your baseline. It tells you immediately whether you're under-allocated — contracted for more than you're using — which is the most commercially significant finding a utilisation audit can produce.

Step 2 — Find the dormant users

The Company Information view tells you how many licences are assigned. It doesn't tell you whether those users are active. For that, build a Users report:

• Create a custom report type with Users as the primary object
• Add Profile and User Licence as related fields
• Run the report grouped by User Licence: Name

The fields that matter most for a renewal review:

• User Name — who holds the licence
• Active — whether the account is enabled
• Profile — what level of access they have
• User Licence — the licence type being consumed
• Last Login — when they last used the system

Last Login is the key field. Any user who hasn't logged in for 30 days or more is a candidate for review — not automatic deactivation. The right process is to reach out to each flagged user and confirm whether the licence is still needed. Seasonal users, executives who access primarily via mobile, people on extended leave can all show as inactive without the licence being redundant.

In most organisations running this exercise properly for the first time, a meaningful number of licences are being consumed by users who have left, changed roles, or simply stopped using the system.

Step 3 — Review Permission Set Licences separately

Permission Set Licences cover add-on entitlements and are frequently overlooked. Go back to Setup → Company Information and review these separately. The same inactive and under-allocated patterns apply, and the same review process resolves them.

Step 4 — Interpret what you've found

Two scenarios typically emerge:

Inactive users consuming licences. A hygiene problem with a straightforward fix — deactivate users who no longer need access. Common, and worth cleaning up regardless of renewal timing.

Under-allocation. You contracted for 100 seats and only 60 are assigned. This is the more commercially significant finding because it's direct evidence for a right-sizing conversation, and it shifts the negotiating dynamic meaningfully in your favour.

A note on timing

Working through flagged users, confirming deactivations, getting sign-off — this takes weeks if the list is long. It's one of several reasons why starting 9 to 12 months before renewal matters. Running this exercise with 30 days to go isn't useful.

Organisations that run this review quarterly or biannually as standard hygiene practice arrive at every renewal already knowing their numbers. Those that run it for the first time because a renewal is approaching are doing it under time pressure, with less opportunity to act on what they find.

2. The discount erosion trap

Before going into any conversation about reducing licence counts, understand the maths. The saving is rarely as large as it appears — and going in without modelling it first is one of the most common sources of renewal disappointment.

Why volume reduction doesn't deliver proportional savings

Your current per-unit price reflects a volume commitment made at a point in time. The discount you received was partly a function of how many seats you were taking on. Reduce the volume, and Salesforce's position is that the basis for that discount has changed.

In practice: an organisation that contracted for 1,000 licences at a substantial volume discount and wants to renew at 500 may find that the per-unit price increases materially to reflect the smaller commitment. The total saving is considerably less than halving the licence count would suggest — and in some cases, depending on the discount differential, the saving is a fraction of what was expected.

This is not a negotiating tactic. It is how volume-based enterprise software pricing works across the industry. But it is structurally predictable — model it before you sit down.

The implication for your renewal strategy

This dynamic is one of the main reasons product reallocation — moving value to where it's genuinely needed rather than simply reducing volume — is often a more productive conversation than trying to cut numbers down. If you have licences you no longer need, the question isn't only "can we reduce the count?" It's "can we move this value somewhere more useful?"

3. The swap-in, swap-out mechanic

At renewal, Salesforce's primary commercial focus is Total Contract Value — the overall dollar amount of the agreement. Within that number, there is considerably more flexibility about which products constitute the value than most buyers realise.

This is the mechanic most buyers never use — and it's often where the best renewal outcomes are found.

How swaps work in practice

If your utilisation audit has identified licences you're over-contracted on, those don't have to simply disappear from the budget conversation. It's often possible at renewal to reallocate that value — converting licences or units from a product you're underusing into something you genuinely need, at the per-unit rates already established in your existing contract.

The mechanics are straightforward when both products are already in your contract:

• Each product has a per-unit rate in your existing agreement
• Reallocation is a conversion at those rates — 100 Sales Cloud licences at their contracted rate become a calculable number of Data Cloud units, additional Service Cloud seats, or capacity in another cloud already present in the contract
• Salesforce is generally amenable because total contract value is maintained

Adding a product that isn't currently in your contract is more involved but happens regularly. New products added at renewal are treated as new business from an AE compensation perspective — which means the AE has genuine incentive to facilitate the conversation. Come with your own view of what you'd add rather than evaluating whatever is introduced.

What this requires from you

The buyers who use this mechanic effectively are the ones who arrive knowing what the composition of their contract should look like — not just what they'd like to pay less for. That means knowing which products are under-utilised and by how much, knowing what the business genuinely needs that isn't currently in the contract, and having a clear view on what a good swap looks like before the conversation starts.

4. The escalation clause as a currency

Your Salesforce contract contains an annual escalation clause — typically in the range of 5 to 7 percent, in the standard terms, not hidden. If your procurement team has read the contract they know it's there.

The more useful framing is to treat the uplift as a currency rather than a cost to resist.

The escalation is a committed spend — it is going to happen. In many renewal conversations, the discussion around that uplift and new product adoption end up happening in the same breath. The informal commercial logic tends to run something like: you're going to pay the uplift regardless, so the question is whether that value goes toward a percentage increase on your existing contract, or toward something the business actually needs.

Whether and how that trade is available depends on the specific renewal and the relationship. But arriving with a clear view of what you'd want if the conditions were right — a product genuinely on your roadmap, a capability the business has been asking for — puts you in a materially stronger position than arriving with no agenda and evaluating whatever is introduced.

5. The give-and-get framework

Every renewal has levers on both sides. Understanding what you have to trade — and what each lever is worth to Salesforce — is the preparation most buyers skip entirely.

The levers available to you

Term length Longer commitments have genuine value to Salesforce — revenue certainty is reflected positively in how deals are assessed internally. A customer willing to commit to five years instead of three has something worth trading. This is particularly relevant in public sector, where long-term cost certainty has independent value to the buyer as well. The trade might be a longer term in exchange for a better per-unit rate, a more favourable escalation structure, or approval for a swap that might otherwise be difficult to get through.

New product adoption Covered in the escalation section above. The key is coming with your own product agenda rather than reacting to the AE's.

Quarter-end timing Salesforce's fiscal year ends January 31, with quarter ends on April 30, July 31, and October 31. The commercial pressure to close deals is highest at these moments. A customer whose renewal falls near a quarter end — or who can influence timing — has structural leverage that has nothing to do with their size or relationship history.

Payment terms Upfront payment or extended commitment can sometimes be traded for commercial concessions, particularly when a deal is being closed under quarter-end pressure.

Reference and case study participation Has genuine internal value at Salesforce and can be traded in commercial conversations — more relevant for larger or more strategically visible customers.

The discipline

Know your positions before the conversation starts. What would you trade, and what would you need in return to make it worth trading? The customers who get the best outcomes aren't the ones who negotiate hardest in the room. They're the ones who decided what they wanted before they walked in.

6. Know your own contract

One of the clearest signals of an unprepared buyer is not knowing what's in their own order form. The contract contains the information that determines what every swap costs, what the escalation structure looks like, and what the commercial parameters of the renewal are. Salesforce's renewals team knows your contract in detail. You should too.

The sections that matter most

The product schedule Lists every contracted product, the per-unit rate, the quantity, and the total annual value. These are the numbers that govern any reallocation conversation — what your existing licences are worth and what other products cost at the contracted rate.

The escalation clause Specifies the annual uplift percentage and when it applies. This is the baseline from which every renewal starts.

The payment and term structure Sets out payment timing, the contract anniversary date, and — critically — any notice requirements for changes. Some contracts require formal written notice of intent to change terms well before the renewal date. Missing that window can remove options you thought you had.

Mid-term amendments Products added mid-term sometimes carry different rates or terms to the original agreement. The picture that matters is the consolidated view — not just the original order form.

None of this requires a legal review. It requires someone to sit down with the documents, understand what they say, and bring that understanding into the commercial conversation.

Mike Roberts spent over eight years at Salesforce, including time as a Strategic Account Director, before founding Aequus Consulting. He works with New Zealand organisations on Salesforce licence optimisation and renewal preparation, with no vendor affiliations.