Guide
How to license your business data to AI labs: a plain-English guide

Key takeaways
- Licensing business data means giving an AI lab limited, written permission to use selected records, such as for training and testing AI systems. You keep ownership.
- Buyers want real work from start to finish: the emails, chat threads, documents, tickets and system records that show how a request became a result.
- Value depends on team size, years of history, how varied and connected your records are, what you have the right to license and how many buyers want it.
- Rights and privacy come first: confirm you're allowed to license the records, exclude high-risk material entirely and de-identify the rest.
- Treat any offer like a significant contract. Compare buyers, negotiate permitted uses, retention and payment, and involve counsel before you sign.
Licensing your business data to an AI lab means giving the lab written permission to use selected records, under terms you approve, in exchange for payment. You don’t sell your company or hand over your systems, and you keep ownership of your records. This guide explains who buys, what qualifies, how the process works and how to protect the people in your records.
It’s written for owners and executives of established businesses: companies with real teams and years of saved email, files and system records. If that’s you, the short version is simple. Your records may be worth real money, and the way you license them matters as much as the price.
What does it mean to license business data to an AI lab?
A data license is a contract that lets a buyer use specific records for specific purposes. It doesn’t transfer ownership. A well-drawn license spells out:
- Which records are included: systems, date ranges, folders and file types.
- What the buyer may do with them, such as train AI models, test (evaluate) them, or build simulated work environments.
- How long the buyer may keep the raw records, and what happens to them afterward.
- Whether the license is exclusive, and for how long.
- What you’re paid, and when.
Everything not granted stays with you. That’s the core difference between licensing and selling, and it’s why the contract deserves as much attention as the headline number. Our guide to AI data license agreement terms walks through each clause.
Why are AI labs paying for business records now?
AI companies have largely trained on what’s public. As Business Insider put it in August 2026, they’ve “run the well dry” on internet text and now want AI to get hands-on job experience in simulated workplaces. Those training grounds need real data and real workflows.
The gap is easy to measure. On the Remote Labor Index, a benchmark built from real, paid freelance projects, the best AI agent completed 15.8% of projects to a client’s standard as of July 2026, up from 2.5% when the benchmark launched, according to the Center for AI Safety. Progress is fast, and most real work is still out of reach. Examples of that work are what buyers want.
The money is real, too. In August 2026, Google paid $10 million for Spirit Airlines’ internal data and custom software in a bankruptcy auction, outbidding an AI training company, Business Insider reported. Earlier in the year, Forbes described shuttered startups selling their Slack archives, Jira tickets and email threads as training data. Operating companies are now getting the same calls, according to lawyers at Frankfurt Kurnit Klein & Selz.
Who buys business data for AI?
Buyers fall into three broad groups:
- AI labs. The companies building frontier models. Some buy directly, as Google did in the Spirit auction.
- AI training-data companies. Intermediaries that license operational data and package it for labs. One told Business Insider that companies “are sitting on decades of records that show how real work gets done.”
- Builders of simulated work environments. Startups that turn real company records into practice environments where AI agents learn to handle realistic tasks, as Forbes reported.
These buyers want different things. Some want raw records they will de-identify themselves; others want records already prepared. Some want training rights; others only need data to test their systems. Those differences show up in price and terms, which is why it pays to talk to more than one.
What kinds of business records qualify?
Buyers want the record of skilled work, not public content. The most common sources are:
- Email and team chat, where work is requested, debated and decided.
- Documents and files: proposals, contracts, procedures, reports and workpapers.
- Projects, tickets and tasks that capture work from brief to result.
- Accounting and operating systems: invoices, ledgers, orders, schedules and inventory.
- CRM and sales records: pipelines, quotes, pricing and renewals.
- Calls and meetings: recordings and transcripts.
- Code and technical work: repositories, reviews and incident notes.
The most valuable records connect. A request in email, the discussion in chat, the change in a system and the finished deliverable tell a story no single source can. One buyer of startup data told Forbes that a ticket tied to a specific code commit is worth more than a standalone document.
As a rule of thumb, businesses with more than 20 employees and several years of saved digital records are the strongest candidates. See what qualifies for a fuller checklist, or browse examples by industry, from accounting firms to logistics companies and IT service providers.
What usually doesn’t qualify: content that’s already public, records you don’t have the right to license, very short histories, and regulated data that can’t be cleared for this use.
What drives the value of business records?
No two licenses are priced the same way. The main drivers are:
- Size. More people doing skilled work means more of it on record.
- Years of history. Long histories show how work changes over time.
- Variety and connection. Several record types that link together beat a single silo.
- Specialization. Work that’s hard to find elsewhere is worth more.
- Rights and exclusions. You can only be paid for what you can actually license.
- Terms. Exclusivity, permitted uses and whether the buyer gets raw or prepared records all move the price.
- Competition. In the Spirit auction, bids climbed from $5 million to $10 million as two buyers competed.
For reported price points and how estimates work, read what your company’s data is worth, or get an indicative range in about a minute with our value estimator.
How does the licensing process work, step by step?
Most licenses follow the same sequence, whether you run it yourself or with help.
- Take inventory. List your systems, record types, approximate volumes and date ranges. A description is enough at this stage; no files are needed.
- Confirm your rights. Review client and vendor contracts, NDAs, privacy notices and the terms of the platforms your data lives in. Not everything you hold is yours to license.
- Set the scope and exclusions. Decide what’s in and what stays out. Exclude high-risk material entirely rather than relying on redaction.
- Approach buyers and compare offers. Share a description of the opportunity, not the data. Compare price, permitted uses, exclusivity and timing.
- Negotiate the agreement. Pin down scope, use restrictions, retention and deletion, payment, warranties and liability.
- Prepare the records. De-identify the in-scope records under an agreed protocol, with review passes before anything leaves your hands.
- Deliver securely and get paid. Transfer through an agreed, secure method, and get paid on the schedule in your agreement.
One caution applies at every step: don’t send samples early. As the Frankfurt Kurnit lawyers note, a sample can itself be a disclosure, so share data only after rights and privacy review and under an agreement.
How do you protect clients, employees and your reputation?
This is where most of the real work sits, and where most of the risk is.
Check your rights first. A company that holds data doesn’t necessarily have the right to license it. Email and chat contain other companies’ confidential information, vendors may claim data their tools generated, and some platforms restrict how their data can be used. Slack’s API terms, for example, bar third-party apps from using API data to train large language models, as the Frankfurt Kurnit post points out.
Honor your privacy commitments. Most privacy notices and employee handbooks never mentioned AI training. Privacy laws may also apply. Under California’s CCPA, a transfer of workplace data for money can count as a sale of personal information unless the data meets the law’s definition of de-identified, according to the same post.
Exclude, then de-identify. High-risk categories should stay out entirely: legal correspondence, HR and payroll matters, personal tax records, bank statements, health information and anything you flag. Everything else should be de-identified consistently, so the work still reads clearly but no one is named. Our guide to how business records are de-identified explains the method and its limits.
Respect your people. Employee conversations about pay and working conditions can be protected under federal labor law, whether or not a workforce is unionized. That’s one more reason to exclude HR and personnel matters.
Plan for permanence. Once records are used to train a model, they can’t practically be pulled back out, and models can sometimes reproduce parts of what they were trained on. Exclusions and use restrictions do the heavy lifting, not deletion clauses alone.
Assume it may become known. California’s AB 2013 requires generative AI developers to publish high-level information about their training data, including whether it was purchased or licensed. License only what you’d be comfortable explaining to a client or employee.
For the protections we hold every license to, see privacy and security.
What are your options for licensing business data?
There are four common paths. Each has a place.
| Path | Who works for you | How price is set | Best for |
|---|---|---|---|
| Self-serve marketplace | The platform serves both sides | The platform’s process and terms | Owners who want speed and accept standard terms |
| A buyer’s own program | No one; you deal with the buyer | The buyer’s offer | Owners with one offer they’ve vetted |
| Going direct to a lab | Your own team and counsel | Negotiated by you | Large data holders with legal resources |
| Seller-side representation | A representative on your side | Offers compared and negotiated for you | Established businesses that want competition and a hands-off process |
Our comparison of marketplaces and representation covers when each path makes sense.
What should you ask before you say yes?
If a buyer has already reached out, start with five questions:
- Who is the end user of the data, and who do you work for?
- Exactly which records do you want, and for what purposes?
- Do you want raw records or prepared ones, and who controls de-identification?
- How long will you keep the records, and what happens to copies and derived datasets?
- What will you pay, when, and what warranties and indemnities do you expect from me?
The full list is in our guide to questions to ask an AI data buyer.
How to get started
You can make real progress in an afternoon:
- Write down your systems and how far back each one goes.
- Note the sensitive categories you’d never want shared.
- Pull the contracts that carry confidentiality terms: key clients, vendors and partners.
- Get an indicative estimate with our value estimator.
- Talk to counsel and, if you’d like, to us.
Cascade Data Partners represents established businesses in licensing selected records to AI labs. We present your opportunity to buyers, compare offers, negotiate price and terms, and manage the process, so you have one point of contact. A conversation is all it takes to start, with no files or logins needed. You approve the terms, rights and privacy are reviewed before any records are shared, and we’re paid a success fee only, so you pay nothing unless a license is signed. See how it works or start a conversation.
This guide is general information, not legal advice. Laws and contracts vary, so review any decision with your own counsel.
Frequently asked questions
Is it legal to license business data to AI companies?
Often it can be, but it depends on your contracts, your privacy notices, the laws that apply to the people in your records and the terms of the platforms the data comes from. Most companies can't license everything a buyer asks for. Review rights before you share anything, including samples, and work with counsel.
Do I lose ownership of my data if I license it?
No. A license grants defined, limited rights, such as using selected records to train or test AI systems, under terms you negotiate. You keep ownership of your records and your systems. Scope, duration, exclusivity and permitted uses are set in the agreement.
How much do AI companies pay for business data?
It varies widely. Reported 2026 deals range from tens of thousands of dollars for small, shuttered startups to $10 million for one airline's corporate data in a bankruptcy auction. Size, years of history, how connected the records are, rights and buyer demand drive the number. Cascade's partner estimate for qualifying businesses is $100,000 to $1 million or more, and it is not a guarantee.
What kind of business data do AI labs want?
Records of real work done well: email and chat threads, documents, tickets and project histories, CRM and accounting records, call transcripts and code. Records that connect across systems and span several years are worth the most.
Do I have to give a buyer access to my systems?
Not to start. A first assessment can be based on a description of your systems and history. When records are eventually shared, it should happen under a signed agreement, with scope, de-identification and the transfer method agreed in advance. Lawyers who advise on these deals recommend against giving buyer tools direct access to company systems.