Data licensing payments and revenue share
Record the amount, payment trigger, deductions and due date separately. For revenue share, also record the revenue base, reporting and what happens when no sale occurs.
On this page
Start with the event that creates payment
A quoted price does not tell you when money becomes due. The trigger might be signing, accepted delivery, an invoice or a later sale. Ask what evidence establishes that event and who decides whether the delivery passes review.
Published programs describe different arrangements. Mercor describes payment on delivery of the anonymized dataset. Turing describes revenue share and no payment if no sale occurs. Confirm the current agreement rather than assuming one model applies across the directory.
Read the full revenue-share definition
Write down the percentage and the amount it multiplies. Does revenue mean the amount billed, cash collected, or the remainder after costs? Ask which costs may be deducted, whether they have limits, and how refunds or bundled sales affect the calculation.
Ask the provider to show a calculation using the proposed terms. Keep it labeled as an example, not an expected payout. Then ask when sales statements arrive, what they contain and how you can challenge a discrepancy.
| Item | Record from the proposal |
|---|---|
| Fixed amount | Currency, amount and any conditions |
| Acceptance | Review period, rejection grounds and repair process |
| Fees | Preparation, transfer, administration or other deductions |
| Share | Percentage and exact revenue base |
| Reporting | Statement schedule, supporting records and dispute process |
| Timing | Due date measured from a named event |
Keep conditional money separate
A future-sale scenario depends on demand, completed sales and the agreed revenue definition. Do not add that scenario to a fixed amount and call the total guaranteed. SuperAnnotate describes payment on delivery and relicensing; the specific proposal still needs to define both.
Our offer worksheet shows the fixed amount less entered fees separately from your revenue-share scenario. It leaves blank values unanswered and does not convert currencies or estimate taxes.
Compare the rights behind the price
Check that both proposals cover the same records, updates and uses. A larger amount may buy broader rights or more work. Read one-time and ongoing licensing and exclusivity terms before choosing which offer to discuss further.
Save the dated agreement version beside your worksheet. Update your worksheet when the provider supplies a written term.
Sources and limitations
Mercor Data | Enterprise Workflow Data for Frontier AI Checked 2026-11-08
Mercor Data · Primary source
Payment is issued via wire transfer upon delivery of the anonymized dataset to the buyer.
The page describes Mercor’s payment process; confirm the agreement and its delivery conditions. Publication date not established.
Data Partnerships | SuperAnnotate Checked 2026-11-08
SuperAnnotate · Primary source
We review a sample for volume, quality, and uniqueness … buyers you approve … licensing rights for a set period
SuperAnnotate describes reviewing samples, licensing to buyers the seller approves and agreeing a licensing period. Confirm these terms in the agreement. Publication date not established.
Project Lazarus | Turing Checked 2026-11-08
Turing Project Lazarus · Primary source
Through revenue share … You owe nothing.
The no-sale FAQ answer addresses what the seller owes. The agreement sets the payment terms. Publication date not established.