Look past the record count.
Look into the process.

Relevance, verification, and a clear handoff matter more when you can see what each one means for your project.

Define the fit

Agree on the companies, roles, markets, and fields that belong in the dataset.

Ask: What makes a record relevant to this brief?

Understand which automated and human checks are included, and what uncertainty remains.

Ask: What was checked, and what was not?

Separate missing fields, uncertain matches, and other records that need review.

Ask: How will unknown values be represented?

Confirm the schema, secure transfer method, and process for addressing a mismatch.

Ask: How will this work in our systems?

Agree on the transfer method, purpose, access, and handling requirements first. An initial inquiry only needs a description of the project.

There is a separate route for questions, corrections, or requests about business contact information.

Before agreeing	What to establish	What to keep
Source context	Which source categories are used, and what access and usage terms apply to this project?	The agreed sourcing and permitted-use summary.
Verification	Which fields were checked, by what method, and when? What remains uncertain?	Field definitions, check descriptions, and available timestamps.
Coverage	Which countries, roles, and fields can actually be supplied?	A relevant sample and a record of missing fields.
Acceptance	What qualifies as a mismatch, and how will it be reviewed?	Written acceptance checks and an agreed resolution process.
Updates	Does a date refer to observation, validation, or export?	Explicit timestamp definitions and any agreed refresh scope.
A problem with a record	Which record ID, field, and correction should the team review?	Your inquiry reference and the project-specific response.

Use this framework to agree project terms. Specific sources, dates, guarantees, and response times must be confirmed in your agreement.