What should we put in a sample request for a review product?

Write the sample request around the customer decision it must support, using the following scope points.

- Name the downstream buyer role and intended task. - Choose one domain and review subject. - Define the evidence available to the agent. - Request routine, unresolved and escalation outcomes. - Specify the required explanation or output artefact. - State which business decisions remain outside scope. - Define who will assess the sample and how.

The sample should demonstrate meaningful variation, rather than only a clean successful path. Request an unresolved case that requires the model to stop and identify missing information. This helps reveal whether the proposed product rewards justified restraint or encourages completion regardless of evidence.

Separate sample acceptance from model performance. A model can fail a well-formed task, and a flawed task can produce an apparently successful answer. Assess record coherence, answer defensibility and suitability for the intended customer before interpreting any trial run.

For a reseller, the immediate deliverable is a brief that can support a clear accept, revise or decline decision. It should also identify which proposed catalogue claims the sample could substantiate and which would require additional coverage.