What should a reseller request in a first sample package?

Request a sample package that lets your team inspect the proposed customer experience and the practical work required to distribute it.

- State the review decision, target customer role and business process boundary in the request. - Request source artefacts, task instructions and an evaluator guide as separately identifiable components. - Specify the delivery format and the schema information your ingestion process needs. - Ask for a manifest describing included files, dependencies and any intentionally omitted components. - Define acceptance checks and identify who will judge business plausibility and technical usability. - List intended preview, download and hosted uses for an explicit onward licensing discussion. - Ask how sample issues would be reported and what a subsequent scope decision would require.

Do not assume a preview represents every proposed difficulty level or delivery mode. Identify which parts of the eventual offering the sample can meaningfully demonstrate and which remain untested.

MirrorFirm could use this request to shape generated material for inspection. For licensed resellers, the next useful artefact is an acceptance note recording findings, unresolved assumptions and requested changes. That gives a broader commissioning decision a concrete basis without inventing delivery commitments or commercial terms.