What does a first scoping step look like for a marketplace?

A data marketplace's catalogue manager wants a set-up pack for professional services firms: turning an accepted engagement proposal into a client record, an engagement code and a billing arrangement. The manager contacts MirrorFirm with a one-page request.

The request lists the trigger, proposal approval PROP-0455 signed off by a partner role. It lists the records, which are client CLI-3021, engagement ENG-8802, a conflict-check task and a billing profile. It lists the exceptions: a related-party conflict, a client that needs a different billing entity, and a scope change after acceptance.

The sample agreed for the first step covers one service line and a small set of cases, with a schema file and the validation checks. The catalogue manager runs the key checks, finds that one scope-change case lacks a link to its original engagement, and sends it back with the finding.

The state change is the sample moving from received to accepted for pilot, and the listing decision stays open. Two marketplace customers then review it under a trial licence on terms agreed in the engagement.

**What it teaches:** a good first step is narrow, checked by the reseller before any customer sees it, and open about what is not yet decided. Sending findings back early is cheaper than correcting a listed product.