SaaS cost optimization for IT leaders is a different problem than it is for finance. Finance sees a number on a renewal. IT sees the tickets that follow when a tool is removed badly. The leaders who do this well treat cost as an engineering problem with a user experience constraint: take out the waste, but do not break the workflow, and do not become the team that took away the app everyone liked.
We work this from the buyer side, with no vendor and no reseller relationship and no commission, paid only by the buyer. That independence matters to IT because it means the recommendation is never to buy more. The recommendation is whatever leaves you with a leaner, calmer stack. This page feeds the wider digital workplace cost optimization program.
Why SaaS cost optimization for IT leaders lands on the technology team
SaaS spend grew up outside procurement. Teams bought tools on cards, admins provisioned seats on request, and renewals rolled over on autopilot. Over a few years that produces a stack nobody fully owns, where the person who can see usage data is IT, and the person who feels the pain of a clumsy cut is also IT. That is why optimization keeps landing on the technology team even when the budget sits with finance. The leaders who get ahead of it own the data and bring the savings story to finance, rather than waiting for a budget cut to arrive from above.
Where the waste actually hides
The core sources of software waste are consistent across organizations. Over licensing, where you bought more seats than you have people. Dormant seats, where active users left or moved and the license kept billing. The wrong plan tier, where users sit on a premium plan they barely touch. Duplicate tools, where two or three apps cover the same capability. Auto renewals nobody reviewed. And shelfware, whole tools bought and forgotten.
For an IT leader the useful move is to instrument these. Pull last login and feature usage from each admin console, reconcile against the headcount you actually employ, and the waste stops being a guess and becomes a list. The digital workplace spend assessment process describes how to gather that data cleanly.
Right size before you negotiate
The instinct under budget pressure is to call the vendor and ask for a discount. That is the wrong first move. A discount on seats you do not use is still waste. Right sizing comes first: reclaim the dormant seats, move overprovisioned users down a tier, and remove the duplicate tool. Only once the stack reflects real need do you negotiate the survivors, because now you are negotiating from an accurate number and the vendor cannot defend the old volume.
This order, right size and rationalize, then negotiate, then govern, is the through line of every effective program. It protects you from the common trap of locking in a multi year deal on a seat count you were about to cut.
Protect the user experience
The fastest way to lose credibility is to remove a tool people depend on without a path to the replacement. Before you consolidate, map who uses the tool you are cutting and what they use it for, then make sure the surviving tool covers that workflow and that the affected users are told before, not after. A good consolidation is barely noticed. A bad one generates a quarter of tickets and a reputation that makes the next cut harder. The savings are only real if adoption survives them.
Build the governance that holds the line
Optimization that is not governed decays. A new tool reappears, a team buys a parallel app on a card, dormant seats accumulate again, and within a year the stack has refilled. The IT leaders who keep the savings put three controls in place. An intake process so new software is requested and reviewed rather than bought quietly. A renewal calendar so no contract auto renews without a deliberate decision. And a periodic utilisation review so dormant seats are caught early rather than at the next audit.
None of this needs heavy tooling to start. A shared register, a calendar, and a quarterly review meeting cover most of the value. Platforms help at scale, but the discipline matters more than the software.
Bring finance along
The last piece is political rather than technical. IT leaders who frame optimization as a savings program they own, with numbers, tend to keep control of the stack. Those who let it arrive as a top down budget cut tend to lose it. Bring finance a ranked list of savings with effort and risk attached, deliver the quick wins first, and the relationship shifts from defending budget to reporting recovery.
For the questions that come up most often, see the digital workplace cost optimization FAQ, and when you are ready to act, the digital workplace spend assessment service turns the savings list into recovered budget.