What should a reseller put in a sample or pilot brief?
Eight items for a pilot brief covering lifecycle stage, formats, schema, policies, tasks, grounding, onward rights and agreed acceptance checks.
When requesting a sample or pilot, a reseller can put these items in the brief so the result is easy to assess and easy to pass on.
- Name one lifecycle stage, such as deferral, arrears recovery or early closure, and one product or sector. - State the formats your customers load, for example JSONL for events and Parquet for tables. - Ask for the schema document, manifest and identifier conventions with the sample files. - Request the governing policy text and structured thresholds for every amendment type included. - Ask for task definitions with starting snapshots, expected end states and a reset method. - Ask how the generated world was grounded and what disclosure checks you should run yourself. - Ask which onward rights, sublicensing and training uses the licence would allow. - Agree in writing the acceptance checks and who will run them, before the sample arrives.
A specific brief makes the pilot easy to assess, easy to repeat and easy to pass on to your customers.
- Audience:
- Licensed resellers
- Content type:
- Checklist
- Buyer question:
- Scope and getting started
Content release: r-a220eb6e099b243b
Related questions
- What might a first pilot look like for a delivery scheduling agent?
- How do I wire a first pilot into my agent stack?
- What limits and licence questions should I raise before starting?
- How should I scope and license a schedule dataset or environment?
- How should a pilot release be delivered and versioned for my pipeline?
- What licensing terms and limits apply to generated schedule data?