Identified savings are only a forecast. Realized savings are the result. The biggest SaaS cost optimization opportunities usually do not fail because they are impossible to win, they fail because no one gives them the executive attention needed to move.
The slide looks good. Seven figures of SaaS savings identified, a tidy pipeline chart, a spend management program that appears to be working. Then a board member asks the question that matters: how much of that is actually in the P&L? The CFO gives the honest answer, which is a fraction of it, and the follow-up arrives before the sentence is finished. If the team already found the money, why hasn’t it landed? Most finance leaders reach for a backlog story here. Too many opportunities, not enough hands. The data points to something more specific and more fixable. The opportunities worth the most are the slowest to move, and what looks like a backlog problem is really a bandwidth problem.
The Core Finding: Value and Velocity Don’t Line Up
Most SaaS spend management content talks about total savings. Industry research says roughly half of purchased SaaS licenses go unused, and SaaS spend per employee climbed by more than a fifth in a single year. Those numbers explain why waste exists. They don’t explain why identified savings take so long to reach the income statement.
To answer that, look at velocity by value. Saasrooms tracks every savings opportunity on a kanban board that runs from Backlog through Scoping, Sourcing and Contracting to Completed. Across 708 opportunities at 36 companies, logged between late 2022 and September 2026, one pattern stands out.
In the largest cohort, opportunities worth $25,000 or more make up fewer than 7% of everything still open. They hold 71% of the open value.
That’s the stage-versus-value mismatch. A pipeline reported by stage looks evenly busy, with dozens of items moving across every column. A pipeline viewed by value shows that the outcome of the entire program depends on a handful of renegotiations, and those are the ones moving slowest. Large opportunities that reached Completed took a median of 138 days to get there, against 117 for small ones. In the second cohort the gap was wider: 106 days for large opportunities, 61 for small.
Inside the Kanban: Small Items Flow, Big Items Wait
The stage-level view makes the pattern concrete.
The Backlog is mostly small stuff. Nearly two thirds of its items are worth under $5,000 each: idle seats, a duplicate collaboration tool, a premium tier nobody uses. These need one decision from one person, and they clear whenever someone has a spare afternoon.
Scoping is where the value pools. A small number of large opportunities hold most of the stage’s dollars. At one healthcare services company, two items alone come to roughly $600,000: a consolidation of IT reseller spend and a CRM renegotiation. Further down the board, the same company has another $300,000 of bundling and right-sizing work in Sourcing.
Contracting is even more concentrated. At a life sciences manufacturer, a single right-sizing program approaching $1 million makes up most of the column on its own.
Then there are the ones that simply stop. A technology company has a supplier switch worth close to $200,000 that has sat in Scoping for nearly three years. An IT services firm has an opportunity of around $80,000 that has waited in Backlog for about as long. Nobody rejected either one. They just never became anyone’s priority.
Why Big SaaS Renegotiations Stall Before Sourcing Can Start
A seat cleanup is a task. A six-figure CRM renegotiation is a negotiation the company has to have with itself before it can have one with the vendor.
The budget owner needs to accept a lower number. The executive sponsor has to decide whether the tool stays, gets consolidated or gets replaced. Key users, who often understand the product better than finance does, need to say which features actually matter. Security and legal want a view on any change to terms. In healthcare and life sciences, compliance joins the conversation too, because a system that touches patient or regulated data can’t be swapped on price alone. And someone has to settle the question every serious vendor negotiation turns on: what is the walk-away option, and is the company willing to use it?
None of that is sourcing. All of it has to happen before sourcing.
Ownership makes this harder. Industry data shows that lines of business now control around 70% of SaaS spend, with IT managing only about a quarter. So the people whose agreement a large renegotiation needs are spread across departments, senior, busy and rarely measured on IT cost optimization. The CFO wants the savings. The CTO wants no disruption to a mission-critical system. The department head wants to keep the tool the team likes. Each position is reasonable. None resolves on its own.
The cost of waiting is concrete. Large SaaS contracts usually carry renewal notice periods of 30 to 90 days, and many renew automatically. Miss the window and the leverage is gone for another year, sometimes three. An opportunity that has sat in Scoping for ten months often isn’t delayed. It’s already lost, and the pipeline just hasn’t recorded it yet.
What shortens the internal debate is evidence. Saasrooms attaches the buyer, the sponsor and the key user to each opportunity, alongside usage data, contract terms and the renewal date. When the sponsor can see how many purchased licenses haven’t been opened in 90 days, the discussion stops being procurement’s opinion against a department’s preference. It becomes the company’s own data on the table.
Triage by Value at Stake, Not Stage Age
Here’s the encouraging part. Large opportunities aren’t harder to win. They’re harder to start.
Among opportunities logged more than a year ago, Saasrooms data shows about half the value of large opportunities has been realized, compared with less than a quarter for small ones. Given time and attention, big renegotiations land. The constraint is getting them the attention early enough.
The same company can show both behaviors at once. A pharmacy services business has closed several wins in the $70,000 to $85,000 range through contract-term renegotiation, yet a license-level opportunity of similar size has sat in Scoping for more than a year. A healthcare technology company with several thousand users has a steady record of completed license and right-sizing savings, alongside a contract-term opportunity that has waited in Scoping for close to two years. The capability is plainly there. What’s missing on those items is an owner with the authority to move them.
Operators who triage by value at stake run the board differently, and the change is smaller than it sounds:
- Sort by savings potential, not by date. The top ten opportunities by dollar value get reviewed weekly, each with a named owner and a next action. Everything else runs on a lighter cadence.
- Assign an executive sponsor above a set threshold. If a renegotiation is big enough to move EBITDA, it needs someone who can settle the internal debate before it leaves Backlog.
- Plan backwards from the renewal notice date. A contract with an auto-renewal clause 120 days out is urgent even if it was logged last week. Saasrooms flags auto-renewal terms and renewal dates on each application, which turns “we should look at this vendor” into “we have until the 14th.”
- Batch the small stuff. Low-dollar license optimization rarely needs deliberation, so clear it in bulk and protect the senior hours the large items need.
None of this adds headcount. It reallocates the scarcest resource in any SaaS cost optimization program, which is executive attention.
What This Means for Anyone Reporting a Pipeline Number to a Board
If 7% of open opportunities carry 71% of the value, a single pipeline total is close to meaningless as a forecast. It blends items that will close this month with items that may never close, and weights them equally.
That’s a governance exposure for CFOs, PE operating partners and anyone else presenting cost optimization results to a board or investment committee. Industry research puts the gap between negotiated and realized procurement savings at 20% at the low end and often well above 30%, and organizations lose around 11% of contract value after signature. Boards have learned to discount savings claims. A pipeline figure that grows quarter after quarter without a matching rise in realized savings erodes credibility faster than a smaller number delivered on time.
A more defensible report separates identified from realized savings in the same view, every time. It shows concentration: how much of the pipeline sits in the top five or ten opportunities and what stage each is in. It puts the age of those large items next to their renewal deadlines. And it names an owner for each, because an opportunity without an executive sponsor is a hope, not a plan.
In a PE context the stakes are sharper. Identified savings often underpins the value creation thesis in a 100-day plan. Realized savings is what appears in the EBITDA bridge at exit. Diligence teams look straight at the gap between the two.
Three questions are worth asking about any savings pipeline before the next board meeting. Which five opportunities hold the most value, and who owns each one? How many days remain before each of those contracts renews? And what share of last year’s identified savings has actually reached the P&L?
Identified Is a Forecast. Realized Is a Result.
Go back to the board meeting. A CFO reporting a large identified number and a small realized one isn’t failing. Two different things are being reported under the same word, and the board is hearing them as one.
In Saasrooms data, the share of identified value that reaches Completed roughly doubles once opportunities have had a year to work through the pipeline. Most of the gap is time, and most of that time is spent waiting for internal alignment on a few big renegotiations that nobody has been given the bandwidth to drive.
The sentence that changes how a board reads the number is a simple one: savings identified shows what the team found, savings realized shows what the company executed, and only the second belongs in the EBITDA forecast.
