Skip to content
MirrorFirm

What should I request in a first sample or pilot?

A checklist of requests for a first sample: coverage, linkage, reference outcomes, policies, reset support and an inspection route for grounding and disclosure risk.

A first sample should test your pipeline end to end, not just show a pleasant file of records. Consider asking for the following.

- A small set of tasks per match pattern you care about, so each failure mode has an example. - Complete linkage: every payment resolves to the accounts and open items it could settle, with no dangling identifiers. - Reference outcomes with accepted alternatives, not only a single answer. - The policy set in both readable text and structured thresholds. - Starting snapshots and a manifest, so you can verify reset behaviour. - At least a few tasks where the correct outcome is to hold, query or escalate. - A written description of how the material was generated, so you can plan your grounding and disclosure review. - A clear statement of the permitted uses of the sample itself, which may differ from those of a full release.

Agree up front how you will judge the sample, such as explaining each failed episode in one line and confirming that two runs from the same seed match. Volumes, formats and delivery are agreed in discussion. Nothing here sets a price, timeline or service level.

Ask for a sample that tests your pipeline end to end, not just a pleasant-looking file of records.

Audience:
Environment builders
Content type:
Checklist
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Payment allocation