What can a reseller pilot reveal about onward licence terms?

A data product manager at a marketplace requests a sample of generated escalation material for a lending workflow. The sample includes cases such as APP-2187, a delegation matrix and a small task set.

Technical review goes well. The team loads the Parquet tables, confirms that each escalation joins to a case, and finds cases clustered around each authority threshold. A reviewer reads twenty handover notes and flags two that contain a figure inconsistent with the record. Those are reported back for correction.

Then the commercial review turns up a gap. The draft licence describes use by the marketplace itself, but is silent on whether an end customer may build and keep a derived task set from the data. The marketplace had planned to advertise exactly that use.

The consequence is a hold. The listing draft stays unpublished while the manager asks MirrorFirm to state, in writing, which onward uses are covered. The technical work is not lost; it simply waits for terms.

**What it teaches:**

- test licence scope alongside data quality, not afterwards - list the downstream uses you intend to advertise and ask about each one - keep the sample's permitted use separate from the full release's

The pilot did its job by finding the problem before any customer saw a listing.