How should a PE platform screen insurance agencies for data licensing?

When should a PE platform screen an acquired insurance agency?

Screen each agency before it is converted onto the platform's agency management system (AMS), because conversion is the moment legacy records get archived, trimmed or switched off. A platform that buys agencies continuously can run the same screen at every closing and keep a clear record of which agencies hold licensable history and which do not.

The sector overview in buy-and-build sectors places agencies next to other roll-up targets. This page is the agency-specific playbook for operating partners and integration leads.

What does the agency conversion timeline look like?

The table anchors actions to the typical order of a brokerage integration. The windows follow the usual order of a brokerage integration and are a planning aid, not a program rule.

If the legacy AMS license ends within weeks of cutover, treat records preservation as the first task. A lapsed subscription is how archives disappear.

What is the carrier-and-NPI screen?

Agencies need more rights scrutiny than most sectors. Run these five checks in order, and stop at the first hard no.

• Headcount: 50+ full-time employees at peak (contractors excluded). Many single-office agencies fall short; larger regional brokerages may qualify.
• Own work product: are the candidate records the agency's internal workflows (service tickets, renewal task chains, internal chat and email on process), rather than a carrier's data?
• Carrier agreements: do appointment or agency agreements restrict how carrier-provided material may be used or shared? Read them; do not assume.
• Nonpublic personal information: policyholder data is likely subject to financial-privacy duties. The FTC's Gramm-Leach-Bliley Act guidance is a starting point, and insurers and agencies are also regulated by state insurance departments. Whether and how records are de-identified is agreed with the company before any work begins.
• Prior licensing: no earlier AI-training license over the same records.

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

Which records make an agency valuable?

Think workflows with outcomes, not policy files.

The policyholder-specific parts are the sensitive core and are exactly what redaction rules address.

How does the introduction work?

1. The integration lead or operating partner speaks to the agency principal or CEO.
2. The agency is submitted through the referral form, or the principal applies using your referral link.
3. SourceX qualifies size, history, breadth and rights.
4. The agency completes a data inventory of systems and years.
5. Price and terms are agreed with the agency before buyers see detail; nothing binds until it signs.
6. After delivery and payment, the partner reward is calculated.

You never export or describe policyholder records.

What do you say to the principal?

The introduction email templates for operating partners have a longer version, and the company fit checker gives a preliminary screen without contact details. For agencies in an active sale, read selling an insurance agency.

Who owns the screen inside the platform?

Assign it to one named person, usually the integration lead or the operating partner covering the platform, and log each agency in a simple tracker with four columns: headcount at peak, AMS and years of history, export status and next action. A repeatable owner keeps the screen from lapsing between closings, and the log shows which agencies are worth revisiting after a later migration.

How are partner rewards handled?

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. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It is a share of SourceX's fee and is never deducted from what the agency receives. Check your fund's policy on fees tied to portfolio companies first, and see program terms.

When to skip an agency

• Policyholder data with no workable de-identification path.
• Carrier terms that bar use of the material.
• Archives already purged at conversion.
• Fewer producers and staff than the baseline.
• A principal who will not consider an exclusive license for a term.

For finance-side support with records, see fractional CFO guidance for contractors; the same preservation habits apply.

Illustrative: a regional agency at cutover

Illustrative and fictional: a platform closes on a regional brokerage with 90 staff and fifteen years in its legacy AMS. The integration plan loads active policies into the platform system and sets the old vendor license to end sixty days after cutover. The operating partner asks one question at the kickoff: is the full activity-note and correspondence history exported, and who holds it? The answer is no. The team adds an export to the cutover checklist, names an owner and stores the file under access control. Only then does the operating partner raise a fit screen with the agency principal. The export, not the pitch, is what preserved the option.

What goes on the integration checklist

• Name the person who owns the legacy export and the date it is verified.
• Record the vendor retention terms in writing.
• Hold any scheduled mailbox or chat purge until the screen is complete.
• Note any producer who keeps a separate book or personal records, since the agency must own what it licenses.

Next step

Add one question to your integration checklist, "is the legacy archive preserved?", then register as a partner and introduce the first agency that clears the screen. The agency can also apply at sourcex.si/apply; see who qualifies for the baseline.