Yes, a running startup can license its own operating records and code to AI developers and keep its equity. It is revenue, not a grant or a loan, so nothing is repaid and nobody joins the cap table. The limits are real: customer content is not yours to license, a deal has no fixed timetable, and many investor agreements require approval before the company licenses material intellectual property outside the ordinary course.
- Licence your own records, never your customers' content.
- Do not plan payroll around a deal that has no timetable.
- It is revenue, but it is not ARR unless it recurs.
- Read the investors' rights agreement and any loan covenants before you sign.
Is data licensing non-dilutive funding?
In effect, yes. It brings in cash without issuing shares or taking on debt. Strictly it is revenue from licensing an asset, which is better than funding in one way: there is no programme to apply to and nothing to repay.
The term usually refers to grants. The US government's small business research programme describes itself as awarding "non-dilutive funding to develop your technology and chart a path toward commercialization" (SBIR.gov). A data licence sits beside that, with different strings.
| Source of cash | Dilutes founders? | Repaid? | Main strings |
|---|---|---|---|
| Equity round | Yes | No | Board seats, preferences, protective provisions |
| Venture debt | A little, through warrants | Yes, with interest | Covenants and a lien, often on intellectual property |
| Research grant | No | No | Eligibility, reporting and use-of-funds rules |
| Data licence | No | No | Contract limits on what you can license, and the terms you give the buyer |
What can a running startup license without hurting the product?
Its own operating history: the records of how the company itself works. That is separate from the product's customer data and separate from the trade secrets that make the product hard to copy. Keep both of those out.
| Record set | Licensable? | Why |
|---|---|---|
| Support tickets and resolutions | Usually, after de-identification | Your record of your own work |
| Internal engineering history: issues, reviews, incident write-ups | Usually | Yours. Screen for secrets and customer names |
| Source code | Your call | It is yours, but decide what a competitor could learn. See the source code guide |
| Warehouse models and pipeline code | Usually | Yours. See the guide for SaaS companies |
| Product usage events | Sometimes, aggregated or de-identified | Depends on the usage-data clause. See product usage data |
| Customer content in the product | No, without consent | It is the customer's |
| Core model weights, proprietary algorithms, roadmap | Leave out | The competitive edge, not an archive |
What limits apply to customer data in a SaaS product?
You hold it to run the service and for little else. Under most contracts and under privacy law, a provider may not license customer content to a third party unless the customer agrees.
European law requires a processor to act "only on documented instructions from the controller", and says a processor that decides purposes for itself "shall be considered to be a controller in respect of that processing" (GDPR, Article 28). California defines a service provider by a contract that prohibits "selling or sharing the personal information" (Cal. Civ. Code 1798.140).
The guide to NDAs and customer contracts shows which clauses to read and how to ask for consent where a record set is worth it.
Does licensing data scare customers?
It can, if their data is involved or if they hear about it from someone else. It rarely does when the licence covers only your own de-identified operating records and your terms say so.
Three habits keep trust. Leave customer content out entirely unless a customer has signed consent. State in your terms what you do and do not do with data, before you do it. And keep an exceptions list, so an enterprise customer who asks can be told in one sentence that its records were excluded.
How long does a deal take compared with runway?
Longer than a founder short of cash would like, and nobody can promise a date. There is no standard timetable, and we have no sourced figure to give you. Treat a data licence as upside on the plan, never as the bridge.
The order of work is fixed even if the duration is not: inventory, contract review, a description and small sample for the buyer, terms, de-identification, delivery, then payment on the agreed trigger. The first two steps need no buyer. A startup that has done them can move when an opportunity appears. One that has not will spend its first month finding out what it owns.
If the company is closer to winding down than to raising, the order of priorities changes. See how to shut down a startup and acquihire or data sale.
Does data licensing count as revenue?
Yes. It is revenue from a licence of intellectual property and is recognised under ASC 606. It is not annual recurring revenue unless the contract recurs, and investors will separate it from subscription revenue.
For a fixed dataset the revenue usually lands at once. The standard treats "a right to use the entity's intellectual property" as "satisfied at a point in time" (FASB ASU 2016-10). Show it on its own line. The guide to how data licensing income is taxed covers recognition and tax, and the CFO guide the board side.
Do investors need to consent?
Often, yes. Standard venture documents give investor-appointed directors a vote on licensing material intellectual property outside the ordinary course. Read your own investors' rights agreement, charter and any loan agreement before signing.
The model term sheet of the National Venture Capital Association lists, among matters needing the preferred director's approval, to "sell, assign, license, pledge or encumber material technology or intellectual property, other than licenses granted in the ordinary course of business" (NVCA model term sheet, as published by CommonAccord). A first licence of company records to an AI developer is hard to call ordinary course.
Lenders are the other check. Venture debt usually comes with a lien or a negative pledge on intellectual property, and a licence can need the lender's consent. This page is general information, not legal advice. Ask company counsel, and tell the board early.
When should a startup not license its data?
When the records are not yours, when the buyer could become a competitor with them, or when the deal would cost more attention than it returns.
- The valuable records are customer content and customers have not agreed.
- The buyer builds a product in your market and the data would teach it your edge.
- The buyer wants exclusivity or a perpetual grant for a price that reflects neither.
- You are in the middle of a fundraise or a sale and the licence would complicate diligence.
- Enterprise customers have audit rights and you cannot yet show what was excluded.
- The team is small and the deal would stall the roadmap for a quarter.
Example: sorting a 40-person startup's data
A fictional B2B software startup with five years of history and nine months of runway sorts what it holds. The figures are invented to show the method.
| Record set | Volume | Position | Decision |
|---|---|---|---|
| Support desk | 38,000 tickets | Company records with customer names | In, de-identified |
| Issue tracker and incident reviews | 21,000 issues, 140 reviews | Company records | In, after a secrets scan |
| Warehouse models and run history | 260 models, 3 years | Company code | In |
| Customer workspaces | 900 GB | Customer content under the DPA | Out |
| Usage events | 1.4 billion rows | Clause allows aggregated use only | Out at record level |
| Core ranking service code | 1 repository | Company trade secret | Out by choice |
Fictional example. Three sets are in. The founder takes the list to the board and the lead investor before any buyer conversation, because the investors' rights agreement has the licensing clause quoted above.
Common mistakes founders make
Most come from treating the licence as found money.
- Counting customer content as the company's data.
- Building the cash plan on a deal with no signed terms.
- Reporting a one-off fee as ARR.
- Telling investors after signing.
- Forgetting the venture lender's lien on intellectual property.
- Granting exclusivity to the first buyer who asks.
- Licensing the code that is the product's edge.
- Changing the privacy policy quietly to make room for the deal.
A startup's operating history as a data asset
Five years of tickets, incidents, code review and pipeline history are a record of how a real software company works, and AI developers license such records from operating companies. For a startup it is one of the few assets that can earn without being sold and without a new line on the cap table.
Origin works with buyers and helps a company describe what it could license, find out what it could be worth and decide whether to go further. Nothing is exported at the start, and no customer data is needed to begin. Origin Data Partners is an independent data partner that helps companies get their data bought. A buyer may pay Origin when a deal closes.
Does your company hold records like these? See what your data is worth.
Common questions
Can a running startup license its data to AI companies?
Yes, its own operating records and code: support tickets, engineering history, warehouse models, once personal data is removed. Customer content in the product belongs to customers and stays out unless they consent in writing.
Is data licensing non-dilutive revenue?
Yes. A licence fee is revenue. No shares are issued and nothing is repaid, so founders are not diluted. It differs from a grant in that there is no application and no use-of-funds rule, only the contract with the buyer.
Can a startup extend runway by licensing data?
Possibly, but do not plan on a date. There is no standard timetable for a data licence, and the contract review is the slow step. Do the inventory and contract review now so the company can move quickly, and treat any fee as upside.
Do investors have to approve a startup data licence?
Often. The NVCA model term sheet lists licensing material technology or intellectual property outside the ordinary course of business among matters that need the preferred director's approval. Check your investors' rights agreement, charter and loan documents.
Does data licensing count toward ARR?
Not unless it recurs under contract. A single fee for a fixed dataset is one-off revenue, usually recognised at delivery under ASC 606. Report it on its own line so investors do not have to strip it out.
Should a founder license company data before a fundraise?
Finish it well before, or wait. A signed, non-exclusive licence with clean paperwork can help a round. A half-negotiated one, or one that used customer data, creates diligence questions at the worst time.
Sources and further reading
- SBIR.gov: about America's Seed Fund
- Regulation (EU) 2016/679 (GDPR): Articles 5 and 28, Recital 26
- California Civil Code section 1798.140: definitions (sell, service provider)
- FASB Accounting Standards Update 2016-10: Revenue from Contracts with Customers (Topic 606), Identifying Performance Obligations and Licensing (PDF)
- NVCA model term sheet (2020), as published by CommonAccord: matters requiring preferred director approval
