Skip to content
App Graveyard
Failure pattern

Marketplace Cold Start

The product needs supply and demand at the same time before either side gets value.

Why it kills apps

Marketplaces often look simple in software and brutal in operations. Without density, users arrive to empty inventory, poor matches, or no response, then leave before the flywheel can begin.

Why vibe coders fall into it

The UI for a marketplace is straightforward to generate, which hides the operational burden. The hard part is usually liquidity, trust, and repeated supply, not cards, filters, or chat.

Symptoms

  • The app needs both buyers and sellers to show up together.
  • Early users cannot get a good match in their location, niche, or timing.
  • The builder spends more time building matching logic than seeding supply.
  • The marketplace works in theory but feels empty in practice.

Prevention checklist

  • Start with one side of the market and manually serve the other side.
  • Constrain geography, category, or use case until matches are dense.
  • Prove successful matches manually before automating the marketplace.
  • Avoid broad browse experiences until inventory feels alive.

Validation questions

  1. 01Which side is harder to acquire and why?
  2. 02Can you manually create 10 successful matches first?
  3. 03What is the narrowest market where inventory can feel dense?
  4. 04What trust signal makes each side willing to transact?
Use this before building

Check whether your idea has this risk.

Run the idea checker before you turn the pattern into code.

Check if your idea has this risk
Use this after building

Find where your page is leaking trust or clarity.

Use the no-crawl app roast when the product exists but the offer is not converting or trust is not landing.

Roast your app for this risk