Before selling company data, ask the buyer who signs and pays, how rights are checked, who de-identifies the data, when funds are committed, which uses the license permits and what happens after delivery. Good answers are specific, in writing and consistent with the contract. Vague or pressured answers are a reason to stop.
How to use these questions
The market for company data is young, and buyers differ in what they are and how they work. A seller usually has one chance to get the terms right, because training on delivered data cannot be undone.
The twenty questions below are grouped into six topics. Each has a note on why it matters and what a good answer looks like. Put them to every buyer you speak to, including Outrich Data, and compare the answers with the draft contract. An answer given on a call counts for little if the agreement says something else.
Ask for answers in writing. A serious buyer will have them ready.
The order is deliberate. Identity comes first because nothing else can be judged without it. Rights and privacy come before money because they decide what can be sold at all. Contract terms and the period after closing come last because they are where early promises are either written down or lost.
Identity and model
Start with who you are dealing with. The same words on a website can describe a company buying for its own account, an agent looking for a buyer, or a listing platform.
Listen for whether the description stays the same when you press on it. A firm that is a direct buyer will say that it signs the license and pays from its own funds. A firm that is arranging a sale for someone else will speak of partners, demand and matching.
| Question | Why it matters | A good answer |
|---|---|---|
| 1. Which legal entity signs the agreement and pays us? | You need to know who owes you money and who holds your data | A named company, its jurisdiction and a signer with authority |
| 2. Are you the buyer, a broker or a marketplace? | It decides who pays, when, and whether your data is shopped around | A plain statement of the model that matches the contract |
| 3. Who uses the data in the end, and do we approve them? | Your data could reach a party you would refuse | Buyer categories disclosed and approved by you in writing before delivery |
| 4. What is your record, and how can we verify it? | Many firms in this market have short histories | Checkable specifics, or a plain statement that the firm is new |
Rights and review
The right to license is the seller's problem if it goes wrong, because the seller gives the warranties. A buyer that checks rights carefully is protecting you as well as itself.
A buyer that skips this step is not doing you a favor. It is leaving the whole risk with you.
| Question | Why it matters | A good answer |
|---|---|---|
| 5. How do you check that we have the right to license this data? | A rights failure lands on the seller through its warranties | A defined review of contracts, notices and prior licenses |
| 6. What happens to data that does not clear? | Pressure to include doubtful data is a warning sign | It is excluded and the offer is rescoped |
| 7. Do we receive the findings in writing? | A record protects you with your board and in any later dispute | A written report you can give to counsel |
Privacy
De-identification is where a deal is most exposed. The questions are who does the work, where the raw data sits while it is done, and who has the last word.
| Question | Why it matters | A good answer |
|---|---|---|
| 8. Who de-identifies the data, by what method, and where? | Raw data leaving your control is the main exposure | A named method, the identifier classes covered, a controlled environment and a written record |
| 9. Do we review and approve the final package before any buyer sees it? | The last check should be yours | Yes, in writing, for each package |
| 10. Does the license bar re-identification by you and anyone downstream? | Some laws require the clause, and it is the contractual backstop | An explicit clause that binds later recipients too |
Money and escrow
Price matters, but so does the path the money takes. A high number that depends on delivering first and invoicing later is worth less than it looks.
Ask about invoicing while you are here. The buyer should be able to say what documents it needs from you in order to pay, and whether payment is a single amount or staged.
| Question | Why it matters | A good answer |
|---|---|---|
| 11. How is the price worked out? | You should understand what moves the number | Stated factors such as data type, volume, history, exclusivity and rights, and a written offer |
| 12. Are there fees, commissions or costs to us? | They reduce what you actually receive | A complete list, or a clear statement that there are none |
| 13. When are funds committed, and who holds them? | Delivering first leaves you chasing payment | Funded into escrow before delivery, under instructions both sides sign |
| 14. What triggers payment, and what if acceptance is disputed? | Loose criteria lead to arguments after you have delivered | Testable acceptance checks, a cure period and a defined path for the funds |
Contract terms
Three terms shape what you are giving up: the permitted uses, exclusivity and your own liability. Ask about each before the draft arrives, then check the draft.
| Question | Why it matters | A good answer |
|---|---|---|
| 15. Which uses does the license permit? | Training, fine-tuning, evaluation and retrieval are different grants | Each use listed separately, with nothing implied |
| 16. Is the license exclusive, and for how long? | Exclusivity stops you licensing the data again | Non-exclusive by default; exclusivity priced and limited in field and time |
| 17. What warranties and indemnities do you expect, and are they capped? | This is where the seller's liability sits | Warranties tied to what the review found, knowledge qualifiers and a cap |
After the deal
A license has a life after closing. Files sit on someone's servers, people in the data may make requests, and the buyer may want more.
| Question | Why it matters | A good answer |
|---|---|---|
| 18. What happens to the delivered files when the term ends? | Files can be deleted, but training cannot be undone | Deletion with certification, and a frank statement about trained models |
| 19. Will our company be named, to buyers or in public? | Disclosure affects staff and customers | Not without your consent |
| 20. How are later requests handled, such as a deletion request or a refresh? | Obligations continue after closing | A named contact, a removal process and refresh terms in the license |
Reading the answers
No buyer will answer all twenty perfectly, and a new firm will have less history to show than an old one. What matters is whether the answers are specific, whether they are consistent with the paperwork, and how the buyer reacts to being asked. Outrich Data publishes its positions on most of these points in its commitments and FAQ. A seller should still ask, and should hold the contract to the answers.
Keep the written answers with the deal file. If a term is later disputed, a dated record of what the buyer said before signing is useful evidence of what both sides understood.
Some responses should end the conversation, or at least pause it until counsel has looked.
- The buyer cannot or will not name the entity that pays.
- The description of the model changes between the website, the call and the contract.
- No rights review is offered, and the seller is asked to warrant everything.
- Raw data is requested before any agreement is signed.
- The seller is asked to deliver before funds are committed.
- The offer expires in days and cannot be extended for legal review.
- The license grants all uses in general words, with no list.
- Questions about re-identification, deletion or naming are brushed aside.