License Reclamation Programs: Recovering Wasted Spend

A licence reclamation programme is the fastest, lowest-risk saving in enterprise IT — it removes cost the business was never using. This guide shows where the waste hides, the workflow that recovers it, and how to stop it from quietly returning before the next renewal.

By Morten Andersen

What a License Reclamation Programme Is

A licence reclamation programme is a structured, repeatable process for finding software licences that are unused, assigned to inactive users, or duplicated — and recovering them so they can be cut at renewal or redeployed to new users instead of buying more. Across the industry, 25–35% of enterprise software spend is recoverable through structured licence management, and at any given moment 20–30% of paid SaaS licences belong to inactive or offboarded users. In unmanaged environments, as much as 51% of purchased SaaS licences sit unused.

Reclamation is the action layer that gives the rest of the enterprise IT cost optimisation framework its teeth. Spend analytics tells you what is wasted; reclamation is the disciplined process that actually takes the cost out — and the single largest line in most software asset management ROI models.

Where the Wasted Spend Hides

Wasted licences accumulate from three predictable causes: over-purchasing during growth phases, employees leaving without their licences being reassigned, and pilots that are never retired. The table maps the most common hiding places and the share of the estate each typically represents.

Source of WasteWhat It Looks LikeTypical Share
Offboarded usersDeparted staff still provisioned and billed20–30% of paid seats
Inactive usersAssigned but unused for 90+ days15–25%
Over-tiered licencesPremium seats used at basic level10–20%
Duplicate toolsOverlapping apps doing one job5–15%
Abandoned pilotsTrials that became standing spend3–10%

Offboarding is the worst offender. Joiner-mover-leaver processes routinely deprovision the email account but miss the dozen SaaS apps the person also held — so the licences keep billing, invisibly, until someone runs a reclamation sweep.

The exposure is heaviest in high-cost, per-seat SaaS. A neglected estate of Salesforce, collaboration, and design seats can carry six figures of dormant licences between renewals — which is why reclamation pays for itself long before the contract comes up.

The Reclamation Workflow

An effective programme runs a continuous four-step loop rather than a one-off audit. Discover consolidates entitlement, SSO, and usage data to build a single picture of who holds what and whether they use it. Verify confirms genuine inactivity against business context — a 90-day-dormant seat may belong to someone on parental leave, so thresholds need human review. Harvest reclaims the confirmed-idle licences into a central pool. Redeploy or remove reuses harvested licences for new requests before any new purchase, and schedules the surplus for removal at the next renewal.

The harvest-and-reuse step is where the largest savings sit, because reuse avoids new spend entirely — the same dynamic that makes right-sizing over-provisioned deployments so effective. Reclamation removes seats; right-sizing downgrades the ones that remain. Run together, they typically take 15–30% out of software spend within a year.

Quantifying the Recovery

The recovery is concrete and fast. One insurer reclaimed 40% of its seats ahead of a renewal using autonomous provisioning and right-sizing, delivering six-figure savings on a single contract. More broadly, enterprises that address dormant licences through structured optimisation reduce SaaS spend by 10–15% annually on a sustained basis — on top of the larger first-sweep gain.

Timing multiplies the value. Licences reclaimed 6–9 months before a renewal become the evidence base for a reduced commitment, turning a clean-up exercise into negotiating leverage. Our SaaS contract optimisation practice sequences reclamation directly into the renewal so the recovered seats translate into a lower contracted baseline, not just an internal saving.

Keeping It From Coming Back

The hardest part of reclamation is not the first sweep — it is stopping the waste re-accumulating. Wire deprovisioning into joiner-mover-leaver workflows so it is automatic, set inactivity thresholds (typically 30–90 days) that trigger review, hold a central pool of harvested licences for reuse before any new purchase, and report waste as a tracked metric against a target of under 10%. Connecting reclamation to IT spend analytics and surfacing unsanctioned apps through shadow IT governance keeps the picture current between renewals.

Done once, reclamation is a saving; done continuously, it is a permanently lower run-rate. To map the recoverable spend across your estate and turn it into a reduced renewal commitment, request a confidential briefing — and use our SaaS optimisation guide as the operating reference.

Common Questions

License Reclamation: FAQ

What is a license reclamation programme?
A licence reclamation programme is a structured, repeatable process for identifying software licences that are unused, assigned to inactive users, or duplicated — then recovering them so they can be removed at renewal or redeployed to new users. It turns the 25–35% of enterprise software spend that is typically recoverable into an actively managed saving rather than a permanent leak.
How much can license reclamation save?
Industry data consistently shows 25–35% of enterprise software spend is recoverable through structured licence management, and 20–30% of paid SaaS licences belong to inactive or offboarded users at any time. One insurer reclaimed 40% of its seats ahead of a renewal, delivering six-figure savings. The first sweep is usually the largest, with continuous reclamation sustaining the gain.
Why do licences become wasted in the first place?
Three causes dominate: over-purchasing during growth phases, employees leaving without their licences being reassigned, and tools adopted for pilots that are never fully rolled out or retired. Offboarding processes frequently miss SaaS deprovisioning, so departed employees stay provisioned and billable. Without a reclamation loop, each of these quietly compounds between renewals.
How do you stop reclaimed licences being wasted again?
Wire reclamation into joiner-mover-leaver workflows and renewal calendars so deprovisioning is automatic, not a periodic clean-up. Set inactivity thresholds (typically 30–90 days) that trigger review, hold a central pool of harvested licences for reuse before any new purchase, and report waste as a tracked metric. Reclamation only stays solved if it is continuous.

Recover the Spend You're Not Using

We map the dormant and duplicated licences across your estate — then convert them into a lower renewal commitment. Independent and buyer-side.

Request a Confidential Briefing Read the Cost Optimization Guide

IT Cost Optimization Intelligence

Monthly briefings on software spend benchmarks, SaaS waste patterns, and renewal tactics — from advisors who negotiate these contracts for a living.