Choose a route or use the form below.
Give your inquiry a clear purpose
The route selector helps you prepare the right kind of context. A seller inquiry should describe the company and its records. A buyer inquiry should explain the task and data requirements. A referral inquiry should identify the relationship and confirm permission to prepare an introduction. A press inquiry should include the topic, publication, questions, and deadline. Choose the route closest to your purpose, then keep the description focused.
You do not need to write a proposal or explain every uncertainty before using the form. State what you know, what you want to understand, and which decision you are trying to make. A short, specific account is easier to act on than a broad claim that the company has valuable data. If the opportunity involves several companies, keep their ownership, systems, and permissions separate in the description.
Describe the archive without sharing it
Useful seller context includes the business activity, major systems, approximate years of history, and the workflows the records preserve. Explain whether outcomes, revisions, or linked discussions are available. If you do not know the volume, describe the coverage rather than inventing a total. Identify the person who understands the archive and any obvious restrictions that would need review before a sample could be prepared.
Keep the inquiry descriptive. Do not paste customer exchanges, employee records, proprietary code, credentials, or confidential documents into the message. A generalized example of the work can make the archive understandable without exposing the original content. If the relevant details cannot be discussed without additional approval, say so. The first conversation can establish the questions and review path before anyone decides what information may be shared.
Include what makes the request specific
For a buyer inquiry, describe the intended use, domain, record categories, historical coverage, and the evidence needed to judge fit. Mention restrictions that materially shape the request, such as recipients or preparation responsibilities. The requirements builder offers a more structured local brief if you need it. Neither tool sources a dataset or confirms that a company with the requested archive is currently available.
For referrals, identify your relationship and whether the owner has agreed to discuss the opportunity. Keep proposed compensation separate from the introduction context until terms are agreed. For press, include the story angle and the claims you want to check, especially when discussing prices or transactions. Clear questions help avoid repeating illustrative figures as verified evidence or implying a relationship that this directory does not establish.
−Unclear intended use
−Undefined next question
+Task and scope
+Decision needing support
Understand what happens next
This version of the form prepares a local file in your browser. The download is not an inquiry sent to SellYourAIData, a buyer message, or an introduction made on your behalf. The status text describes that boundary so you can tell the difference between preparing information and delivering it. Review the file before deciding how to use it in a later conversation through an appropriate channel.
Keep your own copy with any source notes or questions that support the description. If the scope changes, revise the brief rather than assuming an earlier version still represents the opportunity. Nothing entered here authorizes access to business systems or creates a licensing, brokerage, referral, or confidentiality agreement. The form gives your next conversation a clearer starting point while leaving decisions and permissions with the relevant people.
- 01Write the contextKnown facts distinguished
- 02Review the downloadFile remains local
- 03Choose later channelNo inquiry sent