Why Validation Comes Before Building

One of the most common — and costly — mistakes first-time founders make is building a product nobody asked for. Months of engineering, design, and iteration can be wasted when the real problem was never confirmed in the first place. Validation is the process of testing your assumptions about a market, problem, and solution before committing major resources.

The good news: you don't need a finished product to validate an idea. You just need a clear hypothesis and a willingness to talk to real people.

Step 1: Define Your Core Assumptions

Every startup idea rests on a stack of assumptions. Start by writing them down explicitly. Common assumptions include:

  • A specific group of people has this problem
  • The problem is painful enough that they would pay to solve it
  • Your proposed solution would actually solve the problem
  • You can reach these customers at a viable cost

Rank your assumptions from riskiest to safest. Your validation efforts should tackle the riskiest ones first — usually whether the problem is real and whether people will pay.

Step 2: Get Out and Talk to Customers

Customer discovery interviews are the most underused tool in a founder's toolkit. The goal isn't to pitch your idea — it's to listen and learn. Ask potential customers about:

  • How they currently handle the problem you're solving
  • What frustrates them most about existing solutions
  • How much time or money the problem costs them
  • What they've already tried to fix it

Aim for at least 20 conversations before drawing conclusions. Look for patterns, not one-off opinions.

Step 3: Build a Minimum Viable Product (MVP)

An MVP is the simplest version of your product that lets you test your core value proposition. It doesn't have to be software. Effective MVPs have taken the form of:

  • Landing pages — describe the product and capture emails to gauge interest
  • Concierge services — manually deliver the solution to early users before automating
  • Wizard of Oz tests — simulate a working product behind the scenes with manual effort
  • Explainer videos — Dropbox famously validated demand with a simple demo video before writing code

Step 4: Measure Real Signals

Validation means gathering evidence, not opinions. Look for behavioral signals — actions people take with their time or money. Strong validation signals include:

  • People signing up for a waitlist with their real email
  • Users completing a pre-order or paying a deposit
  • Organic referrals — users telling others without being asked
  • High engagement or repeat usage of a prototype

Verbal enthusiasm ("sounds great!") is a weak signal. Money exchanging hands is a strong one.

Step 5: Know When to Pivot or Proceed

Validation isn't a one-time event. It's a continuous loop of hypothesize → test → learn → iterate. If your tests reveal weak demand or a misunderstood problem, that's valuable information — not failure. A well-timed pivot based on validation data is far less costly than launching a product the market doesn't want.

Key Takeaways

  1. List and rank your riskiest assumptions first
  2. Conduct at least 20 customer discovery interviews
  3. Build the simplest possible MVP to test your core value proposition
  4. Prioritize behavioral signals (payment, signups) over verbal feedback
  5. Treat every result — positive or negative — as useful data

Validation is what separates startups that build something people want from those that build something founders think people want. The earlier you validate, the more time and money you preserve for when it really matters.