Data licensing referrals for corporate development and integration teams

Why corporate development teams spot licensing candidates early

Corporate development teams hold two lists most partners never see: the companies the business has acquired, and the companies it evaluated and declined. Both can contain years of operational records that AI labs and data buyers want to license, and corp dev usually learns which ones before anyone else does.

The daily work puts the team close to that evidence. Pipeline reviews, diligence calls, integration management office meetings, synergy tracking and transition services agreement exits all raise the same questions: which systems a company runs, how far back its records go, and what happens to them after integration. A data license adds one more: could those records earn a one-time license payment before they are archived or switched off?

This page covers which companies fit, who signs, and the employer-policy checks that come before any reward.

Which companies in a corp dev book could qualify?

Four kinds of company are worth a look. Each still has to meet the baseline on the who qualifies page: a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license its records and an authorized sponsor.

Records that show work being done and decided, such as tickets and their resolutions, proposals won and lost, and approvals and exceptions, matter more than raw volume. The guide to data synergies in M&A explains how licensing value differs from the operational synergies corp dev usually models.

Who signs as the authorized sponsor?

The signer is whoever has authority over the entity that owns the records, not the person who made the introduction.

A parent that owns the company outright can also apply directly at sourcex.si/apply; a referral is not required for an owned company to be considered.

The two-gate check before you introduce anyone

Run two gates in order: a policy gate for you, then a fit gate for the company. Stop at the first clear no.

Gate 1: policy

• Your code of conduct and conflict-of-interest policy allow you to accept compensation for introducing a company your employer owns, invests in or evaluated, or compliance has approved it in writing
• Nothing you would rely on came from a data room, a management presentation or other material covered by an NDA
• The business leader responsible for the subsidiary, for example a segment president or the parent CFO, knows about and supports the conversation
• Any NDA with a declined target allows you to contact its management about an unrelated matter

Gate 2: fit

• 50+ full-time employees at peak, contractors excluded
• Several years of documented operations, with records spread across many systems
• The company created the records, and its customer contracts and privacy notices allow licensing
• Someone can still export the data, including from archived systems

A preliminary version of the fit gate takes a few minutes in the company fit checker, with no contact details required. For a deeper look at completeness, borrow the questions in the data quality due diligence checklist.

Privacy terms deserve particular care after an acquisition. FTC staff warned in February 2024 that adopting more permissive data practices, such as using consumer data for AI training, through a quiet, retroactive change to terms of service or a privacy policy could be unfair or deceptive. A parent should not assume an acquired company's old customer terms permit a license, or that it can rewrite them to fit. This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

When to raise it in the deal calendar

The best moments are the ones where systems, owners or budgets are already being decided.

Integration consultants work through the same calendar from the delivery side; see the page for post-merger integration consultants.

How the introduction works

Your role ends at the introduction and basic fit information. You never export, upload or describe confidential records.

1. Register as a partner, then give the company's sponsor your referral link or submit the company through the referral form.
2. SourceX reviews headcount, operating history, data breadth and rights with the sponsor.
3. The company documents its systems, years of history and exportable records in a data inventory.
4. The company and SourceX settle one all-in price and the license terms before any buyer sees the opportunity.
5. AI labs and data buyers review the package, and responses typically arrive within about two weeks of the company being deal-ready.
6. The company signs, the redaction and de-identification rules agreed at the start are applied, the data is delivered, and the company is paid.

What to say

For a subsidiary president, tie it to the integration plan:

For the founder of a target you declined, keep it general and separate from the deal:

How rewards work for corp dev team members

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.

For an employee of an acquirer, the policy gate decides whether a personal reward is acceptable at all. Introducing a company your employer owns can create a conflict even when the company benefits, so disclose it, get written approval or decline the reward. The reward is a share of SourceX's fee and is never deducted from what the company receives. The program terms govern registration and payment.

When not to bother

Next step

Pick one acquired company whose systems are scheduled for retirement and run both gates. If it passes, register as a partner and make the introduction, or have the parent apply directly.