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

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

Ask for a slice you can test end to end: a small set of complete cases with their items, checks, routing decisions and handovers, plus the policy file and schema. Include some exceptions, reopened cases and free text.

**Can our customers train models on it?**

That depends on the licence. Ask for permitted uses to be written explicitly: training, fine-tuning, evaluation, internal testing and redistribution of derivatives. Do not assume that one implies another.

**Are there limits on what a release can contain?**

Yes. A release contains generated records, not real business records, and its coverage is bounded by the domain and components agreed in scope. It will not cover every product, jurisdiction or process variant. State those boundaries in your listing.

**Can we get a custom domain?**

You can ask. Whether a domain can be covered, and how, is a scoping conversation, not something to assume from this page.

**What do we owe our customers?**

Clear descriptions: that the data is generated, what it covers, which schema version applies, and that grounding and disclosure risk should be inspected. Avoid wording that promises anonymity, privacy compliance or regulatory approval.

**What is a sensible first step?**

A narrow pilot with an acceptance test that you write before the sample arrives.