Private equity and portfolios
Pooling several portfolio companies' records into one license: pros and risks
By SourceX Editorial · Updated
Short answer
Pooling several portfolio companies' records into one license works when delivery is bundled but each company stays a separate supplier with its own rights review, privacy preparation and signed release. The gains are one buyer process and broader workflow coverage; the risks are mixed rights, shared liability and harder exits. Tag every record with its source company.
Key takeaways
- A pooled license bundles delivery; it does not merge ownership, rights or approval across companies.
- Each portfolio company runs its own rights review and signs its own release authorization, even inside a master agreement.
- A source-company tag on every record lets one restriction or one exit remove a slice instead of forcing a rebuild.
- Pricing, wage or capacity records from portfolio companies that compete need antitrust review before anything is combined.
- Agree how payment is split between companies in writing before delivery, not after the buyer pays.
Can several portfolio companies license their records under one deal?#
Several portfolio companies can license their records under one deal, but the deal works best as a bundled delivery from separate suppliers rather than one merged dataset owned by the group. Each operating company holds its own records, contracts and obligations, so each one stays the licensor of its own slice.
The sponsor's role is coordination. An operating partner can line up the companies, agree a common scope and present one supply to a buyer. Nothing changes hands permanently: each company licenses its slice rather than selling it, and keeps ownership of what it contributes.
Buyers can find a pooled supply attractive because it covers more of one workflow, such as quotes, production, quality holds and warranty returns seen across several manufacturers. That coverage only helps when every slice is documented to the same standard.
Three ways to structure a pooled license#
A pooled license usually takes one of three structures, and the choice decides who signs, who carries liability and how easily one company can leave later. Counsel for each participating company should review the structure before a term sheet is discussed.
| Structure | How it works | Who signs | Fits when |
|---|---|---|---|
| Coordinated separate licenses | Each company signs its own license with the same buyer on aligned terms | Each company's authorized signer | Companies differ in rights, systems or ownership |
| Master agreement with company schedules | One framework agreement; each company joins through a schedule listing its records and permitted use | The buyer, plus each company for its own schedule | Companies share a record type and want one negotiation |
| Single group licensing entity | Companies license records to a group entity, which licenses the combined set onward | The group entity, after intercompany licenses are in place | Ownership is uniform and tax and liability effects have been reviewed |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Pros and risks of pooling records across companies#
The pros and risks of pooling records across companies come down to one trade: a broader, more useful supply in exchange for more coordination and more ways for one company's problem to spread to the others.
Liability is the risk operating partners most often underestimate. Ask counsel whether each company can warrant only its own records and answer only for its own breaches, rather than sharing joint obligations or cross-default terms with sister companies.
| Factor | Pro | Risk |
|---|---|---|
| Coverage | The same workflow appears in several settings | Inconsistent fields make the combined set harder to use |
| Buyer process | One diligence process and one delivery plan | One company's delay holds up every slice |
| Rights | One rights checklist and privacy approach reused across slices | A restriction in one company's contracts can taint an untagged slice |
| Liability | Shared templates and controls | Joint terms make every company answer for one breach |
| Exclusivity | A broader exclusive grant may interest a buyer | Exclusivity binds every participant, including companies later sold |
| Exit | Documented slices are simple to describe in diligence | An acquirer may inherit obligations it cannot separate |
| Competition | Combined records cover a wider market | Current prices, wages or capacity from competing companies raise antitrust questions |
The rule that does not change: each company approves its own slice#
Each portfolio company keeps its own rights review and its own approval even when delivery is bundled, because rights and obligations sit with the entity that holds the records. A group signature cannot clear a customer contract the group never signed.
Buyers increasingly expect documentation at this level. The Data & Trust Alliance's Data Provenance Standards, for example, include elements for license to use, intended data use, consent documentation location and confidentiality classification, which only make sense when recorded per source.
- Rights review: that company's customer contracts, vendor terms, employee notices and obligations inherited from its own past acquisitions.
- Privacy preparation: removal of personal and confidential details suited to that company's record types, checked on its own sample.
- Consents: its own board, minority holders and lenders, which may differ from a sister company's.
- Release authorization: a named signer at that company approves the exact records and permitted use.
- Evidence: its own provenance, rights and privacy record, kept apart from the other slices.
Where pooled licenses go wrong#
Pooled licenses usually go wrong at the seams between companies rather than inside any one archive. The same few patterns come up across groups.
Untagged records come first. Once rows from several companies are merged into one file, pulling out one company's slice after a customer objection or a sale becomes a rebuild. Keep a source-company field on every record and every file in the delivery manifest.
Payment allocation comes next. Groups that leave the split until money arrives end up arguing over whose records mattered most. Agree the method in writing before delivery, by schedule or by a documented formula each company's board has seen.
Competitors and exits close the list. Portfolio companies that compete should not pool current pricing, wage or capacity detail without antitrust review, and every pooled license needs a clause on what happens when one participant leaves the group.
Illustrative: three machine shops weighing one license#
Illustrative: a fictional lower-middle-market fund owns Ironvale Precision Group, a buy-and-build platform of three contract manufacturers. Two shops run Epicor with a separate QMS holding nonconformance reports, CAPAs and supplier corrective actions. The third runs an older Infor instance where most job travelers reference customer-owned drawings.
The operating partner proposes one license for quality records, and each shop runs its own rights review. The two Epicor shops clear their NCR and CAPA histories once customer names, part numbers tied to customer designs and inspector names are removed. The third shop is held back because its useful detail cannot be separated from customer-owned designs.
The group signs a master agreement with one schedule per participating shop, and every delivered record carries a source-company tag. When one shop is later sold, its schedule ends under the exit clause, and the other shop's slice continues without being rebuilt.
How SourceX approaches a pooled supply#
SourceX treats a pooled supply as several transactions delivered together. Each company moves through the SourceX five-step transaction, Supply, Rights, Preparation, Approval and Delivery, on its own, and bundling happens only at Delivery, after every slice has been approved by its own signer.
Because the SourceX Evidence Packet is kept slice by slice, a company that later leaves the license takes its own documentation with it, from provenance and licensing rights to permitted use, the privacy record and release authorization, and the remaining slices stay fully documented. When a group weighs whether pooling is worth the coordination, the SourceX Enterprise Data Value Framework frames the trade: scale and domain expertise can increase value, while added preparation cost and privacy burden reduce net value.
Frequently asked questions
Does pooling records make each company's share worth more?
Not automatically. A buyer weighs uniqueness, linkage, recency and cleanliness, so adding a weak slice can dilute a strong one. Pooling helps when companies cover different parts or settings of the same workflow and every slice meets the same documentation standard. Nobody can promise an uplift in advance; what a pooled supply is worth becomes clear only when a buyer reviews it.
Can a company the fund only partly owns join a pooled license?
Often, but its other owners may need to consent, and its shareholder agreement may limit IP licenses or require minority approval. Treat a partly owned company as a separate governance decision, and keep its slice easy to remove if consent is withdrawn or never given.
Should portfolio companies see each other's records in a pooled deal?
As a rule, no. Each company's slice should reach the buyer without passing through sister companies, and any shared preparation should run under access controls. Separation matters most where companies compete or serve the same customers, and it keeps each company's confidentiality duties to its own customers intact.
Who speaks to the buyer in a pooled deal?
Usually one coordinator speaks for the group on scope and logistics, while each company's signer approves its own slice. Put in writing that the coordinator cannot bind any company to terms its signer has not approved, so the buyer knows whose signature governs which records.
Can the group add another company to the license later?
Yes, if the master agreement or the separate licenses allow new schedules. The new company completes its own rights review, preparation and approval before joining, and the buyer's acceptance criteria should apply to its slice on the same terms as the original participants.
Sources
- The Use group of the Data & Trust Alliance Data Provenance Standards includes elements for confidentiality classification, consent documentation location, privacy-enhancing technologies applied, allowed and excluded processing and storage geographies, license to use, intended data use, and copyright, patent and trademark status. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.