Recurring data revenue

Sell your history once. Get paid every month after.

Most data deals are a single sale of an export. Ours add a refresh term, so the records your team creates next month earn money too, with no extra work.

How it works

One setup, then monthly batches

01

The first license sells your history

Every past record in the system, up to the day of the first run, goes out as one dataset with its own price.

02

The SDK sends new records each month

On a schedule (monthly by default) it pulls only what changed since the last run, scrubs it on your machine and uploads a new batch.

03

Each accepted batch pays again

Every license with a refresh term pays its refresh price for each accepted batch. Once the schedule is set, there's nothing to do.

The difference

A one-off sale stays flat. A refresh term keeps adding.

The history license pays once. Each month after that, the new records your team created go out as a refresh batch, and each accepted batch pays again. More people working in your systems means more records per month, so the batches grow with your company.

See the SDK Read the docs

Illustration

Cumulative earnings over 24 months

  • History license plus monthly refresh
  • One-off sale
Illustrative cumulative earnings over 24 monthsWith made-up numbers: a one-off sale of $60k stays flat. The same sale plus a monthly refresh term starting at $2.5k and growing 3% a month reaches about $141k by month 24.$0$40k$80k$120k$160kMo 1Mo 6Mo 12Mo 18Mo 24~$141k$60k one-offMonth 1: the history sells
Made-up numbers to show the shape: a $60k history license in month 1, then a refresh payment from month 2 that starts at $2.5k and grows 3% a month as the team creates more records. Real prices depend on your data and the buyer. This is not a quote or a forecast.

What pays

Two kinds of payment

EventWhat pays
First license signedThe license's price for your history
Monthly batch acceptedThe refresh price, once for each license with an active refresh term

Your share is set in your seller agreement. By default it is 80% of what the buyer pays for that license and period.

What stays with you

Raw data never leaves

  • The SDK runs on your machine with read-only access to the systems you choose.
  • Names, contact details, account numbers and secrets are removed before upload. Rare values are rounded into ranges.
  • You see the scrub report for every batch, the same one buyers see in diligence.
  • You approve every buyer before a license is signed and can rule out any company.

Questions

Recurring revenue, answered

What do I have to do each month?
Nothing, once the SDK is scheduled. The scheduled run pulls new records, scrubs them on your machine and uploads the batch. You come back when we ask you to approve a new buyer, or when a credential such as an expired token needs fixing.
Does raw data ever leave my company?
Not through the SDK. Only the scrubbed output and the scrub report are uploaded. The one exception is the sample you can share under NDA for a readiness report: we scrub it on our server, keep only the scrubbed output and report, and delete the raw file.
How is a refresh payment calculated?
Each license sets a refresh price per batch. Every accepted batch pays that price once for each license with an active refresh term, so two licenses with refresh terms mean two payments for the same batch.
Why would batches get bigger?
Batches grow with activity. A team that sends more invoices, closes more deals or handles more tickets creates more records each month, so each refresh batch carries more data.
Can I stop?
Yes. Unschedule the SDK and no new batches go out. Your seller agreement covers what happens to licenses already signed, and data already used to train a model can't be pulled back out of it.

Find out what your history is worth.

Value my data