What should we include in a sample request to make the first review useful?

Use this checklist to write a sample request that can support a concrete buying decision.

- Name the downstream customer use case. - Select the obligation and triggering policy. - Specify the decision the sample must expose. - State the customer's available input context. - Identify the required delivery format. - Describe the intended redistribution route. - List the evidence needed for acceptance. - Record processes explicitly outside the sample.

Acceptance evidence should relate to the sample's purpose. If the question is whether a customer's ingestion pipeline can load linked cases, request a schema and connected records. If the question is whether the policy can be evaluated, request enough contrasting states to inspect its decision boundaries.

Tell MirrorFirm which constraints come from the customer's system and which are preferences. A mandatory field mapping may determine the sample structure, while a preferred display label may be easy to change later. This distinction helps keep the first scope discussion focused.

The sample request should also state what decision follows the review: refining requirements, proceeding to a pilot or declining the fit. A sample can inform that decision without establishing production suitability, broad domain coverage or rights beyond the agreed sample use.