Home  ›  Blog  ›  SaaS Spend Optimization Guide
SaaS · Optimization · Framework

SaaS spend optimization — the 20–40% framework that holds.

Enterprises that run a structured SaaS optimization programme recover 20–40% of total SaaS spend within twelve months. The framework is consistent: discover the estate, classify the spend, recover quick wins, renegotiate the renewals, then enforce a governance cadence that prevents drift. This guide walks through the operating model we have deployed across 340+ engagements.

Updated: April 2026 Reading time: 14 min Audience: CIO, CFO, Head of Procurement, IT Asset Manager
Enterprise SaaS portfolio analytics
The optimization problem

Why most SaaS optimization programmes stall after the first year.

SaaS optimization is one of the most-attempted and least-completed disciplines in enterprise procurement. Most programmes start with a SAM tool implementation, deliver a credible Year 1 recovery, and then decay because the governance cadence is never institutionalised. By Year 3, the portfolio is back to within 5–8% of where it started — a depressingly common pattern we see at the start of new engagements. The framework that holds combines a one-time recovery sprint with an enforced annual cadence.

The optimisation maths are forgiving. Across 340+ engagements, the average enterprise we onboard runs between 200 and 600 SaaS contracts and recovers between 22% and 38% of total annual SaaS spend in the first twelve months. The high end is dominated by auto-renewal recapture, shelfware reduction on the top ten vendors, and edition right-sizing on Salesforce, ServiceNow and Workday. Everything else — vendor consolidation, contract restructuring, multi-year deal repricing — compounds over Years 2 and 3 once the governance discipline is in place.

The five recovery lines

Want a baseline assessment of where your SaaS spend leaks?

Our 4–6 week optimization assessment quantifies the recoverable spend before any negotiation begins.

Contact Us →
Programme architecture

The operating model that delivers and holds.

A SaaS optimization programme that holds beyond Year 1 is built around five components: a discovery layer, a contract registry, a tiered governance model, a renewal calendar with notice triggers, and a quarterly enforcement cadence. Skip any one and the programme decays. Most internal teams attempt the first three and stop, which explains the Year 2 drift.

1. Discovery layer

A SaaS Management Platform (Zylo, Productiv, BetterCloud, Torii) or a CASB-derived inventory. The platform's purpose is reconciliation: every active SaaS application surfaced through SSO or expense data, matched against every contracted SaaS vendor in the contract registry. The gap between the two is shadow IT, the first remediation target.

2. Contract registry

A single source-of-truth registry for every SaaS contract, with notice-period flags at 150, 90 and 30 days before term end. The registry is more important than the SaaS Management Platform; many programmes deliver substantial Year 1 savings with a registry alone. Most enterprises operate without one, relying on procurement memory or fragmented contract systems.

3. Tiered governance

Spend tiering — Core, Business, Departmental, Individual — with proportional governance applied to each tier. Core (ERP, CRM, productivity, communications) gets executive review and multi-quarter renewal preparation. Business gets procurement-led review at 120 days. Departmental gets templated negotiation. Individual gets policy enforcement. Without tiering, programmes either over-govern small contracts (wasting time) or under-govern large ones (losing money).

4. Renewal calendar

Every SaaS contract assigned to a calendar with three notice triggers. 150 days: strategy review begins. 90 days: termination notice issued by default. 30 days: final commercial close. The 90-day default is the most controversial and the most valuable; it forces every renewal into a real negotiation rather than passive auto-renewal.

5. Enforcement cadence

Quarterly governance review with CFO or CIO sponsorship. Top ten vendors reviewed by spend, usage and renewal status. Off-schedule renewals investigated. New SaaS purchases reconciled against the registry. Without this cadence, programmes drift; with it, they compound.

Download the SaaS Spend Optimization Guide.

The full programme architecture, the renewal playbook, and the templates we deploy in engagements.

Get the guide →
Sequencing the recovery

What to do in the first 90 days.

The first 90 days of an optimization programme is where executive credibility is established. The temptation is to start with the largest vendor; the better move is to start with the contracts already inside the auto-renewal window. Quick wins surface in week two and three, fund the rest of the programme politically, and establish the discipline before the harder work begins.

  1. Day 1–14: Discovery. Build the contract registry. Source data from procurement, finance ERP, SSO, expense reports. Identify the top fifty vendors by spend and the next ten with auto-renewal windows in the next 120 days.
  2. Day 15–30: Usage reconciliation. Run active-user reconciliation on the top ten vendors. Compute the shelfware percentage and the negotiation opening for each.
  3. Day 31–60: Quick-win execution. Issue termination notice on every contract within the 90-day window. Run the renegotiation on three to five contracts where the maths is clear.
  4. Day 61–90: Governance build. Stand up the renewal calendar, the tiered governance model, and the quarterly review cadence. Brief the CFO on Year 1 savings forecast.

Auto-renewals approaching in the next quarter?

The 90-day window is where the largest recovery line lives. Our team runs the playbook in parallel with internal procurement.

Contact Us →
Vendor patterns

Where the highest-percentage recoveries live.

Some SaaS vendors are structurally more recoverable than others. The pattern correlates with three variables: contract complexity, edition over-provisioning risk, and auto-renewal behaviour. The vendors that consistently surface in the top recovery lines:

Salesforce

Salesforce edition over-provisioning is the most common high-percentage recovery. Sales Cloud Unlimited deployed where Enterprise would serve, with add-ons (CPQ, Inbox, High Velocity Sales) that few users actually consume. A typical Salesforce optimization recovers 15–25% of annual spend through edition right-sizing and add-on rationalisation.

ServiceNow

ServiceNow's subscription unit model rewards customers who run a true-up discipline at six-month intervals rather than at renewal. The recovery lines are fulfiller right-sizing, module footprint review, and platform-edition rationalisation. Typical 12–18% recovery without losing functionality.

Workday

Workday's Average Worker Count metric drives cost in real time and only opens to renegotiation at renewal. Customers with declining headcount or significant contractor populations frequently overpay; the renewal is the only window to reset the AWC definition.

Atlassian, Slack, Zoom, Asana, Monday

The modern SaaS tier prices per active user with no mid-term downward adjustment. Recovery comes from deprovisioning discipline tied to HR offboarding, edition right-sizing (most enterprises over-provision Premium where Standard would serve), and consolidation across overlapping tools.

Internal next steps

Three actions begin the recovery curve. First, build a single contract registry with notice flags for every SaaS vendor. Second, run an active-user reconciliation on the top ten vendors by spend. Third, adopt notice-and-negotiate as standard practice on every renewal. None requires new tooling; all require executive sponsorship and a quarterly governance cadence. For estates where the recoverable spend runs into the millions, a dedicated software license optimization engagement compresses that timeline and holds the savings across renewals.

FAQ

Common SaaS optimization questions.

What savings range should a SaaS optimization programme target?
20–40% of total SaaS spend within twelve months for enterprises that have not previously run a structured programme. The lower end applies to portfolios already managed by procurement; the upper end to estates dominated by departmental purchasing and auto-renewal.
Where is the largest recovery line in most portfolios?
Auto-renewal recapture. The notice-and-negotiate posture on the top fifty vendors by spend typically recovers 18–28% versus the auto-renewal baseline.
How long does a programme take to deliver first savings?
Quick wins surface in 30–60 days from shelfware reduction on the top ten vendors. Structural savings on renewals materialise over the first contract cycle, typically 6–12 months.
Do we need a SaaS Management Platform first?
For estates above one hundred SaaS contracts, yes — but only as a discovery layer. The platform surfaces what already exists; it does not negotiate, classify, or rationalise.
Who should own the programme internally?
Procurement runs commercial activity; IT runs technical deprovisioning; Finance owns budget allocation. A single executive sponsor — typically CIO or CFO — holds the integrated programme.
How do we avoid the savings decaying after year one?
A quarterly enforcement cadence and policy that auto-renewal is never permitted at list price. Without enforcement, portfolios drift back within eighteen months.

Ready to run a SaaS optimization programme?
We bring the playbook.

Our team has run SaaS optimization programmes across Fortune 500 estates. We work for buyers exclusively.

The Compliance Brief

Weekly compliance intelligence for IT leaders.