The guide to selling your data to AI labs.

Begin with a simple inventory organized around business activity rather than file type. For each team, identify the tools used to receive requests, discuss decisions, record actions, and capture outcomes. Those events may sit across several systems. A completed support case, for example, may link a ticket, an internal discussion, a product change, and a customer response. Note the relationships you can actually reconstruct.

Then add the history available and the person who understands each source. Distinguish an active system from an old export and a complete archive from a partial backup. Record known gaps without trying to solve every problem immediately. Your first goal is to understand what exists well enough to describe it accurately, including where apparent volume does not translate into connected or interpretable records.

Write a short account of one representative workflow using ordinary language. Describe the original problem, the steps taken, the decisions recorded, and the outcome. Explain which systems preserve those parts and which are missing. Use a hypothetical or generalized description for the initial profile, rather than copying a customer conversation or confidential document to demonstrate what the archive contains.

Add context that would help someone outside the company understand the description. Identify specialist terms, changes in tools, and differences between teams or periods. Avoid presenting assumptions as measured facts. If you do not know the number of complete cases, say so and explain how that number could be established. A candid profile is more useful than a confident estimate that cannot be traced to the records.

Create a list of the people who need to be involved before any sample or transfer. Include the business owner, the person responsible for the systems, and anyone who reviews contractual or privacy restrictions. Explain which categories may contain customer, employee, supplier, or licensed third-party material. This map helps prevent a technical ability to export records from being mistaken for permission to license them.

Keep possible exclusions attached to the archive description. Removing an attachment, identity field, or related conversation may change the meaning of the remaining material, so scope and usefulness need to be reviewed together. Where the answer depends on specialist judgment, record the question and the person who can address it. You do not need to resolve those questions through this website before creating a descriptive assessment brief.

When a potential opportunity becomes concrete, combine the company profile, archive description, authority questions, and proposed terms into one working packet. Ask what the recipient wants to do, which material is needed, and what preparation is required. Compare the license, acceptance conditions, fees, and payment process. Keep versions together so a change in scope does not disappear inside a later commercial discussion.

Use the chapters and checklist as preparation aids, not as approval for a transaction. Reading the guide does not establish ownership, complete a privacy review, or authorize a transfer. The local assessment download can preserve your description for a later conversation. Before anything is shared, the relevant parties still need to agree the exact scope, responsibilities, recipients, and evidence showing that the handoff has been completed.