Skip to content
Idea Validation12 min read

Customer Discovery Interviews: The Complete Guide for First-Time Founders

Share

Everyone tells first-time founders to "talk to customers." Nobody tells them how.

I've coached hundreds of founders through Startmate and in my own practice. The number one thing I look for when reviewing accelerator applications isn't revenue, traction, or even the idea itself. It's customer obsession. Have you actually sat down with the people you're building for and listened?

But here's what I've noticed: even founders who do customer interviews often do them badly. They pitch their product. They ask leading questions. They interview their friends. They do three interviews and declare the problem validated. Or worst of all - they send out a survey and call it customer discovery.

As Richard Feynman put it: "The first principle is that you must not fool yourself - and you are the easiest person to fool."

Customer interviews done badly are just an expensive way of fooling yourself. This guide is the playbook for doing them properly.

The Green Flag vs The Red Flag

After reviewing hundreds of accelerator applications, I can tell within thirty seconds whether a founder has done real customer discovery or is faking it.

The red flag: "We did 10 customer interviews" or "We sent out a survey to 200 people." Surveys are almost always a red flag. They give you data that feels scientific but is usually garbage - people tick boxes differently than they behave. And "10 interviews" as a one-off exercise is better than nothing, but it's not customer obsession. It's a checkbox.

The green flag: The founder talks to customers every single day. Not as a formal exercise. Not as a scheduled "customer discovery sprint." As part of how they work. They're spending time with customers wherever those customers actually work or live. They're running a community. They're at the events. They're on the support calls. They're in the Slack channels.

When customer discovery is just part of your workflow - woven into the fabric of how you operate - you don't need structured interviews in the same way. You're learning constantly, in real time, from real behaviour.

But you have to start somewhere. And for most first-time founders, that means learning how to have these conversations properly. So let's break down the mechanics.

Before the Interview: Who to Talk To

The biggest mistake founders make isn't asking bad questions. It's talking to the wrong people.

Your mum thinks your idea is brilliant. Your best friend says they'd definitely use it. Your co-worker nods along politely. None of these people will give you the truth, because they have a relationship with you that's more important to them than your startup idea. This is exactly why Rob Fitzpatrick wrote The Mom Test - even your mum will tell you your idea is great, and she's the last person you should trust for honest feedback.

You need to talk to strangers. Specifically, strangers who match your target customer profile and who are currently experiencing the problem you're trying to solve.

Here's how to find them:

1. Go where they already hang out. If you're building for small business owners, join Facebook groups, Reddit communities, and LinkedIn groups where they gather. If you're building for parents, go to the school pickup line. If you're building for tradespeople, visit the supply store at 6am. As Twitter's ex-VP Product says, you need to "get in the van" - go to where customers naturally are, not drag them into your conference room.

2. Use your network as a bridge, not a source. Don't interview your friends. Ask your friends to introduce you to people who fit your target profile. "Hey, do you know anyone who runs a small accounting firm? I'm doing some research and would love to pick their brain for 20 minutes." Second-degree connections are gold - warm enough to say yes, distant enough to be honest.

3. Cold outreach works better than you think. Australian founder Nathan Merzvinskis (Startmate mentor, founder of Freckle) booked 22 meetings from 250 leads in five days using a simple two-email system. His follow-up email generated 17 of those 22 meetings. The lesson: don't overthink it. Send the message. Follow up once. Most people are happy to chat for 20 minutes if you're genuinely curious about their problems.

4. Offer to share your findings. People are more likely to give you time if they get something back. "I'm interviewing 20 founders about their hiring challenges - happy to send you the summary of what everyone said." Now you're giving value, not just extracting it.

Aim for 5-8 interviews in your first round. Not 2. Not 50. Five to eight gives you enough pattern recognition to spot themes without drowning in data.

The Questions That Actually Work

I covered this in depth in how to validate your startup idea, but the core principle bears repeating: never ask people about the future. Only ask about the past.

People are terrible at predicting their own future behaviour. They'll tell you what you want to hear, not what's true. So instead of "Would you use an app that does X?" ask "Tell me about the last time you dealt with [problem]. Walk me through what happened."

Here's the interview structure I teach every founder, informed by The Mom Test, YC's Gustaf Alstromer, and Eric Migicovsky's Startup School talk:

Opening (2 minutes) "Thanks for chatting. I'm researching how [type of person] deals with [problem area]. There are no right or wrong answers - I'm just trying to understand your experience."

The Story (10-15 minutes) One question to start, then follow the thread:

"Tell me about the last time you dealt with [problem]. What happened?"

Follow up with: - "What happened next?" - "Why did you do it that way?" - "What was the hardest part?" - "How long did that take?"

The magic is in the follow-ups. The first answer is always surface-level. The fifth follow-up is where the real pain lives. Eric Migicovsky's framework from Pebble nails this: ask "Tell me about the last time...", "Why was this hard?", and "What have you done to try to solve this?" If they haven't tried anything, the problem isn't burning enough.

Current Solutions (5 minutes) - "What are you currently doing to solve this?" - "What have you tried that didn't work?" - "What have you already spent - time or money - trying to fix this?"

What they've already spent is more predictive than what they say they'd spend. If someone has cobbled together spreadsheets, three apps, and a manual workaround, you've found real pain.

The Magic Wand (3 minutes) - "If you could wave a magic wand and change one thing about how you deal with this, what would it be?"

This reveals their priority, not yours. The answer often surprises founders.

Close (2 minutes) - "Is there anything else about this that I should have asked?" - "Who else should I talk to about this?"

That last question is your referral engine. Every good interview should generate 1-2 more interviews.

IDEA VALIDATOR

Test your idea before you build it

Score your startup idea across 6 dimensions using frameworks from YC, Sequoia, and Blackbird. The Problem score is free - see if the pain point your customers described is worth building for.

Validate your idea

The Deadly Sins of Customer Interviews

The single worst customer interview mistake I've seen - and I've seen it dozens of times - is founders who literally pitch to the customer and then ask whether they would buy.

That's not an interview. That's a sales call with extra steps. And the answer is always "yeah sounds great" because people are polite and you've just spent ten minutes telling them how excited you are about your idea. What are they going to say?

Here are the five deadly sins:

Sin #1: Pitching instead of listening. You're there to learn, not sell. The moment you start explaining your solution, the interview is contaminated. They'll either agree to be polite or give you feedback on your solution instead of telling you about their problem.

Sin #2: Asking hypothetical questions. "Would you pay $10/month for this?" is worthless. "What's the most you've ever paid for a tool like this?" is useful. Nathan Merzvinskis wrote a great piece on pricing discovery surveys - using Van Westendorp's four-question method instead of a single "what would you pay?" question. Past behaviour, not future intentions.

Sin #3: Talking more than 30% of the time. If you're doing more than a third of the talking, you're doing it wrong. Your job is to ask short questions and then shut up. Uncomfortable silences are your friend - people fill them with truth.

Sin #4: Only interviewing people who are easy to find. Your first instinct is to interview friends, family, and people who respond quickly. Those are the wrong people. The people hardest to reach are often your actual target customers.

Sin #5: Stopping after three interviews. Three interviews give you three opinions. That's not a pattern - it's a coincidence. You need at least five to start seeing themes, and ideally eight to ten before making any major product decisions.

The antidote to all five: remind yourself before every interview that you are a detective, not a salesperson. Your job is to uncover truth, not confirm what you already believe.

Making Sense of What You Heard

This is where most founders drop the ball. They do the interviews, feel good about them, and then... nothing. No synthesis. No structured analysis. Just a vague feeling that "people seemed interested."

Vague feelings don't build products. Patterns do.

And here's where Feynman's principle becomes critical. "The first principle is that you must not fool yourself - and you are the easiest person to fool." You will unconsciously filter what you heard to match what you wanted to hear. Your brain will amplify the positive signals and downplay the lukewarm ones. This is human nature, not a character flaw. But you need a system to counteract it.

Here's my synthesis process:

Step 1: Transcribe everything Use your recordings. Upload them to an AI transcription tool - Granola (which I love for this), Otter, or just dump the audio into Claude. You want the actual words, not your memory of the words.

Step 2: Let AI find the patterns This is where AI-assisted discovery becomes genuinely powerful. Feed all your transcripts to an AI and ask: "What are the top 3 pain points across these interviews, ranked by frequency? What surprised you? Where do the interviewees disagree?"

The reason AI is so valuable here is that it can't lie to itself. You can. You will. AI will give you the patterns as they actually are - not as you wish they were. It will flag the interviewee who said "I probably wouldn't pay for this" that you conveniently forgot. It will notice that 4 out of 6 people described a completely different pain point than the one you're building for.

Step 3: Build the pattern grid Create a simple table:

ThemeInterviewee 1Interviewee 2Interviewee 3...
Time spent on problem3hrs/week"half my Monday"5hrs/week...
Current solutionSpreadsheetPaper + penTried 2 apps...
Biggest frustrationAccuracyRemembering to do itTeam doesn't follow process...
Money spent trying to fix$0$50/month on app$200 on consultant...

When you see the same theme in 4 out of 6 interviews, that's a signal. When you see it in 6 out of 6, that's a foundation to build on.

Step 4: Write the one-page summary One page. Not ten. Not a slide deck. One page: - The top 3 pain points (ranked by frequency and intensity) - The most common current solution (this is who you're really competing with) - The single biggest surprise (this is usually your unique insight) - What you still don't know (this becomes your next round of interviews)

Teresa Torres' Opportunity Solution Trees are a great framework for mapping insights to product decisions if you want to go deeper.

How Many Interviews Is Enough?

Founders always ask me this. The answer is simple: you've done enough when the interviews get boring.

When the sixth person tells you the same thing as the first five, you've reached saturation. You're hearing patterns, not new information. That's your signal to stop interviewing and start building.

Here's a rough guide:

  • 5-8 interviews: Enough to spot initial patterns and decide if the problem is worth pursuing
  • 10-15 interviews: Enough to have high confidence in your top 3 pain points and start designing a solution
  • 20+ interviews: Only if you're entering a complex market or the first 15 gave you conflicting signals

Most early-stage founders should aim for 10. That's two weeks of work if you do one interview per day. Two weeks of interviews will save you months of building the wrong thing.

But here's what separates good founders from great ones: customer discovery never stops. The best founders I've worked with don't treat it as a phase. They weave it into everything they do. They run communities. They host events. They jump on support calls. They sit in on customer onboarding sessions. They use their own product every day - as Nathan Merzvinskis puts it, they become the voice of the customer by being a power user of their own product.

This is what Steve Blank meant when he coined the term "customer development" in The Four Steps to the Epiphany. Startups aren't small companies executing a known model - they're searching for a model. And the search engine is customer conversations.

At Startmate, customer discovery wasn't just something we told founders to do. It was the core of how we operated. Every single day we interacted with founders, asked them questions, lined up conversations, ran community events. It was natural because it was part of the culture and fabric of the company. That's the level you're aiming for.

Everything else - fundraising, hiring, strategy - is a function of how well you know your customers. When I review accelerator applications, I jump straight to the customer question. Not revenue, not the team, not the TAM. Have you talked to real humans about a real problem? That tells me more about your chances than anything else.

Start this week. Find five people who match your target customer. Send the messages today. Book the calls. Twenty minutes each. Use the structure in this guide.

You'll learn more in those five conversations than in a month of Googling, competitor analysis, and feature planning. That's not motivational fluff. That's what I've seen play out hundreds of times.

Sources and Further Reading

Share

Need help pressure-testing whether the problem you've uncovered is worth building for? The Idea Validator scores your startup idea across 6 dimensions using frameworks from YC, Sequoia, and Blackbird. The Problem score is free.

For the full framework on why customer interviews matter, read how to validate your startup idea.

And if you want to go deeper on the best resources from this article: - The Mom Test by Rob Fitzpatrick - the definitive book on asking the right questions - YC: How to Talk to Users - Gustaf Alstromer's essential lecture - YC: Secrets From Your Customers - Dalton Caldwell and Michael Seibel on non-obvious insights - First Round: Founder's Guide to Customer Discovery - step-by-step tactical playbook - Continuous Discovery Habits by Teresa Torres - the Opportunity Solution Tree framework

Always keen to hear how your interviews go. DM me on LinkedIn with what you learned.

IDEA VALIDATOR

Test your idea before you build it

Score your startup idea across 6 dimensions using frameworks from YC, Sequoia, and Blackbird. The Problem score is free - see if the pain point your customers described is worth building for.

Validate your idea

Top-rated Accelerator on Founder Signal

View all →

Related articles

NEWSLETTER

Batko OS

Writing on startups, leadership, AI, and building a personal operating system.One email, whenever I have something worth saying.

  • Lessons from coaching founders - fundraising, ops, strategy
  • How I use AI to build, write, and think faster
  • Systems for productivity, leadership, and life

4,000+ founders and operators read it. Free. Unsubscribe anytime.