← All articles

SaaS Sprawl: How to Audit, Cut and Renegotiate Your SaaS Budget

SaaS Sprawl: How to Audit, Cut and Renegotiate Your SaaS Budget
Free tool

SaaS Consolidation Calculator — estimate your wasted SaaS spend.

Nobody decided to spend this much

Zylo's 2025 SaaS Management Index, built from more than 40 million SaaS licences and $40 billion of spend under management, reports that SaaS spend now averages $4,830 per employee — up 21.9% year on year. Organisations in the study waste an average of $21 million a year on unused licences, itself up 14.2%.

The number that explains the other two: lines of business now account for 70% of SaaS spend, while IT accounts for 26.1%. Nobody sat down and approved a sprawling stack. Each team bought a sensible tool to solve a real problem, on a card, in about four minutes. Sprawl is the sum of reasonable decisions taken without a shared view.

  • $4,830SaaS spend per employee
  • +21.9%year-on-year increase
  • 70%bought outside IT
  • 152apps at companies under 500 staff

That last figure is the one small businesses find hardest to believe. Organisations with fewer than 500 employees in the study run an average of 152 applications. Most leaders asked to guess say twenty.

Key takeaways

  • You cannot cut what you cannot see. The audit has five sources, and the card statement is the most revealing of them.
  • Consolidate by category, not by app — overlap hides inside functions, not inside names.
  • A renewal calendar is the single highest-value artefact. Almost all negotiating leverage is a function of time remaining.
  • The levers that move price are term length, payment timing, seat commitment and the auto-renewal clause — not asking for a discount.
  • Without an intake process, sprawl regrows to its previous level within about a year.

The five-source audit

Any single source will miss a third of your stack. Pull all five, then reconcile.

Five sources, one inventory 1 Card & bank statements 2 SSO / identity logs 3 Accounts payable invoices 4 Browser extensions & OAuth 5 Ask every team lead Reconciled inventory app · owner · cost · renewal Renewal calendar
Card statements find shadow spend; SSO logs find usage; the survey finds the free tools holding company data.

Record four fields and no more: application, internal owner, annual cost, renewal date. Teams that try to capture fifteen fields never finish the audit.

Pro tip

Search card statements for charges under $50. Sprawl hides in small recurring amounts that never trip an approval threshold — and those same subscriptions are the ones nobody remembers signing up for.

Consolidate by category, not by app

Overlap is invisible when you list applications by name, because two tools that do the same job rarely sound alike. List by function and the duplication becomes obvious. Work down this checklist and write the app names you found beside each row.

CategoryCommonly duplicated withConsolidation opportunity
Document managementCloud storage, intranet, e-signatureHigh — storage suites now cover most needs
Project & work managementTask apps, spreadsheets, dev trackersHigh — teams often run three
Learning management (LMS)HR suite, video hosting, intranetMedium — check the HR platform first
Legal practice managementDocument management, time tracking, billingMedium — vertical suites overlap heavily
Warehouse & inventory managementERP modules, accounting add-onsMedium — often already in the ERP
Fleet managementField service, telematics, expensesMedium
Advertising & campaign managementMarketing automation, analyticsHigh — platform-native tools often suffice
Talent & recruitmentHR suite, job boards, assessment toolsHigh
Employee engagement / surveyHR suite, forms, internal commsHigh — rarely needs its own product
Compliance managementPolicy tools, e-signature, GRC modulesMedium
Analytics & BISpreadsheets, product analytics, CRM reportsMedium — consolidate the source, not the viewer
Design & creativeWhiteboards, presentation toolsLow — genuine specialist need

The pattern that repeats: a suite you already pay for covers 80% of a point solution's job. That is not always a reason to switch — the last 20% may be exactly why the team bought it — but it is always a reason to ask the question at renewal. The SaaS consolidation calculator will do the arithmetic on a specific overlap.

Keep, cut or merge

Once the inventory exists, four questions settle most rows:

  1. How many people used it in the last 30 days? Not licences bought — licences opened. Under 40% utilisation is a resizing conversation, not a renewal.
  2. Does it hold data we would need if it vanished? If yes, it needs an owner and an export path regardless of cost.
  3. Is there a suite we already pay for that covers it? Check before assuming not.
  4. What breaks if we switch it off on Friday? If nobody can answer, that is your answer.
Pro tip

Do not cancel outright — downgrade first. Move the tool to its free tier or a minimum seat count for one renewal cycle. If nobody complains within a month, cancel properly. This avoids the painful case where a "dead" tool turns out to run one critical monthly report.

The renewal calendar

Nearly all negotiating leverage is a function of time. A vendor contacted 90 days out has options; a vendor contacted the week of renewal has you. Build one calendar with every renewal date, and set two reminders per contract:

Days before renewalAction
120Pull usage data. Decide keep / resize / cut. Check the notice period
90Open the conversation. Ask for the renewal quote in writing
60Benchmark alternatives properly — genuinely, not as a bluff
30Final terms, or serve notice

Find the auto-renewal clause before anything else. Many contracts renew automatically unless you give notice 30, 60 or even 90 days ahead. Missing that window removes every lever you have, for a full year.

Negotiating the renewal

"Can we have a discount?" is the weakest opening available. Vendors have a fixed answer for it. What actually moves price is giving the vendor something their sales team is measured on:

LeverWhat you offerTypical response
Term lengthTwo or three years instead of oneMeaningful annual reduction
Payment timingAnnual up front instead of monthlyCommonly 10–20%
Timing of signatureClose inside their quarter or year endBest discounts of the year
Seat commitmentCommitted floor with room to growBetter unit price
Reference or case studyLogo use, a quote, a reference callReal, and often undervalued
Removing modulesDrop tiers nobody usesCleanest saving of all

Three clauses worth fixing while the contract is open, because they cost nothing at signature and a great deal later: a cap on renewal uplift (say CPI or 5%, whichever is lower), a data export guarantee in a usable format, and the removal of automatic renewal in favour of an explicit opt-in.

Stopping it coming back

Sprawl regrows unless something changes structurally. Three low-friction controls do most of the work:

  • An intake step. One short form before any new subscription: what it does, what it replaces, what data it holds, who owns it. The goal is a five-minute pause, not a committee.
  • Single sign-on as policy. If a tool cannot sit behind SSO, that is a security decision as much as a cost one — and SSO logs are what make next year's audit take an hour.
  • A quarterly review of the inventory. Fifteen minutes, four columns, one owner.

This is the same discipline as any other operations improvement: fix the process, then automate the check. The approach is set out in the business automation roadmap, and the storage side is covered in the paperless business system guide.

Frequently asked questions

How many SaaS applications should a small business have?

There is no correct number, and chasing one is a distraction. The Zylo data shows organisations under 500 employees averaging 152 applications, which is far higher than most leaders expect. The useful measure is not the count but the overlap: how many applications serve the same function, and how many have fewer than 40% of their licences actually in use. Fix those two and the count takes care of itself.

When is the best time to negotiate a SaaS contract?

Ninety days before renewal, ideally landing your signature inside the vendor's quarter end or financial year end, when their sales team is most motivated. The prerequisite is knowing your notice period: many contracts renew automatically unless cancelled 30 to 90 days ahead, and missing that date removes your leverage entirely for another year. Check the auto-renewal clause first, then plan backwards from it.

Is shadow IT always a problem?

Not inherently — it usually signals that a team had a real need and the official route was too slow. The risks are concrete rather than moral: company data sitting in an account nobody controls, no offboarding when someone leaves, and duplicate spend. The productive response is a fast, light intake process that makes the sanctioned path easier than the card, rather than a ban that simply pushes purchases further out of sight.

Should we consolidate onto one big suite?

Partially, and with clear eyes. Suites genuinely reduce cost, integration burden and vendor count, and the marginal module you already own is usually the cheapest option available. The trade is concentration risk and a weaker negotiating position at the next renewal, because switching costs rise with every function you move in. A reasonable rule: consolidate commodity functions such as storage, forms and surveys; keep genuine specialisms separate.

How do we measure whether the exercise worked?

Track annual SaaS spend per employee, because it normalises for headcount changes and is directly comparable to the published benchmarks. Alongside it, track licence utilisation and the number of applications without a named owner. A one-off cut that is not accompanied by an intake process will show up as a saving this year and a return to the previous level within about a year.

Sources

  1. Zylo, 2025 SaaS Management Index — analysis of over 40 million SaaS licences and $40 billion in spend under management. Source of the $4,830 per employee, 21.9%, $21M, 70% / 26.1% and 152-application figures.
  2. Flexera, State of the Cloud research — ongoing industry benchmarking of cloud and software waste.
  3. FinOps Foundation, What is FinOps — the discipline and vocabulary for managing variable technology spend.

Want this working
in your business?