Marketplace Launch Readiness Diagnostic
Should you launch this marketplace vertical — and what's the readiness level?
Jump to interactive diagnostic ↓What This Is
A structured diagnostic for marketplace launch decisions. Most teams evaluate demand, supply, and regulatory barriers in isolation — this tool integrates them into a single readiness assessment with explicit pass/warn/fail thresholds.
The framework applies to any two-sided platform: ride-hailing, food delivery, logistics, or emerging verticals. Nine rules across three layers — Market Viability, Supply & Unit Economics, and Execution Readiness — produce a structured go/no-go verdict with specific actions for each gap.
Framework
| Rule | Tests | |
|---|---|---|
| 1 | Market Scale Floor | Addressable population threshold |
| 2 | Demand Density | Geographic demand concentration |
| 3 | Displacement Difficulty | Alternative solution coverage |
| 4 | Supply Sufficiency | Available provider pool depth |
| 5 | Provider Economics | Earnings vs. opportunity cost |
| 6 | Liquidity Timeline | Months to minimum viable liquidity |
| 7 | Regulatory Risk | Legal framework + government partnership |
| 8 | Platform Leverage | Infrastructure reuse potential |
| 9 | Competitive Defensibility | Timing × moat composite |
How Marketplace Verticals Fail
Four structural failure modes, each detected by specific rule combinations: Economics Trap (provider economics + liquidity timeline both fail — the flywheel never engages), Regulatory Blocker (viable market but regulation blocks entry), Saturated Late (fully-served market + late entry with no structural opening), and No Market (below scale and density — not viable for on-demand).
Decision Rules Summary
| Tier | Condition |
|---|---|
| Launch Ready | 0 fails, 0–1 warnings |
| Conditional Go | 0 fails, 2–3 warnings |
| Significant Gaps | 1 fail OR 4+ warnings |
| Not Ready | 2+ fails |
How to Use
Start with a preset scenario to see how the diagnostic works, then adjust inputs to match your specific vertical × market combination. Each input directly affects one or more rules. The diagnosis updates in real time.
Cross-Domain Note
This tool applies the same diagnostic architecture used across six payments tools to a different domain: platform economics. It is a cross-domain portfolio example, not evidence that the method has been deployed or validated by a client.
What This Demonstrates
Six payments tools show repeated application within one domain; this seventh tool shows how the architecture can be adapted to another. The evidence is the inspectable structure and behavior of the artifact—not client adoption or realised results.
Thresholds are author-defined heuristics for illustrating the diagnostic logic, not definitive marketplace benchmarks. Calibrate them to the market, vertical, and business model before making a live decision.