You’re staring at the Salesforce renewal invoice and the total went up again. Headcount didn’t change. Nobody added a new Cloud this year. When you ask around, half the names on the user list haven’t logged in since spring, and nobody can tell you why three different platform add-ons are still on the contract. How much is Salesforce shelfware costing your mid-market org? Most orgs have never actually run the numbers, and the answer is almost always higher than they expect. This post walks through where shelfware actually comes from, what it typically runs at each license type, and how to find your own number before your next renewal conversation.
Quick Answer: Mid-market Salesforce orgs typically carry 20-40% in underutilized licenses, with the rate climbing in deployments three or more years old. The waste clusters in a few predictable places: (1) licenses bought for a pilot that never scaled back down, (2) seats left active after someone changes roles or leaves the company, (3) overlapping license pools left over from a merger or reorg, and (4) platform and add-on licenses, which run 30-50% underutilized because nobody assigns an owner to track them. A license and usage audit before renewal is the fastest way to find the real number for your org. See our post on how to ensure your Salesforce org is secure for the related access-hygiene side of this same problem.
Shelfware isn’t a Cloud Nexus term and it isn’t unique to Salesforce. It’s the standard industry word for software you’re paying for but not using, and Salesforce’s per-seat pricing model makes it unusually easy to accumulate without anyone noticing. Unlike a one-time software purchase, a stale Salesforce license renews itself every year at whatever rate your contract allows, which is typically 8-10% annually. That makes shelfware a compounding cost, not a one-time mistake, and it’s exactly the kind of problem a license and usage review at Cloud Nexus is built to catch before a renewal locks it in for another year.
1. You Licensed for the Pilot, Not the Rollout
Pilot-stage license counts rarely get right-sized once a project moves to full production. A team negotiating a new Cloud will often buy a buffer of extra seats to cover an uncertain rollout, planning to true it down once adoption numbers are clear. In practice, that true-down conversation never happens, because nobody owns it. The seats roll forward at full price, year after year, long after the pilot is a distant memory.
Fix: Pull your Setup → Company Information license counts against actual Login History for the last 90 days. Any license type with a meaningfully lower active-user count than assigned-seat count is a pilot that never got reconciled.
2. Nobody Deactivates a License When Someone Leaves
Offboarding checklists cover email and building access far more reliably than they cover Salesforce license deactivation. A departing employee’s user record often just sits there, Active, with a full license attached, because deactivating it isn’t anyone’s explicit job. Role changes cause the same problem in a quieter way: a rep promoted into a non-quota role keeps a full Sales Cloud license long after they stop touching Opportunities.
Fix: Run a report on Users where Last Login is null or older than 90 days, filtered to Active = true. In most mid-market orgs this single report surfaces the fastest, least controversial license count reduction available.
3. Mergers and Reorgs Leave Two License Pools Running
A merger or an internal reorg routinely leaves two overlapping sets of licenses active well past the point either team actually needs both. One documented case involved a company that kept 280 sales licenses running for two full years after an acquisition when the combined, de-duplicated team only needed 210 — a gap worth roughly $1.26 million in wasted license spend over that period. Nobody owned the consolidation, so the extra seventy seats simply never got cut.
Fix: Any merger, acquisition, or reorg should trigger a license reconciliation on a fixed calendar date — 90 days out, not “whenever someone gets around to it.” Treat it as a standing checklist item, not a judgment call.
4. Platform and Add-On Licenses Are the Worst Offenders
Platform and add-on licenses carry the highest shelfware rate of any Salesforce license category, commonly running 30-50% underutilized. These licenses get bundled into a deal during negotiation, assigned to a handful of users for a specific project, and then never revisited once that project wraps. Unlike core Sales Cloud or Service Cloud seats, nobody is watching daily usage on a platform license, so it quietly renews at full price indefinitely.
Fix: List every distinct license type on your contract, not just the two or three everyone thinks of first. For each one, name a single owner responsible for confirming it’s still needed before the next renewal cycle.
Here’s roughly what shelfware rates look like by license category in a typical mid-market deployment, based on aggregated license-utilization benchmarking across enterprise Salesforce orgs:
Service Cloud’s higher average is worth noting on its own. Service Cloud licenses are frequently assigned to a wider circle of occasional case-touchers — a sales rep who logs the odd case, a manager who checks in during an escalation — rather than to a tight core team of daily users the way Sales Cloud licenses usually are. That wider, shallower assignment pattern is exactly what produces a higher shelfware rate. Importantly, none of this means your org is being careless. It means license hygiene has no natural owner once the initial rollout is done, which is precisely the gap an outside Salesforce consulting engagement is positioned to close.
When to Act: Time the Audit to Your Renewal, Not After It
Salesforce’s own discount authority is typically highest in the final quarter of its fiscal year, from November through January. Running your license audit before that window, rather than after your renewal is already signed, is what actually turns the findings into negotiating leverage instead of a report nobody acts on. An audit completed in October gives you time to right-size counts, document the reduction, and walk into the renewal conversation with a number instead of a guess.
This is the exact exercise Cloud Nexus runs as part of a Salesforce org review: a full license and usage audit against your actual Login History, cross-referenced against every license type on your contract, not just the obvious ones. Most mid-market orgs that go through this process for the first time are surprised by which license category turns out to be the biggest offender, and it’s rarely the one they expected going in.
Frequently Asked Questions
How do I find out how much shelfware my org actually has?
Pull a report of all Active users filtered by Last Login date, cross-referenced against your full license inventory from your contract, not just what’s visible in the user list. Any license type where assigned seats meaningfully exceed 90-day active logins is a shelfware candidate. A formal org review will also catch platform and add-on licenses that don’t show up in a simple user-list check.
Is shelfware the same thing as a license being “inactive”?
Not exactly. An inactive license is one nobody is using at all. Shelfware is the broader, costlier category: it includes inactive seats, but also seats that are technically logged into occasionally while sitting on a far more expensive license tier than the user’s actual activity justifies.
How much does a license and usage audit typically cost compared to what it saves?
Audit scope and pricing vary by org size and license complexity, so there’s no single number that applies everywhere. As a reference point, mid-market orgs with multi-year-old deployments and 20-40% average shelfware rates typically find that even a partial right-sizing more than covers the cost of the review itself, especially when it’s timed ahead of a renewal rather than after one.
Does switching to fractional admin support help prevent shelfware from building back up?
Yes, because shelfware accumulates precisely when nobody owns license hygiene as an ongoing responsibility. Our post on full-time vs. fractional Salesforce developer support covers how a fractional arrangement can include this kind of recurring license review as a standing deliverable, rather than something that only happens once, right before a crisis.
What’s the first thing I should check before calling a consultant about this?
Start with your full license inventory from your actual Salesforce contract, not just the licenses visible in Setup, since platform and add-on licenses are easy to overlook. If you’re also unsure whether your organization is set up to catch this kind of drift on an ongoing basis, our post on red flags to watch for when evaluating a Salesforce consulting partner covers what a thorough partner should be checking as standard practice, license hygiene included.
Not Sure How Much Shelfware Is Hiding in Your Renewal?
Book a free 90-minute Salesforce Org Review with the Cloud Nexus team. We’ll audit your full license inventory against actual usage, flag the license types most likely to be overbought, and give you a phased plan for right-sizing before your next renewal lands.
Book Your Free Org Review →



