Shelfware is the share of paid software licenses that delivers no business value. Three patterns dominate. Licenses purchased and never deployed. Licenses deployed and never used. Licenses deployed, used briefly, and abandoned. Together they regularly account for 15% to 35% of an enterprise software estate.
The audit finds the volume across every named publisher. The quantification turns license counts into recoverable dollars. The recovery moves that follow turn quantified savings into reduced renewal commitment.
Read this alongside the Software Spend Assessment, the Spend Health Check, the Renewal Program, the Benchmark Program, and the Vendor Shield subscription.
Key Takeaways
What a CFO and procurement lead need in 60 seconds
- Shelfware is 15% to 35% of most enterprise estates. Higher on M365, Salesforce, and ServiceNow.
- Three patterns cover most shelfware. Purchased and undeployed, deployed and unused, abandoned after pilot.
- Audit method is mechanical. Entitlement reconciliation, deployment proof, usage telemetry, business owner sign off.
- Quantification has three layers. Annual cost, recoverable on renewal, multi year value.
- Recovery moves are five. Reduce at anniversary, mix shift, sublease internally, cancel, redeploy.
- The audit cycle runs ninety days. Scope, evidence, recommendation, sign off, action.
- The savings fund the program ten times over. Even at modest hit rates on a mid market estate.
Three shelfware patterns
Almost every shelfware finding maps to one of three patterns. The pattern dictates the recovery move.
The three patterns in detail
- Purchased and undeployed. Licenses bought during a discount window, ULA, or commitment, and never installed or assigned.
- Deployed and unused. Licenses assigned to users or instances, with no login, no API call, or no measurable activity over a defined period.
- Abandoned after pilot. Licenses deployed for a pilot, the pilot ended, the licenses remained on the bill.
Common root causes per pattern
- Discount window over commitment. The pattern one driver. Vendor pushes a larger commitment for a deeper headline discount.
- Provisioning without process. The pattern two driver. Licenses assigned during onboarding without offboarding discipline.
- Pilot without exit. The pattern three driver. Pilot success criteria undefined, contract auto renews.
Audit scope and method
A shelfware audit covers every paid license across every vendor in scope. The method is mechanical and reproducible.
Six audit steps
- Scope. Vendor list, license types, time window. Typically the trailing twelve months.
- Entitlement reconciliation. Contracted license count per SKU, per vendor, per cost center.
- Deployment proof. Provisioning records, identity provider exports, vendor admin console exports.
- Usage telemetry. Login records, API call counts, feature usage flags over the window.
- Business owner sign off. Manager or product owner confirms each unused license set.
- Recommendation. Reduce at renewal, mix shift, cancel, redeploy.
- SAM tooling. Flexera, ServiceNow SAM Pro, Snow, USU. Useful but not sufficient for cloud SaaS shelfware.
- Vendor admin consoles. Microsoft 365 admin center, Salesforce setup, Adobe admin console, ServiceNow user records.
- Identity provider exports. Azure AD, Okta, Ping. Drives the deployment proof step.
- Cost center reconciliation. Finance system export. Joins license to budget owner.
- Custom telemetry. Direct API queries to vendors that publish detailed usage data.
Where shelfware hides per vendor
Each major publisher has signature shelfware patterns. The table below maps the patterns to the recovery move.
Shelfware hotspots and recovery levers per vendor
| Vendor | Common shelfware hotspot | Primary recovery lever |
|---|
| Microsoft | E5 over assigned, Power Platform per user idle | EA mix shift to E3 or F3, Power Apps per app |
| Oracle | ULA over deployed at certification, options enabled but unused | Right size at certification, deselect unused options |
| SAP | Indirect access named users, S/4HANA conversion buffer | RISE conversion credit, contract reduction right |
| Salesforce | Unlimited or Enterprise users without login in 90 days | Reduce at anniversary, downgrade SKU |
| IBM | ILMT measured PVU spread over unused VMs | Sub capacity rebaseline, deactivate workloads |
| Broadcom and VMware | VCF cores over committed, vSAN entitlement excess | Renewal reduction, alternative hypervisor |
| AWS | EDP committed spend higher than burn | Renegotiate commit, mix to Savings Plans |
| ServiceNow | Fulfiller seats inactive, ITAM and ITOM under used | Renewal reduction, module trade out |
| Workday | Module activated but not consumed by HR processes | Module deactivate at renewal |
| Cisco | EA commitment higher than actual ELA consumption | Reduction at true forward, mix to consumption |
Cloud SaaS shelfware specifics
- Default activity threshold. Ninety days no login as the shelfware flag.
- Feature usage layer. Login alone is not enough on high tier SKUs. Tag feature usage as well.
- Bot and integration accounts. Often counted as licensed users without business value.
- Sandbox seats. Often licensed at full SKU cost when a developer SKU would cover the use case.
Quantifying the loss
Three layers turn a shelfware finding into a dollar number on the CFO's spreadsheet.
Three quantification layers
- Annual cost. Unit price times shelfware license count times utilization gap. Today's direct cost.
- Recoverable on renewal. Share of shelfware that can be removed at the next anniversary, given contract terms.
- Multi year value. Three to five year cumulative impact, including assumed price uplift avoided.
Indicative quantification on a 5,000 seat estate
| Vendor | Total spend (USD) | Shelfware share | Annual recoverable (USD) |
|---|
| Microsoft | 10,000,000 | 22% | 2,200,000 |
| Oracle | 5,000,000 | 18% | 900,000 |
| Salesforce | 4,000,000 | 28% | 1,120,000 |
| ServiceNow | 3,000,000 | 20% | 600,000 |
| SAP | 3,500,000 | 15% | 525,000 |
The recoverable layer is not the same as the annual cost
Contracts rarely allow full mid term reduction. The recoverable layer is the share of identified shelfware that can be removed at the next anniversary under existing clause language. The multi year value layer captures the avoided uplift on the removed licenses.
Recovery moves
Five recovery moves cover almost every shelfware finding. The right move depends on the pattern, the contract, and the vendor relationship.
The five recovery moves
- Reduce at anniversary. Step down the SKU count at the next contractually allowed reduction window.
- Mix shift. Move users to a lower SKU. Common on Microsoft EA and Salesforce.
- Sublease internally. Reassign licenses across business units, removing duplicate procurement.
- Cancel. Decommission the workload entirely. Most viable on abandoned pilots.
- Redeploy. Move licenses to high value workloads, demonstrating fully deployed status to the vendor.
Clause language that unlocks recovery
- Reduction right. 10% to 20% step down at each anniversary on named SKUs.
- Mix shift right. Convert higher SKU to lower SKU at the same anniversary.
- True forward only. Growth re priced annually, never list, never with retroactive uplift.
- Conversion credit. ULA or commitment unwound into credit for new services.
- Exit clause. Right to terminate on material change, with a defined notice period.
Common shelfware audit traps
Five traps catch most internal shelfware programs. Each carries a buyer side fix.
The five traps
- Login as proxy for value. Login alone misses high tier shelfware where feature usage is the real metric.
- Annual cost as the headline. Recoverable on renewal is the more useful figure.
- SAM tool only. SAM coverage rarely covers every SaaS, GenAI, or industry specific tool.
- No business owner sign off. Recommendations stall without named owner accountability.
- Vendor led audit. Vendor SAM engagements rarely surface shelfware findings.
Shelfware is the only line item where the customer pays for nothing in return. The audit finds it. The contract recovers it. The discipline keeps it out the next time around.
What to do next
The eight step buyer side checklist below carries a shelfware audit from scope to recovered spend.
- Define scope. Vendor list, license types, trailing twelve months window.
- Pull entitlements. Contracted license counts per SKU per vendor.
- Pull deployment proof. Admin console exports plus identity provider records.
- Pull usage telemetry. Login, API, and feature usage over the window.
- Score every license. Active, partially active, dormant, abandoned.
- Get business owner sign off. Named owner confirms each dormant set.
- Quantify the loss in three layers. Annual cost, recoverable on renewal, multi year value.
- Feed the recovery moves into the next renewal. Buyer side advisor on the call.
Frequently asked questions
What counts as software shelfware?
Shelfware is any paid software license that delivers no measurable business value. Three patterns dominate.
Licenses purchased and never deployed, often during a discount window or ULA. Licenses deployed to users or instances but never logged in or used over a defined period. Licenses deployed for a pilot that subsequently ended without the contract being cancelled.
The audit identifies all three patterns across every paid vendor in scope.
How much shelfware is normal in an enterprise estate?
The typical enterprise estate carries between 15% and 35% shelfware across paid software vendors. Higher concentrations are common on Microsoft 365 high tier SKUs, Salesforce Unlimited Edition seats, ServiceNow fulfiller licenses, and Power Platform per user licenses. Lower concentrations appear on infrastructure software bought against a hard capacity requirement.
How long does a shelfware audit take?
A focused shelfware audit on a single major publisher typically runs four to six weeks from scope to recommendation. A multi vendor audit covering Microsoft, Oracle, Salesforce, ServiceNow, and SAP runs around ninety days. The duration depends on contract complexity, the maturity of the SAM data, and the speed of business owner sign off on dormant license sets.
What is the difference between annual cost and recoverable on renewal?
Annual cost is the direct dollar value of the shelfware licenses at the current contracted unit price.
Recoverable on renewal is the share of that annual cost that can be removed at the next anniversary under existing contract terms.
Most contracts allow only partial mid term reduction, so recoverable on renewal is the more useful figure for negotiation modeling and CFO reporting.
Can shelfware be removed mid term?
Mid term reduction is rare but possible on a small set of contract structures.
SaaS contracts with explicit reduction rights, on demand or pay as you go cloud commitments above a defined floor, and certain Microsoft CSP arrangements all allow some form of mid term step down.
Most Enterprise Agreements and ULA structures only allow reduction at anniversary or renewal, with the buyer side leverage rising sharply at those windows.
How does Redress engage on shelfware audits?
Redress runs shelfware audits inside the Software Spend Assessment and the Vendor Shield subscription. Every engagement is led by an independent buyer side advisor with no vendor sales conflict. The engagement covers entitlement reconciliation, deployment proof, usage telemetry, business owner sign off, multi vendor quantification, and the recovery moves fed into each renewal in the trailing twelve months.
How Redress engages on shelfware strategy
Redress runs shelfware advisory inside the Software Spend Assessment, the Vendor Shield subscription, the Renewal Program, and the Benchmark Program.
Read the related benchmarking page, the about us page, the locations page, and the contact page.
