First-call data licensing question sheet

Use this first-call data licensing question sheet to record answers before you send a sample or connect a company system. Copy the prompts into your notes and make one sheet for each program. Leave with a next step, a named contact and a list of unanswered questions.

Before the call

Prepare a company data summary describing the systems, date range and approximate volume you could discuss. Keep customer records, credentials and sample files out of the agenda. Check who can authorize the conversation and which data rights questions still need an answer.

• Program and contact:
• Call date and people attending:
• Records we can describe today:
• Records excluded from this discussion:
• Person who can approve any later access:

Open with fit and scope

Ask which parts of your summary match the program's current demand. Ask what is missing before you spend time preparing files.

• Which systems, periods and formats would you consider?
• Are historical records enough, or do you want future updates?
• What would rule this dataset out?
• What can you assess from a written description?
• Who would receive a sample, and what would they do with it?

Beside each answer, note the document or follow-up needed. An encouraging call does not establish acceptance. Leave unresolved fields marked unanswered.

Ask what makes payment due

Mercor's captured data page describes wire payment when the anonymized dataset reaches the buyer. Turing's captured Lazarus FAQ describes revenue sharing. Ask what must happen before you get paid, then discuss the amount. Mercor Data and Turing Lazarus, checked November 8, 2026.

• Fixed amount or share of later sales?
• Event that makes payment due:
• Currency, deductions and payment deadline:
• For a share: percentage, calculation and sales reports:
• If nothing sells, or the buyer rejects delivery:

Do not fill these blanks from another program's page. Public statements do not establish the amount or conditions of your own proposal.

Split permission into separate answers

Turing's FAQ describes an initial 90-day selling right. SuperAnnotate says it licenses to buyers the seller approves. Ask where the proposed agreement records each restriction and approval. Turing Lazarus and SuperAnnotate, checked November 8, 2026.

• During evaluation: permitted access, use and retention:
• After signing: permitted uses and recipients:
• Selling restriction: records covered, start and end:
• Licenses elsewhere: what remains permitted?
• Approval requests: who decides, and how is consent recorded?
• Exit: what happens to files, copies and trained models?

Name the person who will send the proposed agreement. Have your adviser review the actual wording before granting access or rights.

Close with a written follow-up

Read back the open items. Agree who will answer each one and when. Keep a copy of the documents and the version discussed.

• Program will send:
• We will send, after approval:
• Unanswered questions and responsible person:
• Next contact date:
• Decision before sharing anything:

When a proposal arrives, move the confirmed answers into the licensing terms comparison. Use the program directory to check the published source for each program you contact.