A ready-to-use script for customer discovery conversations, with the questions to ask, the traps to avoid, and a note-taking template so every interview produces comparable insights.
Customer discovery interviews help you learn how people experience a problem today. The goal is to learn, not to sell. Use this script for 20–30 minute conversations and adapt the wording to your market.
"Thank you for your time. I'm researching how [type of people/companies] handle [topic]. I'm not selling anything today. There are no right or wrong answers, and the most helpful thing you can do is tell me honestly how things work for you. Is it okay if I take notes?"
| Avoid | Why | Ask instead |
|---|---|---|
| "Would you use a product that...?" | People are optimistic about the future and polite to you | "When did you last try to solve this?" |
| "Do you think this is a good idea?" | Invites compliments, not facts | "What have you tried so far?" |
| "How much would you pay for this?" | Hypothetical prices are unreliable | "What do you spend on this today?" |
| Leading questions ("Isn't it annoying when...?") | You put words in their mouth | "How do you feel about the current process?" |
| Pitching your solution early | The rest of the interview becomes feedback on your pitch | Keep the solution for a separate follow-up |
Other good habits: let silences last a few seconds, ask "why?" and "can you give me an example?" often, and talk much less than the interviewee.
Copy this block for every interview so notes stay comparable:
Interview #:
Date:
Name / role / company (or anonymised ID):
Segment match: Yes / Partial / No
Context (1–2 lines):
Last time they faced the problem:
Steps they took:
Biggest frustration (use their exact words):
Frequency:
Current solution and its cost (time / money):
Have they paid for a solution? Which?
Strong signals (emotion, spending, workarounds):
Surprises / things that challenge our assumptions:
Referrals offered:
Follow-up agreed:
Assumption tested → Supported / Not supported / Unclear
A useful sign that you have interviewed enough people in one segment is when new conversations stop surprising you and you can predict the answers.
A day-by-day plan to test whether a real problem exists, whether people will act on it, and whether your idea deserves more of your time, before you write a line of code.
OpenA practical slide-by-slide outline for an early-stage pitch deck, with the question every slide must answer, what to include, and common mistakes to avoid.
OpenA fill-in worksheet to define the smallest version of your product that tests your riskiest assumption, separating must-haves from later features and setting a clear success metric and timeline.
Open