Exit Ready Portfolio Company Cleans Up Licensing

This exit ready portfolio company cleans up licensing case study shows how a sponsor owned business removed the software exposure that would have surfaced in buyer diligence, protecting its headline valuation in the months before a sale process opened.

The situation

The composite is a private equity backed software and services company of around 1,400 staff, two years into the sponsor hold and being readied for a sale within twelve months. The investment thesis depended on a clean exit at a strong multiple. The deal team knew that a buyer would run its own software due diligence, and that anything it found would be priced against the seller. The portfolio company had grown through two bolt on acquisitions during the hold, and nobody had reconciled the inherited estates against entitlement. The licensing position was, in the sponsor own words, a known unknown.

The cost to resolve an exposure before a sale is consistently a fraction of the price chip the same exposure supports once a buyer finds it.

The exposure we found

We built an effective license position across the tier one publishers and tested it against deployment. The two bolt ons had each carried their own Oracle and Microsoft estates, and the integration had quietly created duplicate deployments and indirect access that exceeded the combined entitlement. One business unit had grown its database footprint well past its purchased processor count. A second had users touching an Oracle backend through a custom front end, a classic indirect access pattern that publishers price aggressively. None of this was visible in the management accounts. All of it would have been visible to a competent buyer side review.

Exposure mapped before the sale process opened
Source	Issue found	Diligence risk if left	Action taken before market
Oracle databases	Deployment past processor entitlement	Price chip and indemnity demand	Resized and trued up at renewal
Oracle via custom app	Indirect access exposure	Worst case settlement estimate	Licensed the access path correctly
Microsoft estate	Duplicate entitlement after bolt ons	Inflated cost base in the model	Consolidated to one agreement
VMware	Legacy perpetual under new model	Repricing risk for the buyer	Modelled and disclosed clearly

Our approach

We worked to the sale timetable, not against it. The priority was to resolve what a buyer would price and to document what a buyer would test. We sequenced each fix against the relevant renewal date so the company corrected its position at the cleanest commercial moment rather than paying a mid term premium. Where a gap could be closed quietly through a true up or a resize, we closed it. Where an item was better disclosed than resolved, such as the VMware model transition, we modelled it and prepared a clear, dated explanation for the data room so the buyer could not inflate it. The goal was a defensible, documented effective license position the seller could stand behind.

Resolving exposure at each renewal point and documenting the rest turned a known unknown into a defensible position before the data room opened.

The outcome

By the time the data room opened, the portfolio company presented a documented effective license position with the material gaps already closed and the remaining items modelled and disclosed. The buyer software diligence confirmed the seller numbers rather than discovering surprises, which removed the single largest software lever a buyer would otherwise have used on price. The cost to cure the exposure before market was a small fraction of the price chip it would have supported in diligence. The sponsor protected its headline valuation and the deal moved without a software driven renegotiation late in the process.

Key takeaways

Latent licensing exposure carried into a sale process is priced by the buyer, almost always at more than the cost the seller would have paid to fix it.
Bolt on acquisitions during a hold create duplicate entitlement and indirect access that standard reporting does not surface.
Resolving gaps at each renewal point is cheaper and cleaner than a mid term correction or a buyer driven indemnity.
Items better disclosed than fixed should be modelled and dated so a buyer cannot inflate them in diligence.

Recommendations for sellers and sponsors

Build the effective license position early. Establish where the estate stands at least two renewal cycles before a planned exit so fixes land at the right commercial moment.
Reconcile every inherited estate. Treat each bolt on as a source of duplicate entitlement and indirect access until proven otherwise.
Resolve quietly, disclose cleanly. Close what can be closed through true ups and resizing, then document the rest with dated, defensible explanations.
Prepare the data room to confirm, not surprise. Give the buyer diligence team a clean estate so software cannot become a late price lever.

Lessons for buyers and sellers

The lesson runs both ways. A seller that cleans up licensing before market keeps the value that an exposure would otherwise transfer to the buyer. A buyer should read a suspiciously clean data room as a reason to verify, not to relax, because a documented position is only as good as the evidence behind it. Either way, the work is the same discipline applied at a different moment in the deal. This is the pre exit application of our license reconciliation service and our software due diligence service. See how the buyer side of the same work plays out in software diligence reprices a deal by 6 million and a PE fund standardises diligence across 12 deals.

Frequently asked questions

What does cleaning up licensing before an exit mean?

It means resolving a portfolio company effective license position before it goes to market: closing compliance gaps, resizing oversized agreements, and documenting entitlement so a buyer diligence team finds a clean estate rather than an unpriced liability.

Why clean up licensing before a sale rather than after?

Because a buyer that finds latent exposure prices it as a risk, with a discount or an indemnity that usually exceeds the cost the seller would have paid to fix it. Resolving it before the data room opens keeps that value with the seller.

How much value can a clean licensing position protect?

It varies with the size of the estate and the publishers involved, but a single unaddressed tier one exposure can support a price chip or holdback running into the millions. The cost to cure is almost always a fraction of the chip it prevents.

Which publishers matter most when preparing for exit?

Oracle, SAP, Microsoft and IBM are the long standing audit leaders, with Broadcom owned VMware, Salesforce and ServiceNow increasingly active as of June 2026. These are the names a buyer diligence team will test hardest.

Does cleaning up licensing help the eventual buyer too?

Yes. A documented, right sized estate transfers cleanly, shortens the buyer own diligence, and reduces the chance of a change of ownership audit landing in the first year after the new deal closes.

Preparing a portfolio company for exit?

Tell us where the hold stands. We respond within one business day with a confidential, scoped software M&A risk assessment that maps and quantifies the licensing exposure a buyer will look for.

Book a confidential call