All 12 systems · System 6
Marketplace demand-first
A demand-first marketplace begins by collecting specific, time-bound buyer requests, then uses that backlog as proof when recruiting supply. It fits markets where buyer intent is easier to aggregate than inventory, requests can be fulfilled manually, and suppliers respond to credible revenue rather than speculative exposure.
Causal engine
Capture structured buyer intent → qualify urgency, budget, and constraints → cluster requests into a concentrated pocket → show suppliers a credible backlog → recruit only the supply needed to fulfill it → manually make and quality-control matches → successful outcomes create repeat demand, supplier proof, and denser future matching.
Preconditions
- Buyers will describe a real request and tolerate a concierge or waitlisted experience
- Urgency, budget, location, and quality constraints can be captured before matching
- The founder can manually source, vet, and coordinate the first transactions
- A concentrated demand segment is economically attractive to a reachable supplier pool
Anti-patterns
- Collecting email addresses without enough request detail to prove purchase intent
- Building matching algorithms before completing and observing manual matches
- Recruiting broad supply with vague promises instead of showing a qualified demand pocket
- Increasing request volume while match quality, fulfillment speed, or buyer trust deteriorates
Solo-founder translation
This week, collect fifty structured requests from one buyer segment and personally call the ten with the highest urgency. Source and coordinate their matches by hand, recording why each candidate was accepted or rejected. Measure qualified-request rate, time to first viable match, request-to-transaction conversion, fulfillment quality, and repeat requests before automating matching.
Qualified demand intake and concierge follow-up
Qualified demand intake
Waitlist promise
Intake questions
Confirmation email
Hi {{first_name}},
We received your request for **{{desired_outcome}}** by **{{needed_date}}**. We will verify the constraints and reply by {{response_deadline}} with either vetted options or one precise follow-up question.
If the request is urgent, reply with the word **URGENT** and the consequence of missing the date.
Founder workflow
View raw markdown
# Qualified demand intake
## Waitlist promise
**Tell us exactly what you need. We will return up to three vetted options within 48 hours—or tell you why the market cannot fulfill it yet.**
## Intake questions
1. What outcome are you trying to achieve? Provide one concrete example.
2. Where must the service or item be available?
3. When do you need to start, and what happens if you wait?
4. Which budget range is already approved: under $250, $250–$1,000, $1,000–$5,000, or $5,000+?
5. Name two non-negotiable requirements and one flexible preference.
6. Have you tried another option? What disqualified it?
7. What is the best email and phone number for a ten-minute clarification call?
## Confirmation email
Subject: We are qualifying your {{request_category}} request
Hi {{first_name}},
We received your request for **{{desired_outcome}}** by **{{needed_date}}**. We will verify the constraints and reply by {{response_deadline}} with either vetted options or one precise follow-up question.
If the request is urgent, reply with the word **URGENT** and the consequence of missing the date.
## Founder workflow
1. Mark each request `unqualified`, `qualified`, `matched`, `fulfilled`, or `closed-lost`.
2. Call qualified buyers within one business day.
3. Cluster requests by shared supplier requirements.
4. Recruit suppliers using anonymized counts, budgets, and dates from the cluster.
5. After fulfillment, collect buyer quality score, supplier quality score, and reason for any failed match.Playbook diffs
Companies on this system
No published cases are mapped to this system yet. Browse the directory or retake the quiz to find a neighboring motion with evidence.