📥 TL;DR — Want the complete playbook? This article covers the core framework. The full guide includes 50 interview questions, 5 tested scripts, response analysis templates, and a 30-day system to find your first 100 paying users.
→ Get the Customer Discovery Playbook — €12, instant PDF · 30-day refund
Most founders run customer discovery interviews wrong. They ask hypothetical questions and get hypothetical answers. They pitch their idea and get polite feedback. They walk away feeling validated — and build the wrong thing anyway.
The problem isn't effort. It's interview design.
The Question That Changes Everything
Stop asking: "Would you use this?"
Start asking: "Tell me about the last time you struggled with X."
The first question activates optimism bias. People imagine a future where they might use your product. They're polite. They say yes.
The second question accesses memory. Real behavior. Actual pain. The specifics you need to build something people will actually pay for.
This single shift — from hypothetical to timeline-based — is what separates founders with 12 pivots from founders who ship the right thing first.
The 5 Questions You Should Ask in Every Interview
These questions work regardless of your market:
1. Walk me through the last time you had to deal with [problem].
Gets you the real workflow, not the idealized one.
2. What did you try first? What happened?
Reveals competing solutions and their failure modes.
3. How did it end up getting resolved?
Shows whether they actually solved it — or learned to live with it.
4. What did that cost you — in time, money, frustration?
Establishes whether the pain is worth paying to fix.
5. If you had a magic wand, what would the ideal outcome look like?
The only hypothetical worth asking — and only after you understand the real problem.
Why Most Customer Discovery Fails Before It Starts
Talking to the wrong people
Your mom will validate your idea. Your Twitter followers will validate your idea. Your co-founder will validate your idea.
None of them are your customer.
Rule: Only interview people who have actively tried to solve the problem you're targeting. Not people who "might have" the problem. People who have already paid (time, money, or both) to address it.
Pitching instead of listening
The moment you describe your solution, the interview is over. You've told them what to validate. They'll tell you what you want to hear.
Interview rule: No pitching. Not even a hint. Your job is to understand the problem, not to sell the solution.
Confirmation bias in analysis
After 10 interviews where 7 people said "yes, this is a real problem," founders ignore the 3 who said "it's annoying but not urgent." The 3 dissenters often carry more signal than the 7 who agreed.
Always go back and read the no's.
The 30-Day Customer Discovery System
Week 1 — Problem hypothesis
Write down your assumptions. Not your product features — your assumptions about the problem. What do you believe is true about who has it, how they experience it, and what they've tried?
Week 2 — First 5 interviews
Find people who've already tried to solve the problem. LinkedIn, Reddit, industry Slacks, direct DM. Ask for 20 minutes to "understand how people deal with [problem] — no pitch, no agenda."
Week 3 — Pattern finding
After 5 interviews, look for repeated phrases. The same vocabulary appearing in 3+ interviews = signal. Build a simple response matrix: [pain point × frequency × intensity].
Week 4 — Validation sprint
Run 5 more interviews, but now test your problem framing. "Based on what I've heard, the core pain is [X]. Does that match your experience?" If 7/10 say yes without prompting you to change the framing — you have problem-market fit. Build.
Finding Your First Interview Subjects
Method 1: Request threads
"I'm doing research on [problem domain] — would anyone be willing to do a 20-minute call? No pitch, just listening." Post this in relevant Subreddits, Discord servers, LinkedIn groups. Conversion rate: ~5%.
Method 2: Competitor review mining
Read 1-star and 2-star reviews of competing products. Every complaint is a potential interview subject. Find them on LinkedIn, send a personalised message referencing their specific complaint.
Method 3: Job posting analysis
Companies hire people to solve problems. Find job descriptions mentioning your target problem. The hiring manager is your ideal customer.
What Good Interview Notes Look Like
Don't write "she said she likes the idea." That's interpretation.
Write: "She said: 'Every time I have to do X, I spend 3 hours pulling data from different places. Last week it cost me a client call because I wasn't prepared.'"
Quotes. Specific time references. Emotional intensity markers. That's the raw material for a product that sells itself.
📥 Get the Complete Playbook
The 5 questions above work. But they're 5 of 50 in the full playbook.
Customer Discovery Playbook for Makers — €12
Includes:
- 50 interview questions organised by stage (problem, solution, pricing, buyer psychology)
- 5 tested scripts (cold DM, warm intro, competitor customer, forum post, email)
- Response analysis template (copy-paste into Notion or spreadsheet)
- The 30-day week-by-week system above, fully detailed
- The 3 red flags that mean "stop building, pivot now"
30-day money-back guarantee. Instant PDF download. One-time payment.
Top comments (0)