Start with the wound. Stay with the wound.
The marketplace pages are built on a five-artifact demand-side framework: Struggling-Moment Timeline, Four Forces Map, Moesta Job Statement, Competing Solutions (including non-consumption), and Demand-Side Outcome. Every artifact is gated by three hard-block checks: timeline must cover both Push and Pull stages; the job statement cannot substitute a demographic for the job; the outcome must be progress, not a product feature.
Source: mrodgersjs-web/rig-jtbd-packs · strategy-studio-v2/workers/jtbd-intake/contracts.py · rubric.json.
PQS, PVP, FIND. The list comes from the wound.
Most lists are firmographic — company size, industry, revenue. Blueprint GTM builds the list from the buyer's pain: Pain-Qualified Segment (PQS), Pain-Validated Persona (PVP), and FIND. The wedge is a paid audit of the buyer's existing broken process — never a generic lead-magnet.
Source: LeadMagic/gtm-skills · references/framework-notes.md · jordan-crawford-blueprint-gtm.md.
The seal is the seal.
Every claim on every page is sealed. Hash, source, date. If a claim cannot be sealed, it does not ship. The seal is not a feature; it is the seatbelt.
Source: mrodgersjs-web/doctrine · mrodgersjs-web/rig-doctrine-overlay.
Because features do not sell. Wounds do.
When you read a page on this marketplace, you are reading a wound-first, JTBD-validated, Blueprint-GTM-aligned, sealed-proof catalog. You will not see a feature list at the top. You will see your own pain described before the product name appears.
That is the deal. We will not ad hoc this.