SaaS consolidation does not fail because the savings are hard to find. It fails because inherited contracts, legacy entities, and renewal dates fall between finance, IT, and integration teams after the deal closes.
It’s the third week of the quarter, and the CFO of a portfolio company is clearing a backlog of vendor emails. Most are routine. Then comes a renewal notice for a tool nobody on the finance team ever approved, billed to a company name that hasn’t appeared on a letterhead in three years. That business was acquired, merged into the group and quietly dissolved, but the subscription carried on as if nothing had changed. It renews in 45 days, the price is going up 8%, and no one still at the company remembers signing it. Moments like this are where post-acquisition IT integration shows its gaps, and where SaaS consolidation should have started long before the invoice arrived.
The renewal is where the mismatch finally shows up
Inherited SaaS rarely announces itself during integration. The integration plan is busy with payroll, email migration and org charts, and a subscription that works quietly in the background doesn’t make anyone’s list.
The vendor, on the other hand, keeps perfect records. So the first time the combined business sees the acquired estate clearly is usually when a vendor sends a bill.
It goes like this. An invoice arrives for a legacy entity. Accounts payable can’t match it to a cost center, so it gets paid to avoid a service interruption. Procurement goes looking for the contract and finds it in the shared drive of a team that was restructured a year ago. The person who signed it has left. By the time anyone reads the renewal clause, the notice window has already closed.
Audits find the same gap from the other direction. A licence review, a SOC 2 evidence request or a year-end close asks for one list of systems, owners and data processors. What comes back is two or three lists, kept by legacy IT teams that never merged their records.
Notice periods in inherited contracts typically run from 30 to 120 days. If a tool renews in March and you find it in February, you’ve probably already bought another year.
Why SaaS consolidation falls between the cracks
Deal teams are measured on getting to signature, and they’re very good at it. Diligence covers valuation, legal exposure, tax structure, financing and key people. When IT gets a workstream, it’s usually about risk: will the target get breached, and will its systems hold up?
Few diligence packs ask the questions that matter a year later. How many software contracts are we inheriting? Which legal entity is on each one? When does each renew, and how much notice does it need?
Once the deal closes, the people who knew the target best move on to the next transaction. Responsibility for what’s left gets split three ways. The integration lead handles people, reporting lines and systems cutover. Finance runs the synergy model, which tends to be written in headcount and property. IT takes identity, email and the network.
Software contracts touch all three teams and sit with none of them. Everyone assumes someone else has picked them up.
The way companies buy SaaS makes the problem worse. Tools get bought by individual departments, on company cards, through resellers, and under whichever entity the buyer worked for at the time. Every acquisition arrives with its own version of that sprawl and stacks it on top of yours. Suddenly the group runs two CRMs, two e-signature tools and two cloud providers, and the finance system treats every one of them as an unrelated line item.
So the estate doubles. And there’s no date in anyone’s plan for retiring the old half.
What three inherited SaaS estates actually looked like
Take an insurance telematics group we work with, built through a string of acquisitions. Once its contracts were in Saasrooms, the combined stack came to 100 applications and about £3.5M in annual spend.
The duplication was easy to see once everything sat in one place. There were eleven cloud and infrastructure vendors, costing close to £690K between them. The group had eight software development tools, two of them code-quality products from the same vendor, each bought by a different team. It paid for two e-signature platforms and two accounting packages. It also had a staff recognition platform signed in 2021 on a three-year term, still filed under a parent name the business no longer trades as.
Then there’s the detail that sums the problem up. In one vendor contract, four different legacy entity names appear as “Customer” across the amendments.
No one did anything wrong. Each amendment was signed by whoever was authorized at the time. But when the renewal came around, no single entity clearly had the authority to cancel it, consolidate it or reopen the price.
Once the full estate was visible, the telematics group found £285K in savings across 19 separate opportunities. That’s roughly 10% of its £2.8M in annual recurring software spend, and none of it needed a new tool or a painful migration. It just needed someone to look.
We see the same thing with other groups we work with. A recruitment and executive search group running five brands had six overlapping CRM and prospecting tools and three separate IT managed service providers. It was even paying two different prices for the same Microsoft licence, depending on which subsidiary held the seat. Sorting that out surfaced £106K across 16 opportunities, about 14.5% of its £730K software bill.
A digital services group with several subsidiaries had one Microsoft reseller contract naming five legal entities at once. It renewed automatically for 12 months at a time and needed 120 days’ notice to change anything, which meant the real decision date sat four months before anyone thought about renewal.
At the recruitment group we work with, the applicant tracking contract tells the story in a single clause. It names the parent “care of” one subsidiary, it has renewed automatically every year since 2022, and it takes one month’s notice to leave. Miss that month and it’s another twelve, whether that subsidiary still hires through it or not.
Saasrooms tracks renewals against the notice date rather than the expiry date, because once an auto-renewal clause is live, the notice date is the only one that counts. Just over £150K of the telematics group’s £285K has already been banked.
The 100-day SaaS consolidation checklist
A bigger integration team won’t fix this. What fixes it is giving SaaS consolidation its own line in the 100-day plan, with a named owner and deadlines, just like headcount and systems cutover already have.
Days 1 to 30: get the full picture before anything renews
- Appoint one owner for the combined SaaS estate, with authority to cancel on behalf of every legal entity.
- Pull spend from every ledger, corporate card and expense tool, not only the contract repository. Card-paid subscriptions are where acquired estates hide.
- Record the contracting entity on every agreement exactly as it’s written, and flag any that names an entity that’s been merged or dissolved.
- Build a renewal calendar around notice dates. Anything whose notice window closes in the next 90 days gets reviewed this month.
- When in doubt, send the non-renewal notice. A notice can usually be withdrawn. A renewal almost never can.
Days 31 to 60: map where the two estates overlap
- Group every tool by function (CRM, e-signature, cloud, developer tooling, collaboration) and list each category where the group now pays twice.
- Compare licences purchased with actual usage on both sides. Inherited seats often belong to people who left during the deal.
- Check what each entity pays for the same product. Resellers regularly charge subsidiaries different rates for identical licences.
- Choose the tool that stays in each category on fit, terms and migration cost, not on which side of the deal it came from.
Days 61 to 100: consolidate and make it stick
- Move users and data off the tools being retired, then cancel against the notice dates you mapped in the first month.
- Renegotiate the surviving contracts on combined volume, and move them onto the right legal entity through a proper novation or amendment.
- Route all new software purchases through one intake process so the sprawl doesn’t grow back.
- Report the recovered spend to the board as EBITDA, next to the rest of the synergy case.
Done well, this is one of the few post-acquisition IT integration workstreams that pays for itself in the first year.
Put the retirement date in the plan
Every deal gets a closing date, a day-one plan and a synergy number. Almost none get a date for retiring the acquired SaaS estate. Without one, inherited contracts keep running on their original terms and under their original names, billed to entities that now exist only on paper.
That’s why the operator holding the renewal notice isn’t really looking at an IT housekeeping job. They’re looking at an EBITDA leak that has been growing quietly since the day the deal closed.
The contract doesn’t care which entity signed it. It just renews.
