Roll-up exit strategy: how to present a platform's combined records footprint

Why the records footprint belongs in a roll-up exit story

A roll-up exit strategy should show buyers what the platform became, including the operating records each add-on brought with it. Map every system and archive to the legal entity that owns it, with years of history and export access, so an exit buyer and any data licensing process both know exactly what exists and who can sign for it.

The pressure on platform exits makes this worth the effort. Bain's Global Private Equity Report 2026 counts about 32,000 unsold companies worth $3.8 trillion, and estimates that a deal which needed 5% EBITDA growth a decade ago now needs about 12% to reach a 2.5x return over five years. Buy-and-build platforms cannot lean on multiple arbitrage alone; buyers want evidence that the combination is worth more than its parts.

A combined records footprint is part of that evidence. A platform assembled from eight regional businesses may hold eight separate histories of customer work, pricing decisions and service outcomes, sometimes across more systems and more years than a single company of its size would have.

How to build a records footprint by legal entity

Work entity by entity, not system by system. Integration usually merges tools faster than it merges legal entities, so one CRM may hold records created by companies that still exist separately on paper.

1. List every legal entity: the platform holding company, the operating company and each add-on, noting whether it was merged, kept as a subsidiary or bought through an asset purchase.
2. List current and retired systems for each entity: email, chat, CRM, ERP, field service, ticketing, project and finance tools, plus anything switched off after integration.
3. Record years of history and export status: how far back each system goes, whether a full export exists and who holds it.
4. Trace the ownership chain: check each purchase agreement to confirm the records transferred, and note which entity holds them today.
5. Flag content created by others: the Copyright Office's circular on works made for hire explains that work prepared by employees within the scope of their jobs belongs to the employer, while content from contractors may not unless rights were assigned in writing.
6. Name the signer for each entity: the officer who can approve a license for the entity that actually holds the rights.
7. Summarize on one page: entities, systems, history, rights notes and signers, ready for the exit data room or a licensing conversation.

What an entity map looks like (Illustrative)

Illustrative: a fictional commercial services platform with four add-ons. All names and details are invented.

The table makes the risks visible at a glance. Add-on C's history may still belong to the seller, and Add-on D's history exists only if someone kept the exports.

How the footprint strengthens the exit

A buyer of a platform asks whether integration actually happened. A clear footprint answers part of that question: it shows which histories were migrated, which were archived and which were lost, and it signals the operational discipline an exit readiness review looks for.

It also forces a decision on licensing timing. If the platform licenses its combined records before a sale, the exclusive AI-training term, scope and remaining duration become disclosed items for the buyer. If it waits, the buyer inherits the records and the option. Either path can work; leaving the question open until the banker's process starts does not.

The guide to post-merger data migration covers how to keep history while systems consolidate, and the guide to value creation in extended hold periods covers options when the exit slips.

Who builds the map, and what to ask the platform CFO

The platform CFO usually owns the entity list, the IT lead or managed service provider knows the systems, and deal counsel holds the purchase agreements. Put the three in one working session rather than sending a questionnaire, because the gaps show up where their answers disagree.

Expect the first draft to be incomplete. Retired systems from early add-ons are the usual blind spot, and they are often the ones with the longest histories.

What it means for an operating partner making an introduction

A platform that combines several add-ons may clear the program baseline where a single add-on would not. SourceX looks for US companies that had 50+ full-time employees at peak (contractors excluded) and have operated for several documented years, with clear rights to their records and an officer authorized to approve a license. Run the platform through the company fit checker and compare it with who qualifies; the private equity operating partners page explains the introduction itself.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. How a multi-entity platform counts as a referred company is set by the program terms and your signed agreement, so ask before assuming each add-on counts separately.

Limits and open questions

• Former owners with rollover equity or board seats may need to approve a license under the platform's governance documents.
• Earn-outs tied to an add-on's results can be affected by one-time proceeds; check the earn-out definitions before any license is signed.
• Records left with sellers in asset deals cannot be licensed by the platform.
• Residential service roll-ups hold large volumes of homeowner personal data, which is a weaker fit; the HVAC and plumbing roll-up screen shows how to separate commercial records from consumer data.
• Work an add-on produced for its own clients, such as outsourced deliverables, may belong to those clients.

This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

Next step

Ask the platform CFO for the entity list and build a first draft of the map this quarter. Once signers are confirmed, register as a partner and introduce the platform, or have its CEO apply directly at sourcex.si/apply.