SaaS License Reclamation: How to Eliminate Waste and Recover Budget (2026)

This article is part of our SaaS Contract Optimization: Enterprise Playbook. License reclamation is the foundational optimisation action that generates immediate budget recovery and establishes the utilisation baseline needed for every subsequent renewal negotiation.

Why SaaS License Waste Is Systemic

SaaS license waste is not a management failure — it is a structural outcome of how SaaS procurement works. Enterprise software is purchased in anticipation of usage that often never fully materialises; it is renewed automatically because the friction of cancellation outweighs the perceived effort of review; and it is never formally deprovisioned because no single person is accountable for doing so.

The three primary sources of SaaS license waste are over-provisioning (purchasing licenses based on optimistic headcount projections), orphaned accounts (employees who have left the organisation but whose licenses were never reclaimed), and project-based applications that were procured for a specific initiative and never decommissioned. Each source requires a different reclamation approach.

Step 1: Build the Utilisation Dataset

Effective license reclamation begins with data, not assumptions. You need utilisation data that is granular enough to identify individual unused licenses and recent enough to reflect current behaviour (not historical patterns from 12+ months ago).

Data Sources by Application Type

For SSO-integrated applications (most enterprise SaaS), your identity provider (Okta, Azure AD, Ping Identity) provides login frequency data at the user level. This is your fastest path to utilisation data and typically covers 60–80% of your enterprise SaaS footprint. Export last-login data for all users across all SSO-connected applications and filter for users with no login in the last 60 days as your initial reclamation candidate pool.

For applications not connected to SSO, utilisation data must be obtained directly from the vendor admin console or via API. Most major SaaS platforms (Salesforce, ServiceNow, Microsoft 365, Workday) have admin-level usage reporting. For smaller or less common applications, request a usage report from the vendor's customer success team — they are generally willing to provide this, particularly if you frame it as a pre-renewal review.

What Counts as "Unused"

Define your reclamation threshold before beginning analysis to avoid ambiguity later. A practical enterprise definition: a license is a reclamation candidate if the assigned user has not logged in within the last 90 days AND there is no documented business reason for the inactivity (such as a planned sabbatical, a seasonal role, or a compliance requirement for dormant account retention). Users inactive for 30–60 days should be flagged for manager review rather than automatic reclamation — they may be on leave or between projects.

Step 2: Validate with Business Owners

Utilisation data alone is not sufficient for reclamation. Before removing any license, you need confirmation from the business owner that the license is genuinely available for reclamation — not just temporarily unused. This validation step protects against reclaiming licenses that will immediately need to be re-provisioned for new hires, returning employees, or seasonal usage peaks.

The Reclamation Communication Process

Send a formal reclamation notification to the application's business owner — not the individual users — listing the identified inactive accounts and the planned reclamation date (typically 10 business days from notification). Ask the business owner to confirm which accounts should be retained and which can be released. Frame the communication positively: this is a budget optimisation exercise, not a cost-cutting mandate.

In practice, business owners respond in three ways: confirming reclamation (most common, 60–70%), identifying specific accounts to retain with documented justification (20–30%), or requesting more time (10–15%). For accounts flagged for retention, document the business justification in your SaaS inventory for the next renewal discussion — these accounts need to be actively used by renewal time or their licenses remain reclamation candidates.

Step 3: Execute Reclamation

Once business owner validation is complete, execute reclamation through the application's admin console. For most SaaS platforms, reclaimed licenses are returned to an available pool rather than deleted — they can be reassigned without additional cost. The goal at this stage is to accurately document your active license count so that at renewal, you have a precise, validated number to present to the vendor.

Key actions at reclamation execution: suspend (not delete) inactive user accounts to preserve audit trails, update your SaaS inventory with the revised active license count, and document the reclamation event with timestamp and business owner approval for audit purposes.

Step 4: Use Reclamation Data in Vendor Negotiations

License reclamation data is your primary negotiation weapon at renewal. When a vendor proposes renewing at or above current license counts, your response is structured and evidence-based: here is our validated active usage, here is the licence count we will renew at, here is the utilisation trend that supports it.

Most enterprise SaaS vendors will resist significant license reductions — particularly when the contract contains minimum purchase commitments. The following tactics are effective in navigating vendor pushback:

Overcoming Vendor Resistance to Right-Sizing

• "You might need those licenses in the future": Counter with documented headcount forecasts from HR/Finance, not vendor speculation. If your headcount plan does not support the higher license count, the vendor's claim is unfounded.
• Minimum purchase commitments: If your contract includes minimums that exceed your actual usage, flag this as a contract failure that the vendor is obligated to address. Minimums set at contract inception based on projected usage that did not materialise are a legitimate renegotiation point.
• Price increases tied to volume maintenance: Vendors sometimes threaten that reducing license count will require a price-per-seat increase that eliminates the cost saving. Model the total-cost impact before accepting this claim — typically the saving from fewer seats exceeds any per-seat increase, especially at high licence volumes.
• Competitive displacement threat: If the vendor will not accommodate right-sizing, initiate a parallel competitive evaluation. For most enterprise SaaS categories, a credible alternative exists and the threat of displacement is more powerful than any utilisation argument.

Platform-Specific Reclamation Guidance

Salesforce License Reclamation

Salesforce has one of the highest average wasted license rates in enterprise — often 25–40% of purchased seats. Use Salesforce's built-in Login History report filtered to users with zero logins in 90 days as your baseline. Salesforce will resist seat reductions at renewal but regularly accepts them at mid-term review when utilisation evidence is presented. See our Salesforce shelfware reclamation guide for the complete playbook.

Microsoft 365 License Reclamation

Microsoft 365 admin centre provides user activity reports across Exchange, Teams, SharePoint, and OneDrive. Use these reports to identify users with no activity across any M365 workload in 90 days. Microsoft's licence recycling policy allows reassignment of reclaimed licences within the same tenant without additional charge. For large enterprises, Azure AD Identity Governance can automate the reclamation workflow.

ServiceNow License Reclamation

ServiceNow's fulfillers (ITSM agents) are the primary pricing unit. Pull a Fulfiller Activity report from the ServiceNow admin console and identify fulfillers with no ticket activity in the last 90 days. These are reclamation candidates — particularly relevant in organisations that have reorganised their ITSM function or consolidated support tiers since the last renewal.

Building a Continuous Reclamation Programme

One-time reclamation generates immediate savings. Continuous reclamation generates sustained savings and eliminates the accumulation of waste between renewals. Building reclamation into your routine SaaS governance cadence — quarterly utilisation reviews with automated alerts for accounts that cross the 60-day inactivity threshold — prevents waste from re-accumulating and ensures you always enter renewal discussions with current, accurate licence data.

Our SaaS optimisation advisory team can implement the continuous reclamation framework alongside your broader SaaS optimisation programme. For the contract terms that govern how reclaimed licenses are treated at renewal, see our guide to SaaS renewal strategy and download our True Cost of SaaS white paper for the complete hidden fee analysis framework.