Which companies should you approach?
Six programs below work with company data. Each can play a different role in the sale. In your first conversation, establish who signs the license, who pays your company and who may use the resulting dataset. Headcount is an initial screen. A buyer will still look at the history, scope and rights you can offer.
| Program | Company size and history | Records to describe | Payment or scope question |
|---|---|---|---|
| Replay | 20+ full-time employees. Its referral criteria specify English-language operations. | Messages, tickets, documents and code that show how a company handled real work. | Replay describes an upfront payment plus a share of later licensing revenue. Ask how that share is calculated. Program details. |
| Handshake AI | Its company referral criteria specify 20+ full-time employees and at least three years in operation. | Historical business records that employees use to perform and document work. | Request the company’s licensing offer. The separately advertised referral bonus goes to an eligible introducer. Program details. |
| Nyne | Operating companies with 20+ full-time U.S. W-2 employees and at least three years in business. | CRM, support, project and other operational records with a traceable history. | Ask for the proposed scope and fee before preparing an export. Count qualifying employees separately from contractors. Program details. |
| micro1 | 30+ full-time employees, mature operations and substantial historical data. Primarily English records. | Support histories, CRM records, operating procedures and internal communications across systems. | micro1 evaluates the data and tailors an offer. Ask which systems and periods the quoted price covers. Program details. |
| Scale AI | 40+ employees is its preferred starting point. It reviews individual cases. | Connected records from tools such as Jira, Slack and data warehouses, especially where a specialist made a decision. | Ask who approves each package, which extracts are included and how later deliveries would be priced. Program details. |
| Mercor | Requirements depend on the industry and the data opportunity. Check the category before assuming a team qualifies. | Workflow histories in the systems requested for the relevant category. | Mercor describes wire payment when the anonymized dataset is delivered to the buyer. Ask what counts as delivery. Program details. |
Two companies, two different shortlists
A 25-person support business with four years of tickets
Suppose your strongest records connect a customer question, an agent’s response, an escalation and the eventual resolution. Start with Replay and Handshake AI if your full-time headcount meets their criteria. Add Nyne if at least 20 employees meet its U.S. W-2 requirement. If the team includes 12 employees and 13 contractors, clarify how each program counts staff before preparing a sample.
Your first message can describe the ticket system, years covered, approximate number of resolved cases and how often you can connect a ticket to its outcome. A customer contract may limit the records you can offer. Have the person responsible for that contract review the proposed scope before sharing examples.
A 60-person software company with six years of engineering history
Consider micro1 and Scale AI if your issue tracker, incident reports and change logs connect across systems. An incident that can be followed from alert to diagnosis, fix and review is easier to explain to a buyer than a folder of unrelated documents. Add Mercor if its current category asks for the tools and records you have.
Give each program the same proposed scope. For example, describe resolved incidents from two specified years and identify the fields that connect an incident to its review. A quote that includes future updates purchases different rights from one limited to the historical extract.
Which offer pays more for the same rights?
Compare the guaranteed amount, the payment trigger and the work you must do to earn it. If there is a revenue share, ask which transactions count, which costs are deducted and when you receive a statement. Replay describes its typical structure on its program overview.
Consider two illustrative offers for the same historical dataset. One pays $18,000 on accepted delivery. The other pays $12,000 upfront plus 20% of eligible downstream receipts. The second needs $30,000 in eligible receipts to close the $6,000 gap, before costs or timing differences. A revenue projection is only useful once you know what counts as a receipt. These figures illustrate the arithmetic, not actual provider offers.
What to send before a buyer requests data
A short description gives a buyer enough information to decide whether a call is worthwhile. Adapt this example with your own figures.
We operate a 25-person customer support business. We hold four years of tickets, escalation notes and resolution codes. Ticket IDs connect the initial request to its outcome. Our operations lead can confirm the systems and date ranges, and our contracts lead will review which records we can license. Does that scope match a current requirement? What information would you need to quote a fixed historical extract?
Ask for the proposed uses, de-identification process, review rights and payment milestone in writing. Describe sample fields in the first inquiry. Agree on the transfer process before sending records. Use the dataset inventory guide to put those details together.
Where to go next
If you meet a program’s criteria, open its profile in the table and check the full requirements before applying. For a company that has closed, first identify who controls its records using the closed-company guide. For the steps from inquiry to agreement, use the business data licensing guide.
We checked the linked provider criteria on November 5, 2026. The selection reflects published fit and the kinds of records a company can offer. Examples and offer calculations are editorial illustrations. Some platform profiles include disclosed referral links. Commercial disclosure.