What should a buyer put in a sample request to make the result reviewable?

Use this checklist to write a sample request that a developer and an operational reviewer can assess together.

- Name the agent capability under investigation. - Describe the starting request and desired business outcome. - Specify the reviewer roles and their questions. - Ask for an annotated walkthrough of one complete task. - Request a data dictionary for unfamiliar business terms. - Define what evidence supports acceptance or revision. - List open assumptions that the sample must resolve.

The annotated walkthrough is especially useful when reviewers bring different expertise. A developer may need to understand how a tool response changes the agent's next action, while an operational reviewer needs to establish why that action is permitted. Linking both explanations to the same task prevents separate reviews from approving incompatible interpretations.

Keep acceptance focused on what the sample can demonstrate. A small sample can establish that the representation is understandable and executable, but it cannot establish performance across every customer circumstance. Record which questions remain open and use those questions to shape any subsequent pilot rather than treating sample approval as universal validation.