Saturday, November 21, 2026
Guide

SaaS spend management: how companies cut software waste and AI cost surprises

The average company in Zylo's 2026 index spends $55.7 million a year on SaaS across 305 apps. The savings are in three numbers: licenses bought, licenses used and the date each contract renews.

A person using a calculator at a desk

Software subscriptions are one of the largest IT costs and one of the hardest to track. Zylo's 2026 SaaS Management Index puts the average company's annual SaaS spend at $55.7 million, up 8% from a year earlier, with a median of $20.6 million. The average portfolio holds 305 applications, and the median holds 240.

Flexera's State of ITAM 2026 report, based on more than 500 IT asset management professionals, finds that 43% of organizations saw wasted SaaS spend rise over the past year. Only 66% say they have visibility into their SaaS environment.

AI is the fastest-moving line

Zylo reports spending on AI-native applications rose 108%, and 78% of IT leaders were surprised by charges from AI features or pay-per-use pricing. Another 61% cut projects because of unplanned SaaS cost increases. Flexera's numbers point the same way: 59% reported more wasted AI software spend, and only 31% have visibility into AI software.

Per-seat plans were easy to forecast. Metered AI features are not, which is why the approval step below applies to usage-based plans as well as new apps. Copilot Business billing is a current example of a per-seat product with a usage cap attached.

The three numbers to bring to a renewal

  1. Licenses bought. This comes from the contract and the vendor's admin page.
  2. Licenses used. Count users with activity in the last 90 days. In Microsoft 365, the Active Users report shows a last active date per product beside each license assignment, and trends run over 7, 30, 90 or 180 days. Microsoft's page describes no inactive-user filter, so export the table to CSV and compare the two columns.
  3. The renewal date and notice period. Both are in the contract. A missed notice date is how a contract renews on the old terms.

The gap between the first two numbers is the saving. As an example, with 1,000 seats at $12 per user per month and 20% of seats inactive for 90 days, 200 seats are unused. Removing them saves $28,800 a year. Those figures are hypothetical, so run the same calculation on your own contracts, and the biggest apps first.

A spend management process

Step What to do
Discover Combine finance records, expense reports, single sign-on logs and browser or network data to find every app
Assign owners Every app gets a business owner and a budget line
Measure use Compare licenses bought with active users over 90 days
Rationalize Pick one tool per job where several overlap
Right-size Remove unused seats and downgrade plans where premium features go unused
Manage renewals Keep a renewal calendar and start reviews 90 days before each date
Govern AI Approve AI features and usage-based plans centrally, with spending caps

Anyone with a credit card can buy software, so the discovery step matters most: you cannot size what you cannot see. Flexera found that 78% of IT asset management teams name an accurate inventory as their top priority.

Renewals are where savings happen

You have the most bargaining power at renewal. Start 90 days out, bring usage data, and know your alternatives. Ask for a cap on future price increases and the right to reduce seats without penalty.

Tools

SaaS management platforms automate discovery and usage tracking. Smaller companies can start with SSO reports, a finance export and a spreadsheet. Cloud infrastructure spend is a separate discipline, covered in our cloud cost guide.

What IT teams should do

  • Build a list of every SaaS app from finance and SSO data, with an owner for each.
  • For your five largest contracts, compare seats bought with users active in the last 90 days.
  • Put every renewal date and notice period on one calendar with a 90-day review reminder.
  • Require approval and spending caps for AI add-ons and usage-based plans.

Sources