Acquiring a company that already licenses its data: what to check

Why an existing data license changes the diligence plan#

An existing data license changes the diligence plan because it is both an asset and a set of continuing obligations. The target may have income from it, a buyer relationship and a working preparation process. It may also have granted rights that limit what a new owner can do with the same records.

Data licenses are newer than most commercial contracts in a data room, so they are often drafted from scratch or from the buyer's template. That makes them less predictable than a standard customer agreement. Read each one in full rather than relying on the CIM summary, and bring counsel in early; the points below are general information, and every agreement and deal differs.

The buy-side checklist#

The buy-side checklist covers seven items, each tied to specific clauses. Work through it for every license, data sharing agreement and AI-related data arrangement the target has signed, including ones described as pilots or evaluations.

Scope and exclusivity: what has already been given away#

Scope and exclusivity clauses show what the target has already given away. A well-drafted license names the record families, systems, date ranges and legal entity, so it is clear what was delivered and what remains free to license. A loose one describes data in general terms that a licensee could later read broadly.

Pay particular attention to affiliate definitions. If the target agreed that it and its affiliates will not license similar records to others, the acquirer's other portfolio companies could arguably become affiliates at closing. Whether that reading holds depends on the drafting, so flag any affiliate language for counsel and, where it matters, seek an amendment before signing.

How to read license revenue in a quality of earnings review#

License revenue should be read through its contract terms, not through where it sits in the income statement. A single fee for a delivered package behaves differently from a multi-year agreement with scheduled refreshes, and a milestone payment that depends on buyer acceptance carries more risk than one already earned.

How the revenue is recognized depends on those terms and is a question for the target's accountants and the buyer's quality of earnings provider, typically under ASC 606. For valuation, separate contracted renewals from one-time deliveries, and do not assume a repeat license unless a renewal is written into the agreement.

• 1One-time delivery fees: treat as non-recurring unless a refresh schedule is contracted.
• 2Contracted refreshes: recurring only for the committed term.
• 3Milestone payments: check the acceptance criteria and who decides acceptance.
• 4Refund or credit clauses: check the triggers, such as disputes over data quality or completeness.

Deletion duties, audit rights and what survives termination#

Deletion and survival clauses decide what continues after a license ends. Some licenses require the buyer to delete the records and certify deletion; others allow models already trained on the records to stay in use. Neither is wrong, but the acquirer should know which applies before describing the asset to its lenders or to a future buyer.

Check whether the target has ever exercised an audit right or received a deletion certificate. An untested right still has value, but a documented certificate is stronger evidence in the next diligence process, and it shows the target actually tracks its obligations.

Change of control and assignment#

Change-of-control and assignment clauses determine whether a license survives the deal unchanged. Some agreements require the licensee's consent before assignment, some let either party terminate if the other is acquired by a competitor, and some are silent. In a stock purchase the license usually stays with the target, but change-of-control language can still apply.

Ask the target which licensees must be notified, which must consent and whether any licensee gains a right to renegotiate. Put those steps on the closing checklist with an owner for each, so they do not surface after signing.

• 1List every data license, data sharing agreement and evaluation agreement with its counterparty and term.
• 2Mark each one as consent required, notice required or silent on change of control.
• 3Note any termination or renegotiation right triggered by the sale itself or by the acquirer's identity.
• 4Assign an owner and a sequence for each notice or consent request, and keep copies of responses in the closing set.

Illustrative: a fleet maintenance software target with one license#

Illustrative: a fictional fleet maintenance software company licensed a prepared package of support tickets, engineering issues and release notes to an AI developer. The sponsor's deal team finds the grant clearly limited to those records and dates, with a field-of-use limit that excludes fleet management products.

Two issues surface. The exclusivity clause bars the target and its affiliates from licensing support records to other developers during the term, which would reach a sister company in the sponsor's portfolio. And the license fee was a single payment that the CIM presented next to subscription revenue.

The sponsor asks the target to obtain an amendment narrowing the affiliate definition before closing, and models the fee as non-recurring. Because the target kept a delivery record and an approval memo, confirming what left the company takes a document review rather than a forensic exercise.

How SourceX documents licenses for diligence#

SourceX records each licensed package in a SourceX Evidence Packet: provenance, licensing rights, permitted use, the privacy record and release authorization. For an acquirer, that packet answers the scope, use and approval questions above without reconstructing them from email threads.

Public provenance vocabularies point the same way. The Data & Trust Alliance's Data Provenance Standards group dataset metadata into Source, Provenance and Use, and the Use group includes elements such as license to use, intended data use and consent documentation location. A target that documents its licenses in comparable terms is far easier to diligence.