Skip to main content
Practical guide

How to Validate a Startup Idea Before Building

A practical way to test assumptions with real people before investing in a product.

Start with the riskiest assumption

A broad question such as ‘Is this a good idea?’ rarely leads to a clear decision.

  • Write down who has the problem, how they solve it today, and what would need to be true for your solution to help.
  • Choose one assumption that could change whether you proceed. Separate demand, usability, and willingness to pay.
  • Define what evidence would cause you to change direction before collecting responses.

Recruit for relevance

The quality of the participants matters more than collecting indiscriminate opinions.

  • Invite people who actually experience the problem, not only friends who want to be encouraging.
  • Be transparent about what you are testing and avoid implying that the product already exists.
  • Keep track of how participants were recruited; convenience samples are not representative of a market.

Ask about behavior, not hypothetical praise

People can sincerely like an idea without ever using or buying it.

  • Ask when they last experienced the problem and what they did about it.
  • Present a concise concept and ask what seems useful, confusing, or missing.
  • Avoid leading questions such as ‘Wouldn't this save you time?’

Decide what happens next

Treat feedback as evidence to investigate, not a vote that automatically determines the roadmap.

  • Look for repeated pain points and contradictory explanations.
  • Distinguish observed past behavior from predictions about future behavior.
  • Follow up with interviews, prototype tasks, or real-world demand tests when the decision requires stronger evidence.

Related workflows

Use these resources to put the guidance into practice.

Turn a question into a validation

Create a focused validation, share it with relevant participants, and review their responses.