Software is the critical path in a carve out. Map, price and re contract every entitlement before close, not after, so no stranded cost or audit lands later.
A carve out software licensing playbook is the buyer side method for taking a business unit off the parent software estate and standing it up on its own entitlements without leaving stranded cost, unlicensed use, or an audit waiting after close. Software is the part of a carve out that looks simple on a contract list and turns out to be the critical path. The applications keep running on day one, but the licenses, identities and shared agreements behind them rarely transfer cleanly, and the gaps only become visible when a publisher counts users that no longer belong to a contract. This playbook sets out the sequence we run so the licensing position is mapped, priced and re contracted before it can cost the buyer money.
In a carve out the parent is motivated to move fast and to keep its own remaining estate clean. The buyer inherits whatever was not resolved. A carve out software licensing playbook protects the buyer because it forces the licensing position into the open before signing, when there is still time to negotiate, rather than after close, when the leverage has gone. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and it lands as a publisher audit once the new entity is operating on its own. The playbook is how that latent exposure is found and quantified while it can still change the deal terms.
The cost of getting this wrong is not theoretical. Publishers track ownership changes and treat them as a trigger to count. SAP pursued Anheuser Busch InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, as reported in UK and US trade coverage of those disputes as of 2017 and 2018. A carve out concentrates exactly the conditions that produce claims of that size, because users, environments and shared agreements all move at once. The playbook exists to make sure the buyer is not the party left holding that bill.
The playbook starts with a complete inventory of the software the carved out unit actually uses, not the software the parent thinks it uses. Discovery tooling, deployment records and access logs reveal what is installed and consumed, while contract records reveal what is licensed. The two rarely match, and the gap between them is the first measure of exposure. From the inventory the work moves to entitlement mapping, where every license is tied to the metric it is counted on, the agreement it sits under and the owner who controls it. This is the step that separates a clean license from a shared one, and shared licenses are where most carve out value leaks, a problem covered in depth in separating shared software licenses in a carve out.
Entitlement mapping also surfaces the difference between a license that can be assigned and one that has to be bought again. Where an entitlement sits on a parent enterprise agreement, the carved out unit usually has no standalone right to it, and the new entity will have to license from scratch. Knowing that before close lets the buyer price it, a calculation set out in re licensing the carved out business from scratch. The inventory and the entitlement map together become the evidence base for every later stage.
Most enterprise agreements contain change of control or anti assignment clauses that can trigger consent, termination or repricing when ownership changes. Whether a clause bites depends on the deal structure. A stock purchase, an asset purchase, a merger and a carve out each engage different clauses, and the same contract can transfer freely in one structure and require publisher consent in another. The consent path stage identifies every clause that gates a transfer, sequences the consents by lead time and starts the conversations early, because publisher consent is outside the buyer control and is the dependency most likely to hold up everything behind it. This is commercial and licensing work, and the buyer own counsel should interpret the clauses themselves.
The consent path is also where pricing leverage is won or lost. A publisher asked for consent at the last minute, with a hard close date approaching, holds all the leverage. The same publisher approached early, with a credible alternative on the table, is far more likely to consent on reasonable terms. Sequencing consent first is the single highest value move in the playbook, and the detail is covered in avoiding vendor consent delays in a carve out.
Where a dependency cannot be severed by close, the parent provides it under a transition services agreement. The TSA scope stage defines exactly which software services the parent runs after close, for how long and at what price, so the new entity is not left on open ended borrowed infrastructure. A tight TSA scope is the difference between a clean exit and a slow, expensive dependence, and the mechanics are set out in the TSA exit timeline and software critical path. The final stage, new entity standup, is where the unit re contracts in its own name, migrates off the parent systems and exits the TSA cleanly without paying twice. That work is the subject of standing up the new entity software estate.
The five stages are sequential because each depends on the one before. There is no point scoping a TSA before the entitlement map shows what cannot transfer, and no point standing up the new entity before the consent path is clear. Run in order, the playbook turns a carve out from a series of licensing surprises into a priced, sequenced plan. Run out of order, or skipped, it leaves the buyer to discover the gaps in an audit. The whole method sits inside our carve out and TSA separation service and the wider carve out and TSA software playbook.
The commercial point of the playbook is to convert licensing uncertainty into a number the deal team can use. Each stage produces a figure: the stranded cost the parent will try to leave behind, the re licensing cost where entitlements do not transfer, the consent and repricing risk on gated contracts, and the TSA cost while the new entity stands on its own. Added together these form the licensing exposure of the carve out, and that number belongs in the deal model as a price adjustment, an indemnity or a condition, not as a surprise in year one. Quantifying it before close is what gives the buyer leverage to push the cost back to the seller where it belongs.
The most common mistake is treating the contract list as the inventory. A contract list shows what was bought, not what is used, and the gap between the two is the exposure. A unit can be running ten times the users a contract allows because the parent never trued up, and that overuse transfers to the new entity as unlicensed deployment the moment the parent agreement no longer covers it. The second mistake is assuming software transfers with the assets. It often does not. Many licenses are personal to the original licensee and need explicit publisher consent to move, which is why the consent path is its own stage rather than an afterthought.
A third mistake is leaving the TSA open ended because the separation feels too complex to finish. Every extra month on the TSA is a month of paying the parent to run software the new entity should already own, and it extends the window in which a publisher can argue the entitlement was never properly transferred. The fourth is negotiating new contracts at the last minute, when the close date removes all leverage and publishers price accordingly. Each of these mistakes is avoidable, and avoiding them is the difference between a carve out that closes clean and one that produces a claim in year one. The playbook is built specifically to design these failures out of the separation.
| Stage | Buyer side objective | Risk if skipped |
|---|---|---|
| License inventory | List every entitlement the unit uses | Stranded cost and unlicensed use go unseen |
| Entitlement mapping | Tie each license to a metric and an owner | Shared agreements split the wrong way |
| Consent path | Identify clauses that gate a transfer | Publisher blocks or reprices at close |
| TSA scope | Define what the parent runs after close | Open ended dependence and audit exposure |
| New entity standup | Re contract and exit the TSA cleanly | Double licensing and missed exit dates |
We run the full licensing playbook before close so the carve out completes without stranded cost or an audit waiting after it.
Request a carve out software assessment