Waitlist or MVP: What Should You Build First?
Build a waitlist first when the riskiest question is demand. Build an MVP first only when the demand is clear and the riskiest question is whether the product can deliver the outcome.
Last updated May 2026
Quick answer: waitlist before MVP
- Waitlist: Best for demand risk
- Use it when you need to know whether the market cares before spending development time.
- MVP: Best for delivery risk
- Use it when customers already want the outcome and you need to prove the product can deliver it.
- Bridge: Use ICP to choose
- The clearer the ICP and pain, the easier it is to know which test comes first.
Choose based on the riskiest assumption
If the risk is 'will anyone care?', start with a waitlist. If the risk is 'can this product work?', start with the smallest MVP that proves delivery.
Make the waitlist specific
A generic waitlist tests nothing. The page should name the ICP, promise an outcome, and ask for a clear action.
Do not overread signups
Waitlist signups are useful, but they are early signal. Follow with interviews, onboarding questions, or a paid test before overbuilding.
Founder checklist
- Riskiest assumption identified
- ICP and pain stated on the page
- One promise and one CTA
- Follow-up questions for signups
- Decision threshold for building the MVP
Common questions
- Should I build a waitlist before an MVP?
- Yes, if you still need demand evidence. A waitlist is faster than an MVP for testing whether the promise and audience are compelling.
- How many waitlist signups are enough?
- It depends on the market, but the better question is whether the signups match your target ICP and respond to follow-up questions.
- What if nobody joins the waitlist?
- That is useful signal. Revisit the ICP, pain, channel, and promise before assuming the idea itself is dead.
Turn the answer into action
Use Demo Studio to test the promise before building the product.