Enterprise SaaS portfolios have grown dramatically over the past decade, but the governance frameworks to manage them have not kept pace. Procurement happens in silos — departments buy tools without cross-referencing what already exists, finance auto-renews contracts without usage review, and IT maintains subscriptions for systems long since replaced. The result is a sprawling, overlapping, expensive SaaS estate that consumes budget without delivering proportionate value.
SaaS rationalization is the structured process of auditing your software portfolio, identifying redundancy and waste, and systematically eliminating tools that are duplicated, underused, or superseded — all while preserving the functionality that teams actually need. Done properly, it is one of the highest-return IT cost reduction activities available to enterprise finance and procurement teams.
What SaaS Rationalization Actually Entails
Many organizations confuse SaaS rationalization with simple spending cuts — cancelling subscriptions and telling teams to make do. That approach destroys productivity, creates shadow IT, and typically reverses within six months as teams re-purchase tools through other budget lines.
Real rationalization is a structured exercise with four distinct phases: discovery (finding everything you pay for), analysis (understanding utilization and overlap), decision-making (keeping, consolidating, or eliminating tools), and execution (managing vendor transitions, contract exits, and internal change management). Each phase requires different skills and different data.
The Scale of the Problem
Zylo's annual SaaS Management Index reports that enterprises with 1,000–5,000 employees typically operate 254 SaaS applications, spending an average of $2,623 per employee annually. Gartner estimates that 35% of SaaS licences go unused in any given month. Our advisory practice's experience with 200+ enterprise SaaS engagements suggests the real redundancy figure — when counting both true duplicates and partial substitutes — is typically 25–35% of total portfolio value.
What "redundancy" looks like in practice: A 3,000-person enterprise we advised was paying for Microsoft 365, Zoom, Slack, Teams, Google Workspace (legacy), Webex, and Miro — seven different collaboration tools for a single user population. Four of them had active user bases. Three were either historical contracts with auto-renewal or departmental purchases that predated the M365 consolidation. Annual cost of the redundant three: £340,000.
Phase 1: SaaS Discovery — Finding the Full Inventory
You cannot rationalize what you cannot see. The first challenge in any rationalization programme is building a complete, authoritative inventory of every SaaS product you pay for. This is harder than it sounds because SaaS procurement has become so decentralized.
Where SaaS Spend Hides
Enterprise SaaS appears in at least four distinct places: central IT-managed contracts (typically tracked in CMDB or ITSM systems); departmental P-card purchases (marketing buys tools on procurement cards without IT visibility); employee-expensed subscriptions (individuals expense Grammarly, Notion, or Calendly through T&E); and ERP-embedded software (functionality bundled with SAP, Oracle, or Workday that is also purchased separately from a specialist vendor).
A complete discovery exercise typically surfaces 30–50% more SaaS tools than IT's existing asset register shows. The primary discovery methods are financial analysis (pulling every recurring SaaS charge from AP, P-cards, and T&E systems), SSO enumeration (listing every application connected to your identity provider), and browser extension scanning (deploying lightweight agents that detect web application usage across the estate).
Building the Master Inventory
For each tool identified, capture: vendor name, product name, annual contract value, renewal date, number of licences purchased, number of active users in the past 90 days, contract owner, primary use case, and department. This data layer is the foundation for all subsequent rationalization decisions.
Phase 2: Usage and Overlap Analysis
With a complete inventory, the second phase analyses each tool's utilization and its relationship to other tools in the portfolio. This produces a prioritized rationalization shortlist.
Utilization Scoring
Every tool receives a utilization score based on the ratio of active users to licenced users, adjusted for the nature of the tool. A project management tool used by 90% of licenced users in the past 90 days scores well. An analytics platform where 12% of licenced users have logged in during the same period represents either a training failure or a candidate for rationalization.
| Usage Rate | Classification | Default Action |
|---|---|---|
| 75%+ | Active tool | Retain, optimize licence count |
| 40–75% | Moderate usage | Review: training gap or over-licensing? |
| 15–40% | Low adoption | Consolidation candidate — analyse alternatives |
| Under 15% | Shelfware | Cancel or right-size at next renewal |
Functional Overlap Mapping
Beyond utilization, rationalization requires identifying tools that perform overlapping functions. This requires categorizing every tool in your portfolio by functional domain — collaboration, CRM, project management, BI and analytics, security, HR, finance, and so on. Tools in the same functional domain with different user bases become consolidation candidates: can the better-adopted tool serve both populations?
Common overlap patterns we encounter include: two CRM systems (Salesforce plus a regional or legacy system); three project management tools (Jira, Monday.com, and Asana coexisting); multiple video conferencing solutions; and duplicate BI tools (Power BI, Tableau, and Looker all active). Each overlap represents both a consolidation opportunity and a negotiation lever — vendors will discount aggressively to become the consolidated standard.
Phase 3: The Rationalization Decision Framework
Not every low-utilization or overlapping tool is a rationalization candidate. The decision framework must account for strategic intent (is low usage because the tool is new and still being rolled out?), contractual position (are you mid-term or near renewal?), and switching costs (what would migration actually cost?). The goal is maximum value recovery with minimum operational disruption.
Contractual Timing
The single most important factor in rationalization execution is contract timing. Tools approaching renewal in the next 90 days are highest priority — you can eliminate or right-size with zero contractual friction. Mid-term tools require either waiting for the renewal window or negotiating an early exit. Tools with 12+ months remaining on contract should be put on a renewal watch list and flagged for re-evaluation when the window opens.
Negotiating Vendor Exits and Consolidations
The commercial dimension of SaaS rationalization is often underestimated. Done well, consolidation creates significant negotiating leverage: you are offering a vendor expanded scope, a longer term, and competitive justification for displacing an alternative. This is worth a substantial discount.
Consolidation Leverage
When consolidating two tools into one, the winning vendor should discount to reflect their expanded wallet share. If you are moving 500 Tableau users to Power BI to consolidate on Microsoft, Microsoft has strong commercial incentive to price aggressively — you are expanding your Microsoft footprint, extending your EA commitment, and displacing a competitor. Typical consolidation discount uplift is 15–30% above what you would achieve on a straight renewal.
Early Termination Negotiations
For SaaS tools you want to exit mid-term, the negotiation framing matters enormously. Never lead with "we want to cancel" — this triggers standard cancellation processes with full remaining-term liability. Instead, frame the conversation as a business review: usage has not grown as expected, you are evaluating your portfolio, and you would like to explore whether a modified arrangement makes sense. Most SaaS vendors will accept 30–50% of the remaining contract value to terminate cleanly rather than risk a non-renewal plus damage to the relationship.
Advisory firms such as Redress Compliance regularly achieve mid-term SaaS exits at 25–40 cents on the dollar through structured commercial negotiations — primarily because they maintain benchmark data on what vendors typically accept and can credibly signal competitive alternatives.
Change Management: The Hidden Rationalization Risk
The biggest rationalization failure mode is not commercial — it is organizational. Teams become attached to their tools, even tools they barely use. Department heads resist the loss of "their" system. Migrations are delayed because nobody owns the cutover. The software portfolio stays bloated because the change management work is too hard.
Successful rationalization programmes treat change management as a first-class workstream, not an afterthought. This means: communicating the programme rationale to affected teams before tools are cancelled; providing clear migration timelines and support resources; designating tool champions in each department who own adoption of the consolidated platform; and establishing a governance body with authority to enforce rationalization decisions.
Shadow IT Prevention
Without governance, rationalization savings reverse within 12–18 months as teams re-purchase eliminated tools through departmental budgets or employee expense claims. Preventing this requires three controls: procurement policy requiring IT approval for new SaaS above a threshold (typically $500/year per user); regular automated scanning for unauthorized SaaS applications via SSO and network monitoring; and a fast-track approval process for legitimate new tool requests so that the governance process does not drive tools underground.
Measuring Rationalization Success
Track four metrics: total portfolio cost before and after (direct saving), licence count reduction (operational efficiency), utilization rate across the portfolio (health indicator), and number of tools in the estate (complexity reduction). A successful rationalization programme typically delivers 20–30% cost reduction, 15–25% reduction in total tool count, and an improvement in average portfolio utilization from around 55% to above 75%.
A Financial Services Case: A 4,200-person financial services firm retained Atonement Licensing for a full SaaS rationalization exercise in late 2024. Discovery surfaced 312 active SaaS applications against an IT register of 187. Usage analysis identified 94 tools with under 20% active utilization. Functional overlap mapping found 11 instances of significant duplication. The 90-day programme eliminated 67 tools outright, consolidated 14 pairs into 7 standard platforms, and right-sized licences across 42 retained tools. Total annual saving: £1.9 million. The remaining portfolio of 245 tools now averages 71% active utilization.
How to Get Started: The 30-Day Quick Win
For organizations that cannot commit to a full rationalization programme immediately, a 30-day quick win exercise focuses on the highest-confidence savings: tools with under 10% utilization that are at renewal within 90 days. Pull your AP and P-card data for recurring SaaS charges, cross-reference with SSO login data, and flag every tool where the renewal is imminent and usage is below threshold. Non-renewing these tools requires no migration work, no change management, and typically no negotiation — just a renewal notice sent on time.
This approach rarely captures more than 20–30% of total rationalization opportunity, but it builds organizational confidence in the programme and demonstrates quick financial return to stakeholders who control the budget for a more comprehensive exercise.
For a complete framework covering the entire SaaS estate — including pricing negotiation, auto-renewal prevention, contract term optimization, and benchmarking — see our SaaS Licensing Complete Guide. For help with specific vendor consolidation negotiations, our SaaS Licence Optimisation practice provides hands-on commercial support.