Software Shelfware Audit Guide: How to Find, Quantify, and Eliminate Wasted Licences

What Is Shelfware and Why Is It Everywhere

Shelfware is software that has been purchased — and is being paid for — but is not meaningfully deployed or used. The term originated in the era of boxed software that literally collected dust on a shelf. In the modern enterprise, shelfware is more likely to be a SaaS subscription where 40 percent of provisioned accounts have not logged in for 90 days, an enterprise software tier that was purchased to meet an anticipated growth trajectory that never materialised, or a bundled module within a larger platform agreement that nobody in the organisation was ever trained to use.

Shelfware is endemic because the buying and consuming functions in most organisations are disconnected. IT procurement negotiates the volume licence or the enterprise agreement — often under commercial pressure to commit to a high seat count to achieve a discount threshold — without certainty about how many users will actually adopt the software at that scale. The business unit that requested the software moves on to the next priority. The licences are provisioned, the invoices are paid, and nobody revisits the utilisation question until the next renewal cycle — at which point the default is to renew at approximately the same level, whether or not the deployment reality supports it.

Zylo's 2026 SaaS Management Index documents that the average enterprise manages approximately 275 SaaS applications, with only 53 percent of provisioned licences actively used. Flexera's research consistently estimates that 25 to 30 percent of total IT budgets are wasted on redundant tools, unused licences, and poor spend visibility. For a £20 million annual software spend, that represents £5 million to £6 million of recoverable waste — much of it directly accessible through a structured shelfware audit.

The Five Types of Enterprise Shelfware

Not all unused software is the same. Understanding the categories of shelfware helps prioritise reclamation effort and identify the root causes that a lasting optimisation programme must address.

Type 1: Zero-Login Accounts

The most straightforward category of shelfware is licences assigned to accounts that have had zero activity for a defined period — typically 30, 60, or 90 days. These accounts fall into three sub-categories: accounts assigned to employees who have left the organisation and whose access was never revoked; accounts assigned to employees who were onboarded with a licence but never adopted the tool; and accounts that were provisioned speculatively — ahead of a project that was subsequently delayed or cancelled — and never activated. Zero-login account shelfware is typically the most immediately recoverable: the licences can be cancelled, reallocated, or removed from the next renewal without any stakeholder engagement beyond confirming that the account holder is not simply on extended leave.

Type 2: Feature-Level Underutilisation

Many enterprise software platforms offer tiered licensing structures where higher tiers provide access to advanced features at a premium price. Feature-level shelfware occurs when a large proportion of users licensed at the premium tier are using only features available in the standard tier. This is particularly common in Salesforce, where Sales Cloud Professional, Enterprise, and Unlimited editions carry significant price differentials but where many users within the enterprise tier are performing the same basic CRM activities available at the Professional level. It is also common in Microsoft 365, where E5 licences are frequently deployed to users whose usage patterns are fully satisfied by E3 or E1 entitlements. Right-sizing from premium to standard tiers for identified users can produce substantial per-seat savings without any reduction in the capability available to the users who actually need the premium features.

Type 3: Functional Duplicates

Functional duplicate shelfware occurs when two or more applications performing essentially the same function are being maintained and paid for simultaneously. This is extremely common in large enterprises where business units have historically made independent software purchasing decisions without visibility into what other parts of the organisation are using. A common pattern: four different business units each paying for separate video conferencing, project management, or document management tools that serve the same purpose. The organisation is paying four times for the same capability, and the users of the less-popular tools are the de facto shelfware holders. Rationalising functional duplicates requires stakeholder engagement and change management but produces the largest per-application savings of any shelfware category.

Type 4: Bundle Overprovisioning

Enterprise software bundles — Microsoft 365 suites, Salesforce platform agreements, IBM Cloud Pak bundles — are frequently purchased at a bundle level that includes capabilities the organisation never intends to use. Microsoft 365 E5 bundles include Microsoft 365 Defender, Microsoft Sentinel, Purview compliance tools, and Power BI Premium among many other capabilities. IBM Cloud Pak bundles include Red Hat OpenShift, which is a significant independent cost if licensed separately but is frequently deployed as an incidental component of the Cloud Pak without the licensing implications being fully understood. Bundle overprovisioning shelfware occurs when the bundle is the licensing vehicle of convenience but large portions of the bundled capability are never deployed. The remedy is either to right-size the bundle level at renewal or to strategically expand deployment of the already-paid-for capabilities to extract value from the existing investment.

Type 5: Vendor-Maintained Legacy Licences

The final category of shelfware is perpetual licences for software that has been effectively superseded within the organisation — either by a newer version of the same product, a migration to a cloud equivalent, or adoption of a competitive alternative. These perpetual licences continue to generate support and maintenance fees (typically 18 to 22 percent of the original licence value annually for major vendors) even when the software is no longer in active use. For IBM, this can include maintenance fees on IBM Rational, IBM Integration Bus, or IBM DataStage licences for products that have been migrated to cloud or open-source alternatives. For Oracle, it can include support fees on on-premises database licences for databases that have been migrated to Amazon RDS or Azure SQL Database. Identifying and cancelling maintenance on superseded perpetual licences is often the most immediately actionable source of shelfware savings in mature on-premises software estates.

The Shelfware Audit Process: Six Steps

A shelfware audit is not a one-time event — it should be an annual discipline embedded in the software asset management function. But for organisations running a shelfware audit for the first time, the following six-step process provides a structured approach to moving from no visibility to actionable savings in six to eight weeks.

Step 1: Build the Software Inventory

The shelfware audit starts with a complete inventory of everything the organisation is paying for. This is deceptively difficult to produce. Enterprise software spend is distributed across IT budgets, business unit budgets, corporate credit cards, and cloud marketplace charges. The inventory should capture: vendor, product, licence type (subscription versus perpetual), number of licences purchased, cost per licence, total annual cost, and the contract renewal date. Do not attempt to assess utilisation before the inventory is complete — an incomplete inventory produces an incomplete audit, and the gaps are typically where the largest waste concentrates.

Practical data sources for the inventory include: accounts payable records (invoice data captures what is being paid for, even if IT does not know about it), the vendor-side customer portals maintained by major SaaS vendors (Salesforce's License Management App, Microsoft's admin centre, ServiceNow's licensing dashboard), procurement contract repositories, and the outputs of any SAM tooling already in place. For organisations with no prior SAM programme, a spend analytics approach — starting from accounts payable and building up — typically produces the fastest first inventory.

Step 2: Establish Utilisation Baselines

With the inventory in place, collect utilisation data for each application. The data sources vary by platform. For Microsoft 365: the Microsoft 365 admin centre provides per-user activity reports showing last login, email activity, Teams usage, SharePoint activity, and which specific Microsoft 365 features each user has accessed in the past 30 days. For Salesforce: the Salesforce License Management App (LMA) tracks per-user login frequency and feature usage. For ServiceNow: platform usage reports show active users and feature adoption by licence type. For IBM software on virtualised infrastructure: IBM License Metric Tool (ILMT) provides the authoritative sub-capacity utilisation data — but only if it has been correctly deployed and is actively scanning. For organisations without ILMT deployed, this step surfaces both the shelfware opportunity and an immediate compliance risk that must be remediated.

Establish a utilisation threshold for each application category. A 30-day no-login threshold is appropriate for daily-use tools like email and CRM. A 90-day threshold is more appropriate for periodic-use tools like HR systems and document management platforms. Apply the threshold consistently, flag accounts below it, and document the count and associated licence cost for each flagged application.

Step 3: Classify and Prioritise by Value

Not all shelfware is worth the same effort to recover. An application with 15 unused licences at £8 per seat per month represents £1,440 of annual recoverable value — meaningful, but not the audit's primary focus. An application with 400 unused licences at £120 per user per year represents £48,000 of annual recoverable value. Classify the audit findings into three tiers: Tier 1 (above £50,000 annual recoverable value — immediate action), Tier 2 (£10,000 to £50,000 — action at next renewal cycle), and Tier 3 (below £10,000 — include in renewal planning but do not require dedicated project resources). The classification ensures that the audit team's capacity is directed at the savings opportunities with the highest financial return.

Step 4: Validate with Application Owners

Before acting on shelfware findings, validate with the application owners and business unit stakeholders. A user who has not logged into Salesforce for 90 days may be on maternity leave, working on a long-term project that does not require CRM access, or in a role where Salesforce is a quarterly-use tool rather than a daily one. Validating the audit findings with application owners takes time but prevents the mistake of cancelling licences that are legitimately needed — a mistake that is both operationally disruptive and commercially embarrassing. A simple questionnaire covering each flagged user or account, sent to the application owner with a two-week response window, catches most legitimate exceptions while confirming the bulk of genuine shelfware.

Step 5: Execute the Reclamation

Confirmed shelfware can be reclaimed through three mechanisms, depending on the contract terms and the timing relative to the renewal date. Immediate cancellation is possible for SaaS subscriptions where the agreement permits mid-term reduction — check the contract, as many enterprise SaaS agreements do not permit seat reduction before the renewal date. Reallocation — reassigning unused licences from a department that does not need them to a department that is approaching its entitlement limit — creates value without requiring a renegotiation. Renewal reduction is the most common reclamation mechanism: the audit findings define the reduced seat count that the organisation will take to renewal, supported by the utilisation data that demonstrates the business case for the reduction.

For vendor agreements with auto-renewal clauses, the timing of the reclamation decision is critical. If the renewal deadline for reducing seats has passed without notification, the organisation may be locked into the current seat count for another contract term regardless of the audit findings. This is why integrating the shelfware audit into the 90-day renewal countdown is so important — the audit output needs to be available before the renewal negotiation begins, not discovered after it has concluded.

Step 6: Quantify and Report Savings

The final step is quantifying the recovered value and reporting it to the stakeholders — finance, the steering committee, and the IT leadership team — who need to see the return from the shelfware audit investment. Savings should be reported in three categories: immediate savings (licences cancelled mid-term), renewal savings (seat count reductions agreed at renewal), and avoided costs (shelfware identified and removed from renewal scope before the vendor could charge for another term). A well-executed shelfware audit across a £20 million software estate typically recovers £1.5 million to £3.5 million in the first cycle. Subsequent annual audits, conducted as a routine part of the SAM programme, produce incremental savings as new shelfware accumulates and is identified before it compounds over multiple renewal cycles.

Vendor-Specific Shelfware Patterns

Microsoft 365 Shelfware

Microsoft 365 is the most common source of enterprise shelfware by volume, because it is typically deployed organisation-wide and licensed at a uniform tier regardless of individual user needs. The most frequent finding is E5 licences assigned to users whose actual usage is fully satisfied by E3 capabilities. The Microsoft 365 admin centre's usage reports provide the evidence base for a tier-down conversation with Microsoft at EA renewal. Microsoft's renewal process for tier changes is well established and manageable, provided the organisation enters the conversation with documented utilisation data and sufficient lead time to negotiate before the auto-renewal date.

Salesforce Shelfware

Salesforce shelfware concentrates in two areas: user licences assigned to employees who have changed roles and no longer need CRM access, and platform licences purchased to accommodate an expected expansion of Salesforce use cases that never progressed. Salesforce's contract terms typically do not permit mid-term seat reduction, which means shelfware identified outside the renewal window can only be addressed at the next renewal. Tracking Salesforce utilisation on a quarterly basis — using the LMA — and surfacing the findings 90 days before renewal ensures that the reclamation opportunity is not missed.

IBM Software Shelfware

IBM software shelfware often takes the form of PVU-licensed products on virtualised infrastructure where the PVU count was set based on a deployment footprint that has since been reduced through infrastructure consolidation. If the IBM software is still licensed at the original PVU count but the underlying server infrastructure has been consolidated, the organisation is paying for processor capacity it no longer consumes. IBM ILMT provides the data to validate a PVU reduction at renewal. Additionally, IBM's transition from PVU-based to VPC-based licensing for many products has created compliance gaps where organisations have not correctly mapped their deployments to the new licensing metric — ILMT is essential for demonstrating compliance under the VPC model as well as the PVU model.

Oracle Database Shelfware

Oracle Database shelfware most commonly occurs as named user plus licences on databases that have been consolidated or migrated. Following a database migration project — from on-premises Oracle to Amazon RDS or Azure SQL Database, for example — the on-premises Oracle Database licences are frequently retained in the Oracle support agreement even when the database deployment has been decommissioned. Validating that retained Oracle licences correspond to live, deployed databases is one of the highest-ROI activities in an Oracle-heavy shelfware audit. Oracle's support cost is typically 22 percent of the original licence fee annually — a substantial recurring charge for a database that is no longer running.

Converting Shelfware Findings into Negotiating Leverage

The shelfware audit's commercial value extends beyond the immediate cost savings. The audit findings change the organisation's position in every renewal conversation. An organisation that enters a Salesforce renewal negotiation with documented evidence that 28 percent of current licences are unused is not in the same position as one that enters the same conversation without that data. The former can credibly propose a 25 percent seat reduction as the baseline for renewal, forcing Salesforce to choose between accepting a smaller contract or demonstrating sufficient value to retain the current commitment. The latter has no alternative to accepting Salesforce's renewal proposal, because it lacks the evidence to challenge it.

Quantifying the shelfware value and presenting it to vendors as part of the renewal conversation is the bridge between the audit and the commercial outcome. The statement "our utilisation analysis shows that we are currently using 72 percent of our Salesforce licences at the Enterprise tier, and we intend to right-size to reflect actual deployment" is a commercial position grounded in data. Vendors can argue against it, but they cannot dismiss it. And vendors who understand that the organisation has done the analytical work to support the position typically respond with a more competitive commercial offer than they would have provided to a customer negotiating on the basis of general dissatisfaction rather than specific evidence.

Making the Shelfware Audit a Continuous Programme

A one-time shelfware audit delivers a one-time saving. The value compounds when the audit becomes a continuous programme: a quarterly utilisation review for tier-1 vendors, an annual full-portfolio shelfware assessment, and a standing obligation to surface shelfware findings as part of every renewal preparation process. Organisations that embed this discipline into their Software Asset Management or Software Licensing CoE function consistently maintain shelfware rates below 20 percent — compared to the 47 percent industry average — and generate ongoing licence savings that fund the SAM programme itself many times over.

The technology to support a continuous shelfware programme does not require a large investment. SaaS management platforms such as Zylo, Torii, or BetterCloud provide continuous visibility into SaaS utilisation and shadow IT at a cost that is typically justified by the first quarter of shelfware savings they surface. For on-premises and hybrid environments, existing SAM tooling combined with vendor-provided usage dashboards provides sufficient data for a quarterly utilisation review. The limiting factor is not tooling — it is governance: someone must own the shelfware programme, set the utilisation thresholds, run the quarterly reviews, and ensure the findings feed into the renewal preparation process. That governance is the Software Licensing CoE's most straightforward value-add, and it is the reason that organisations with a functioning CoE consistently outperform peers on total software spend efficiency year after year.

Getting External Support for the Shelfware Audit

The shelfware audit is a task that can be executed entirely with internal resources — provided the SAM programme has the data infrastructure, the staff capacity, and the vendor expertise to interpret the findings correctly. Organisations that lack one or more of these elements frequently benefit from external support, particularly for the analysis of complex on-premises vendor environments (Oracle, IBM, SAP) where licence metrics require specialist knowledge to interpret correctly.

External support is particularly valuable for two specific aspects of the shelfware audit process. First, the vendor-specific licence interpretation layer: identifying that an Oracle Database deployment has 80 unused named user plus licences is relatively straightforward; understanding whether those licences can be cancelled at renewal without triggering support cost changes, and whether the reduced entitlement creates any compliance risk given Oracle's deployment rules, requires Oracle licensing expertise that most internal teams do not have. Second, the negotiation translation layer: converting the shelfware findings into a commercially effective renewal position requires understanding how the vendor's account team will respond to a proposed seat reduction, what counter-arguments they will make, and how to structure the negotiating position to maximise the probability of achieving the target outcome. This is where specialist advisors with active knowledge of current vendor commercial behaviour add consistent and measurable value.

Redress Compliance has conducted shelfware audits across some of the largest enterprise software estates in Europe and North America, covering Oracle, Microsoft, SAP, IBM, Salesforce, ServiceNow, and the full range of SaaS platforms. If you are preparing to run a shelfware audit or want an independent assessment of your current software utilisation, our team is available for an initial consultation at no charge.