Customer Discovery Interview Template

What This Template Is For

Customer discovery interviews are the fastest way to learn whether your product idea solves a real problem. But most founders run them wrong. They describe their idea, ask "would you use this?", and hear "yes" from polite people who will never buy. Rob Fitzpatrick's Mom Test principle solves this: talk about the customer's life, not your idea. Ask about past behavior, not future intentions.

This template gives you a structured interview script that follows Mom Test principles. It includes pre-interview preparation, a question flow designed to surface real pain, and a post-interview synthesis framework for turning raw notes into product decisions.

Use this template alongside the Product Discovery Handbook, which covers the full discovery methodology from identifying assumptions to validating solutions. The Founder Fit Assessment helps you evaluate whether you are pursuing the right problem before you invest time in interviews.

For quantitative validation after interviews, the TAM Calculator helps you size the opportunity, and product-market fit indicators help you gauge whether your solution resonates.

How to Use This Template

1. Prepare before the interview. Fill in Part 1 (your assumptions and what you need to learn) before scheduling a single call. If you cannot articulate what you are trying to learn, you are not ready.
2. Use the question script as a guide, not a script. The questions are starting points. Follow the customer's energy. When they lean into a topic, dig deeper. When they give short answers, move on.
3. Never pitch during discovery. The goal is to learn, not to sell. If you describe your product and then ask for feedback, you will get polite lies. Talk about their world, not yours.
4. Take notes during the call. Record direct quotes. Write down specific behaviors, timelines, and dollar amounts. Avoid interpreting during the interview. Interpret afterward.
5. Synthesize after every 5 interviews. Patterns emerge quickly. Use the synthesis framework (Part 4) to identify recurring themes, surprising insights, and evidence that challenges your assumptions.
6. Run 15-20 interviews minimum. Five interviews feel informative but produce false patterns. Fifteen interviews reveal real trends. Twenty interviews give you confidence to act.

The Template

Part 1: Pre-Interview Preparation

Fill this out before your first interview. Revisit it after every 5 interviews.

Target customer segment: [Who are you interviewing? Be specific: role, company size, industry]

Core assumptions to test:

• ☐ Assumption 1: [e.g., "Engineering managers spend 5+ hours/week on scheduling"]
• ☐ Assumption 2: [e.g., "Current tools (Google Calendar, Calendly) do not handle team-wide coordination"]
• ☐ Assumption 3: [e.g., "They would pay $15-25/user/month for a solution"]

Top 3 things I need to learn from this interview:

1. [What specific behavior or pain point am I trying to validate?]
2. [What alternatives have they tried, and why did those fail?]
3. [How much are they currently spending (time or money) on this problem?]

Part 2: Interview Question Script

Opening (2 minutes):

• ☐ "Thanks for making time. I am researching how [target segment] handles [problem area]. I would love to hear about your experience. There are no right or wrong answers."
• ☐ Do NOT describe your product or idea

Context questions (5 minutes):

• ☐ "Tell me about your role. What does a typical week look like?"
• ☐ "What are the 2-3 biggest time sinks in your work right now?"
• ☐ "How does [problem area] fit into your daily workflow?"

Problem exploration (10 minutes):

• ☐ "Walk me through the last time you dealt with [specific problem]. What happened?"
• ☐ "How did you handle it? What tools or process did you use?"
• ☐ "What was the most frustrating part of that experience?"
• ☐ "How often does this come up? Daily? Weekly? Monthly?"
• ☐ "What does this problem cost you in terms of time, money, or missed outcomes?"

Current solutions (5 minutes):

• ☐ "What are you using today to handle this? Walk me through your current setup."
• ☐ "What do you like about your current approach?"
• ☐ "What is broken or missing? If you could fix one thing, what would it be?"
• ☐ "Have you tried other tools or approaches? What happened?"
• ☐ "How much are you paying for your current solution (including time spent)?"

Emotional depth (3 minutes):

• ☐ "On a scale of 1-10, how painful is this problem? Why that number and not higher?"
• ☐ "What would change for you if this problem were completely solved?"
• ☐ "Have you actively searched for a better solution in the past 6 months?"

Closing (2 minutes):

• ☐ "Is there anything about [problem area] that I should have asked but did not?"
• ☐ "Who else on your team deals with this problem? Would they be open to a conversation?"
• ☐ "Thanks for your time. I may follow up with a few more questions. Is email the best way?"

Part 3: Post-Interview Notes

Fill this out immediately after each interview (within 30 minutes while memory is fresh).

Interview #: [1, 2, 3...]

Date: [YYYY-MM-DD]

Interviewee: [Name, role, company, company size]

Duration: [minutes]

Key quotes (direct quotes, not paraphrases):

1. "[Exact words they used]"
2. "[Exact words they used]"
3. "[Exact words they used]"

Problem severity (1-10): [Their self-reported score]

Current solution: [What they use today and what they pay for it]

Behaviors observed (things they DO, not things they SAY):

• ☐ [e.g., "Has tried 3 different tools in the past year"]
• ☐ [e.g., "Spends 45 minutes every Monday morning on manual scheduling"]
• ☐ [e.g., "Built a custom spreadsheet to work around the tool's limitations"]

Surprising insights (things I did not expect):

• ☐ [Insight 1]
• ☐ [Insight 2]

Assumptions validated or challenged:

Part 4: Synthesis Framework (After Every 5 Interviews)

Interviews completed: [X] of [target total]

Pattern tracker:

Willingness to pay signals:

• ☐ [X] of [total] interviewees are actively paying for a partial solution
• ☐ [X] of [total] have searched for a better solution in the past 6 months
• ☐ [X] of [total] described the problem as 7+ out of 10 severity
• ☐ Average reported cost of the problem: $[amount] per [week/month]

Decision checkpoint:

• ☐ Continue building: 12+ of 15 interviews validate the core assumption. Pain is severe (7+/10), current solutions are inadequate, and willingness to pay signals are present.
• ☐ Pivot the solution: The problem is real but the solution direction is wrong. Interviewees want something different from what we planned to build.
• ☐ Pivot the customer: The problem exists but not in our target segment. A different segment reports higher pain and willingness to pay.
• ☐ Kill the idea: Fewer than 5 of 15 interviews validate the problem. Pain is low, current solutions are good enough, or no willingness to pay.

Filled Example: TeamSync (Team Scheduling for Engineering Managers)

Pre-Interview Preparation

Target customer segment: Engineering managers at B2B SaaS companies with 20-100 engineers.

Core assumptions:

1. Engineering managers spend 5+ hours/week on meeting scheduling and coordination
2. Google Calendar and Calendly do not handle cross-team sprint ceremony coordination
3. They would pay $12-20/user/month for automated team scheduling

Sample Interview Notes (Interview #4)

Interviewee: Sarah K., Engineering Manager, 45-person fintech startup

Duration: 25 minutes

Key quotes:

1. "I spend every Monday morning playing calendar Tetris for the entire week. It takes me about an hour just for my team of 8."
2. "Calendly is fine for external meetings. But for internal sprint planning across 3 squads? Forget it. I end up in a group Slack thread negotiating times."
3. "I tried Reclaim.ai for a month. It moved meetings around without telling people, and engineers got upset. I went back to doing it manually."

Problem severity: 7/10. "It is not the worst part of my job, but it is the most pointless part."

Current solution: Google Calendar + Slack polls. Costs ~5 hours/week of her time.

Behaviors observed:

• ☑ Has tried 2 alternative tools in the past year (Reclaim, Clockwise)
• ☑ Built a spreadsheet to track team availability across sprints
• ☑ Delegates some scheduling to a senior engineer (who also dislikes it)

Assumptions validated:

Synthesis (After 5 Interviews)

Decision: Continue building. 4/5 interviews validate core assumptions. Pain is consistent (avg 7.2/10). All interviewees use workarounds, indicating unmet need.

Key Takeaways

• Talk about the customer's life, not your idea. The Mom Test principle prevents polite lies from derailing your strategy
• Ask about past behavior ("the last time you..."), not future intentions ("would you use...")
• Record direct quotes, not paraphrases. Exact words reveal emotional intensity that summaries obscure
• Synthesize after every 5 interviews. Look for patterns in behavior and spending, not just complaints
• 15-20 interviews minimum before making build decisions. Five interviews produce false patterns

About This Template

Created by: Tim Adair

Last Updated: 3/4/2026

Version: 1.0.0

License: Free for personal and commercial use