Why customer discovery comes first

The cheapest way to find out you are wrong. Twenty conversations cost two weeks; building the wrong thing costs a year.

What is it?

Customer discovery is talking to people who have the problem, before and while you build, to find out what is actually true rather than what you assume.

It is not market research, not usability testing, and not selling. It is finding out how someone's day actually works.

Why does a founder care?

Because the most expensive thing a founder can do is build something nobody wants, and it is also the easiest thing to do accidentally.

Twenty conversations take about two weeks. Building the wrong product takes six months to a year and produces no information — you learn only that nobody signed up, not why.

Discovery converts a year-long expensive experiment into a two-week cheap one.

Example

A founder is certain that freelancers need better invoicing software. They plan four months of building.

Instead they do fifteen interviews first. What they find:

  • Invoicing is fine. Everyone uses an existing tool and nobody complains about it.
  • Chasing late payments is the real pain — mentioned unprompted in 12 of 15 conversations.
  • Most people track chasing in their head or a notes app, and forget.
  • Three said they had lost money entirely by forgetting to chase.
  • When asked what they had tried, two had paid for a tool and stopped using it because it needed manual data entry.

    • The product that comes out of this is completely different from the one they were about to build — and the last point tells them the single thing that must not be true of it.

    Cost: two weeks. Value: four months not wasted, plus a much better product.

    The common mistake

    First-time founders often skip discovery because they are sure they already know — particularly when they have the problem themselves. Having the problem makes you one customer, and often an unusual one. Your workarounds, tolerance and budget are not representative.

    The second mistake: treating discovery as a phase that ends. Discovery continues for the life of the company. The founders who keep talking to customers at scale are the ones who keep building the right things.

    How it works

    Step 1: Write down what you believe

    Before any conversation, list your assumptions about the problem, who has it, and what it costs them. This makes being wrong visible.

    Step 2: Find ten people who have it

    Not friends being supportive. People in the actual situation. Your own network, communities, cold outreach, introductions.

    Step 3: Ask about the past, not the future

    'Tell me about the last time this happened' produces facts. 'Would you use this?' produces politeness.

    Step 4: Do not pitch

    The moment you describe your solution, the conversation becomes about your feelings and the data stops being useful.

    Step 5: Write it up within an hour

    Memory rewrites conversations towards what you hoped to hear. Notes within the hour are far more reliable.

    Step 6: Look for patterns after ten

    One conversation is an anecdote. Ten is a pattern. Twenty is a decision.

    When to use this

    Before building anything, and continuously after. It never stops being valuable.

    When not to use it

    Do not use interviews to test a UI — that is usability testing, a different technique with a different script. And do not use them to decide details customers cannot know, like architecture.

    Do this now

    Apply this to your own startup in My Full Journey (free account).