Carve Out Buyer Stands Up Estate in 60 Days

This software M&A case study shows how a carve out buyer stood up its software estate in 60 days, relicensing the new entity in its own name and exiting the transition services agreement before stranded costs and TSA fees ate into the deal.

The situation

The composite is a private equity buyer acquiring a carved out business unit, roughly 700 employees, from a large industrial parent. On day one the unit ran almost entirely on the parent contracts: the parent Microsoft agreement, a shared Oracle estate, and a dozen subscription tools licensed at the parent level. A transition services agreement kept the lights on, but every month under the TSA carried a fee and a hard end date. The new entity had no licenses of its own and no time to waste.

A timeline showing dependency mapping, prioritisation, relicensing of critical systems and a clean exit from the transition services agreement in 60 days.

The exposure we found

The risk in a carve out is not a single audit claim. It is the slow bleed of stranded costs and TSA overrun. Every system still running on the parent contract was a system the new entity could not control, could not renegotiate, and was paying a premium for through TSA fees. Mapping the estate showed which systems were genuinely critical to day one operations and which were carrying cost without carrying weight. Several subscription tools were duplicated or simply unused.

Carve out estate, mapped for relicensing priority
System	Day one critical	Relicense path	TSA exit
ERP and database	Yes	New entity Oracle agreement	Week 4
Productivity suite	Yes	New Microsoft agreement	Week 5
Niche subscription tools	Partly	New contract or retire	Week 7
Duplicated or unused tools	No	Retired, not replaced	Removed

Our approach

We mapped the dependencies first, then sequenced the work by criticality. The systems the business could not run without were relicensed in the new entity name early, so the most expensive TSA lines could be switched off first. The non critical and duplicated tools were retired rather than replaced, which removed cost permanently. Every step was timed against the TSA exit schedule so the new entity left the agreement on its own terms rather than drifting past the deadline into penalty pricing.

A bar comparison showing the planned transition services agreement duration against the shorter actual duration achieved by relicensing critical systems early.

The outcome

The new entity stood up its own software estate in 60 days and exited the transition services agreement well ahead of the original schedule. Retiring duplicated and unused tools removed recurring cost the unit had been carrying for years inside the parent. The buyer entered ownership with contracts in its own name, a clean estate it controlled, and none of the stranded cost overhang that drags on so many carve outs.

Key takeaways

In a carve out the main software risk is stranded cost and TSA overrun, not a single audit claim.
Every month on the parent contract under a TSA carries a fee and removes the buyer control of the system.
Mapping dependencies by criticality lets the most expensive TSA lines be switched off first.
Duplicated and unused tools should be retired, not relicensed, which removes cost permanently.

Recommendations for buyers

Map dependencies before you migrate. You cannot sequence the exit until you know what the business truly needs on day one.
Relicense the critical systems first. Switching off the most expensive TSA lines early saves the most money.
Retire, do not replace, the dead weight. Duplicated and unused tools are an opportunity to cut cost permanently.
Time every step to the TSA clock. Exiting on your schedule avoids the penalty pricing that kicks in past the deadline.

Lessons for buyers

The lesson for buyers is that a carve out is a race against the transition services agreement. The new entity does not own its software until it relicenses in its own name, and every day it waits is a day of TSA fees and lost control. The buyers who plan the estate before close and sequence the work by criticality leave the TSA early and clean. The ones who treat it as an afterthought pay for the parent estate long after they should have.

This is the focus of our carve out and TSA separation service. Read the playbook in our carve out software licensing playbook and a related carve out relicensing case study.

Frequently asked questions

How fast can a carve out buyer stand up its own software estate?

In this composite the new entity relicensed its critical systems and exited the transition services agreement in 60 days. The pace depends on dependency complexity, but sequencing the work by day one criticality lets a buyer move the most expensive systems first and leave the TSA early.

What is the biggest software cost risk in a carve out?

Stranded cost and transition services agreement overrun. Every system still running on the parent contract carries a TSA fee and sits outside the buyer control. Drifting past the TSA deadline usually triggers penalty pricing.

Should every system be relicensed in a carve out?

No. Duplicated and unused tools should be retired rather than replaced, which removes recurring cost permanently. Only the systems the business genuinely needs on day one should be relicensed in the new entity name.

Do you handle the legal side of relicensing?

We provide commercial and licensing advisory and sequence the separation. We recommend you engage your own counsel for the contract terms of any new agreement or TSA exit.

Facing a similar exposure on a live deal?

Tell us where the transaction stands. We respond within one business day with a confidential, scoped software M&A risk assessment.

Book a confidential call