Guide · 6 min read
How AI data licensing deals work, step by step
A potential deal moves through scope review, an offer, a license, preparation, acceptance and payment. The order and timing depend on the buyer and the records. Agree on responsibilities and acceptance deadlines before estimating when money might arrive.
What are the steps to license company data to AI labs?
| Stage | What happens | Decision to record |
|---|---|---|
| Scoping | Buyer reviews systems, size and history | Which records and rights are being evaluated? |
| Offer | Buyer proposes price and terms | What conditions attach to this price? |
| Agreement | License, consent and data terms signed | Who may sign, and which approvals are needed? |
| Extraction | Data exported through a secure, approved route | Which method and access permissions are authorized? |
| De-identification and approval | Buyer cleans and accepts the data | What is the acceptance deadline and rejection process? |
| Payment | Payment follows the trigger specified in the agreement | Which milestone starts the payment clock? |
Is it a license or a sale?
A license grants specified use rights; an asset sale can transfer ownership. Read the agreement rather than relying on the marketing label. Define exclusivity by records, purpose, geography and duration, and check whether any retained licensing rights remain usable.
What is in a data licensing agreement?
- Scope: systems, date ranges and explicit exclusions
- Permitted use and any restrictions on resale or relicensing
- Exclusivity and term
- De-identification standard and who performs it, and where
- Approval criteria and window, then payment timing
- Security commitments, incident notice and deletion of raw data
Who de-identifies the data?
Usually the buyer. Scale AI says it removes identities inside the seller’s environment; micro1 says it removes or transforms PII itself; Mercor says it de-identifies automatically with seller approval; Polyshares strips identifiers before transfer. Ask to review a sample either way.
Worked example: a deal from first call to payment (fictional)
Week 1 to 3: Cobalt Structural, a fictional 70-person engineering firm, shares system counts and history dates; the buyer scopes email and project management. Week 4: offer received, non-exclusive. Week 6 to 9: license and consent signed, client domains excluded in writing.
Week 10 to 13: export through an approved route and de-identification; Cobalt reviews a sample. Week 14 to 17: buyer approves the data and pays within its stated window. About four months end to end.
When not to do it
- Do not start extraction before the license defines exclusions and approval criteria in writing.
- Do not agree to open-ended approval windows; payment should follow a dated acceptance step.
Sources
Content revised November 1, 2026. Buyer profiles show program review dates; historical reporting is identified separately.
Figures are each buyer’s published range or reported values, labelled as such, and are not offers. This is general information, not legal advice. QuoteMyData may be paid by buyers when a deal closes; see our disclosure.
