# Two-Sided Marketplace Liquidity Planner

Design a marketplace launch around a narrow transaction, local density, supply quality, demand acquisition, trust, and liquidity milestones.

## Prompt

You are a marketplace strategist who specializes in liquidity, trust, and constrained launch design for two-sided businesses.

Inputs:
1. Marketplace concept, transaction, and participants: {{marketplace}}
2. Geography, category, frequency, and urgency: {{market_scope}}
3. Supply and demand acquisition options: {{acquisition}}
4. Pricing, take rate, fulfillment, and trust mechanisms: {{business_model}}
5. Budget, team, regulation, and launch constraints: {{constraints}}

Do the following:
1. Define the atomic transaction and the conditions under which both sides consider a match successful, including quality, timing, price, location, and repeat behavior.
2. Choose the narrowest viable launch wedge and explain how it creates density, using frequency, fragmentation, existing alternatives, supply responsiveness, and demand urgency.
3. Design the supply-first, demand-first, or managed-market sequence, including manual operations, quality control, trust, cancellation, payment, dispute, and off-platform leakage controls.
4. Define liquidity metrics and thresholds such as fill rate, time to match, search-to-booking, provider utilization, repeat rate, and contribution per transaction.
5. Produce a launch playbook, side-by-side acquisition plan, transaction workflow, trust and failure matrix, weekly liquidity dashboard, and stop or expansion criteria. Do not confuse registrations or listings with marketplace liquidity.

## Best for

Founders evaluating or launching marketplaces that need enough high-quality supply and demand in the same place and time.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Define one atomic transaction.
- Choose a narrow geography or category.
- Include quality, payment, and cancellation operations.
- Measure completed matches rather than sign-ups.

## Customization tips

- Model both sides by time and location.
- Use managed operations before premature automation.
- Set a liquidity threshold before expansion.
- Track off-platform leakage and repeat behavior.

## Example input

Concept: Marketplace connecting small apartment buildings with vetted bicycle mechanics for on-site repair days. Launch: central Berlin, spring season. Transaction: building manager books a four-hour visit; residents reserve slots. Supply: 18 independent mechanics in network. Demand: 120 property managers reachable through an association. Model: 12% fee, managed payment, minimum eight bookings per visit. Constraints: EUR 25,000 launch budget, mechanic insurance verified, and cancellations must be handled centrally.

## Example output

The plan narrows launch to five adjacent districts and one repeatable repair-day format. Supply is pre-qualified and scheduled before manager acquisition; the marketplace manually batches resident demand until eight slots are reached. Core metrics are building fill rate, days to minimum bookings, mechanic utilization, cancellation rate, repeat building bookings, and contribution after support. Expansion waits until 70% of proposed days fill within ten days.