Product Development

    Customer Discovery: How to Talk to Users Before You Build Anything

    The fastest way to build something nobody wants is to skip customer discovery. Here's the exact process for conducting interviews that generate real insights — not just validation of your assumptions.

    LVL1 Team
    May 26, 2025
    7 min read

    You have an idea. You're excited. Every instinct says "build it." The most disciplined thing you can do is pause, pick up the phone, and talk to 50 potential users before writing a single line of code.

    Why Customer Discovery Fails

    Most founders do customer discovery wrong. They call it "research" but what they do is pitch — asking "Would you use something like this?" and counting the yeses. This is worse than useless because:

    • People are polite. They say yes to avoid awkward conversations.
    • Hypothetical behavior doesn't predict real behavior.
    • You learn nothing you didn't already believe.

    The right approach comes from the Mom Test (Rob Fitzpatrick): ask questions your mom couldn't lie to you about. Focus on the past, not the future.

    The Customer Discovery Interview Framework

    Who to Talk To

    - 50 minimum before building anything - Target your ICP exactly (don't talk to friends if they're not your customer) - Mix of people who already pay for similar solutions and those using workarounds

    What to Ask

    Opening (get context): - "Walk me through a typical day / week as it relates to [problem area]" - "How do you currently handle [the problem]?" Go deeper (understand the pain): - "What's the hardest part of that process?" - "How much time does that take you?" - "What have you tried to fix it?" Understand real behavior: - "Can you show me how you do it now?" (screen share is gold) - "How much did that workaround cost you?" - "The last time this went wrong, what happened?" What NOT to ask: - "Would you use a product that does X?" - "How much would you pay for this?" - "What features would you want?"

    After the Interview

    - Transcribe or take detailed notes immediately - Tag insights by theme: pain points, current solutions, willingness to pay signals - Look for patterns across 20+ interviews

    The Insights That Actually Matter

    You're listening for:

    1.Frequency: How often does this problem occur?

    2.Intensity: How frustrated are they? (Watch body language / tone)

    3.Current spend: Are they already paying money to solve this?

    4.Urgency: Have they actively sought a solution recently?

    Turning Insights Into Features

    After 50 interviews, you should know:

    • The top 3 pain points (ranked by frequency AND intensity)
    • The exact language customers use to describe their problem (use it in your copy)
    • Who in the organization owns the problem and the budget
    • What "good" looks like to them

    This becomes your entire product roadmap and your first marketing copy.

    [Lvl1 Accelerator helps founders structure their customer discovery before they build](https://lvl1accelerator.com/accelerator) — join a cohort where experienced mentors guide your research process.

    Tags:
    customer discovery
    user research
    startup research
    product market fit
    user interviews