Customer Discovery Interview Guide & Script

Why this matters

Customer discovery interviews are the fastest way to learn what real people struggle with and whether they will pay for a solution. Done well, short interviews uncover problems you hadn’t noticed, prevent wasted product effort, and point to the smallest, highest-confidence experiments you can run next. Done poorly, they confirm assumptions and consume time and cash.

Before the interview — define clear learning goals

Start with 1–3 specific questions you need answered. A clear learning goal keeps interviews focused and lets you compare answers across interviews. Examples:

• Do local coffee shops struggle with inventory spoilage more than ordering complexity?
• Would independent landscapers pay $X/month for scheduling automation?
• Which part of onboarding causes the most churn: paperwork, scheduling, or training?

Write your goals as testable hypotheses or decision points. For each goal, decide what evidence would increase or decrease your confidence (e.g., “If 6 of 8 say X is painful and they currently workaround Y, we’ll prioritize feature A”).

Recruit 5–10 target customers (practical rules)

Rapid discovery favors depth over breadth. Aim for 5–10 interviews with real target users or buyers. Keep these rules in mind:

• Screen for fit: create a 1–3 question screener tied to your learning goal (role, frequency of task, recent experience).
• Prefer recent experience: talk to people who faced the problem in the last 1–3 months.
• Mix existing and prospective customers if relevant, but label them in your notes.
• Offer a small incentive (gift card, discount, or product trial). Be transparent about time required (20–40 minutes).

Recruit channels: existing customers, LinkedIn messages, community forums, warm introductions, or local events. Keep your outreach short: one sentence on why you’re asking + clear ask + time commitment.

Run the interview — use non-leading questions and listen

Goal: surface behaviors, context, and consequences, not opinions. Use open-ended prompts, follow-up WHY/WHEN/SHOW ME questions, and avoid pitching.

Practical structure (30–40 minutes)

1. Warm welcome (2–3 min): introduce yourself, remind them this is a learning conversation, get permission to record or take notes.
2. Context & recent example (5–8 min): ask them to tell a recent story about the task or problem. Stories beat hypotheticals.
3. Probe for behavior (10–15 min): dig into steps, tools used, frequency, time spent, workarounds, and costs—both money and friction.
4. Prioritization & trade-offs (5–8 min): what would make them change behavior? How urgent is the problem? Would they pay or trade for relief?
5. Close (2–3 min): ask for referrals, confirm contact permission, and thank them.

Sample script (use as a template, not a checklist)

Intro: “Thanks for joining. I’m talking to people who [describe role/problem]. I want to understand how you handle [task/problem] so we can learn—this isn’t a sales call. Can I record? This will take about 30 minutes.”

Context: “Tell me about the last time you [experienced the problem or did the task]. What happened from start to finish?”

Probe: “Walk me through each step. What tool did you use? Who else was involved? How long did that take? What did you wish worked differently?”

Consequences: “What happens if you don’t solve this? Has it cost you time or money recently? How do you currently cope?”

Willingness to act: “Have you tried buying anything to solve this? Would you consider paying for a solution—why or why not?”

Close: “Who else should I talk to? Would you be open to a short follow-up if we want to test an idea?”

Dos and Don’ts

• Do ask for concrete recent examples (“the last time…”).
• Do follow interesting threads with “Tell me more” and “Why?”
• Don’t ask “Would you use X?” or pitch during discovery.
• Don’t ask leading yes/no questions early on.

Note-taking and recording

Record when possible, but always take a short typed summary immediately after each interview: context, key quotes, pain points, existing workarounds, and any explicit willingness-to-pay statements. Use a shared template so different interviewers produce comparable notes.

Synthesize outcomes into prioritized problems

After 5–10 interviews, run a short synthesis session (30–60 minutes) with your team or 1–2 peers:

1. Affinity map: transfer quotes and observations onto sticky notes (digital or physical) and group them by theme.
2. Identify problem statements: convert themes into clear problem statements in the form "Who has problem X when doing Y causing Z".
3. Score each problem: frequency, severity, willingness-to-pay/ease of monetization, and alignment with your capabilities.
4. Choose 1–2 prioritized problems to prototype and design the smallest possible test (concierge service, landing page, mock-up interview, or paid pilot).

Document decisions: for each prioritized problem, capture the evidence, remaining uncertainties, and the next experiment to reduce those uncertainties.

Follow-up and validation

Share draft prototypes or pricing ideas with interviewees for quick validation. Use the same discovery mindset—seek evidence, not validation. Iterate on the prototype and measurement plan until you have a clear go/no-go decision.

Tips for common situations

• Busy operators: offer shorter 15-minute sessions and focus on the single most recent example.
• Multiple stakeholders: interview users and buyers separately and compare priorities.
• Quantitative signal needed: combine discovery with a short survey that tests prevalence after qualitative patterns emerge.

Quick checklist before you start

• Clear learning goals written down.
• 5–10 screened interviewees scheduled.
• Consent to record and a simple note template ready.
• Sample script and probes printed or open on your device.
• Plan for a 60-minute synthesis session after interviews.

Good discovery is generous: focus on listening, learning, and leaving people feeling heard. When you treat interviews as a pathway to clearer evidence, you’ll reduce wasted effort and choose growth moves that actually work.