BPO and contact center platforms under PE: whose records are they?

Why most BPO data is not the BPO's to license

In private equity BPO acquisitions, the hardest truth comes first: most of what an outsourcer processes belongs to someone else. Call recordings, chat transcripts, tickets, case notes and back-office files describe the client's customers, and they sit under the client's master services agreement, data processing terms and security requirements. Data that belongs to an outsourcer's clients is a stated red flag for SourceX unless those clients consent.

That does not end the conversation. A contact center or back-office BPO also runs a large operation of its own: it recruits and trains agents, scores quality, forecasts and schedules staff, documents processes and runs improvement projects. Those records are created by the BPO's employees for the BPO's own operations, and they can show AI developers how service work is taught, measured and corrected at scale.

Own, client or consent: sorting a BPO's records

Call recordings, financial data and other consent questions

Recordings deserve their own warning because they look like the obvious asset. Federal law, at 18 U.S.C. 2511, generally allows a call to be recorded by a party to it or with one party's prior consent, but California's Penal Code section 632 requires the consent of all parties to record a confidential communication. Even a lawful recording made for quality and training says nothing about licensing it to a third party for AI training; that turns on the notices customers received, the client's contract and privacy law. Recordings stay in the client pile.

Financial services work adds another layer. The FTC's Gramm-Leach-Bliley Act guidance describes the notice and opt-out requirements financial institutions face before sharing customer information with nonaffiliated third parties, and BPOs serving lenders, card issuers or insurers handle that information under their clients' obligations. For BPOs with hospital or health plan clients, patient information is in play, and the healthcare services exit readiness guide sets out why only back-office records are worth discussing in that sector. Records created at offshore delivery centers may also fall under the laws of those countries.

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

Which BPO platforms fit

The SourceX baseline, read for an outsourcer: a US company that reached 50+ full-time employees at peak (contractors excluded), with several years of documented operations, clear rights to the records in scope, mostly English-language material, and an owner, CEO, CFO or authorized representative willing to consider an exclusive AI-training license for an agreed term. Headcount is rarely the obstacle in this sector; rights are. Everything else on the checklist is spelled out on the who qualifies page.

Stronger candidates:

• US-headquartered contact center and back-office BPOs with a central quality team, a training academy and a workforce management function that have kept records for years.
• Technical support outsourcers whose troubleshooting methods and internal knowledge base were written by their own staff.
• BPOs with a documented delivery method they sell to clients as their own intellectual property.

Weaker candidates:

• Healthcare revenue cycle outsourcers and collections agencies, whose working records are mainly patients' or debtors' information.
• Content moderation providers, whose material belongs to the platforms they serve.
• BPOs whose master services agreements bar any use of client-derived data, including aggregated or derived records.

Sometimes the better introduction is the client

A BPO's largest clients hold the interaction history the BPO cannot license. A US insurer, software company or distributor that meets the baseline owns its own customer service records, and it can decide with its counsel whether any of them could be licensed, with the BPO helping on export. That is the client's decision, made on the client's terms. A partner connected to a portfolio BPO should never approach its clients about this without the BPO's leadership agreeing first; the relationship belongs to the BPO.

Which moments open the conversation at a BPO

How the introduction runs

1. Ask the CEO or COO, in general terms, which records the BPO itself authored; never request a scorecard, recording or SOP.
2. Put the company through the company fit checker, which screens fit on a preliminary, non-binding basis.
3. Register as a partner, then send your referral link or use the referral form.
4. SourceX tests the BPO against its baseline, looking hardest at how much of the record base the BPO itself owns.
5. The company inventories its systems and marks each record set own, client or consent.
6. Price and terms are agreed before AI labs and data buyers review; delivery follows only a signed agreement and the company's authorization.

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, and the reward becomes payable only after the buyer pays and SourceX receives its fee. The BPO's own payment is never reduced by it, and no reward is guaranteed.

Talking points for the BPO's chief executive

Next step

Draw the own, client and consent piles with the COO before anyone mentions recordings. When the own pile turns out to hold years of material, register as a partner; the CEO can then apply at sourcex.si/apply using the link you send. The testing, inspection and certification brief covers a sector with a similar ownership split, and the operating partner guide shows portfolio-wide screening.