Real AI data licensing deals: five disclosed amounts and the terms behind them

Five published amounts, with their source and terms

The providers' case studies anonymize the sellers and omit employee counts.^[1][2] We describe them as business examples without assigning them to a small-business size category. They are not North Fox transactions.

The rights granted change the meaning of the amount

Polyshares specifies perpetual, exclusive terms for its four examples.^[1] Compare those rights with any limited-duration or nonexclusive proposal before assessing the amounts. The headline amount alone cannot tell you which offer gives your organization the better arrangement.

Ask what the exclusivity covers: the defined dataset, a category of use, particular buyers, or another restriction. Ask whether you can keep using the material internally and whether future records are included. The contract should answer those questions. A brief case-study label cannot settle them.

For your internal review, put rights and dollars on the same page. Record the proposed duration, recipients, permitted activities, future-delivery duties, and restrictions on another license. Then assess whether the payment is acceptable for that complete package. Avoid adjusting a case-study price with an arbitrary percentage to account for rights you have not read.

Red Deer's logistics case reports a payout and an inventory

Red Deer reports a completed $350,000 payout. Its described inventory included Google Workspace, Slack, QuickBooks, and warehouse and transportation systems. The article distinguishes those potential sources from the final licensed collection, which it does not disclose. It also leaves the preparation details and elapsed deal timeline private.^[2]

That distinction is useful when preparing your own inventory. Naming several tools tells a reviewer where records may exist. It does not establish that every tool is relevant, every record can be licensed, or the full inventory would appear in an agreement. Keep an inventory column for potential sources and a separate column for the scope eventually approved.

The case was published in September 2026.^[2] Publication and research-check dates should not be treated as transaction dates. Our chart compares selected amounts by business category; it does not imply a sequence of deals or a rising price trend.

Other published outcomes provide different levels of detail

SimpleClosure names cielo24 in a customer story about a business closure. It describes structured transcription data accumulated over more than a decade, a workforce that peaked near 70, and an acquisition of the data assets for mid-six figures by an organization working in language technology.^[3] That offers a named company and operating context, but no exact price or complete rights schedule. We do not turn the wording into an invented dollar value on the chart.

Ooak Data says its smallest completed deal was $20,000 and that other deals reached several hundred thousand dollars. It separately presents licensed dataset profiles, but does not pair a specific price with each profile.^[5] Assigning its smallest payment to its smallest displayed company would create a transaction the source never reported.

These disclosures help distinguish the existence of completed transactions from a provider's advertised maximum. They also show why a five-bar chart is an incomplete view of possible outcomes. A collection can receive a smaller offer, a larger one, or no offer.

A platform's cumulative payouts answer another question

Troveo announced more than $20 million paid to content owners in its 2026 platform-expansion release. The announcement covered a platform spanning video, audio, text, enterprise workflows, gameplay, and robotics.^[4] It did not publish an annual payout series specifically for small-business operational records.

A cumulative total can help show that a provider reports activity at scale. It cannot be divided by the current number of listed datasets to calculate a typical seller payment. The groups may cover different periods, repeated licenses, and collections that have not sold. We keep this total separate from individual transaction amounts and from annual revenue or investment statistics.

The examples do not support an average price for your data

The public cases omit record volumes and several commercial terms.^[1][2] Their publishers selected them. Averaging this small set would hide gaps in coverage: there is no denominator showing how many organizations were considered or declined, or how often accepted sellers received a different amount.

An average would hide those gaps behind a precise-looking number. It would also mix a clearly described exclusive license with a case whose exclusivity is unknown. Sorting bars by amount is useful for reading the disclosures; it does not make the cases comparable enough to predict a price.

North Fox's calculator has its own published source and arithmetic. These case studies provide transaction context and are not calibration records for that calculation. The calculator's output remains separate from an actual offer after buyer review.

Build a comparison sheet when a proposal arrives

For a real proposal, replace the missing details with answers from the proposed agreement. If you receive multiple proposals, compare the same approved collection and identify any scope changes before comparing dollar amounts. This worksheet is North Fox's practical recommendation.

• Collection: the systems, dates, record categories, exclusions, and approximate usable volume included.
• Rights: permitted uses, recipients, duration, exclusivity, sublicensing, and treatment of future records.
• Work required: exports, preparation, review, corrections, access, and responsibilities for any continuing delivery.
• Payment: amount, currency, milestones, acceptance conditions, deductions, and whether another license generates another payment.
• Net proceeds: the amount remaining after the actual agreed fees and your preparation costs; keep tax analysis separate with your adviser.
• Approval: who may authorize the defined use and what unresolved ownership or contractual questions remain.

Start with a description that a buyer can evaluate

A useful first conversation can begin with the kind of work your organization performs, the years of history available, and the tools holding the records. Explain one complete process and any known gaps. You do not need to share actual messages, customer details, exported files, or login credentials with North Fox.

For an Orlando or Central Florida organization, Neil can discuss that inventory in person and help prepare questions for an appropriate licensing company. An introduction requires your agreement. Bring the questions left unanswered by these examples, especially scope, rights, and payment conditions, into that discussion.