Marketplace Launch Readiness Diagnostic
Should you launch this marketplace vertical — and what's the readiness level?
Read the framework ↓Diagnostic
Use one service, geography, time window and cohort consistently. Population is not demand, registered providers are not available supply, and months to liquidity is your assumption.
Rule-by-Rule Results
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.
Use this screen for one service, geography, time window and cohort. Population, supply and reuse assumptions expose constraints; they do not estimate standalone contribution or establish that a launch is funded.
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 | Potential providers; availability still unverified |
| 5 | Provider Economics | Earnings vs. opportunity cost |
| 6 | Liquidity Timeline | Months to minimum viable liquidity |
| 7 | Regulatory & partnership prerequisites | Legal framework + government partnership |
| 8 | Platform Leverage | Infrastructure reuse potential |
| 9 | Entry-position proxy | Timing, reuse and density proxy |
How Marketplace Verticals Fail
A large market can still have weak matching in a particular service area or time window. A reused customer base can also generate orders that lose money after incentives and fulfilment. Test those separately before expanding.
Decision Rules Summary
| Tier | Condition |
|---|---|
| Candidate for a scoped pilot | 0 fails, 0–1 warnings |
| Resolve constraints before a pilot | 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 demonstration assumptions. Review their purpose and sensitivity before replacing the examples with an actual market and business model.
When the conclusion changes
Read supply and demand in the same local market cell. Company-wide population, membership or registered supply can conceal mismatches in the hours and places where service is needed.
Keep three views: incremental demand from reused distribution; vertical contribution after fulfilment, payments, refunds, incentives and local fixed costs; and separately attributable advertising / membership income. Set funded milestones for scale, hold or stop.
How these assumptions were set
Scenario construction
The pilot candidate and partnership-required cases have identical numeric inputs. The missing prerequisite alone changes the next decision. Separate cases place supply below the 2K review band or combine earnings below alternatives with a long assumed liquidity period. These are constructed service cells, not city statistics.
Why these bands
An earnings ratio of 1.0 is parity with the stated alternative. The 0.8 cutoff, 12/24-month horizon, population and supply floors, and layer weights are demonstration assumptions. They are not minimum market sizes, runway forecasts or estimated launch-success probabilities.
Test the sensitivity
Keep the pilot numbers fixed and mark a required partnership unconfirmed: the tool holds commitment to launch. Moving assumed liquidity from 12 to 13 months adds a review flag; it cannot show whether cash is sufficient because cash and burn are not inputs.