Supply, demand, liquidity, matching, trust.
Supply, demand, liquidity strategy, matching, and trust mechanics — the marketplace plan.
When it triggers
Marketplace generates against a locked Foundation — for both sides.
A marketplace is two products in a trench-coat. Foundation locks the wedge for both sides; Market Intelligence supplies the density and intent signals; this blueprint commits to the cold-start, liquidity, matching, and trust plan.
An idea scored on commercial fit
A Foundation Blueprint locking buyer + seller wedge
Market intelligence on supply density + demand intent
Strategic input
Read from strategy and evidence — not from a famous marketplace blog post.
From your Strategy Map
- Which side leads cold-start, and why
- Differentiation vectors that earn supply trust
- Trade-offs between take rate and liquidity speed
From Market Intelligence
- Existing supply pools you can recruit
- Demand-side buying triggers and frequency
- Take-rate bands per vertical and benchmark conventions
Blueprint outputs
A matching mechanism + trust mechanics + a liquidity ladder.
The actual product renders these as the live Marketplace Blueprint.
Matching mechanism (sample)
Three example matches with the underlying rule
- Solo bookkeeperPre-revenue founder
Match rule · Skill + jurisdiction match + first-call discount
- Specialist agencySeries-A startup
Match rule · Capacity-window match + outcome guarantee
- Vetted fractional CFOGrowth-stage SaaS
Match rule · Pricing-thesis fit + reference-check pass
Trust mechanics (sample)
Three mechanics every transaction earns trust from
Verification
ID + credentials checked before listing goes live
Dispute path
Tiered resolution with neutral review by day seven
Reputation
Outcome score from buyer + outcome-verified badge
Example data — matching + trust mechanics shaped by your Foundation + Market Intelligence.
Roadmap outputs
From a marketplace plan to the tasks your team executes.
Cold-start
- Recruit the first supply cohort by hand
- Run founder-led demand for the first 50 matches
- Pay supply to stay engaged before liquidity arrives
Ignite
- Move from manual matching to assisted matching
- Tighten the take rate to the rationale band
- Ship the trust-mechanic baseline
Defend
- Quarterly liquidity audit
- Cost-of-trust budget review
- Retire low-liquidity verticals, promote high-velocity ones
Prompt-pack outputs
Context for your AI ops + analyst agents.
Cold-start briefing
Side-led acquisition plan + first-50 transaction script packaged for an AI ops agent
Trust-pack
Pre-written verification flow, dispute script, and reputation-event copy
Liquidity dashboard brief
Metrics, alerts, and weekly review template — ready for an AI analyst
Sibling blueprints
Where Marketplace stops — and where each sibling picks up.
Foundation Blueprint
Foundation locks each side's wedge. Marketplace commits to the cold-start, matching, and trust plan that links them.
Business Model Blueprint
Business Model defines the take-rate architecture. Marketplace decides the liquidity trade-off that take rate is tuned for.
Retention Blueprint
Retention defines lifecycle loops. Marketplace defines side-specific retention (re-list, re-buy) per supply and demand cohort.
Start free
Score the idea, lock both wedges, generate the marketplace plan.
No credit card. Generate the cold-start plan, matching mechanism, and trust mechanics — upgrade for deeper roadmaps, prompt packs, and exports.
FAQ
Marketplace questions, answered.
How does the Marketplace Blueprint handle cold-start?
It commits to one side first — the side with the weaker fallback option — then defines the wedge that makes that side show up before the other side exists. The plan names the side, the wedge, and the first 50 transactions explicitly.
What take-rate benchmarks does it use?
Reference take-rate bands by vertical (services, goods, digital), with the rationale per band. Your committed rate carries the trade-off explicitly: lower rate → faster liquidity, higher rate → longer payback.
Two-sided vs one-sided — when does each make sense?
One-sided plays where you own one side as a managed service first, two-sided where the network effect compounds value for both. The blueprint argues the right shape for your wedge instead of defaulting to two-sided.
How does supply-side acquisition work?
Supply comes from named pools (existing customer bases, communities, partner networks). The plan defines the offer, the activation flow, and the first-transaction guarantee that keeps supply engaged before liquidity arrives.
What liquidity ladder does it commit to?
A staged liquidity plan — weekly transactions, week-over-week growth, time-to-match — with the unlock criteria for each rung. Liquidity is engineered, not waited on.
How does it handle trust + disputes at scale?
A trust-mechanics layer: identity verification, escrow or holds, reputation, dispute path. Each mechanic carries a rationale tied to the segment and a cost-of-trust budget you can adjust.
Continue reading
Where the Marketplace plan goes next.
Stop hoping for liquidity. Engineer it.
Cold-start, matching, take-rate, trust mechanics — one plan your team runs the marketplace from.