A roll up eliminates USD 1.8M duplicate SaaS spend

This case study is an anonymised composite drawn from representative engagements. It names no real parties and uses approximate figures to illustrate typical outcomes.

This roll up eliminates usd 1.8m duplicate saas spend case study shows how a post merger review of the combined software estate removed overlapping subscriptions across a private equity backed roll up and cut about one point eight million dollars from the annual run rate. Duplicate SaaS spend is the most common and most recoverable form of waste in a roll up, because each acquired company arrives with its own stack and no one owns the combined picture until someone is asked to reconcile it.

Inside the roll up eliminates usd 1.8m duplicate saas spend case study

Situation

The platform was a private equity backed roll up that had acquired five companies in a vertical software and services market over eighteen months. Each acquisition had been bought quickly and left to run on its own systems, with the thesis that integration would follow once the platform reached scale. By the fifth deal the combined business was carrying five separate SaaS stacks, five sets of renewals and no central view of what was being paid for or used.

The sponsor engaged us to reconcile the combined estate and quantify the duplicate spend that could be removed without disrupting the operating companies, as part of the value creation plan for the platform.

Risk faced

The exposure here was not a publisher audit but pure overspend compounding every month. Reconciling the five estates against each other surfaced heavy duplication. Three overlapping CRM tenants. Two collaboration suites bought in parallel with seats double counted across shared staff. Four endpoint and identity tools with overlapping coverage. Observability and analytics contracted company by company at small volume pricing when the combined volume qualified for far better terms. And a long tail of niche and shadow SaaS bought team by team and never cancelled.

Left alone, this duplication would have been renewed automatically across the next twelve months, locking in roughly one point eight million dollars of avoidable annual spend and eroding the margin the value creation plan depended on.

Approach

We built a single inventory of every SaaS contract, seat and renewal across the five companies, then mapped overlap by category and by user. For each category we identified the tool to keep, the tools to retire and the renewal dates that set the timing. Because the operating companies still needed to run, we sequenced the consolidation around renewal windows so no contract was cancelled before its replacement was in place and no team lost a tool it depended on.

We modelled the saving per category on a conservative basis, counting only seats and contracts that could be removed without operational risk, and presented the plan as a prioritised schedule the platform finance team could execute against. This is the same discipline as post close license reconciliation, applied to subscription rather than perpetual licensing.

Outcome

The platform executed the schedule over three renewal cycles. CRM standardised onto one tenant, collaboration consolidated to one suite at a negotiated portfolio rate, the security stack was rationalised to one set of tools, and observability and analytics were combined into a single volume agreement. The long tail of shadow SaaS was cancelled and procurement was centralised so it could not regrow.

The result was about one point eight million dollars removed from the annual run rate, lifting platform margin and freeing budget for the systems the combined business actually needed. The reconciliation also gave the sponsor a clean software baseline to carry into the next acquisition, so the same duplication would not simply rebuild with the sixth deal.

Lessons for buyers

A roll up multiplies SaaS spend by default. Each acquired company brings a full stack, and without a central inventory the duplication is invisible because no single operating company sees the whole picture. The waste is not hidden in a contract, it is hidden in the gaps between five contracts that no one reconciles.

The lesson is to reconcile the combined estate early and treat SaaS consolidation as a named workstream in the value creation plan, not an afterthought. Timed around renewals, the saving is large, durable and carries no operational risk, and it compounds with every further acquisition the platform makes.

This outcome is the work of our license reconciliation service, applied across a portfolio. For the diligence that prevents duplication building in the first place, see our software due diligence service.