Can a private equity firm license portfolio company data to AI developers?

Who is the licensor when a sponsor wants to license portfolio data?#

The licensor is the portfolio company entity that created the records and keeps them in its own systems. Support conversations sit in the company's Zendesk or Intercom account, deal histories in its Salesforce or HubSpot instance, and job records in its ServiceTitan or ERP database, all under contracts the company signed.

A private equity fund owns shares, usually through a holding company, and that ownership gives it control and information rights. It does not make the fund the owner of the company's operating records, so the fund cannot grant rights to them on its own. What a fund can do is sponsor the effort: nominate companies, pay for the work and give the consents its investment documents require.

The five prerequisites for a portfolio company data license#

A portfolio company data license can proceed only when five prerequisites are met, and missing any one of them stops the deal however strong the records look. Operating partners can test all five on metadata before anyone exports a file.

Ownership and contract room are where most portfolio deals narrow. A company that grew by acquisition may hold one brand's records under a clean asset transfer and another's under a stock deal whose legacy customer terms still apply.

• 1Ownership: the company created the records in its own systems, or acquired them with clear transfer language in the purchase agreement.
• 2Contract room: customer agreements, vendor terms of service and confidentiality obligations do not prohibit the intended use, or the restricted records can be carved out.
• 3Privacy preparation: personal and confidential details can be removed or masked, and the company's privacy notices and employee policies are consistent with the intended use.
• 4An authorized signer: an officer or board with authority to bind the operating company approves the license and its permitted use.
• 5Consents: any sponsor consent rights, credit agreement covenants that may reach licenses of company assets, and minority or co-investor approvals are identified and cleared.

What the sponsor does and what the company decides#

The sponsor's job is coordination and consent, while the operating company decides what leaves its systems. Keeping that split clear protects the board's authority, keeps the decision with the directors who owe duties to the company and makes the license easier for a future acquirer to review.

When the sponsor drives too hard, management can read the project as a fund initiative rather than a company decision. Operating partners who frame licensing as an option the CEO controls tend to get faster, more candid answers about what the records actually contain.

Which portfolio records are worth the effort?#

Portfolio records worth licensing show real work with an outcome: support tickets linked to the bug fix that resolved them, CRM opportunities with stage changes and loss reasons, dispatch records tied to callbacks, or quality nonconformances tied to corrective actions. AI developers use records like these to train and test systems on how businesses actually make decisions.

Records that rarely justify the effort include client-owned deliverables, customer source code, candidate files at staffing firms and anything centered on health or consumer financial details. A screen that removes those early keeps the rights review short and focused.

History matters as much as type. Ask each company how many years of records it can still export from its current systems, and whether a past migration left older history in a retired platform. An archive that survives only as invoice PDFs has little of the reasoning or outcome detail that makes operational records useful.

Illustrative: a lower-middle-market fund tests the idea#

Illustrative: a fictional lower-middle-market fund owns a vertical software company serving property managers, a commercial roofing contractor and a specialty distributor. A deal partner asks whether the fund could license portfolio data to an AI developer as one package.

Fund counsel answers that the fund holds no records, so each company would license separately. The software company has years of Jira issues, GitHub pull requests and Zendesk tickets linked by issue keys, and its board approves a metadata fit check. The credit agreement requires lender consent for licenses outside the ordinary course, so the CFO raises it with the agent bank before scoping begins.

The roofing contractor is parked because its job photos and notes center on homeowner addresses. The distributor is deferred until its ERP migration finishes. The fund ends up supporting one licensor rather than marketing a portfolio bundle.

Mistakes sponsors make when they raise the idea#

The most damaging mistake is presenting the license as fund revenue. That framing misstates who has authority to sign, invites questions from minority holders and management equity holders about who benefits, and puts the sponsor in the middle of a contract it is not party to.

Other mistakes are practical. Deal teams sometimes ask a portfolio IT lead for a sample export before any rights review, which moves records outside the company with no permitted-use terms. Others promise a group-level figure before scoping, or forget that records shared with the sponsor under information rights came with confidentiality limits on their use.

How SourceX works with sponsors and portfolio companies#

SourceX treats each operating company as its own supplier and runs the SourceX five-step transaction for it: Supply, Rights, Preparation, Approval and Delivery. The sponsor can open the door and clear its consents, but the company's authorized signer approves every step, and nothing is shared during the initial assessment.

For each package that proceeds, the SourceX Evidence Packet records provenance, licensing rights, permitted use, the privacy record and release authorization, including who signed and which consents were obtained. That is the record a lender, a board or a later acquirer will ask to see.