FOUNDER & VENTURE Q&A SOURCE-REVIEWED

What should a founder validate before building a product?

Test the user, recurring problem, current workaround, buyer path and value hypothesis before committing to a larger build.

SHORT ANSWER

Start by validating a narrow problem and the people affected by it. A founder should understand the current workflow and alternative, why the issue matters, who can authorize a change, and what evidence would show that a proposed solution improves an outcome. The NSF’s I-Corps approach emphasizes customer discovery with potential customers and stakeholders; SBA guidance also stresses a defined target market and competitive analysis.

Direct answer

Start by validating a narrow problem and the people affected by it. A founder should understand the current workflow and alternative, why the issue matters, who can authorize a change, and what evidence would show that a proposed solution improves an outcome. The NSF’s I-Corps approach emphasizes customer discovery with potential customers and stakeholders; SBA guidance also stresses a defined target market and competitive analysis.

A practical sequence

  1. Name a segment, use case and job in plain language.
  2. Collect recent behavioral examples and observe the process where appropriate.
  3. Identify competing products, manual workarounds and the cost of doing nothing.
  4. Clarify user, buyer, procurement and switching constraints.
  5. Test the riskiest assumption with the smallest credible experiment.

Limits and boundaries

A founder should distinguish evidence from assumption and record sample limitations. Positive feedback, a waitlist or a prototype demo may not predict purchase or repeat use.

Sources and review

General education, not individualized business, investment, legal, technical or regulatory advice. Reviewed 31 October 2026. Context and requirements vary; consult qualified specialists where appropriate.