Business idea validation

Validate the painful event before validating the product idea

People are generous with opinions about a future product. Ask instead about the last time the problem happened, what they did, what it cost, who approved a purchase, and what they have already tried. Decide in advance which answer would make you narrow, change, continue, or stop.

Good fit for

  • The idea is based mainly on personal intuition or friend feedback
  • Potential users praise the concept but make no commitment
  • The founder is deciding which customer segment feels the pain most
  • Another build cycle depends on an untested buyer assumption

Not the right fit for

  • A regulated product that requires formal clinical, legal, or safety validation
  • A mature product whose problem is retention rather than initial demand
  • A market forecast that needs audited financial or industry data

What changes the answer

Match the next move to the real bottleneck

Past behavior beats future enthusiasm

A recent event exposes the steps, cost, urgency, and workaround that hypothetical questions hide.

A costly workaround is stronger than interest

Time, money, risk, repeated manual work, and political effort show that the problem already changes behavior.

Define the decision before the interview

Write what evidence would change the segment, offer, price, solution, or decision to continue before hearing flattering answers.

Produce the first result

Open the path that creates the needed output

Separate the adjacent questions

Related problems need different answers

Questions people ask before choosing a path

How many interviews do I need to validate a business idea?

There is no universal count. Begin with a narrow segment and repeat the same core questions until behavior patterns and contradictions become visible; one enthusiastic interview is not a market.

What questions should I ask to validate a startup idea?

Ask about the last occurrence, current steps, workaround, consequence, money or time spent, decision process, alternatives tried, and what happened next.

Does a waitlist validate an idea?

A waitlist validates willingness to share contact information. Payment, a deposit, a pilot, repeated usage, or another costly action is stronger evidence.

Should I build an MVP before customer interviews?

A rough artifact can make a workflow easier to discuss, but it should not replace questions about current behavior. Build only enough to test the next risky assumption.

Tell us which problem should get the next Program cycle.

Choose up to three topics. The results guide product work, Program releases, and coach recruitment.

Choose my topics Coach this topic