Salesforce Shelfware Elimination:
Reclaim Wasted Spend 2026

The Salesforce Shelfware Problem

Salesforce shelfware — licensed seats and capabilities that enterprises pay for but don't use — is one of the largest sources of avoidable IT spending in enterprise budgets. It accumulates for structural reasons: Salesforce's commercial model rewards expansion, account teams are incentivised to add licenses and features at every opportunity, and annual auto-renewals mean unused licenses persist indefinitely unless actively challenged. By the time an enterprise conducts its first formal utilisation analysis, the shelfware backlog is typically 30–40% of total Salesforce spend.

This article is part of our complete guide to Salesforce contract negotiation. The shelfware elimination process described here is one component of a broader renewal strategy — the data it generates informs the pricing negotiation, the competitive positioning, and the contract restructuring that produce the best commercial outcomes.

Types of Salesforce Shelfware

Salesforce shelfware takes several forms, each with different identification methodologies and negotiation approaches. Understanding the different shelfware categories — and building a comprehensive case across all of them — produces the strongest negotiating position.

Conducting the Utilisation Analysis

The utilisation analysis is the evidentiary foundation of any shelfware negotiation. Salesforce will resist license count reductions — they need specific, documented evidence to accept that a reduction is commercially justified. A well-constructed utilisation analysis makes this case quantitatively and is difficult for Salesforce to dispute.

Step 1: Pull Login History Data

In Salesforce, navigate to Setup → Monitoring → Login History. Export login data for the trailing 90 days (the minimum period; 180 days provides a more robust baseline). Analyse by user: users with fewer than five logins in 90 days are strong shelfware candidates. Users with zero logins in 90 days are almost certainly inactive. Filter out system users, integration users, and sandbox users — these are technical accounts that may show low login activity despite being genuinely necessary.

Step 2: Analyse Feature Utilisation

Salesforce's Setup Audit Trail and Feature Usage reports (available in Enterprise and Unlimited editions) show which premium features have been activated and accessed. Pull these reports for: Einstein features (if you're on Unlimited or have Einstein add-ons), Sales Engagement / High Velocity Sales, Salesforce Inbox, Sales Cloud Einstein, and any add-on products. Features that show zero or near-zero utilisation across active users are strong candidates for license tier downgrade or add-on removal.

Step 3: Map Users to License Tiers

Create a user-level mapping of: current license type, login frequency (from Step 1), features actually accessed, and the minimum license tier required for their actual usage. This mapping identifies users who are on Enterprise or Unlimited licenses but whose actual usage could be accommodated by Professional, Platform, or even Salesforce Platform Starter licenses. The per-license cost difference between Unlimited ($330/user/month) and Platform ($25–$100/user/month) is substantial for users whose actual usage is light.

Step 4: Quantify the Shelfware Value

Using the current contracted per-license rates, calculate the annual cost of each shelfware category: inactive users × current license price, tier-reducible users × (current tier price minus appropriate tier price), unused add-ons × add-on contract price. This quantification — the total annual value of identified shelfware — is the number that frames the negotiation with Salesforce. It becomes your target reduction ask.

Step 5: Apply the Organisational Context

Salesforce will challenge shelfware analyses that don't account for legitimate low-activity patterns. Before presenting the analysis, validate with business stakeholders: are any "inactive" users actually needed for future projects? Are any zero-login users technical accounts needed for integrations? Are any premium features genuinely planned for deployment in the near term? Removing these legitimate cases from the shelfware claim makes the remaining case stronger and more defensible.

The Shelfware Reduction Negotiation

Salesforce will not proactively reduce your license count. Their commercial model depends on maintaining or growing contract value at each renewal. The shelfware elimination negotiation is therefore adversarial in a specific sense: you are asking Salesforce to accept a contractual reduction that reduces their ACV from your account. Effective negotiation requires understanding Salesforce's incentives, framing the request appropriately, and having a credible consequence if Salesforce refuses.

Framing: The Long-Term Relationship Argument

The most effective framing for a shelfware reduction request is not "we want to pay less" — it's "we need to ensure our investment in Salesforce is justified to internal stakeholders." When CFOs and CIOs see 35% of Salesforce licenses going unused, the internal challenge to the Salesforce investment becomes acute. Presenting this as a sustainability problem for the Salesforce relationship — rather than purely a cost-cutting exercise — positions Salesforce's account team as partners in solving it, rather than adversaries protecting ACV.

Timing: Use the Renewal Window

Shelfware reductions are most achievable as part of a renewal negotiation, not mid-contract. Mid-contract shelfware requests are technically possible but require Salesforce to process a contract amendment — which is a more complex and commercially uncomfortable request for their team than adjusting license counts at renewal. Timing the shelfware elimination as a renewal action, presented well in advance of the renewal date, gives Salesforce's team the commercial framework to process the reduction within their standard renewal workflow.

The Credible Alternative

Salesforce's willingness to accept license count reductions increases significantly when the enterprise has a documented competitive evaluation in progress. If a credible alternative is available — even as a partial replacement for specific use cases — Salesforce's commercial calculus shifts from "we can resist this reduction" to "we should accept this reduction to preserve the relationship." The shelfware elimination negotiation and the competitive positioning from the renewal strategy work together: neither is as effective alone as they are combined.

What Salesforce Will Offer Instead

Salesforce's standard response to shelfware reduction requests is to offer alternatives to a hard license count reduction: adoption success packages (Salesforce will provide implementation support to increase adoption), product add-ons that provide additional value (attempting to replace the shelfware with upsell), or flat renewals (no reduction, but no increase either). Evaluate each of these offers on their merits. An adoption success package can be genuinely valuable if the shelfware is due to deployment gaps rather than genuine lack of need. Product substitutions are often not equivalent value. Flat renewals should only be accepted if they come with price cap and other structural improvements.

Preventing Future Shelfware Accumulation

Eliminating existing shelfware is only half the challenge. Without governance changes, shelfware will re-accumulate between renewals — through ad hoc license additions requested by business units, scope creep in expansion discussions with Salesforce, and the natural attrition of users who are provisioned but not deprovisioned when they change roles or leave. The structural changes that prevent shelfware re-accumulation are as important as the elimination itself.

The most effective prevention measures: a central license management function that controls all Salesforce provisioning requests; quarterly utilisation reviews that identify inactive users before they accumulate to renewal scale; a defined SLA for deprovisioning users who leave or change roles (typically 5 business days from HR notification); and a requirement that all Salesforce expansion requests include documented utilisation justification before approval. Our SaaS contract optimisation service includes governance framework design that makes these processes sustainable at scale.