Marketplace model — mockup previews

One model across Requex and FixTrade. Each page below has a REF so it can be named in feedback.

Read these as arguments, not as designs. Several of these surfaces do not exist yet — there is no trades guest console (ledger B117), and the quote object itself is an open question (Q2). They are here so the model can be discussed against something concrete. Layout and copy are illustrative; the STATES and the GATES are the point.

M01	Company profile — Requex tenant (verified) A verified Requex tenant. Prices are promoted to the marketplace and a customer can buy. Compare with M02, which is the same page for an unverified business.	Requex
M02	Company profile — FixTrade tenant (unverified) The same page for an UNVERIFIED FixTrade business. Equipment and services are visible, prices are NOT promoted, and the buy action is disabled — a quote is the designed path. Compare with M01.	FixTrade
M03	Marketplace listing page The marketplace as the plan describes it. A verified business shows a real price; an unverified one shows an estimate or POA and the action is Find a fitter, never Buy.	Requex
M04	Quote page — customer facing What the customer sees after a business responds. The unverified state travels ON THE QUOTE, because a quote gets forwarded, printed and read away from the page it came from.	FixTrade
M05	Quote submission — customer facing Everything from checkout except payment. Note the promise made at the point of submission: details are not shared until a price is agreed. That promise is what constrains M08–M11.	FixTrade
M06	Quote received — customer email The email that lands when a business responds. It carries the same unverified state as the page, because the email is where most people will first read it.	FixTrade
M07	Quote received — the request page The customer's window onto their request: every response in one place. The same public link is delivered in the checkout response, by email and by SMS (§6b).	FixTrade
M08	Public quote request — Requex tyres The page a scraped tyre fitter is sent to. It must be safe to hand to a stranger: the job and its distance from the reader, never the customer or their postcode.	Requex
M09	Public quote request — Requex service & repair The same page shape for a service or repair job rather than a tyre. One request object, one page, different content.	Requex
M10	Public quote request — FixTrade equipment Equipment supply-and-fit. This is the surface where the purchase gate matters: an unverified business may quote it, but a customer cannot buy from them directly.	FixTrade
M11	Public quote request — FixTrade home call-out A call-out rather than an installation — the shortest form of the request, and the one most likely to arrive by phone agent.	FixTrade
M12	Guest portal — after converting to a plan What a converted tenant sees if they log in at the OLD guest portal. Without this they land in a stale console and conclude the product is broken; the account did not disappear, it moved.	FixTrade

What each mockup is arguing

M01 vs M02 — the same profile, verified and unverified. Qualifications are listed either way; only one carries a badge, and only one can be bought from.
M03 — three price states, one action. A verified price says Buy; an estimate or POA says Find a fitter.
M04, M06, M07 — the unverified state travels on the QUOTE and the EMAIL, not only the profile, because a quote is read away from the page it came from.
M05 — the privacy promise is made at submission, which is what constrains every request page below it.
M08–M11 — the public request pages a scraped supplier is sent to. Each one is built to be safe to hand to a stranger: the job and how far it is from the reader, never the customer, their address or their postcode (Q6).

Open questions these raise are tracked in roadmap/marketplace-commerce-model.md §7 (Q1–Q11).