What should we ask for in a sample, and what limits apply?

**What should we ask for in a first sample?**

One domain, one trigger approval and the full chain of linked records, plus a schema file, a manifest and a short note on how the cases were chosen. Ask for a mix that includes clean cases and several exception types.

**How large should a pilot be?**

Size depends on your customers' use. Scope it around the checks you want to run and the number of exception types, not a target row count. Volumes, pricing and timing are agreed per engagement.

**What licence limits should we expect to discuss?**

Permitted onward uses, whether your customers may train models on the material, whether they may redistribute or build derivatives, attribution, version handling and what happens when a release is corrected. Raise these before listing.

**Can we customise for a particular customer?**

A release can be shaped to vocabulary, product codes, roles and the exception mix. Ask what is changeable and what is fixed, and whether a customised release can be resold to others.

**What do we need to tell our customers?**

That the material is generated, informed by direct observation of how businesses operate, and does not contain real business records. Tell them grounding and disclosure risk should be inspected, and that the data does not by itself provide privacy or regulatory assurance.