Should you underwrite data licensing upside in an acquisition model?

The short answer: keep it out of the price

Do not pay for data licensing upside, and do not put it in the base case. A license of historical operational records is a one-time payment for an agreed dataset, typically exclusive for AI training for an agreed term, and it becomes payable only after a buyer selects the data and pays. None of that can be tested before you own the company.

Treat it the way you would treat an unconfirmed add-on target: worth a line in the thesis, worth a diligence question, worth nothing in the returns bridge. If the opportunity turns out to be real, it becomes upside you did not pay for. The broader AI value creation playbook covers the AI levers that can carry a number.

Why licensing upside fails the underwriting test

Four facts make it unsuitable for a base case or a management case.

• No payment is assured. Nothing is binding until the company agrees price and terms and signs, and money arrives only after a buyer selects the data. Buyers can pass.
• Rights are unknown before close. Whether the company created the records, and whether client contracts, employee notices and privacy promises allow licensing, takes a document review most sellers will not allow before signing.
• Archives may be gone. Retention policies, cancelled SaaS tools and past migrations can delete the years of history that make records valuable. You often learn this only after close.
• There are no usable comps. Public disclosures describe very different assets. Reddit's February 2024 IPO registration statement disclosed data licensing arrangements with an aggregate contract value of $203.0 million over terms of two to three years. That is a multi-year total for a large consumer platform, not annual revenue, and it says nothing about what a 200-person logistics company's records are worth.

Where licensing can sit in the model instead

Give it a home in the deal materials without giving it a number.

There is a second reason to keep it out of EBITDA. A license payment is non-recurring, and a future buyer's quality of earnings work is likely to separate it from run-rate earnings. How a license is recognized can also depend on its structure: guidance on licenses of intellectual property under ASC 606 distinguishes a right to use from a right to access, so ask the company's auditors before anyone forecasts timing. This is general information, not legal, tax or financial advice.

The three-gate rule before it earns a number

Licensing upside earns a number in any plan only when all three gates are cleared, and even then it belongs in a scenario, not the base case.

• Rights: the company created the records, and a review of client contracts, employee notices and privacy policies shows they can be licensed. The data rights documentation guide shows what that file looks like.
• Records: archives going back several years still exist across the company's systems, and someone can export them.
• Buyer interest: the company has completed a data inventory, agreed price and terms, and buyers have reviewed it. Once a company is deal-ready, buyers typically respond within about two weeks.

The first two gates can often be answered in the first months of ownership. The third exists only after the company has done the work, so any number before that point is a guess. Companies that fail the first or second gate are described in which portfolio companies are not a fit.

What to tell the investment committee

When a deal team member or the seller's banker raises a data asset, answer with one paragraph that shows you saw it and declined to pay for it.

If the CIM presents a data asset as a reason for a higher multiple, ask for evidence behind the rights and records gates. A seller who cannot show either is describing an idea, not an asset.

When the concern cuts the other way

Sometimes the worry is not overpaying but missing something: a partner fears that ignoring the data leaves value on the table. That concern is valid, and the fix is process, not price.

1. Add two rights questions and one retention question to confirmatory diligence.
2. In the 100-day plan, stop any archive deletion or old-system cancellation without a full export.
3. Put a licensing review in the value creation plan with an owner, usually the CFO, and a decision date.
4. Check the company against the who qualifies baseline: 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license the data and an authorized sponsor.
5. If it passes, introduce the company to SourceX and take any license proposal to the board; see board approval for a data license.

The operating partner's job is the introduction. The company works with SourceX on the inventory, rights review, pricing and delivery, and keeps ownership of its data throughout.

How the reward fits if your firm makes the introduction

If someone at your firm registers as a partner and introduces the company, 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. It is paid only after the buyer pays and SourceX receives its fee, no reward is guaranteed, and it is never deducted from what the company receives. Do not model it either. Check your firm's policies and fund documents on fees connected to portfolio companies first, including any management fee offset provision in the LPA. The operating partner hub covers the role in more detail.

Next step

Before your next IC memo, add the three gates to the diligence workplan and leave the model at zero. To see which current holdings might already pass, map them with the network opportunity finder, then register as a partner to make introductions once a company clears the gates.