In distressed sales and carve outs the usual safety nets are weak or gone. Here is why software risk concentrates in these deals and how buyers protect themselves through price and a day one plan.
Software risk in distressed and carve out deals is more concentrated and harder to recover than in a standard acquisition. In a solvent share sale the buyer inherits the target software estate intact and can usually pursue the seller if a licensing problem emerges. In a distressed sale or a carve out, the protections that normally catch software exposure are weak or absent. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and in these deals it compounds, because consents may not transfer, licences may belong to a parent, maintenance may have lapsed, and recourse to the seller is limited or gone. This page explains why these deals carry concentrated software risk and how buyers protect themselves when the usual safety nets do not apply.
Three features of these deals push software risk up at the same time as recourse falls. First, the structure is usually an asset purchase or a carve out rather than a share sale, so the agreements do not transfer automatically. Change of control and anti assignment clauses can trigger consent, termination, or repricing, and an asset deal frequently requires fresh consents that the publisher can price or refuse. Second, the target often runs on licences held by a parent or another group entity, so what looks like an operating estate may have no standalone right to use after separation. Third, distressed sellers commonly stop paying maintenance and let compliance slip before sale, leaving lapsed support and accumulated under deployment for the buyer to inherit.
The recourse problem makes all of this worse. In a solvent deal the buyer can rely on reps, warranties, and an indemnity backed by a creditworthy seller or an escrow. In a distressed sale the seller may be in administration or insolvent, so warranties are of little value and there may be no party left to indemnify. The buyer is effectively buying the software risk outright. That is why the analysis has to be done before the deal closes, because afterwards there is rarely anyone to turn to.
A carve out adds a separation dimension that a whole company deal does not have. The business being sold often shares software with the parent under enterprise agreements, shared services, or group wide licences. Once it leaves the group, it needs its own entitlement for everything it uses, and that entitlement has to be bought or transferred on terms the publisher controls. A transition services agreement can keep the lights on for a period, but it is a bridge, not a solution. The buyer that does not map standalone entitlement before close can find that the carved out business has no compliant right to run its core systems on day one of independence.
This is where a transition services agreement and the licensing analysis have to work together. The TSA buys time, but the clock is running, and the publisher knows it. Buyers should treat the standalone licensing position as a day one requirement, scoped during diligence, rather than something to resolve during the TSA period under time pressure. The separation analysis and the cost to cure are two views of the same estate, and both feed the price the buyer should be willing to pay.
| Risk factor | Standard share sale | Distressed or carve out |
|---|---|---|
| Agreement transfer | Usually automatic | Consent or fresh licence needed |
| Standalone entitlement | Intact | Often shared with parent |
| Maintenance status | Generally current | Frequently lapsed |
| Recourse to seller | Reps, warranty, indemnity | Limited or none |
| Time to remediate | Flexible after close | TSA period only |
Because recourse is weak, the protection has to come from price and structure rather than from warranties. The buyer prices the cure cost into the consideration, as covered in pricing software exposure into the purchase price, and builds the standalone entitlement requirement into the day one plan. Where any recourse is available it should be ring fenced through a specific software licensing indemnity, even if its practical value is limited by the seller financial position.
The discipline in a distressed or carve out deal is to assume the buyer will carry the full software exposure and to price accordingly. That means quantifying the cost to cure using the method in quantifying cost to cure for the deal model, mapping the standalone entitlement gap, and adding the cost of any consents the publisher can demand. The number is then deducted from the price, because there is no seller to recover it from later. A buyer that prices a distressed deal as though warranties will hold is underwriting a risk it cannot transfer.
The scale these exposures can reach is well documented. In publicly reported disputes, SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, as of June 2026. Those were solvent groups with the means to fight and settle. A distressed buyer inheriting a similar position has neither a seller to share it with nor the time a solvent group enjoys, which is why the exposure has to be on the table before the price is agreed rather than discovered after completion.
The upside is that a buyer who does this work can often acquire a distressed or carved out business at a price that properly reflects the risk, and can plan the remediation rather than be surprised by it. The exposure does not disappear, but it becomes a known cost that the buyer has chosen to take on at the right price, with a day one plan to resolve it. That is a far stronger position than discovering the gap after close, when the seller is gone and the publisher holds every card.
Because the protections of a normal deal are missing, the integration plan for a distressed or carve out acquisition has to treat licensing as a day one item. The buyer needs to know, before close, which systems the business has a compliant right to run, which depend on consents that may not arrive, and which require fresh licences to be bought. Where the TSA covers a system temporarily, the plan should set the date by which standalone entitlement must be in place, with the cost already in the model. Treating this as a clean up project to be handled after integration is how a carve out runs into a compliance wall in its first months of independence.
The same analysis that prices the deal therefore doubles as the day one operating plan. A reconciliation that maps deployment, entitlement, and separation requirements tells the buyer both what to pay and what to do on the morning after completion. That dual use is why the work belongs in diligence and not in post close integration, and why it sits within software in deal valuation alongside pricing and structure, drawing on software spend diligence for the underlying reconciliation.
Engage your own counsel for legal interpretation of any agreement, consent requirement, or change of control clause.
Tell us where the deal stands. We respond within one business day with a scoped, buyer side engagement that protects the value you underwrote.
Book a confidential call