What should a reseller ask for in a first sample or pilot brief?
A checklist of requests for a first sample: named domain and exceptions, readable files, manifest and card, grounding note, scorer, draft licence terms, known limits and success criteria.
Put these requests in your first sample or pilot brief, so the review produces something you can decide on.
- One named domain and a list of exception types you want represented, rather than a general request. - A small sample you can read by hand, with inputs, labels and policies in separate files. - A manifest, dataset card and schema, so you can check structure before looking at content. - A note on how the material was grounded and how it was generated, in general terms. - A scorer and a baseline method, so you can reproduce the scoring yourself. - The draft onward-licence terms, including preview rights and what customers may do with the data. - A statement of known limits and the exceptions the sample does not cover. - Agreed success criteria and a named reviewer on your side, written down before generation starts.
Put these requests in the brief so the first review produces evidence you can decide on, not just a file to look at.
- Audience:
- Licensed resellers
- Content type:
- Checklist
- Buyer question:
- Scope and getting started
Content release: r-a220eb6e099b243b
Related questions
- What delivery formats, splits and versioning should I agree before a first sample?
- What does a scoping meeting for a freight billing agent pilot produce?
- Will I receive real customer payments, and does generated data settle privacy questions?
- What should I ask for in a sample or pilot before committing to a larger release?
- How should I scope a first engagement for a payment matching agent?
- What does a scoping conversation look like for an insurer premium desk pilot?