Skip to content
Outrich Data

How AI data buyers pay sellers, and when

Updated 2026-11-17 · 8 min read · By the Outrich Data team

Buyers of company data publish different payment terms. Some pay a set number of days after acceptance or invoice, one pays on delivery of the dataset to the buyer, one shares revenue on each sale, and Outrich Data funds payment into escrow before delivery. The table in this guide records what each buyer's own page stated on November 17, 2026.

Four things a payment term decides

Three buyers publish what they say raises or lowers an offer. See what buyers say moves the price of company data for a side by side reading.

A price tells a seller how much. Payment terms tell a seller when, on what condition and with what certainty. Two offers at the same price can differ by months and by who carries the risk in between.

Every payment term answers four things. The trigger is the event that makes money due, such as signing, delivery, acceptance or a later sale. The clock is the number of days from the trigger to payment. The form is a single payment, installments or a share of revenue. The location is where the money sits while the seller performs.

Buyers' web pages usually state one or two of the four. The contract states all of them. Treat a web page as a starting point and ask for the rest in writing.

What each buyer publishes

We read each buyer's own page on November 17, 2026. The table records what the page states about payment and nothing else. Where a page is silent on a point, the table says so. Terms change, so confirm with the buyer before relying on a row.

The table covers the same companies as our comparison of companies that buy data for AI, which also lists published ranges and minimum company sizes.

BuyerWhat its page states about paymentTrigger namedSource
micro1"We pay in full within 30 days of acceptance." Its FAQ says micro1 has 30 days to review and approve transferred data, then asks for an invoice and pays within 30 days of invoicingAcceptance, then invoicemicro1
Polyshares"Net 30 to 60 once the data is approved, shared, and anonymized"Approval, sharing and anonymizationPolyshares
MercorWire transfer on delivery of the anonymized dataset to the buyer, which it says typically occurs within 2 to 4 weeks of the signed agreementDelivery to the buyerMercor
DataPaid"Typically 20 to 60 days from discovery to payment received"Not statedDataPaid
ModeThe written agreement sets the amount and payment schedule before export. Mode says it generally expects about three months from first conversation through paymentSet in the agreementMode
TroveoThe seller shares in the revenue on every sale. Terms are stated in the agreementEach sale to a buyerTroveo
Scale AINo payment timing stated. Its FAQ says partnerships are designed so there is opportunity for recurring revenueNot statedScale AI
Outrich DataPayment is funded into escrow before the seller delivers and released when delivery passes the agreed checksAcceptance checks, with funds already depositedData escrow

Payment on acceptance, and what acceptance means

The most common trigger is acceptance. The seller delivers, the buyer reviews, and money becomes due once the buyer accepts. How long that takes depends on how the contract defines acceptance.

Most buyers do not publish that definition. micro1 does, in its Data License Master Terms. Section 1.3 gives it 30 business days after delivery is complete to reject data by written notice. Data not rejected in that time is deemed accepted. Early acceptance requires a written notice from its General Counsel or Chief Financial Officer. Section 3 says the seller may invoice only after acceptance. Our plain-English reading of those terms covers the detail.

Those terms show the parts every acceptance clause has. A seller comparing offers can check each part in each contract. The list below names them.

Subjective standards are the main source of delay. A test such as quality or usability depends on the reviewer. A test such as record count, schema and checksum match can be run by either side with the same result. Our guide to acceptance criteria and the acceptance criteria template show how to write tests that can be measured.

  • The standard. What the data is tested against: a written specification, or the buyer's judgment of quality.
  • The review period. How many days, counted in calendar or business days, and from what event.
  • Deemed acceptance. Whether silence at the end of the period counts as acceptance.
  • Who can accept. Whether any confirmation counts or only a notice from a named officer.
  • Partial rejection. Whether the buyer can reject part and keep part, and whether a partial rejection can become a full one.
  • Cure. How long the seller has to fix a rejected delivery and how many attempts it gets.
  • After acceptance. Whether the buyer can still claim a refund later, and for how long.

Net terms and the invoice step

Net terms add a second clock after the trigger. Net 30 means payment is due 30 days after an invoice or another stated event. Polyshares publishes net 30 to 60, counted from the point the data is approved, shared and anonymized. Its page adds that it does not pay for a record it has not seen, so its review comes first.

Where an invoice is required, the sequence has three stages: delivery to acceptance, acceptance to invoice, and invoice to payment. micro1's FAQ describes this sequence, with up to 30 days for review and payment within 30 days of invoicing. A seller controls only the middle stage, by invoicing on the day acceptance arrives.

The practical step is to add the stages together. Ask each buyer for the longest possible time from the day delivery is complete to the day funds arrive, assuming every period runs to its limit. Put that number of days next to the price when you compare offers.

Check what the contract says about disputed amounts. Many payment clauses promise payment of undisputed amounts only. Ask how a dispute is raised, how fast it must be resolved and whether the undisputed part is still paid on time.

Payment on delivery, upfront payments and installments

Mercor's page ties payment to a different event: delivery of the anonymized dataset to the buyer, by wire. It gives a typical timing counted from the signed agreement and says the timing depends on extraction and processing. A seller would want to know which party is the buyer in that sentence and what happens if that delivery is delayed.

None of the seven buyer pages we read states that it pays any part of the price at signing. That does not mean no buyer will agree to it. It means a seller who wants a payment at signing has to ask for it in the negotiation.

Installments split the price across milestones, for example part on acceptance of a first delivery and part on each later refresh. They suit deals with ongoing deliveries. Each installment needs its own trigger and its own clock in the contract, or the later payments become hard to enforce.

Revenue share and recurring payments

Troveo's page describes a different model. It licenses a company's data to multiple buyers on the company's behalf, and the company shares in the revenue on every sale. Its page says there are no fees or deductions from payouts. Under this model the trigger is a sale to a third party, and the timing depends on when buyers purchase.

Recurring payments also appear in direct purchases. Scale AI's page says its partnerships are designed for recurring revenue. micro1's page says it licenses qualifying agent trajectories for $1M to $2M annually, with the company's approval. Our guide to selling AI agent logs and trajectories covers that data type.

A share of revenue is harder to verify than a fixed fee. The seller depends on the other party's sales effort and on its reports. Before agreeing, ask what share applies, what it is a share of, how often statements arrive, whether you may audit them and whether any exclusivity applies while the data is on offer. Troveo's page says its exclusivity is time-limited and that the agreement includes exit terms.

A fixed fee and a revenue share answer different needs. A fixed fee gives a known amount on a known condition. A share may pay more over time and may pay nothing. Our guide on direct buyers, brokers and marketplaces compares the structures.

How escrow changes who carries the risk

In a deal paid on acceptance, the seller delivers first. Between delivery and payment the buyer holds the data and the seller holds a promise. If the buyer rejects, disputes or delays, the seller's data has already left its systems. The seller carries the risk for the whole review and payment period.

In a deal paid at signing, the position reverses. The buyer pays first and carries the risk that the data does not match what was described. This is why few buyers offer it.

Escrow removes the need for either side to go first. The buyer deposits the price with a neutral holder when the agreement is signed. The seller delivers. The data is checked against tests both sides wrote down in advance. If it passes, the funds release to the seller. If it fails and cannot be cured, the funds return to the buyer and the data is deleted.

Escrow does not make payment faster in every case. It changes what the seller is waiting for. The seller is no longer waiting to learn whether the buyer will pay. It is waiting for a defined check to finish, with the money already set aside. When Outrich Data buys, its payment is deposited into escrow before the seller delivers, and delivery is verified against a checksum manifest. Two parties who have agreed terms elsewhere can also close through Outrich Data as the escrow company.

Escrow depends on its instructions. The release conditions, the review period, the cure period and the return of funds must match the license word for word. Our guide to data escrow explains the instructions.

What to get in writing before you deliver

Use the list below with any buyer. The data license term sheet has a row for each item so two offers can be compared line by line. The guide to AI data licensing agreements explains the clauses, and the micro1 comparison page shows one buyer's published terms next to ours. The data valuation calculator gives an illustrative range for the price itself.

  • The event that makes payment due, in one sentence.
  • The number of days from that event to payment, and whether they are calendar or business days.
  • Whether an invoice is required and when you are allowed to send it.
  • The acceptance tests, the review period and what happens if the buyer says nothing.
  • The longest possible time from complete delivery to funds received.
  • Where the money is during that time, and whether it is in escrow.
  • What happens to delivered data if the buyer rejects or the deal ends.
  • For revenue share: the percentage, the base, the reporting schedule and audit rights.
  • The method of payment and who pays bank or transfer charges.

Common questions

Do AI data buyers pay upfront?
None of the seven buyer pages we read on November 17, 2026 states that it pays at signing. Most name acceptance, approval or delivery as the trigger. A payment at signing is something a seller has to negotiate. Escrow is an alternative: the money is deposited at signing and released on acceptance.
What does payment on acceptance mean?
It means money becomes due only after the buyer accepts the delivered data. The contract defines acceptance: the tests, the review period, who can accept and whether silence counts. Read that definition before you read the number of days.
How long does it take to get paid for company data?
It depends on the buyer and the contract. Published figures on November 17, 2026 include net 30 to 60 after approval (Polyshares), 2 to 4 weeks from the signed agreement (Mercor) and 20 to 60 days from discovery to payment (DataPaid). Each buyer describes these as typical, not guaranteed.
Is revenue share better than a fixed fee?
Neither is better in general. A fixed fee is a known amount on a known condition. A revenue share depends on later sales and on reports from the other party. Ask counsel to review the reporting, audit and exclusivity terms before agreeing to a share.
How does escrow protect a seller?
The buyer's funds are deposited with a neutral holder before the seller delivers. The seller is not relying on a promise to pay after review. Funds release when the delivery passes checks both sides agreed in advance, and return to the buyer if it does not.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc