Article
Free Customer Interview Kit: Script, Questions and Note Sheets
Updated · Fonda editorial team ·How we write these pages
Short answer
This free kit has what you need to run your first 10 customer interviews: a one-page script, a question bank grouped by goal, 13 bad questions rewritten as better ones, a note sheet for each call and a tally sheet that counts problem signals across calls. Print one note sheet per person and read the tally after every five interviews.
Your roadmap
- 1Open and ask for consent
- 2Warm up with their context
- 3Replay the last time
- 4Find workarounds and spend
- 5Size the cost and priority
- 6Close and ask for referrals
Key takeaways
- Use the script as a guide. Its job is to get the story of the last time the problem happened.
- Pick five to seven questions from the bank before each call.
- Fill in the note sheet within an hour, in the person's own words.
- Count only signals backed by a past example. Compliments and future promises stay out of the tally.
- Recruit where the problem already shows up, and end every call by asking for an introduction.
How to use this kit
This page is the kit. Print it or download it, and keep the script beside you during calls. Use one note sheet per interview and one tally sheet for 10 interviews with one customer group. New to interviews? Read how to do customer interviews for the method. This kit is the paperwork.
Interviews are the part of idea validation that shows whether a problem is real before you spend money building. Plan 20 to 30 minutes per call.
- Interview script: six parts, in the order you run them.
- Question bank: extra questions grouped by goal.
- Bad questions rewritten: 13 questions that produce false hope, with better versions.
- Note sheet: one per interview.
- Tally sheet: counts problem signals across 10 interviews.
- Recruiting plan and checklist: how to find 10 people and what to do around each call.
The one-page interview script
Read the quoted lines as written for your first few calls, then use your own voice. Fill the brackets with your topic. Spend most of the call on parts 3 and 4, and keep your idea out of it.
- 1
Open and ask for consent.
"Thanks for making time. I am researching how [type of person] handle [topic]. I am not selling anything. This takes about 25 minutes. Is it OK if I take notes, and may I record the call so I can check them later?" If they decline recording, take notes only. Recording rules differ by country and state, so check the ones that apply to you both.
- 2
Warm up with their context.
"Can you tell me about your role and what a normal week looks like?" "Which parts take the most time?" Check that this person belongs to the group you meant to study.
- 3
Replay the last time.
"Tell me about the last time [problem] happened." Walk through it in order: "What were you trying to do? What did you do first? Then what? How did it end?" If they cannot recall a recent time, write that down. It is a finding.
- 4
Find workarounds and spend.
"What have you tried to fix this?" "What do you use today?" "Have you paid for anything to deal with it?" Ask to see any spreadsheet or template they built. A workaround that took effort is a strong signal.
- 5
Size the cost and priority.
"What did it cost you last time, in hours or money?" "How often does it come up?" "Where does it rank against everything else on your plate this month?" Ask for past facts, not a guess about what they would pay.
- 6
Close and ask for referrals.
"Is there anything I should have asked?" "Who else deals with this? Would you introduce me?" "Can I follow up later?" Thank them and say what happens next.
Three habits for every call
Let them do most of the talking. When an answer sounds general, ask for a specific example. After each answer, wait a few seconds before you speak, because people often fill the silence with the detail you need.
Question bank, grouped by goal
Before each call, pick five to seven questions that cover what you still do not know. For a longer list with follow-ups, see the full set of customer interview questions.
Goal: understand who they are.
- What is your role, and who do you work with most?
- What does a busy day look like for you?
- What has changed in your work over the last year?
Goal: get the story of a real event.
- When did this last happen? What set it off?
- Who else was involved, and what did each person do?
- Which step took the longest?
- Is that typical, or was that time unusual?
Goal: find what they already do about it.
- What are you using to handle this right now?
- What did you try before that, and why did you stop?
- Have you searched for a better way? What did you find?
- What do you dislike about the tools you have tried?
Goal: measure how much it matters.
- How many hours did this take you last month?
- What did the last bad case cost you?
- Is there a budget or a person assigned to this today?
- What else is competing for your time and money right now?
Goal: learn who decides and pays (for business customers).
- Who signed off the last time your team bought a tool for work?
- How did you find and choose the last tool you started using?
- Whose budget would a fix for this come from?
Bad questions rewritten as good ones
This table follows the approach of The Mom Test, Rob Fitzpatrick's short book on learning whether your business is a good idea "when everyone is lying to you", as its subtitle puts it. Eric Migicovsky based his Y Combinator Startup School advice on talking to users on the book, and YC's recap of his talk says the same: do not pitch, avoid hypotheticals, ask about specifics from the person's past and discard compliments. The rewrites below are written for this kit, not quoted from the book.
Scroll sideways to see the whole table.
| Bad question | Why it misleads | Ask this instead |
|---|---|---|
| Do you think this is a good idea? | Asks for an opinion, and people want to be kind. | How do you handle this today? |
| Would you buy a product that did X? | A promise about the future costs nothing. | When did you last pay for something to solve this? |
| How much would you pay for this? | Gets a guess, not a fact. | What does this problem cost you now, in time or money? |
| Would you use an app for this? | Hypothetical, and invites a polite yes. | What have you tried so far, and why did you stop? |
| Don't you hate it when X happens? | Tells them the answer you want. | Tell me about the last time X happened. |
| How often do you usually do X? | "Usually" invites a flattering average. | When did you last do X? And the time before? |
| What features would you want? | Customers know problems. Designing the fix is your job. | What is the hardest part of doing X? |
| Would you recommend this to friends? | Asks about a product that does not exist. | Who else do you know who deals with this? |
| Is X a big problem for you? | Yes or no, and invites exaggeration. | Where does X rank among the things you are working on this month? |
| Would it help if X were faster? | Everyone says yes to faster. | What happens when X is slow? What did that cost you last time? |
| Do you ever struggle with X? | Closed and general, so you get a shrug. | Walk me through how you did X last week. |
| Would you switch from your current tool? | Saying yes is easier than switching. | When did you last look for an alternative? What happened? |
| What do you think of my demo? | Fishes for a compliment. | Can we book a time next week for you to try it with your own data? |
Note sheet for one interview
Print one copy per interview and fill it in during the call or within an hour after. Write their words, not your summary: "It eats my Sunday nights" tells you more than "time issue". Score pain last, after the call, so the number reflects the whole conversation.
Scroll sideways to see the whole table.
| Field | Notes |
|---|---|
| Name, role and company or setting | |
| Date, length and how you found them | |
| Customer group they belong to | |
| The last time it happened (when, what, who) | |
| What they did about it | |
| Tools, workarounds or people they use now | |
| Money spent on the problem or workaround | |
| Time spent on it, and how often it comes up | |
| Exact words they used to describe it | |
| Where it ranks among their priorities | |
| Next step they agreed to (intro, follow-up, trial, pre-order) | |
| What surprised you | |
| Pain score from 1 (mild) to 5 (urgent), your judgment |
Leave the Notes column blank on the printout and fill it in by hand.
Tally sheet: counting problem signals across interviews
After each call, fill in one numbered column. Score 1 only when the person gave a specific past example, otherwise 0. "That sounds annoying" with no story behind it scores 0. Use one sheet per customer group, because mixing groups hides patterns.
Scroll sideways to see the whole table.
| Signal | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Total |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Had the problem recently, with a date or event | |||||||||||
| Described the last time in detail | |||||||||||
| Built or uses a workaround | |||||||||||
| Has paid for a fix or workaround | |||||||||||
| Spends real time on it each month | |||||||||||
| Ranks it in their top three priorities | |||||||||||
| Used words similar to other interviewees | |||||||||||
| Offered an introduction | |||||||||||
| Agreed to a concrete next step |
Columns 1 to 10 are interviews. Add across for the Total. Fill the similar-words row when you review each batch of five, once you have other calls to compare.
A simple rule for reading the tally
After 10 interviews, look at the top row and at the money and next-step rows. Move to a demand test if 7 or more people had the problem recently and at least 3 people have paid for a fix or agreed to a concrete next step (count each person once). Refine and run 5 more if 4 to 6 people had the problem, or if 7 or more had it but fewer than 3 paid or agreed to a next step. Rethink the problem or the group if 3 or fewer had it recently. This is a rule of thumb for deciding what to do next, not a statistical test.
A demand test asks for something real, such as a deposit or a pre-order, as in how to get pre-orders. To check whether 10 calls is enough for your situation, see how many customer interviews you need.
How to recruit 10 interviewees
You need people who have the problem now, not people who like you. Write one sentence that defines who counts, for example "freelance designers who invoice several clients a month". Then try these channels.
- Second-degree introductions. Ask friends and colleagues who they know that fits your sentence. A stranger introduced by someone they trust is easy to reach and less likely to flatter you than a friend.
- Communities where the problem is discussed. Forums, subreddits, Slack and Discord groups and industry associations. Read the rules and ask moderators whether research requests are allowed.
- Professional networks. Search LinkedIn for the job title and send a short, specific note.
- Public reviews of existing tools. People who wrote detailed reviews of a competing product already care. Contact them only where the platform allows it.
- Local groups and events. Meetups, trade events and business groups suit problems tied to a place or a trade.
- Referrals from each interview. The script's close asks for introductions, so each good call can lead to the next.
Outreach message you can adapt
Hi [name], I am researching how [type of person] deal with [problem]. I am not selling anything. Could I ask you about your experience in a 25 minute call this week or next? I am happy to share a summary of what I learn.
Contact more people than you need, since many will not reply, and screen with one question about when the problem last happened. Book calls close together so you can compare them. As a reference point, Steve Blank's Lean LaunchPad classes at Stanford and Berkeley asked each team to speak with 10 customers before the first class. Treat 10 as your first round, not your last.
Checklist for each round of interviews
- Write one sentence that defines who you want to talk to.
- Write down the three assumptions you most need to check.
- Send outreach to more people than the 10 you need.
- Pick five to seven questions from the bank for each call.
- Print the script and one note sheet per call.
- Ask for consent to take notes and to record.
- Keep your idea out of the call until the last few minutes, if you mention it at all.
- Fill in the note sheet within an hour of each call.
- Add each call to the tally sheet the same day.
- Ask every person for one introduction.
- Read the tally after every five interviews and adjust your questions.
- Decide: demand test, another round, or a new problem or group.
What to do after 10 interviews
Interviews tell you what the problem is and how people describe it. They do not tell you how many people share it. If you need that number, turn what you heard into a short survey and use the survey sample size calculator to see how many responses you need. Reuse the words from your note sheets so people recognize the problem.
If the tally points to a real problem, test demand with a small offer before you build. If you want a guided path, Fonda, an AI co-founder for people starting a business, includes Interviews as a step in its Validate phase, before a Verdict of go, refine or pivot, with reasons and a next step. It is free to start, and the pricing page explains paid use.
Frequently asked questions
Can I run customer interviews by video or phone?
Yes. Video and phone calls work for most topics and make it easier to reach people outside your area. Ask permission before recording. In-person visits are worth the effort when the problem happens in a physical place, such as a shop floor or a kitchen, because you can see the workaround.
Should I pay people for an interview?
You do not have to. People who have the problem are often willing to talk about it. A small thank-you, such as a gift card or a copy of your findings, is reasonable for hard-to-reach groups. Avoid large payments, which can attract people who do not have the problem.
Can I reuse the same script for every interview?
Keep the structure and the opening, and change the questions as you learn. If three people in a row give the same answer to a question, swap it for one that tests something you still do not know.
Sources
Keep reading
- How to do customer interviews
- Customer interview questions
- How many customer interviews do you need?
- Survey sample size calculator
- What is idea validation?
- How to validate a startup idea
- Validation surveys that actually tell you something useful
- How to Build a Landing Page That Tests Demand
- How to Build a Waitlist for a New Product
- How to Do a Competitor Analysis for a New Business