A platform company CEO's playbook for buy-and-build integration and combined records

What does a platform company CEO own in a buy-and-build?

The platform CEO owns the operating model every add-on folds into. The sponsor's deal team sources and prices acquisitions; the CEO makes them work, which means integration sequencing, leadership retention, systems consolidation and one decision that usually gets missed: what happens to the records each acquired company brings with it.

That last decision is the focus of most of this playbook, because only the platform can make it. Each add-on arrives with years of email, CRM history, job files, tickets and finance records. Many of those systems are migrated or switched off during integration. Whether the history is kept, who owns it and whether it could ever be licensed are choices the platform CEO, as the authorized sponsor, should put in front of the board before IT makes them by default.

A platform CEO's month already contains the right forums: a weekly integration stand-up, a monthly operating review with the sponsor's operating partner, a quarterly board meeting and a standing add-on pipeline call. The decision fits into those existing meetings.

Which integration priorities come first after each add-on closes?

Sequence by risk: people and customers first, then cash, then systems. Every one of those workstreams contains a records decision, and the table shows where it hides.

If your sponsor screens targets with a records note, as described in add-on acquisition criteria, most of the inputs for the right-hand column already sit in the diligence file.

Why the combined-records decision belongs to the platform

Nobody else is positioned to make it. The founders of the add-ons have sold, the sponsor's deal team is working the next target, and IT is measured on cutting duplicate licenses. Left alone, the default answer is to migrate the active data and delete the legacy tenant.

The decision has three parts.

• Ownership. Confirm which legal entity owns each archive after closing and after any entity merger. The US Copyright Office's circular on works made for hire explains that material an employee prepares within the scope of employment generally belongs to the employer, while work by contractors may not unless rights were assigned in a signed writing. Acquired companies that leaned on freelancers need their contractor agreements checked.
• Retention. Set what must be kept for legal, tax and contractual reasons, what is under legal hold, and what the business wants to keep beyond the minimum.
• Licensing. Decide whether the board would consider licensing the combined history to AI labs and data buyers, or rule it out. Check what each add-on promised its own customers: Federal Trade Commission staff wrote in January 2024 that privacy and confidentiality commitments, including promises not to use customer data for purposes such as model training, are enforceable whether made in privacy policies, terms of service or promotional materials. That is staff guidance, not a rule.

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

The platform records charter

Put the decision on one page that the board can approve and IT can follow. Tick each line for every add-on.

• Acquired legal entity named, with a note on whether it survives or merges
• System list with years of history, record owner and export method
• Customer contract clauses on confidentiality, data use and deletion at termination
• Employee notices and policies covering work communications
• Contractor agreements checked for written IP assignment
• Export-before-retire rule written into every cutover plan
• Legal holds and the retention schedule recorded
• One named owner for the records inventory
• Board position on licensing: explore now, revisit later, or never

Sector changes the picture. A dental or physician practice platform has to separate patient records from business-office records before any of this applies; the guide on non-PHI records in practice platforms explains why many such platforms will not fit.

When should the CEO put licensing on the board agenda?

Raise it when systems, budgets or the equity story are already under review, so it costs no extra board time.

When a sale process is live, let the deal team decide timing. A license carries an exclusivity term and a counterparty that the buyer's counsel will want to read.

How the assessment works with the CEO as sponsor

As CEO you are an authorized sponsor, so you can start the process yourself or have the operating partner introduce you.

1. Apply at sourcex.si/apply, or ask the operating partner to submit the platform through the referral form.
2. SourceX checks the business against its qualification baseline: 50+ full-time employees at peak (contractors excluded), several years of documented operations, records across many systems and the rights to license them.
3. Your inventory owner lists each acquired entity's systems separately, with years of history and export method, so rights can be checked entity by entity.
4. You agree one all-in price and the license terms. SourceX's fee is inside that price, with no separate charges.
5. AI labs and data buyers review the opportunity; once a company is deal-ready, buyers typically respond within about two weeks.
6. After signature, data is prepared under redaction rules agreed in advance and delivered with your authorization. Payment is one-time, typically within about 60 days of invoicing once the buyer selects the data.

The platform keeps ownership throughout. The data is licensed, not sold, and nothing binds the company until price and terms are agreed and signed.

What to tell the operating partner and the board

Frame it as a records decision with an option attached, not a revenue promise.

Operating partners who want the sponsor-side view can read the guide for private equity operating partners. Boards weighing whether to run licensing themselves can compare an in-house team with a licensing intermediary.

Where partner rewards fit for a platform CEO

When your platform applies, you are the company, not a partner. If an operating partner or adviser introduced the platform, their reward comes out of SourceX's fee and never reduces what the platform receives.

You may also know owners outside your group: founders whose businesses fell outside the add-on thesis, or peers from a CEO forum. You can register to introduce those companies. Partners earn 25% of the eligible platform fees SourceX actually collects from a referred company's licensing deals, capped at $100,000 per referred company, payable only after the buyer pays and SourceX receives its fee. No reward is guaranteed. Check your employment agreement and your sponsor's policies on outside compensation first.

When to leave the archives alone

Skip licensing, or park it, when:

• An add-on's records mostly belong to its clients, as at agencies and outsourcers, and those clients have not consented.
• The valuable records are patient charts, claims or consumer personal data.
• A legacy system was cancelled without an export.
• An acquired company already licensed the same data for AI training.
• Nobody on the team can own the inventory.

Preserving the exports is still worth doing in every case, because it keeps the decision open.

Next step

If you lead the platform, run the preliminary company fit checker, then apply at sourcex.si/apply. If you are an operating partner or adviser to the platform, or you want to introduce a company outside your group, register as a partner.