How can a reseller scope a pilot for buyers with different complaint-handling use cases?

A marketplace curator prepares a pilot around complaint `CASE-0953` in professional services. A customer disputes whether a requested revision falls within the agreed scope. The sample contains the complaint, the acknowledgement, the scope record and an unresolved authority question.

A buyer's evaluation engineer wants inputs for drafting an acknowledgement. Another buyer's workflow engineer wants an agent to investigate and route the case for a decision. The curator initially places both uses under the same listing concept.

During sample review, the drafting view needs a clear concern and communication constraints. The action-taking view also needs permissions, investigation state and a route to the authorised decision role. The catalogue record changes from a combined proposal to separate proposed offerings, with the shared generated case providing the common basis.

The consequence is a more precise pilot: each offering has its own acceptance question and required material. MirrorFirm could generate the corresponding views for assessment. This teaches the reseller to use a sample to discover packaging boundaries, rather than interpreting interest in the same workflow as evidence that buyers need the same product.