Home / Case Studies / Carve Out Re Licensed Without TSA Overrun
Case study

A carve out re licensed without TSA overrun

A divested unit stood up its own software estate and exited the Transition Services Agreement on schedule, because the software separation was planned from the start rather than left to the deadline.

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 carve out re licensed without tsa overrun case study shows how early separation planning kept a standalone business off an open ended dependency on its former parent. A carve out is the hardest software separation, because the divested unit often runs on the parent agreements and loses that entitlement on day one.

Inside the carve out re licensed without TSA overrun case study

TSA cost: drifting exit versus planned exitAn unplanned TSA exit drifts well past the deadline and runs up extension fees, while a planned exit closes on schedule at a fraction of the cost.TSA cost: drifting exit versus planned exitUnplanned exit costHighExtension feesAvoidedPlanned exit costOn budgetSchedule slipNone
Planning the software exit early closed the TSA on schedule and avoided the extension fees of a drifting exit.
Separation outcomes against the plan
WorkstreamWithout planningWith early planning
Shared agreementsDiscovered lateMapped before close
Standalone licensesBought under pressureRight sized and funded
TSA scopeOpen endedBounded and priced
Exit dateSlippedMet on schedule

Situation

This case study follows the carve out of a 900 employee business unit from a larger industrial parent in Europe, sold to a financial buyer who would run it as a standalone company. The unit relied on software that had been licensed at the parent level, including major publisher agreements for databases, collaboration and virtualisation. A Transition Services Agreement gave the parent a defined window to keep providing access while the new entity built its own capability.

The buyer engaged us early to plan the software separation, because software is the workstream that most often makes a carve out run long and overrun the TSA.

Risk faced

The mapping showed that the unit had almost no standalone software rights. The agreements it depended on were group wide or licensed to the parent entity, and several contained anti assignment and change of control terms that the carve out would trigger. Without a plan, the unit would reach TSA exit with no rights to the software it ran every day, the parent would carry stranded cost for capacity it no longer used, and the TSA would extend while both sides argued over who owed what.

The major publishers were the hardest, because their agreements bind usage to named entities and metrics that a divestiture disrupts, and re licensing through them required consent and procurement that take months.

Approach

We built a separation plan that classified every material agreement as assign, split, repurchase or replace, and quantified the cost of each path. We mapped the software critical path backward from the TSA exit date, which showed which long lead items had to start immediately. We sequenced the new entity's agreements to come into effect as the corresponding TSA services ended, avoiding both double licensing and gaps in access.

Because the new entity was entering the market as a fresh buyer, we used that leverage to negotiate agreements sized for its actual scale rather than a proportional slice of the parent's deal. We provided the commercial and licensing analysis and worked alongside the entity's own counsel on the contracts.

Outcome

The new entity exited the TSA on its original schedule with full standalone rights to everything it needed. There was no double licensing during the transition and no gap where access lapsed. The agreements it signed were right sized, leaving it with a leaner software cost base than the share of the parent estate it had previously consumed.

The parent released the stranded cost tied to the unit by reconciling its post separation estate against its reduced usage and acting at renewal. Both sides protected the value the carve out was meant to deliver, and neither carried cost it should have shed.

Lessons for buyers

Software is on the critical path of a carve out, and the items that overrun are almost always the ones left until the parent flagged them. Starting the long lead publisher agreements first is what kept this TSA on schedule. The separation also created a rare moment of leverage for the new entity, which a deliberate plan turned into better terms rather than a rushed repurchase.

The lesson is to treat the software exit as a planned workstream from the start of the separation, not a late clean up. The cost of planning early is small against the cost of an extended TSA and a forced re licensing.

Key takeaways
  • A carved business often runs on the parent agreements and loses that entitlement on close.
  • Shared and group wide contracts rarely assign cleanly, so new agreements are usually needed.
  • Planning the exit early avoids the extension fees of a drifting TSA.
  • A bounded, priced TSA is a managed dependency, not an open one.
  • The standalone estate was right sized rather than over bought under deadline pressure.
Recommendations for buyers
  1. Map the shared estate before close. Establish what the carved business relies on from the parent.
  2. Bound and price the TSA. Scope the transitional services and set a firm exit date.
  3. Fund the re licensing. Right size the new agreements rather than buying under pressure.
  4. Stand up the estate early. Build the clean standalone footing before the TSA ends.

This outcome is the work of our carve out and TSA service, applied to the method in the carve outs and TSA guide. For the questions buyers ask most, see the FAQ below.

Frequently asked questions

Is this a real named carve out?

No. It is an anonymised composite drawn from representative engagements, using approximate figures and a representative deal profile. No real parties are named.

Why do carve out TSAs overrun on software?

Re licensing the divested unit through consents and new agreements takes longer than planned, so the parent keeps providing access. Planning the software exit early keeps the TSA on schedule.

What is stranded cost in a carve out?

It is licensing the parent keeps paying for after the unit leaves, because capacity or agreements were sized for the combined business. It must be reconciled and released deliberately.

How did the new entity get better terms?

A carve out entity enters the market as a fresh buyer the publishers want to win. A deliberate plan used that leverage to negotiate agreements sized for actual need rather than a proportional slice of the parent deal.

Is this legal advice?

No. We provide commercial and licensing advisory on the buyer side and work alongside your own counsel on any legal interpretation.

Planning a carve out separation?

Request a confidential software M&A risk assessment. We map the shared estate and plan the exit onto a clean footing.

Book a confidential assessment