Why Validation Comes Before Building

The most expensive mistake a founder can make is spending months — or years — building a product only to discover the market doesn't want it. Post-mortems of failed startups consistently identify "no market need" as one of the top causes of failure. Fortunately, this is a preventable mistake.

Validation is the process of testing your core assumptions about customers, problems, and solutions before committing significant resources. Done well, it saves time, money, and morale.

Step 1: Define Your Core Assumptions

Every startup idea rests on a set of beliefs about the world. Your job is to make these explicit. Common assumptions include:

  • A specific group of people has this problem
  • The problem is painful enough that they actively seek solutions
  • Existing solutions are inadequate
  • People will pay a specific amount to solve it
  • You can reach these customers through viable channels

Write each assumption down. Rank them by risk — which ones, if wrong, would kill the business entirely? Those are your leap-of-faith assumptions and must be tested first.

Step 2: Talk to Real People (The Right Way)

Customer discovery interviews are the highest-leverage validation tool available. The goal is not to pitch your idea — it's to understand the person's world deeply.

Follow these principles, drawn from the "Mom Test" approach:

  1. Ask about their life and past behavior, not hypothetical futures ("Would you use X?" is a bad question)
  2. Dig into how they currently solve the problem — tools, workarounds, costs
  3. Listen for emotional language — frustration, embarrassment, urgency — these signal real pain
  4. Ask about the last time they experienced the problem in detail

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

Step 3: Build a Minimum Viable Signal (Not a Product)

Before writing code, test demand with lightweight signals:

  • Landing page test: Describe your solution and add a sign-up or waitlist button. Drive traffic with a small ad budget and measure conversion rate.
  • Concierge MVP: Manually deliver the service to early customers before automating. This validates the value proposition, not the technology.
  • Pre-sales: Offer early access at a discounted price. Real payment intent is far more meaningful than verbal enthusiasm.
  • Wizard of Oz test: Build a front-end experience while handling the back-end manually, so customers believe the product is real.

Step 4: Define Your Validation Threshold

Validation without benchmarks is just activity. Before running experiments, define what success looks like:

  • What landing page conversion rate would indicate genuine demand?
  • How many people need to pre-pay before you start building?
  • What retention or engagement metric would confirm real value?

These thresholds keep you honest and prevent motivated reasoning from warping your interpretation of results.

When to Pivot vs. Persevere

Validation often reveals gaps between your initial vision and what customers actually need. This is valuable data, not failure. Use it to:

  • Pivot the customer segment — a different group values your solution more
  • Pivot the problem — a related pain point is more acute
  • Pivot the solution — the same problem has a better-fit answer

The goal of validation isn't to confirm your idea — it's to find the truth, even if it's uncomfortable. Founders who embrace this mindset build companies that last.