When I was brought into a large digital transformation program as a subject matter expert, the mandate was clear before my laptop even opened: “SaaS costs had become a concern, and leadership wanted to move quickly to rein them in.”
The CFO had flagged ballooning subscription spend. Business leaders complained about overlapping tools. Procurement wanted to renegotiate contracts. From the outside, it looked like a familiar problem with an obvious solution — reduce licenses, consolidate vendors and stabilize spending.
Early on, it became clear that SaaS cost optimization wasn’t really a financial problem. It was an operating model problem. And treating it purely as a budget exercise was about to make things worse.
By the time I joined the program, the decision had already been made. SaaS costs were considered excessive, and leadership had acted quickly. Licenses were reduced, several platforms were slated for retirement and aggressive targets were set to bring spending down within the quarter.
On paper, the initiative looked decisive. Early dashboards showed immediate savings, and leadership felt confident the problem was being addressed.
What I walked into, however, was the aftermath. Teams were already adjusting to changes they hadn’t fully anticipated. Some employees no longer had access to tools embedded deeply in their daily workflows. Others were rebuilding lost functionality manually, while a few quietly adopted new, unapproved tools to fill the gaps — a pattern that often follows rapid tool consolidation efforts, as noted by Harvard Business Review in its analysis of collaboration overload.
What stood out wasn’t resistance to cost discipline — it was confusion. People weren’t sure which platforms were still supported, who owned decisions going forward or how work was supposed to flow now. Productivity issues surfaced quickly, but they didn’t appear in SaaS spend reports. They showed up in longer cycle times, missed handoffs and growing frustration across teams.
This wasn’t a failure of intent. It was the predictable outcome of treating SaaS cost optimization as a financial correction rather than an operating decision. The organization had moved fast to reduce spend, but without a clear understanding of dependencies, ownership and how work actually happened across systems.
The cost problem was real — but the operational cost of fixing it the wrong way was becoming just as visible.
SaaS sprawl is rarely accidental
When CIOs ask why SaaS costs spiral, the answer is rarely “poor discipline.” It’s usually structural.
In the engagement I described, SaaS sprawl had accumulated over years for understandable reasons:
- Business units bought tools to move faster.
- IT teams enabled experimentation during growth phases.
- Mergers brought duplicate platforms.
- Pandemic-era urgency favored speed over standardization.
No one made a single bad decision. Hundreds of reasonable decisions added up to an unreasonable outcome.
When we conducted a portfolio review, we found well over a hundred SaaS applications in active use across the organization. A significant portion had overlapping functionality. Several had no clear business owner. A handful were mission-critical — but poorly documented or understood outside the teams that used them.
Cutting costs without first mapping ownership, dependency and usage was like pulling wires out of a live control panel.
The real driver of SaaS waste: unclear ownership
One moment crystallized the problem for me.
During a review session, I asked a simple question about one of the highest-cost platforms: “Who owns this product?”
The room went quiet.
IT assumed the business owned it. The business assumed IT managed it. Procurement negotiated the contract. Security reviewed access annually. No one was accountable for adoption, value realization or lifecycle decisions.
This lack of accountability wasn’t unique to that tool — it was systemic. Best-practice guidance on SaaS governance consistently emphasizes the importance of assigning a clearly named owner for every application, accountable for cost, security, compliance and ongoing value.
Without that ownership, redundancy and unmanaged spend tend to persist across portfolios (as outlined in this overview of SaaS governance best practices.
That tool wasn’t expensive because it was misused — it was expensive because it was ownerless.
This is where many SaaS cost initiatives stall. CIOs focus on licenses and contracts, but the real issue is the absence of a product mindset. SaaS platforms behave like products, but many organizations manage them like utilities.
Without clear ownership:
- Usage decays quietly.
- Redundant tools creep in.
- Contracts auto-renew.
- No one feels responsible for retiring platforms.
Cost optimization fails not because leaders don’t try hard enough, but because no one is accountable for value.
When “savings” create downstream costs
In another phase of the program, leadership decided to eliminate a niche workflow tool used by operations teams. The savings were modest, but the platform wasn’t widely understood, so it became an easy target.
Within weeks, exception rates increased. Manual rework grew. Managers spent more time coordinating tasks informally. None of this showed up in the SaaS budget — but it showed up in cycle time and morale.
A frontline manager told me, “We didn’t realize how much that tool did until it was gone.”
These downstream impacts are rarely captured in license reports, but they’re well documented. The hidden costs of SaaS sprawl — including security exposure and operational drag — often outweigh the savings achieved through blunt consolidation efforts.
This is the hidden danger of treating SaaS as interchangeable. Not all tools deliver value at scale, but the ones that do often embed themselves deeply into how work gets done. Removing them without redesigning the process creates invisible costs that finance dashboards never capture.
True optimization requires understanding what breaks when a tool disappears.
Reframing SaaS cost optimization as an operating decision
The turning point came when we paused the cost-cutting exercise and reframed the effort. Instead of asking “How do we spend less?” we asked:
- Which platforms directly support critical workflows?
- Where do we have duplication without differentiation?
- Who is accountable for outcomes enabled by each tool?
- What capabilities must remain stable as we simplify?
We created a lightweight classification model:
- Systems of record — protected, stable, tightly governed
- Systems of differentiation — actively owned and optimized
- Systems of experimentation — time-bound and sunset-driven
This allowed leadership to cut with intention instead of urgency. Tools without owners were flagged. Experimental platforms were given expiration dates. Core systems were protected from blunt reductions.
Costs declined more slowly — but sustainably.
Governance is not bureaucracy — when it’s done right
One of the most common objections I hear when SaaS governance comes up is that it will slow teams down. In theory, fewer controls feel like freedom. In practice, the absence of governance often creates more friction — unclear decisions, duplicated effort and constant rework.
In this program, introducing governance wasn’t about adding process for its own sake. It was about clarifying ownership, decision rights and expectations. We established simple rules: every SaaS platform needed a named owner, usage and value had to be reviewed ahead of renewals, and new tools required a basic justification tied to an existing gap.
None of this required a heavy PMO or extensive documentation to get started. What it required was discipline. And once those guardrails were in place, teams actually moved faster. Decisions that previously stalled due to ambiguity became easier to make. Redundant tools stopped creeping in.
This aligns with broader research showing that structure and clarity don’t suppress innovation — they enable it. As Harvard Business Review has noted, well-designed processes and governance mechanisms help organizations innovate more effectively by reducing friction and uncertainty, not increasing them.
In other words, governance wasn’t the obstacle. It was the enabler that allowed the organization to simplify its SaaS environment without breaking how work got done.
What CIOs can do differently
From this and similar engagements, a few lessons stand out:
First, don’t start with procurement. Start with visibility. Map ownership, usage and dependency before touching contracts.
Second, assign product ownership. Every SaaS tool needs someone accountable for value, not just uptime.
Third, protect what works. Blunt cuts damage credibility. Preserve platforms that truly enable productivity.
Fourth, design for exit. If a tool is experimental, define when and how it will be retired.
Finally, treat optimization as continuous. SaaS cost discipline isn’t a one-time initiative — it’s an operating habit.
The bigger lesson
The most effective SaaS cost programs I’ve seen weren’t about spending less. They were about focusing more. Fewer platforms, clearer ownership and stronger alignment between technology and work.
In the end, the organization I worked with didn’t just reduce costs — it reduced noise. Leaders spent less time debating tools and more time improving outcomes.
That’s the shift CIOs need to make. SaaS cost optimization isn’t about cutting subscriptions. It’s about designing an environment where technology earns its place.
The views expressed are my own and do not represent the views of Deloitte or its clients.
This article is published as part of the Foundry Expert Contributor Network.
Want to join?
Read More from This Article: Why SaaS cost optimization is an operating model problem, not a budget exercise
Source: News