Consider an illustrative 400-user company that opens its Salesforce renewal notice and finds the total has grown again. The sales director insists nobody can lose access, the finance director wants a lower number and the admin suspects that at least some of the 400 seats haven’t been used in months. Both leaders are partly right. The usual saving doesn’t come from taking tools away from people who use them. It comes from finding the seats, editions and add-ons that nobody is using and removing them before the renewal date locks them in.
This article shows how to run that review: what to measure, how to retire inactive seats safely, when a cheaper license type fits a real user, what the contract allows and how to negotiate. It draws on a licensing advisory firm’s renewal guidance, a SalesforceBen license explainer, a SaaS-management vendor’s deactivation guide and arithmetic done in code. The advisory and vendor pages sell services and give mostly unsourced figures, so every percentage is labeled. Check your own order forms and master agreement, and confirm contract terms with counsel.
TL;DR
- Rightsize first, negotiate second. Redress Compliance, a buyer-side advisory firm that sells services, advises a 90-day active-user audit before any price conversation. Its 18 to 32 percent recoverable-cost claim is unsourced, so build your own number from your own login and feature data rather than anchoring on a headline.
- The contract sets the calendar. The same advisor says Salesforce contracts generally allow no mid-term reduction and that renewal is the main point at which quantity can fall, with notice windows commonly 30 to 60 days. Pull every order form now and diary each date, because a missed window is the costliest mistake.
- Move users, don’t remove them. Inactive seats can be deactivated, some users may fit a lower license type or edition, and unused add-ons can be dropped. In an illustrative 400-user example, that adds up to $208,800 a year, about 24.9 percent of licenses, with every active user still covered.
What “cut the renewal without losing users” means
The phrase sounds contradictory, but it describes a specific discipline: reduce what you pay for, not what people can do. A renewal is a bundle of seats, editions, add-ons, support level and term. Each can be larger than your actual need. Seats are over-provisioned when people leave or change roles and nobody deactivates them. Editions are over-provisioned when a premium tier was bought for a feature that a handful of people use. Add-ons are over-provisioned when a pilot ends and the subscription keeps renewing. None of these changes the experience of an active user.
Redress Compliance puts the principle bluntly as “rightsize first, negotiate second,” and the logic holds even if you discount its numbers. A negotiation starts from your current footprint. If the footprint contains 50 or 100 seats that nobody touches, you’re negotiating a discount on waste. Removing the waste first lowers the base, and any percentage discount then applies to a smaller number. The page also says the edition is often wrong rather than the user count, which means the audit has to look at what each person does inside the system.
Where the waste hides
Dormant seats are the easiest saving. A dormant seat belongs to someone who left, changed roles or never started using the system. Redress’s advice is to run a 90-day active-user audit, and its contract page suggests starting a 90-day login extract about 180 days before the term ends. Another page claims 10 to 20 percent of seats renew as shelfware, but it gives no sample size or method, so measure your own rate. Even a modest percentage is worth finding.
Over-edition users are the next layer. Many organizations license everyone at the same edition because that was simpler to purchase. Yet a service agent who answers cases may not need the same capabilities as an executive who views dashboards. Redress argues that edition mismatch matters more than user count and lists swap patterns such as Unlimited to Enterprise. Its unit-cost reductions come from undisclosed client renewals, so treat them as illustrations. The test is whether the features that justify the higher edition are actually used.
Unused add-ons are the quietest cost. Redress names Sales Engagement, CPQ, Inbox, Field Service and Service Cloud Voice as common candidates for review, and Folio3’s pricing page says CPQ add-ons start around $75 per user per month. An add-on bought for a project that ended 18 months ago continues to renew until someone cancels it. List every add-on, its assigned users, its last meaningful use and the business owner. If no owner can be named, put it at the top of the reduction list and ask why it’s still there.
The audit data to pull
| Data point | Where to find it | What it tells you |
| Last login date per user | User list or login history report | Seats with no activity in 90 days or more |
| License type and edition per user | Setup user list and company information | Who is on which license and what it costs |
| Permission set licenses and add-on assignments | Permission set license assignments | Paid add-ons attached to inactive or wrong users |
| Feature usage by role | Reports on objects, dashboards and flows | Whether a premium edition feature is used |
| Integration and API users | User list filtered by profile or user type | Users that must stay active though nobody logs in |
| Contract inventory | Order forms and master agreement | Quantities, prices, dates and notice windows |
| HR joiner, mover and leaver list | HR system export | Departed or reassigned staff still holding seats |
Collect the data at the start of the 90-day window and again at the end, so you can see whether usage changed. Add context to the raw logins: a regional manager who logs in once a quarter to approve discounts is active, and so is a service account that an integration depends on. Exclude those from the dormant list after confirming with owners. Redress’s guidance is to combine dormant seats, over-edition users and unused add-ons into a single reduction figure, which is a sensible way to present results to leadership.
Deactivating seats safely
- Contact the user or manager first. Send a list of inactive users to each manager with a deadline and a plain explanation: if you need access, say so by this date, and if not, the seat will be deactivated and can be restored on request. Keep the replies. Managers often reveal that a user left months ago or that the person uses the system through another account. Treat the reply as a record of consent: a manager who confirms a seat can go has shared responsibility for the outcome, which makes later disputes much easier to settle.
- Freeze when you’re not ready to cut. Torii’s guide, which comes from a SaaS-management vendor, explains that freezing blocks new logins and ends the current session without setting the user to inactive, and that it’s useful for pending approvals, batch jobs or audits. Deactivation is the permanent step. Torii doesn’t say how either action changes license counts, so verify the effect in your own org before you rely on it. A freeze is a useful holding position for borderline users, because it stops risk from an unused login while the manager decides, and it can be reversed in seconds.
- Clear the blockers before deactivation. The guide lists cases that prevent deactivation: scheduled jobs owned by the user, default ownership of leads or cases, workflow alerts where the user is the only recipient and the last active system administrator. Reassign or delete those items first. A deactivation that fails halfway through a quarter-end cleanup creates its own work, so plan the sequence and test with a few users. Build a short checklist covering jobs, ownership, alerts and admin roles, and have a second admin review it before the first batch runs.
- Preserve the records and the rationale. The guide says records owned by deactivated users are kept. Even so, reassign ownership of important accounts and opportunities before the change, so reports and territories stay accurate. Log each deactivation with the date, reason and approver. If someone asks half a year later why they lost access, or if an auditor asks how you manage seats, the log answers both questions. Store the log in the same place as your license inventory so the next reviewer finds the history without asking anyone.
- Keep integration users out of the sweep. API accounts rarely log in interactively, so a naive login report marks them dormant. Deactivating such an account can break a sync with billing or marketing systems. Maintain a separate list of integration users with owners and purposes, and exclude them from the audit. Review that list yearly to remove accounts for systems you’ve retired. Tag them clearly and name an owner for each.
Moving the right users to a lighter license
SalesforceBen describes the Platform license as a lower-cost option that includes accounts, contacts, reports and automation tools but severely curtails the standard sales and service objects, with no opportunities. It lists custom object limits of 10 per user on Platform Starter and 110 on Platform Plus, says it’s available only on Enterprise and Unlimited editions and notes that users on different license types can coexist in the same org. The article gives no price, so confirm current pricing and limits with Salesforce.
Good candidates are people who work in custom apps or managed packages rather than in sales and service objects. The article suggests organizations that run most processes on managed packages, departments that don’t use opportunities, such as post-sales operations, and nonprofits with non-standard models. Walk through each candidate’s daily work. If they need cases beyond internal queries or any sales object the license excludes, a move will fail, and the cost of reversing it can exceed the savings.
Edition swaps and add-on decisions
| Question | Keep if | Reduce or drop if |
| Is the premium edition justified? | A named group uses features only that edition offers | The distinguishing features are unused or used by a handful |
| Is a mixed-edition estate possible? | Contract and technical rules allow different editions per cloud or user group | The agreement requires a single edition across the org |
| Does the add-on have an owner? | A business owner can state the use case and results | No owner, or a project that ended |
| Is the add-on assigned to active users? | Assigned users log in and use its features | Assigned to departed or dormant users |
| Is a cheaper tier available? | The tier covers actual usage and limits | Limits would block routine work |
| Does the renewal bundle hide the add-on? | Line items are visible and priced | The price is buried in a bundle with no breakdown |
Redress argues that over-provisioned editions can matter more than user counts and claims Unlimited carries a premium of roughly 50 percent over Enterprise, with about 60 percent of features unused. Neither figure has a source. Folio3’s page lists Enterprise at $175 and Unlimited at $330 to $350 per user per month, which would be a larger gap, and neither is verified against Salesforce’s price page. Use your own contract prices to compute the swap, and test whether the lower edition covers your limits for sandboxes, automation and storage.
What the contract allows
- Mid-term reductions are generally not available. Redress says there’s no mid-term reduction at all under standard terms, that fees are non-cancelable and non-refundable and that seats from cancelled projects keep billing until expiry. Its source is archived master agreement language it doesn’t link. Your own agreement and order forms govern, so read them rather than relying on any summary. Plan on that assumption, and treat any exception as a favor to negotiate for rather than a right.
- Renewal is the point of change. The same page says the reduction right in the archived language takes effect only on expiration of the current license term. That makes the renewal the only moment when quantity can fall, and it explains why preparation must begin months earlier. Ask Salesforce in writing how reductions are handled in your contract. Everything you do before that date is preparation, so the schedule matters more than the sales conversation.
- Notice windows are short and inconsistent in the sources. Redress’s pages cite 30 to 60 days, mention 30 days for the master agreement, say order forms commonly override it and describe a 5 business day deadline in archived language. The pages contradict each other on details. Treat the shortest date in your own documents as the deadline, and send formal written notice earlier than the last day. A date that looks generous in a single document may be shorter in another, so compile them all.
- Order forms override the master agreement. The advisor says order forms commonly set their own notice terms, and different products can carry different dates. Build a grid with a row for each product line showing quantity, price, term end, notice date and who holds the document. Put the dates in a shared calendar with reminders at 180, 90 and 60 days. Assign the grid to a named owner and review it whenever a new order form is signed.
- Silence can renew you. If your agreement auto-renews and the notice date passes, you may be committed to the next term at the old quantity, or worse, at a higher price. Ask counsel to read the renewal and termination clauses, and confirm the effective dates with your account team. Don’t assume that a verbal discussion with the account executive changes a written term. Ask counsel to flag renewal clauses in a short summary you can check each quarter.
Negotiation levers once the footprint is lean
Cap the annual increase. Redress recommends capping the annual escalator at 0 to 4 percent for the term, or fixing the price flat. It says the default escalator is 7 to 9 percent in some places and 7 percent elsewhere, and that most enterprise renewals cap at 2 to 4 percent, none of it sourced. On the illustrative $840,000 license base, 7 percent versus 3 percent is a $33,600 difference in a single year, and it compounds across a multi-year term.
Settle quantity and edition before price. Redress advises negotiating reduction and swap language before discussing price, and setting quantity before rate. The reason is practical: a discount applied to a large, wasteful quantity feels like a win while costing more than a smaller quantity at a lower discount. Present your audit results first, ask for confirmation of the reduced quantity in the draft order form, then move to price and term.
Use term, co-terming and timing deliberately. Redress lists multi-year terms, co-terming and multi-cloud bundles as levers that can raise discount bands, adds that Salesforce’s January fiscal year end may offer more discretion and warns that bundles don’t always reduce cost if you already sit at the top band. A longer term trades flexibility for price. Weigh that against your growth uncertainty before committing. Co-terming aligns several products to a single end date, which simplifies the calendar but can also remove a natural moment to reduce a single line on its own.
Document alternatives. The advisor recommends a documented competitive set as bargaining power, even if you don’t intend to switch. Evaluate alternatives honestly: switching a CRM costs far more than a renewal discount. The credible alternative, and the option that changes account team behavior, is often a reduced footprint with a different edition mix. Be ready to say what you’ll buy if the terms aren’t acceptable, and confirm all terms in writing.
Risks of cutting too deep
Rightsizing can go wrong if it ignores growth and seasonality. If you plan to hire 30 salespeople next year, a renewal cut to the bone leaves you buying seats mid-term at whatever price Salesforce offers. Ask for the price of additional licenses during the term, and request that it matches your renewal rate. Also ask what happens if usage exceeds your licensed quantity, and have counsel confirm any true-up or compliance terms in your agreement.
Beware of removing seats from people with infrequent but critical roles. The quarterly approver, the finance user who closes the books, the auditor who needs read access once a year and the executive who looks at pipeline before board meetings can all look dormant. A wrongly removed seat produces an urgent request at the worst time. Use the manager confirmation step, keep a short list of approved exceptions and review it each year.
A renewal calendar working back from the term end
- A year out, January 31, 2026 in this example. Redress suggests opening the process 12 months ahead for large contracts and 6 months ahead for smaller ones. Collect order forms, build the notice grid and name an owner. If you’re reading this late, as the example would be on October 14, 2026, compress the early steps into the next few weeks rather than skipping them. The point is that early preparation gives you options that a late start can’t.
- 180 days out, August 4, 2026. Start the login extract, which Redress recommends beginning about 180 days before term end for a 90-day window. Pull the HR joiner, mover and leaver list, inventory the add-ons and begin conversations with department heads. This is also the time to ask Salesforce for the renewal quote format and for any price protections in your agreement. Starting here also leaves time to find and fix data problems before they distort the reduction figure.
- 90 days out, November 2, 2026. Finish the audit and have the reduction number agreed internally. Move inactive users to a freeze or deactivation plan and complete pilots of any license changes. Share the draft renewal position with finance and legal. Redress also recommends negotiating the notice window itself out to 90 days, a good point to raise now. Agree who signs off internally, so approval doesn’t become the bottleneck.
- 60 days out, December 2, 2026. Redress recommends sending formal written notice around day 60 with a utilization file. Check this date against your order forms, since your own may be shorter or longer. Ask for written acknowledgment, and keep the transmission record. Negotiation continues after the notice, but the notice protects your right to reduce. Send it to every address and contact the agreement names, rather than only the account executive.
- 30 days out, January 1, 2027. Treat this as a hard stop, as the advisor does. Confirm the final order form quantities, editions, add-ons, uplift cap and term before signing. Have counsel review the document. Check that each line matches what you negotiated, because renewal paperwork sometimes restores items that were discussed and removed. Allow time for a second review of the final paperwork, since errors found after signing are expensive to correct.
Worked savings example
| Item (illustrative) | Assumption | Annual effect |
| Starting licenses | 400 users at $175 per month | $840,000 |
| Dormant seats | 48 users (12 percent) with no login in 90 days, deactivated | Save $100,800 |
| Lighter license type | 60 users moved from $175 to an assumed $75 per month | Save $72,000 |
| Unused add-on | 40 seats at an assumed $75 per month dropped | Save $36,000 |
| Total reduction | Sum of the items above | $208,800, or 24.9 percent |
| Licenses after review | $840,000 minus $208,800 | $631,200 |
The $175 price is Folio3’s reported Enterprise figure, and the $75 lighter license and $75 add-on prices are placeholders I chose for illustration, not Salesforce list prices. The 12 percent dormant rate is invented. Active users remain covered, since 352 of 400 keep access, and 60 of those move to a lighter license. The result lands inside Redress’s unsourced 18 to 32 percent range, but that proves nothing, since I built the example. Your audit will produce its own percentage.
Now add the contract effect. On the reduced base of $631,200, a 7 percent uplift gives $675,384 and a 4 percent cap gives $656,448, a $18,936 difference in the first renewal year alone. Without the review, a 7 percent uplift on $840,000 would be $898,800. The gap between that and the reviewed 4 percent case is $242,352 a year. Premium support, if priced at the 30 percent Redress suggests without a source, would be $252,000 on the original base and $189,360 on the reduced base, so the base shrinks that line too.
Keeping the savings after the renewal
Make license review a monthly habit. Assign an owner to review the user list each month for inactive seats, leavers and role changes. Connect the process to HR so a departure triggers deactivation within a defined number of days. Track the dormant rate over time. A renewal audit that finds 12 percent dormant seats and a monthly process that keeps the rate under 3 percent saves money every month, every month as well as on renewal day.
Control how licenses are requested. Create a simple request form that asks for the role, the manager’s approval, the required license type and the end date for temporary access. Default new requests to the lightest license that meets the need and require justification for an upgrade. This keeps the edition creep from rebuilding the problem. Publish the rules and the approver names, so requests don’t depend on who a user happens to know.
Report to leadership each quarter. Show seats purchased, seats active, dormant seats, add-on utilization and spend against budget, along with any planned hires or reductions. Use the report to prepare next year’s renewal rather than starting from scratch 6 months out. Include the next contract dates and who holds them. A leadership team that sees the numbers quarterly asks better questions, and the renewal stops being a surprise. Keep the report to a single page so people read it.
Questions to put to your account team in writing
- What quantity, edition and add-on lines are in the renewal quote, with unit prices? Ask for a complete line-item breakdown for every product, including any bundles. Compare each line with your current order forms and your audit results. A quote that shows only a total makes it impossible to see what has changed, and any discount offered on a bundle needs a visible baseline. Ask for the prior-term prices alongside, so any change is visible at a glance.
- What reductions are permitted at renewal, and by when must we notify you? Ask for the answer in writing, citing the clause in your agreement. Ask whether notice must be delivered in a particular form and to a particular address, and whether the account executive can acknowledge receipt. Confirm whether different order forms have different dates, and ask for a consolidated schedule. Keep the reply with your contract file, since it’s evidence if a dispute arises later.
- What’s the cap on annual price increases for the next term? Ask for it in the order form, rather than only in an email. Request the price for additional licenses during the term, and whether it matches your renewal rate. If the cap isn’t available on a single-year term, ask what a longer term would offer and what flexibility you’d give up. Compare the cap with the uplift in the draft quote, and challenge any gap before signing.
- Can we mix license types and editions? Ask which clouds and products allow it, what the technical and contractual limits are and whether any minimums apply. Ask what happens to permission sets when users move. Request written confirmation before you restructure the org, because a move that violates a rule is hard to undo. Share the answer with your admin and finance teams so the plan reflects what’s allowed. Keep it.
Measuring success
| Metric | How to calculate | Target direction |
| Dormant seat rate | Seats with no login in 90 days divided by total seats | Down |
| License cost per active user | Annual license spend divided by active users | Down |
| Add-on utilization | Active users of the add-on divided by assigned seats | Up |
| Renewal uplift achieved | New annual price divided by old, minus 1 | At or below the cap |
| Time to deactivate a leaver | Days from HR departure date to deactivation | Down |
| Access restore requests | Requests to reinstate removed seats | Low and falling |
Track the access restore requests carefully, because they measure whether the review removed seats it shouldn’t have. A handful of requests in the first month is normal. A flood means the audit window or exceptions list was wrong, and you should adjust before the next cycle. Present the full set of metrics at the quarterly review so leadership sees both the savings and the service effect. Log each request with its cause, because the pattern will show which rule needs adjusting.
In the illustrative example, license cost per active user falls from $2,100 a year across 400 users to $1,793 across 352 active users, a figure you can compute by dividing $631,200 by 352. That drop comes from removing waste, not from taking anything away from active people. If your numbers show a drop in active users after the review, investigate. The aim is that active users stay constant while the cost base shrinks.
Mistakes that cost renewals
The most expensive mistake is missing the notice date. A thorough audit achieves nothing if the written notice arrives after the window closes, and the pages reviewed here disagree on dates, which is a reason to read your own documents. Put the dates in a calendar owned by more than 1 person, send notice early and keep proof of delivery. Have counsel confirm the effective date of any change before you rely on it.
Another mistake is starting the audit too late. A login extract needs 90 days to mean anything, and negotiations take weeks, so beginning 6 weeks before renewal leaves no room for either. Teams that start late tend to accept the quote with a small discount because nothing else is ready. Start at least 6 to 12 months ahead, and compress the schedule only with a plan for which steps you’ll skip. Late starts also shorten your window to pilot license changes safely.
FAQs
Can I reduce my Salesforce license count in the middle of the term?
Redress Compliance says standard terms allow no mid-term reduction and treat fees as non-cancelable and non-refundable, with renewal as the usual point of change. It cites archived agreement language without a link. Your own order forms and master agreement control, so ask Salesforce in writing and have counsel read the clauses before you plan around any reduction. If a sales rep says otherwise, ask for it in the order form before you plan savings around it.
How do I find unused Salesforce licenses?
Pull last login dates for every user, the license type and edition assigned, add-on and permission set license assignments and feature usage by role. Flag users with no login in 90 days, confirm exceptions with managers and exclude integration accounts. Redress suggests a 90-day active-user audit, though its guidance doesn’t cite Salesforce as the source of that test. Keep the extract and your notes, because you’ll want to compare them against the post-renewal state.
Is freezing a user the same as deactivating them?
No. Torii’s guide says freezing blocks new logins and ends the current session while the user stays active, and deactivation sets the user to inactive. The guide doesn’t explain how either action affects license counts, so check in your own org. Clear blockers such as scheduled jobs and default ownership before deactivating. Treat freezing as a pause and deactivation as a decision, and record which action you used. Note the date.
What’s a Platform license, and who can use it?
SalesforceBen describes it as a lower-cost license with accounts, contacts, reports and automation but severely limited standard sales and service objects and no opportunities. It lists custom object limits of 10 on Platform Starter and 110 on Platform Plus and says it requires Enterprise or Unlimited. Confirm the price and limits with Salesforce, and pilot before moving users. Candidates are users whose daily work happens in custom apps rather than in sales objects.
How much can I realistically save at renewal?
It depends on your audit. Redress claims 18 to 32 percent is recoverable, but gives no method, so don’t treat it as a benchmark. In an illustrative 400-user example with 12 percent dormant seats, 60 users moved to a lighter license and an add-on dropped, the saving is $208,800, or 24.9 percent. Those inputs are invented, so measure your own. The size of the savings also depends on your contract prices, so recompute with your own figures.
When should I start preparing for a renewal?
Redress suggests opening the process 12 months ahead for large contracts and 6 months ahead for smaller ones, with a login extract about 180 days before term end. Because notice windows can be as short as 30 to 60 days, start earlier if you can. Late starts leave little room to pilot changes or compare options before dates arrive, so build in slack from the beginning. Pull every order form first and build a dated notice grid.
What should I negotiate besides price?
Negotiate quantity and edition first, then a cap on annual increases, the right to reduce at renewal, the price of additional licenses during the term, a line-item breakdown of bundles and the notice window itself. Redress suggests a cap of 0 to 4 percent, though its claims about typical caps are unsourced. Get every term in the order form and have counsel review it. Ask for each concession in writing as you go.
Will cutting licenses hurt users?
Not if the audit targets inactive seats, wrong editions and unused add-ons, and each change is confirmed with the user’s manager. Pilot license moves with a small group, keep a rollback plan and track access restore requests. If requests spike, adjust your exceptions list. Always keep integration accounts and infrequent critical roles out of automated sweeps. A short note to affected users explaining how to request access again also reduces frustration.
