Home  ›  Blog  ›  Salesforce Shelfware Audit
Salesforce · Optimization · Renewal

Salesforce shelfware — found, quantified, eliminated.

Salesforce contracts are designed to grow. Every renewal adds a small percentage of seats, every acquisition layers on a CPQ or Service Cloud line, and the True-Up provision quietly converts pilot deployments into permanent commitments. The shelfware mostly sits in plain view — in the User Login History, the Permission Set assignments, and the Last Login Date. Finding it takes a week. Removing it takes a renewal cycle.

Updated: July 2026 Reading time: 12 min Audience: IT Asset Manager, Salesforce Admin, Procurement
Salesforce dashboard
The shelfware signature

What unused Salesforce actually looks like.

Salesforce shelfware breaks down into five recognisable categories. Inactive users — accounts that have not logged in for 90+ days. Over-tiered users — Sales Cloud Enterprise users who only need Sales Cloud Professional features. Misallocated users — Service Cloud licences assigned to people who never open a case. Duplicated add-ons — CPQ licences sitting alongside out-of-the-box quoting workflows. Pilot residue — pilots that ended without de-provisioning the licences. Each pattern has a different remediation path, and mapping them org-wide is the opening step of any serious software license optimization exercise.

The Last Login signal

The single highest-value query against any Salesforce org is the user list filtered by Last Login Date > 60 days. In our experience across 340+ engagements, this query alone surfaces 8–22% of the active licence count as candidates for reclaim. The number creeps higher with org age — 5-year-old orgs typically run 15–25%.

The Permission Set signal

Sales Cloud Enterprise carries Permission Set entitlements that Sales Cloud Professional does not — Territory Management, Advanced Forecasting, Customizable Forecasts. Users who hold an Enterprise licence but no Enterprise-only Permission Set assignment are tier-mismatched. The same logic applies to Service Cloud, Marketing Cloud and CPQ tiers.

Salesforce renewal in 9 months or less?

The shelfware identification window closes at the order form. We typically reclaim 15–25% of the licence count before signature.

Contact Us →
The True-Up overlay

Why most shelfware never gets removed.

Salesforce contracts contain a True-Up clause that allows the customer to add seats mid-term at the prevailing rate, but they do not allow seat reductions mid-term. The seat count is locked at the high-water mark, which means every mid-term addition compounds — and only renewal allows reduction. Customers who provision freely between renewals find themselves over-committed at the renewal point, with very limited window to reduce.

The renewal-window reduction right

Most Salesforce master agreements give the customer a 90-day pre-renewal window in which to notify Salesforce of seat reductions. The notice has to be in writing, has to reference the renewal date, and has to be specific about the SKUs being reduced. Customers who miss this window cannot reduce at renewal — only at the renewal after that. We have seen multi-million-dollar shelfware locked in because the 90-day notice was missed.

The annualisation problem

Mid-term additions are not always annualised properly. A seat added in month 8 of a 12-month term is sometimes billed as a full year, even though it expires in 4 months. The pro-ration mechanics depend on the contract version — some explicitly pro-rate, some do not. Read the clause. Customers on legacy contracts often have shelfware that is being billed past its actual term.

The renewal reduction playbook

Six moves that actually reduce the bill.

  1. 180-day audit. Run the full inactive-user / Permission-Set / case-volume queries 180 days before renewal. Earlier than that and the data drifts; later and the order-form work is rushed.
  2. 90-day notice. File the formal seat-reduction notice in writing inside the contractual window. Without it, the reduction is not enforceable.
  3. Tier remap. Re-tier users individually — Enterprise to Professional, Service Cloud to Lightning Service, Marketing Cloud Pro to Engagement.
  4. Add-on rationalisation. CPQ, Sales Engagement, Inbox, Pardot add-ons each have separate usage thresholds and should be assessed independently.
  5. Data Cloud / Einstein cap. Usage-based SKUs ratchet up; renegotiate the consumption commit at renewal, not after.
  6. Multi-year discount trade. Salesforce offers material discounts for 3-year commits; trade discount depth for flat-line seat counts to protect against future shelfware compounding.

Download the Salesforce Renewal Playbook.

Includes the shelfware identification queries, the 90-day notice template and the tier remap worksheet.

Get the playbook →
What Salesforce account teams expect

Why pushback is structurally light.

Salesforce account executives are compensated on growth, not on contraction. A reduction conversation is something most AEs will push back on with a default response — "you might need them later" — but most do not have the commercial mandate to refuse a contractually-permitted reduction. The pushback is theatre. The leverage is contractual.

What pushback looks like

Common AE responses: a counter-offer of additional add-ons at a discount, a multi-year extension with the same seat count, an Einstein/Data Cloud add-on instead of the reduction. Each of these is a tactic to preserve total contract value rather than reduce it. The customer's response should be the contractual reduction right, in writing, on the timeline.

Salesforce AE refusing a reduction request?

We escalate reduction conversations to the right commercial point of contact. The contractual right is enforceable.

Contact Us →
FAQ

Common questions.

Can Salesforce licences be reduced mid-term?
No. Salesforce contracts allow seat additions mid-term at the prevailing rate but not seat reductions. Reductions can only be made at renewal, and only if the formal pre-renewal notice has been filed inside the contractual window.
How long is the pre-renewal notice window?
Most Salesforce master agreements set the notice window at 90 days before renewal. Some legacy contracts run 60 days; some recent ones run 120 days. Read the specific contract — missing the window forfeits the reduction right for that renewal.
What counts as an inactive user in Salesforce?
Operationally, a user with no Last Login activity for 60+ days is a candidate. Permanent inactivity (no login for 180+ days) is high-confidence shelfware. The Last Login Date field is the primary signal.
Can I downgrade Sales Cloud Enterprise users to Professional?
Yes, at renewal. Users moving from Enterprise to Professional lose access to Enterprise-only features (Territory Management, Customizable Forecasts). The downgrade saves roughly 30% per affected seat.
Does Salesforce True-Up create permanent shelfware?
Sometimes. Seats added mid-term lock to the renewal — if usage drops, the seats stay until the next renewal window. The contractual reduction right only operates at renewal, not on usage.
How much shelfware do typical Salesforce orgs run?
In our experience across 340+ engagements, mature Salesforce orgs run 12–25% shelfware against the active seat count. Five-year-old orgs trend higher. The number is reliably reducible with disciplined renewal-window work.

Salesforce renewal in the next 12 months?
Reclaim the shelfware before the order form locks.

Our Salesforce practice runs the shelfware identification, the 90-day notice and the AE pushback for a living.

The Compliance Brief

Weekly compliance intelligence for IT leaders.