What does a private equity firm data team do, and where do data assets fit?

What a private equity firm data team does

A PE firm's data team builds the analytics the firm uses to source deals, run diligence and monitor its portfolio, mostly from data the firm already collects or buys. Its internal customers are the deal team, the operating partners and investor relations. Few of these teams look at the other side of the ledger: which portfolio companies hold records that are valuable assets in their own right.

These teams are growing because operations now carry more of the return. McKinsey's Global Private Markets Report 2026 says multiple expansion and cheap leverage, which accounted for 59 percent of PE returns between 2010 and 2022, have faded, so operational value creation is now likely the primary source of returns. The same report says firms have more than doubled their operating groups since 2021 and that sponsors are applying AI to operating levers.

Typical roles include a head of data or data science, data engineers who maintain the firm's warehouse and connectors, and analysts embedded with the deal or operating teams. Some firms also run a center of excellence that portfolio companies can call on.

How firm data teams usually organize their work

Monitoring and comparison across companies are covered in KPI benchmarking across portfolio companies. This page concentrates on the last row.

Portfolio analytics vs data assets

The difference comes down to who benefits and who owns the result.

• Portfolio analytics uses data to help the firm decide: what to buy, where a company is drifting, which initiative to fund. The firm consumes the output.
• A data asset is a body of records a portfolio company owns that an outside licensee would pay to use: years of support tickets with resolutions, engineering histories, project files, sales conversations with outcomes. The company, not the firm, can license it.

A firm data team is well placed to spot data assets because it already knows each company's systems from diligence and the 100-day plan. It is badly placed to run licensing, for the reasons set out below.

The system census: adding the asset view without moving data

The asset view runs on metadata only: system lists, date ranges and rough record counts, never record content. Send a short census to each portfolio company's CIO or controller:

• Which systems does the company run (email, Slack or Teams, CRM, ERP, support desk, engineering tools, field apps), and since when?
• How many years of history does each system keep, and which retired systems still have archives or exports?
• Are the records connected, for example tickets linked to CRM accounts and email threads?
• Do the records capture outcomes, such as resolved or escalated, won or lost, approved or rejected?
• Is the company US-based, with 50+ full-time employees at peak (contractors excluded) and several years of documented operations?
• Are there obvious rights problems: client-owned data, mainly consumer personal data, protected health information, or data already licensed for AI training?
• Is there an owner, CEO, CFO or other authorized executive who would consider an exclusive AI training license for an agreed term?

The strongest candidates usually run 10-15 or more systems with long histories. The who qualifies page lists the full baseline. Upcoming migrations deserve a flag of their own, because an ERP or finance system replacement is the moment old records are most at risk; see finance transformation in PE portfolio companies.

Why licensing stays company-led, not run by the firm data team

1. Ownership. The portfolio company owns its records; the fund owns equity in the company. Only the company can license them, acting through an authorized executive and its own governance.
2. Rights and confidentiality. Customer contracts, employee notices and privacy commitments sit at the company level and have to be reviewed there. The company's counsel leads that work, and the general counsel's guide to reviewing a data license sets out what to check.
3. Risk. Pulling record content into the firm's warehouse would create confidentiality and privacy exposure for no benefit. SourceX works with the company directly, and the company settles its redaction and de-identification rules with SourceX before anything is prepared.
4. Each company is its own deal. Scope, price, terms and buyer review are handled company by company, and nothing binds a company until it signs.

The firm's role is to notice, introduce and support. The data team supplies the census, an operating partner makes the introduction, and the company does the rest with SourceX.

Which portfolio companies the asset view tends to surface

Back-office-heavy and engineering-led businesses tend to rise to the top: IT services, B2B software, professional services and the operating side of manufacturers and distributors. Some sectors need extra checks before anyone gets excited. Defense suppliers, for example, may hold technical data subject to export controls or customer restrictions, which needs specialist review first; see aerospace and defense suppliers in PE portfolios.

How the introduction works

1. The data team shares census results with the operating partner who covers the company.
2. The operating partner raises it with the portfolio CEO or CFO and confirms there is interest.
3. The company applies at sourcex.si/apply through the partner's referral link, or the partner submits it with the referral form.
4. SourceX qualifies the company on size, history, data breadth and rights.
5. The company's own team completes a data inventory; the firm data team stays out of record content.
6. The company agrees price and terms, buyers review the opportunity, the deal closes, records are delivered under the agreed redaction rules and the company is paid.

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, payable only after the buyer pays and SourceX receives its fee. It is funded from SourceX's share, so the company's proceeds are untouched. Check the LPA's fee provisions and the firm's policy before anyone at the firm accepts a reward linked to a portfolio company.

When the asset view finds nothing, and why that is still useful

Plenty of portfolios will produce a short list, or none at all. Consumer-facing businesses whose records are mostly personal data, healthcare companies whose records are mostly patient information, agencies and outsourcers whose files belong to their clients, and companies that never reached 50+ full-time employees at peak (contractors excluded) will usually drop out. So will any company whose archives were deleted or whose owner will not consider an exclusive license.

The census still earns its keep. It documents how long each company retains records, which systems are about to be retired and where exports are missing, which is information the CIO and the general counsel need anyway. A no today is not permanent either: a company that keeps full exports through its next system migration may look quite different a year later.

Next step

Add an asset column to the next portfolio review, with one line per company drawn from the census. For a structured approach, read how private equity teams can assess portfolio company data opportunities or try the network opportunity finder. When a company fits, register as a partner and put the company forward.