Diligence questions buyers ask about your existing data licenses

Why buyers look hard at data licenses signed during the hold#

Buyers look hard at data licenses because a license is a promise that outlives the seller's ownership. Deal counsel asks what the acquirer inherits, the quality of earnings team asks whether the revenue repeats, and the buyer's technology team asks which records left the company and under what controls.

For a CFO, the practical consequence is that the same contract gets read three times by three groups with different worries. A folder organized around their questions saves rounds of follow-up and keeps the license from becoming a late surprise in the purchase agreement.

The 15 questions, mapped to the documents that answer them#

The 15 questions below cover what most acquirers ask about an existing data license, grouped by topic. The right-hand column names the document that should answer each one; most sit in the license itself or in the record of how the records were prepared and released.

Scope and exclusivity: where follow-ups start#

Scope questions usually come first because a vague scope makes every other answer uncertain. A license granting rights to company data in general is far harder to diligence than one that lists support tickets from a named help desk between two dates, with customer identifiers removed.

Permitted use is the second scope test. Buyers check whether the license allows training, evaluation or both, whether the licensee may share records with its own contractors, and whether resale or onward licensing is prohibited. Clear, narrow language here answers several later questions at once.

Exclusivity is the term most likely to affect the buyer's plans. A strategic acquirer with its own AI ambitions will want to know whether an earlier licensee holds exclusive rights to the same records, even in a narrow field. Non-exclusive, time-limited grants are the easiest to explain and the least likely to need a special provision.

Assignment, change of control and survival#

Assignment terms decide whether the license follows the company in a sale and whether the licensee can walk away. In a stock sale the contract generally stays with the company, but a change-of-control clause can still give the licensee a consent or termination right; in an asset sale the license may need to be assigned, which can require the licensee's consent.

Survival terms matter just as much. Buyers ask whether the licensee may keep models trained on delivered records after the term ends and whether delivered copies must be deleted. Ambiguity here tends to end up in a disclosure schedule or a specific indemnity, so settle it in the contract rather than in the purchase agreement.

Revenue questions from the quality of earnings team#

Revenue questions focus on whether license fees should count as recurring earnings. A single upfront fee for a fixed set of records is often treated as non-recurring, while renewals or ongoing deliveries may be viewed differently, and the treatment always depends on the actual terms.

Expect the team to ask how the fee was recognized and whether any part depends on future deliveries, acceptance or milestones. Revenue recognition for a license can turn on whether the company delivered records once or keeps delivering under the contract, so confirm the treatment with your accountants before the process rather than defending it during one.

How to build the data license folder before the process#

A data license folder gathers every document an acquirer will request in one place, organized to match the questions above. Building it before the sale process starts lets the CFO close gaps, such as a missing deletion confirmation, while there is still time and goodwill with the licensee.

• 1The signed license, every amendment and any side letter or email that changed terms.
• 2A one-page summary: licensee, record families, date ranges, permitted use, exclusivity, term and fees.
• 3The delivery record: what was sent, when, how and to whom.
• 4The privacy preparation record and the release authorization.
• 5Deletion certificates or the licensee's written confirmation where a term has ended.
• 6Invoices, receipts and the revenue recognition memo.
• 7Rights review notes showing which customers or records were excluded and why.

Illustrative: a pump manufacturer CFO prepares for a sale#

Illustrative: a fictional PE-backed manufacturer of industrial pumps licensed several years of field service reports, warranty claims and quality nonconformance records from its ERP and QMS to an AI developer during the hold, with customer-owned designs excluded. The sponsor plans a sale, and the CFO builds the data license folder ahead of the banker's request list.

Assembling the folder surfaces two gaps. The board deck described the license as exclusive, while the signed contract granted exclusivity only for one narrow evaluation use, and the licensee never confirmed deletion of an early test delivery. The CFO corrects the summary and obtains the written confirmation.

When the buyer's counsel sends questions, each one maps to a document already in the folder. The quality of earnings team classifies the fee as non-recurring, which the sponsor had already reflected in its own adjusted figures.

How SourceX documents licenses for later diligence#

SourceX builds the diligence record as the license happens rather than afterward. Each package that moves through the SourceX five-step transaction produces a SourceX Evidence Packet with provenance, licensing rights, permitted use, the privacy record and release authorization.

Those five records answer most of the scope, privacy and approval questions in the table directly. The signed license, payment records and any deletion confirmations complete the folder.