08TemplateFoundational
Customer interview guide
A printable prep checklist, opening script, question bank, and note-taking template for customer discovery interviews that produce facts instead of compliments.
By Khalel Dumaz, Founder of Vora IQ
Published
The short answer
Use this guide to prepare for, run, and record a 20- to 30-minute customer discovery interview. It includes a prep checklist, an opening script, questions grouped by what you need to learn, questions to avoid, and a note-taking structure that keeps facts separate from your interpretation.
- Level
- Foundational
- Reading time
- 4 minutes
- Updated
- Sources
- Editorial analysis
- Useful for
- All business types
This guide is the working companion to how to run customer interviews that get honest answers, which explains the reasoning behind each part. Copy it, print it, and adapt the wording to your customers. Replace anything in [square brackets].
Before the interview
- Write down the one thing this round of interviews needs to answer.
- Confirm the person matches your customer description and has dealt with the problem in the last few months.
- Schedule 20 to 30 minutes, by phone, video, or in person.
- Ask permission to take notes or record, and note their answer.
- Pick 6 to 8 questions from the list below. You won't get to all of them.
- Decide on a small next step to ask for at the end, such as an introduction or a follow-up call.
- Open your note-taking template before the call starts.
- Block 15 minutes after the call to write up your notes.
Opening script
Thanks for making time. I'm [name], and I'm researching how [type of customer] handle [problem area]. I'm not selling anything today. I'm trying to understand how this works in real life, so there are no right or wrong answers. The more specific you can be, the more it helps.
Is it OK if I take notes? [If true: I won't share anything you say with your name attached.]
Then go straight to the first context question. Don't describe your idea.
Questions to ask
Pick from each group. Follow up on interesting answers with "Why?", "Can you give me an example?", or "What happened next?"
Context: understand their situation
- Tell me a bit about your role and what a typical [day or week] looks like.
- Where does [problem area] fit into that?
The problem: get a specific story
- Tell me about the last time [problem] happened. What was going on?
- What did you do next?
- How often does this come up?
Cost and workarounds: measure the pain
- What did that cost you, in money, time, or hassle?
- How do you handle it today? What do you use?
- What have you tried that didn't work? Why did you stop?
- If you've never tried to fix it, why not?
Buying: understand how decisions get made
- The last time you paid for something to deal with this, how did you choose it, and who else was involved?
- Have you ever switched from one way of handling this to another? What made you switch?
Close: ask for a next step
- Who else do you know who deals with this? Would you be willing to introduce me?
Questions to avoid
| Avoid | Why |
|---|---|
| Would you use a product that does [X]? | It asks for a prediction, and people are generous when they predict. |
| How much would you pay for [X]? | A hypothetical price isn't a commitment. Ask what they spend now. |
| Don't you hate it when [problem]? | It's leading. It tells them the answer you want. |
| What do you think of my idea? | It turns the interview into a request for encouragement. |
| Would [feature] be useful? | Almost any feature sounds useful in the abstract. |
Closing the interview
This has been really helpful. Is there anything I should have asked but didn't? [Pause.] Would it be OK to follow up if I have another question?
If they offered an introduction or another next step, confirm the details before you hang up.
Note-taking structure
Copy this for each interview. Keep facts and your interpretation in separate sections, so you can always see what people actually said.
| Section | What to write |
|---|---|
| Interview details | Date, name or code, role, and how you found them |
| Their situation | The context that shapes the problem for them |
| Last time it happened | The specific story, in order |
| Frequency and cost | How often it happens, and what it cost in money, time, or hassle, in their words |
| Current solution | What they use now, what it costs, and what they dislike about it |
| Things they've tried | What they tried, and why they stopped |
| Exact quotes | Phrases worth keeping word for word |
| Commitments | Introductions, follow-ups, or other next steps they agreed to, and whether they followed through |
| My interpretation | What you think it means, kept apart from the facts above |
| Surprises | Anything that contradicts what you expected |
After every five interviews
Read your notes side by side and count how often each problem, workaround, and cost comes up. When one pattern clearly repeats, use how to validate a business idea before spending money to turn it into a commitment test.
Questions founders also ask
Frequently asked questions
How many questions should you ask in a customer interview?
Pick 6 to 8 questions for a 20- to 30-minute customer interview. You won't get to all of them, and you'll want time to follow up on interesting answers with "Why?", "Can you give me an example?", or "What happened next?" Choose from each group: context, the problem, cost and workarounds, buying, and a close that asks for an introduction or another next step.
Should you record customer interviews?
You can record a customer interview if the person agrees. Ask permission to take notes or record before you start, and write down their answer. Only promise that you won't share what they say with their name attached if that's true. Whether you record or not, open your note-taking template before the call so you can capture the specific story, costs, and exact quotes.
What should you do after a customer interview?
Spend 15 minutes right after each customer interview writing up your notes, keeping facts, exact quotes, and commitments apart from your own interpretation. Confirm any introduction or next step the person offered. After every five interviews, read your notes side by side and count how often each problem, workaround, and cost comes up. When one pattern clearly repeats, turn it into a commitment test.
Continue on a Founder Path
Validate Your Business Idea
5 lessons. You'll finish with a validation decision memo.
Khalel Dumaz is the founder of Vora IQ, which publishes The Founder Almanac, and the author of The Vibe Code Bible, a free guide to building software with AI.
Keep building
Related reading
Start a BusinessField guide8 min
How to run customer interviews that get honest answers
A customer discovery interview is a short conversation about someone's real experience with a problem, not a pitch for your idea. Ask about specific past events, such as the last time the problem happened, what it cost, and what they tried, because what people did is more reliable than what they predict. Save your idea for the end, and ask for a small next step.
Start a BusinessField guide13 min
How to validate a business idea before spending money
Validating a business idea means collecting evidence that a specific group of people has a problem and will pay you to solve it, before you invest heavily. Write down your riskiest assumptions, talk to people who have the problem, then ask for a real commitment, such as a deposit, pre-order, or paid pilot. A commitment is far stronger evidence than a compliment.
Founder LibraryCalculator2 min
Unit economics calculator: lifetime value, LTV:CAC, and payback
This calculator takes your average monthly revenue per customer, gross margin, customer acquisition cost, and monthly churn, and returns monthly contribution, expected customer lifetime, lifetime value, LTV:CAC, and CAC payback. Use it to check whether each customer is worth more than it costs to win.