SaaS Contract Optimization · Licence Reclamation

SaaS License Reclamation:
Finding and Eliminating Waste

The average enterprise wastes 12–18% of its SaaS portfolio on unused licences. Here is the complete audit methodology to find, reclaim, and prevent that waste — before your next renewal.

Licence reclamation is the highest-ROI activity in enterprise SaaS management. It requires no vendor negotiation, no competitive evaluation, and no executive approval. It simply requires knowing what you're paying for and whether anyone is using it. Yet most enterprises conduct no formal reclamation activity between contract signings, allowing waste to accumulate unchecked for months or years.

This guide forms part of our SaaS contract optimization pillar. It is the starting point for any SaaS optimisation programme — reclamation before renewal, audit before negotiation.

Benchmark Data

Analysis of enterprise SaaS portfolios consistently finds 12–18% of licences are unused or redundant. On a £2M SaaS portfolio, that represents £240K–£360K in immediately recoverable spend — before a single negotiation conversation.

The Licence Waste Reality

SaaS waste is structural, not accidental. It accumulates through predictable mechanisms that most procurement functions don't have processes to detect or prevent:

  • Employee offboarding: Departed employees' accounts are deprovisioned from IT systems but licences are not returned to the pool. Most SaaS vendors charge for provisioned seats, not active sessions. A company with 10% annual attrition and no reclamation process can accumulate 30–40% ghost licence volume over 3 years.
  • Role changes: An employee promoted to a manager role no longer needs a front-line CRM seat — but the licence remains provisioned. Across a large organisation, role-based over-provisioning is endemic.
  • Shadow IT consolidation: A team adopts a new tool. The old tool's licences continue renewing because they're tied to a centralised budget owner who is unaware the product is no longer used.
  • Project-based adoption: Licences acquired for a specific project or initiative continue renewing after the project ends.
  • Feature tier over-buying: Teams buy Enterprise edition when Standard would cover 95% of their use cases. The upgrade decision is made once and never reviewed.

Categories of SaaS Waste

Category Definition Typical % of Seats Detection Method
Never-logged-in Provisioned but zero login activity 3–6% Last login timestamp = null
60-day inactive No login in last 60 calendar days 8–14% Last login < [current date – 60]
Offboarded users Not in HR system but still provisioned 2–5% HR roster diff against SaaS user list
Duplicate accounts Same person with multiple active accounts 1–3% Email address deduplication
Over-tiered Using fewer than 30% of tier features 15–25% of budget Feature utilisation analysis

4-Phase Audit Methodology

Phase 1: Inventory (Weeks 1–2)

The first step is establishing a complete inventory of what you have. This sounds obvious but is frequently missing. Most organisations have a partial view: the IT team knows what's centrally provisioned, but shadow IT creates a long tail of applications that finance teams discover only when reviewing credit card statements.

Expert Advisory

Want independent help negotiating better terms? We rank the top advisory firms across 14 vendor categories — free matching, no commitment.

Inventory sources to combine:

  • IT asset management system (ITAM) — if it exists and is current
  • Accounts payable records: any vendor billing on a subscription basis
  • Corporate credit card statements: filter for recurring SaaS charges
  • Employee expense reports: personal cards used for business SaaS
  • SSO/identity provider logs (Okta, Azure AD, Ping): all apps connected via SSO
  • Browser extension audits: tools deployed at the browser level
Common Finding

Organisations that conduct their first comprehensive SaaS inventory typically find 20–40% more active subscriptions than IT records show. Shadow IT and department-level purchasing consistently exceed centrally managed spend at organisations without formal SaaS management policies.

Phase 2: Usage Data Collection (Weeks 2–4)

For each application in the inventory, collect usage data. The primary metrics are: last login date, login frequency (monthly active users), and feature utilisation where available.

Data sources vary by vendor. Most enterprise SaaS platforms expose usage data via admin portal or API:

  • Salesforce: Setup → Users → Last Login Date; also available via User API and Salesforce Optimizer
  • Microsoft 365: Microsoft 365 Admin Center → Usage Reports; also accessible via Graph API
  • Slack: Admin → Analytics → Member Activity; bulk export available
  • Zoom: Dashboard → Users → Last Activity Date
  • ServiceNow: System Administration → Usage Analytics

For vendors without native usage reporting, SSO login logs (Okta, Azure AD) provide a proxy — if a user hasn't authenticated to an application in 60+ days, they are effectively inactive regardless of what the vendor reports.

Phase 3: Analysis and Prioritisation (Weeks 3–5)

With inventory and usage data combined, the analysis phase identifies specific reclamation opportunities and quantifies their value.

Apply a tiered classification to each licence:

  • Reclaim now: Never logged in, or offboarded user still provisioned. Zero usage justification. Return licence immediately.
  • Reclaim at renewal: 60-day inactive but may be a seasonal user or someone on leave. Flag for confirmation, reclaim unless confirmed needed.
  • Investigate: Low usage (below 30% of available features). May be appropriate for tier downgrade or training intervention.
  • Retain: Active users with adequate feature utilisation. No action required.

Phase 4: Reclamation and Documentation (Weeks 5–8)

Execute the reclamation plan. This involves deprovisioning flagged users, confirming IT and HR records are aligned, and documenting the reclaimed licence count for use in renewal negotiations.

The documentation step is critical. At renewal, you will present the vendor with your actual usage data: "We had X licences, of which Y are active. We are renewing for Y." The reclamation data is your evidence base. Without it, vendors will argue for renewing at existing seat count or higher.

Contractual Note

Most SaaS contracts specify minimum seat counts and renewal terms that limit your ability to reduce licences mid-contract. Licence reclamation typically takes effect at the renewal date, not immediately. Review your contract's seat reduction provisions before attempting mid-term reclamation — and negotiate flex-down rights into every future agreement. See our SaaS contract optimization guide for standard language.

Vendor-Specific Audit Tactics

Salesforce

Salesforce is the highest-value reclamation target for most organisations. The "60-day login rule" in Salesforce's standard terms — which permits licence reclamation for users inactive for 60 days — is widely known but rarely enforced by customers. Use Salesforce Optimizer and the User object's LastLoginDate field to identify candidates.

Free Resource

Get the IT Negotiation Playbook — free

Used by 4,200+ IT directors and procurement leads. Oracle, Microsoft, SAP, Cloud — all covered.

For detailed Salesforce reclamation methodology, see our dedicated Salesforce shelfware reduction guide. A typical enterprise Salesforce audit recovers 15–25% of provisioned seats.

Microsoft 365

Microsoft 365 usage analytics (available in the admin centre) show per-user activity across Exchange, Teams, SharePoint, and other workloads. The key metric for licence reclamation is users with zero activity across all M365 workloads for 30+ days. These are prime candidates for downgrade from E5 to E3 or E3 to Business Standard.

Also identify users assigned E5 licences who aren't using E5-specific features (advanced security, analytics). Licence downgrades — moving users from higher to lower tiers — can deliver significant savings without seat count reduction. Review our Microsoft licence right-sizing guide for the full framework.

Slack

Slack's Admin Analytics dashboard shows message-sent and days-active metrics at the user level. Export the full user list and filter for users who haven't sent a message or opened the app in 60+ days. These users can be downgraded to Guest status (free) or deprovisioned entirely.

Other SaaS Platforms

The same methodology applies across platforms: extract user list with last-activity timestamps, diff against HR active employee roster, reclaim inactive or offboarded accounts. Tools such as Torii, Zylo, Productiv, and Blissfully automate this process across your full SaaS portfolio and are worth evaluating for organisations with 100+ applications.

Turning Reclamation into Negotiation Leverage

Licence reclamation does more than reduce the number of seats you're renewing — it fundamentally changes the negotiation dynamic. When you walk into a renewal conversation with documented evidence of 20% licence waste, you are saying to the vendor: "We know exactly what we use and what we don't. We're not paying for what we don't use."

This posture shifts power from the vendor to the buyer. The vendor can no longer anchor on "you've been paying for X seats for three years so let's renew at X." Your counter-anchor is your usage data, and it's specific and defensible.

Combine reclamation data with benchmark pricing data and a credible alternative evaluation, and you have a three-part negotiation position that is very difficult for the vendor to overcome without real pricing movement.

Ready to reclaim your SaaS waste?

Our advisors run SaaS audits and use the data to negotiate significantly better renewal terms. Average recovery: 20–30% of portfolio spend.
Start Audit →

Preventing Future Waste

The audit-and-reclaim cycle is valuable but reactive. The goal is to build governance that prevents waste from accumulating in the first place. The three key mechanisms:

Automated Offboarding Provisioning

Configure your identity provider (Okta, Azure AD) to automatically deprovision SaaS licences when an employee is offboarded in HR. This eliminates the most common source of ghost licences. Most modern SaaS platforms support SCIM provisioning that automates this process.

Quarterly Usage Reviews

Schedule quarterly reviews of licence utilisation for any application with annual spend above £10K. Flag applications where active user rate falls below 70%. This is a governance process, not a technology solution — it requires a named owner and an escalation path.

Renewal Triggers

Ensure every SaaS renewal is preceded by a usage review, not just a budget approval. The review should produce a recommended seat count based on actual active users, not historical provisioned quantity. Make this a procurement policy: no renewal above £25K without a usage report. See our auto-renewal negotiation guide for the process to build around renewal triggers.

ROI Model: What to Expect

The economics of a SaaS licence reclamation programme depend on portfolio size, current governance maturity, and vendor mix. The following model is based on observed outcomes from enterprise programmes:

Portfolio Size Typical Reclamation Rate Estimated Annual Saving Programme Cost ROI
£500K SaaS 12–15% £60K–£75K £15K–£25K 3–5×
£2M SaaS 14–18% £280K–£360K £25K–£50K 6–10×
£10M SaaS 15–20% £1.5M–£2M £75K–£150K 10–15×

These figures represent licence reclamation alone — before any pricing negotiation. Adding negotiation to the reclamation exercise typically doubles the total savings figure. Organisations that conduct a full reclamation-plus-negotiation programme typically save 25–35% of their SaaS portfolio value within 12 months.

Frequently Asked Questions

Can we reclaim licences mid-contract?
Most SaaS contracts fix the minimum seat count for the contract term, with adjustments only at renewal. However, some contracts include mid-term true-down rights — check your specific agreement. Even where mid-term reduction is not possible, running the reclamation audit before renewal ensures you enter the renewal with accurate usage data and a strong reduction request.
What if the vendor refuses to reduce seat counts at renewal?
Vendors who refuse to acknowledge licence reclamation at renewal are applying pressure that isn't contractually justified in most cases. Your contract specifies the minimum renewal quantity — if it doesn't specify a floor above your requested count, you have the right to renew at lower volume. Vendors who push back hard are signalling pricing flexibility they can unlock when pushed. Escalate to senior account management and make the alternative explicit.
How long does a SaaS audit take?
A focused audit of the top 10–15 applications by spend typically takes 4–6 weeks with internal resource, or 2–3 weeks with specialist advisory support. A full portfolio audit of 50+ applications typically takes 8–12 weeks. The fastest path is to focus first on the highest-spend applications — 20% of your applications likely represent 80% of your SaaS spend.
Should we use a SaaS management platform?
For organisations with 50+ SaaS applications or £500K+ in SaaS spend, a SaaS management platform (Torii, Zylo, Productiv, Blissfully) typically pays for itself within 6–12 months through automated waste detection alone. For smaller organisations, a structured spreadsheet-based process may be sufficient. The key is having a repeatable process — the tool is secondary.

Stop Paying for Licences
Nobody Uses

Our advisors conduct SaaS usage audits, identify reclamation opportunities, and use the data to drive better renewal terms across your entire portfolio.