The average enterprise runs hundreds of SaaS contracts and actively governs a fraction of them. The result is a portfolio where 25–35% of spend is unused, duplicated, or contracted on auto-renewal at list price. This pillar walks through where that spend hides, which vendor patterns monetise governance gaps, and the rationalisation framework that consistently recovers 20–40% within twelve months.
Enterprise SaaS spend grew faster than the disciplines required to manage it. The average Fortune 1000 enterprise now runs between 200 and 600 distinct SaaS contracts; only 30–40% are actively governed by procurement, the rest renew on auto-pilot, sit in the budgets of business-unit owners who acquired them outside IT, or hide inside expense reports as $50/user shadow purchases. The cumulative effect is that 25–35% of enterprise SaaS spend is, on any given day, either unused, duplicated, or contracted on auto-renewal at list price.
Reversing this requires more than a SAM tool — it requires a contract-level rationalisation programme and a renewal cadence that anticipates each vendor's commercial model. In our experience across 340+ engagements, the buyers who recover the most are those who treat SaaS spend as a contract portfolio, not as a series of independent renewals. The SaaS Spend Optimization Guide walks through the framework.
Our license optimization assessment quantifies the recoverable spend in 4–6 weeks.
Some SaaS vendors are designed around customer governance maturity. The contract architecture, renewal cadence, and SKU complexity all assume that the buyer's internal SAM function is one or two iterations behind. Three vendor patterns repeat.
ServiceNow's licensing is built around "subscription units" that map non-linearly to deployed product modules. The Now Platform creates Fulfillers, Requesters, Approvers and other personas at different rates; each new module (HR Service Delivery, IT Operations Management, Security Operations) introduces its own unit count. Customers who acquire ServiceNow as ITSM and expand into adjacent modules often discover at renewal that the platform footprint has changed in a way the contract did not anticipate. The defence is a true-up discipline run at six-month intervals, not at renewal.
Workday prices on Average Worker Count (AWC), with employee growth driving cost in real time. The contract typically permits annual true-up; mid-term reductions are not contractually allowed. Customers with declining headcount — or with significant contractor/agency populations that should not count as workers — frequently overpay for years until the next renewal opens the metric for renegotiation. The defensive move is to clarify worker definition at signature and re-baseline at every renewal.
The "modern SaaS" tier prices per active user and offers no contractual mechanism for downward adjustment. Customers who provision seats during growth phases and never deprovision them during retraction end up paying for ghost users for years. The discipline is monthly automated deprovisioning tied to HR offboarding events.
The framework we use to recover 20–40% of enterprise SaaS spend within twelve months.
Auto-renewal is the most consistent recoverable line in SaaS spend audits. The standard SaaS contract auto-renews for an additional term — usually 12 months — unless the buyer provides written notice 30 to 90 days before term end. The mechanic favours the vendor for three reasons. First, the notice window is often forgotten in the buyer's contract management system, especially for mid-tier vendors. Second, the auto-renewal triggers at list price, not at the negotiated discount, so the buyer loses the discount band. Third, once triggered, the new term is contractually binding for 12 months, leaving no recovery window.
The defensive system is straightforward and rarely implemented. A single source-of-truth contract registry with 150-day, 90-day and 30-day notice triggers; a procurement RACI that assigns named accountability for each contract; and a default policy of issuing termination notice on every contract by the 90-day window, even when continuation is the intended outcome. Termination notice does not commit the buyer to leaving — it preserves the negotiation window.
Issuing termination notice is uncomfortable. Vendor account teams treat it as an escalation. The point is precisely that: the notice resets the negotiation, opens discount conversations that would not otherwise be on the table, and forces the vendor to re-prove value. Customers who adopt this as standard practice across all SaaS contracts recover an average of 18–28% of renewal spend versus the auto-renewal baseline.
The 90-day window is where the recoverable spend lives. Our team runs the playbook for you.
SaaS rationalisation programmes that work share four characteristics. They start with a discovery layer (SaaS Management Platform — Zylo, Productiv, BetterCloud — or a CASB-derived inventory). They classify spend into "core, business, departmental, individual" tiers. They apply differentiated governance — heavy on core, light on individual — to each. And they enforce a quarterly review cadence that closes the loop between provisioning data, contract data, and budget data. Without all four, the programme decays back to the starting point within 18 months.
Three actions start the recovery curve. First, build a single contract registry with notice-period flags 150/90/30 days before term end. Second, run an active-user reconciliation against contracted seats for the top ten SaaS vendors by spend. Third, adopt notice-and-negotiate as standard practice on every renewal. None require new tooling; all require executive sponsorship. Where the portfolio is large enough to warrant it, a dedicated license cost reduction engagement turns the registry and reconciliation into recovered spend on a fixed timeline.
Our team has run SaaS rationalisation programmes across Fortune 500 estates. We work for buyers, not the vendors.
Weekly compliance intelligence for IT leaders.