SaaS Spend Management: Finding Waste, Rightsizing Licenses, Beating Renewals

Zylo's 2026 SaaS Management Index, drawn from more than 40 million licenses, found that the average organization uses 54% of the SaaS licenses it pays for. That was an improvement on 47% a year earlier, and it still means close to half of paid seats sat idle. The same data showed business units, not IT, controlling 81% of SaaS spend, and most IT leaders reporting unexpected charges from usage-based or AI pricing in the past year.

Those numbers describe the problem well. SaaS costs are spread across hundreds of small contracts owned by people who do not see each other's bills, and each contract renews on its own schedule with its own notice period. This guide covers how to find the spend, where the waste usually is, how to use renewal dates as leverage, and how to report savings that finance will accept.

Step 1: Find everything you pay for

You cannot manage contracts you do not know about. Three data sources, combined, catch most of them:

1. Finance systems. Pull 12 months of payables, corporate card, and expense report transactions and filter for software vendors. This finds the tools bought outside procurement, which SSO data misses.
2. Identity provider. Okta, Microsoft Entra ID, or Google Workspace logs show which apps people sign into and how often. This gives you usage but only for apps connected to SSO.
3. Vendor admin consoles. For the 20 largest contracts, pull seat assignments and last-login dates directly from the vendor. It is manual, but it is the most accurate usage data you will get.

Browser-extension discovery tools can find apps that appear in neither finance nor SSO data, mostly free tiers and personal accounts. Weigh the privacy implications and tell employees before deploying one.

A dedicated SaaS management platform automates this, but a spreadsheet works for a company with fewer than about 100 apps. The output you need is the same either way: one row per contract with vendor, owner, annual cost, seat count, active users, renewal date, and cancellation notice deadline.

Step 2: Find the waste

Waste in SaaS falls into four groups, roughly in order of how easy it is to recover.

Unused seats

Seats assigned to people who have not logged in for 60 to 90 days, including people who have left the company. Here is an illustration: a tool with 500 seats at $40 per user per month shows 360 users active in the last 60 days. Keeping a buffer of 40 for hiring and reclaiming 100 seats saves 100 × $40 × 12 = $48,000 a year, from one contract.

The catch is timing. Most contracts allow adding seats at any time but reducing them only at renewal. Reclaimed seats can be reassigned to new hires immediately, which avoids buying more, but the bill does not fall until the contract renews.

Wrong tier

Users on a premium tier who only use features from a cheaper one. If 150 people on a $40 plan only use features available on a $20 plan, downgrading them saves 150 × $20 × 12 = $36,000 a year. Vendor admin reports on feature usage make this visible.

Duplicate tools

Three project management tools, two video conferencing platforms, four diagramming apps. Consolidating onto one tool per job saves licenses and usually earns a better volume price. It also takes change management, so pick the duplicates where the second tool has few users.

AI add-ons

AI features are now sold as separate per-seat add-ons, bundled into price rises, or billed by usage. Seats bought for a pilot tend to stay after the pilot ends. Check active usage for each AI add-on the same way as for any other license. Microsoft 365, for example, has Copilot usage reports in its admin center. Usage-based AI pricing also needs budget alerts, since a single automation can burn through credits quickly.

Step 3: Use the renewal calendar

The most expensive mistake in SaaS management is missing a cancellation notice deadline. Many contracts auto-renew unless you give written notice 30, 60, or 90 days before the end of the term. Miss it and you are committed to another year at whatever price the vendor sets, with no leverage.

Consumer auto-renewal protections mostly do not help here. They are aimed at consumer subscriptions, and the FTC's "click-to-cancel" rule was struck down by the Eighth Circuit in July 2025 before taking effect. For business contracts, the contract terms are what count.

A workable schedule for any contract above a set threshold (say $25,000 a year):

Sending notice protects you. It does not stop you from renewing, and it tells the vendor you are serious.

Price increases in 2026

Budget for list price rises at renewal. Microsoft raised most Microsoft 365 commercial prices from July 1, 2026, applied at each customer's first renewal after that date. Microsoft 365 E3 went from $36 to $39 per user per month, E5 from $57 to $60, Office 365 E3 from $23 to $26, and Business Standard from $12.50 to $14. Business Premium and Office 365 E1 were unchanged. For a company with 1,000 E3 users, that is about $36,000 a year more at renewal. Google raised Workspace prices in January 2025 when it bundled Gemini into its business plans.

Negotiating points that commonly work:

• A cap on renewal price increases (for example, no more than 3 to 5% a year)
• The right to reduce seats by a set percentage at each anniversary
• Price protection for added seats at the original per-seat rate
• Removal of auto-renewal, or a shorter notice period
• Credits or discounts in exchange for a longer term, if you are confident in the tool

For detailed tactics, see our guide to SaaS contract negotiation, and for managing vendors over the whole relationship, SaaS vendor management.

Step 4: Close the offboarding gap

Unused seats and security risk come from the same place: accounts that outlive the employee. Disabling someone in the identity provider removes access to SSO-connected apps, but not to tools with their own passwords, shared team logins, or API keys the person created.

• Connect as many apps as possible to SSO, and turn on automated provisioning (SCIM) so that removing a user in the identity provider also removes the seat in the app.
• For apps that cannot use SSO, list them in the offboarding checklist with a named owner who removes access.
• Rotate shared credentials and API keys when someone with access leaves.
• Review access for high-risk apps (code repositories, customer databases, finance tools) every quarter.

Orphaned accounts are also a finding in SOC 2 audits. Our SaaS security guide covers access reviews in more depth.

Step 5: Report savings finance will believe

Savings claims lose credibility fast when "we avoided a 10% increase" is reported the same way as "we cancelled a $50,000 tool." Keep three categories:

Report hard savings against the prior year's actual cost, and have finance agree the method before the first report.

Ownership

SaaS spend management works best as a shared job. Finance owns the data and the savings reporting. IT or security owns discovery, SSO, and offboarding. Procurement owns contracts and negotiation. And each business unit names an owner for each of its tools who answers the question "do we still need this, and how many seats?" before every renewal.

The same ownership model runs cloud infrastructure costs, and many companies now review both together. See cloud cost optimization and FinOps for that side, and cash flow management for fitting software commitments into the wider budget.

This guide is for informational purposes only and is not legal or accounting advice. Review contract terms with counsel before sending notices or signing renewals.