20 Customer Discovery Questions to Ask Before Launching
By Sumizeit · Posted on
20 customer discovery questions to ask before launching, grouped by problem, current fix, budget, and buying habits, plus tips on running the interview.
For 15 minute nonfiction book summaries of bestselling books, check out sumizeit.com
TL;DR
The best interview questions ask about what people already did, never about what they might do. Below are 20 of them, grouped by what you are trying to learn, with a note on what a strong or weak answer sounds like. Ask them to 10 or 15 people before you launch and you will know whether the problem is real, who feels it most, and what they would pay to make it go away.
Why most founder interviews are useless
I have watched smart people spend a year building something and then ask their first real customer question the week of launch. By then it is too late to hear the answer.
The other common mistake is asking early but asking badly. You pitch your idea, your eyes light up, and the person across the table says it sounds great. Of course they do. You are standing right there, and nobody wants to kick a puppy.
Steve Blank has been telling founders to "get out of the building" for about twenty years now, and The Startup Owner's Manual is still the thickest guide to doing it. But the book that fixed my own interviews was a much shorter one. In The Mom Test, Rob Fitzpatrick gives three rules I repeat to myself before every call. Talk about their life and not your idea. Ask about specific things that happened in the past. Talk less, listen more.
Every question below follows those rules. You will notice that none of them mention your product until the very end. That is on purpose.
Questions about the problem
Start here. You are checking whether the problem exists in this person's life at all, and how much it bugs them.
1. What is the hardest part of doing this?
Leave it open and let them pick the pain. If they name something different from the problem you want to solve, pay attention. That gap is the most useful thing you will hear all day.
2. Tell me about the last time that happened.
This is the workhorse question. A real story has a date, a place, and details. A vague "oh, it happens all the time" with no example usually means it does not happen much.
3. Why was that hard?
Ask why, then ask why again. The first answer is often polite and surface level. The second or third is where the real reason lives.
4. How often does this come up?
A problem that shows up once a year rarely supports a business. Daily or weekly pain is what you want to hear.
5. What does it cost you when it goes wrong?
Listen for hours lost, money lost, or a boss getting angry. If they cannot name a cost, the problem is an annoyance, and people do not pay to fix annoyances.
Questions about what they do today
Everybody already has a solution, even if it is a sticky note or doing nothing. Your real competitor is whatever they do now.
6. How do you handle this today?
Get the step by step version. Spreadsheets, a part time assistant, three apps taped together. Each clumsy step is something you could remove.
7. What do you like about the way you do it now?
People skip this one. Do not. If your product takes away the thing they like, they will not switch, no matter how much better the rest is.
8. What do you wish it did better?
Now you get the complaints. Write down their exact words, because those words belong on your landing page later.
9. What else have you tried?
Someone who has tested four tools and dropped them all is in real pain. Someone who has never looked for anything is telling you the problem ranks low on their list.
10. Why did you stop using those?
The reasons they quit are a free list of mistakes to avoid. Price, setup time, a missing feature, bad support. Whatever it was, do not repeat it.
Questions about money and decisions
This group feels awkward to ask. Ask anyway. It is far more awkward to launch and find out nobody has a budget.
11. Have you paid for anything to fix this?
Past spending is the best signal you can get. If they have never spent a dollar on the problem, you will have a hard time being the first.
12. How much did you spend?
You are not asking what they would pay you. You are asking what they already paid someone else. That number is your price anchor, and it is worth more than any pricing survey.
13. Who else is involved when you decide to buy something like this?
This matters most when you sell to companies. The person you are talking to may love the idea and have zero power to approve it. Find out early who signs.
14. What would have to be true for you to switch from what you use now?
You will hear things like "it has to work with my calendar" or "my team would need to learn it in a day." Those are your launch requirements, handed to you for free.
Questions about how they buy
Building the product is half the job. Getting it in front of people is the other half, and these three questions help with that.
15. Where did you find the tools you use today?
A friend, a Google search, a podcast ad, a Reddit thread. Their answer tells you where to show up. If ten people in a row say "a coworker told me," you know referrals matter more than ads.
16. What do you read, watch, or listen to for work?
Collect the names. Newsletters, YouTube channels, communities. That list becomes your marketing plan, and it pairs well with this guide on finding your first 10 customers when nobody knows you exist.
17. Who do you ask for advice on this kind of thing?
Every group has a few people everyone else copies. Learn who they are. One of them using your product does more than a month of cold emails.
Questions that close the conversation
Do not end with "thanks, bye." The last five minutes can be the best part.
18. Is there anything I should have asked that I did not?
People often save their biggest point for this one. I have had whole interviews turn around on it.
19. Who else should I talk to?
If they offer two names without thinking, they care about the problem. If they say "hmm, nobody comes to mind," that tells you something too. Either way, it keeps your interview list full.
20. Can I come back and show you what I build?
This is the only question about your product, and it is a small ask. A yes gives you a tester and maybe a first buyer. For a stronger test, ask if they would join a paid pilot. Their face will answer before their mouth does.
How to run the interview
You do not need all 20 customer discovery questions in one call. Pick six or seven, starting with numbers 2, 6, 9, 11, and 19, and let the conversation wander. A good interview feels like a chat with a curious stranger. A bad one feels like a form.
Keep it to 20 or 30 minutes. Ask if you can record, or bring a friend to take notes, so you can look at the person and not your laptop. Right after the call, write down three things while they are fresh. What surprised you? What did they already pay for? What exact phrase did they use to describe the problem?
Aim for 10 to 15 conversations with the same type of person. Mixing students, dentists, and startup founders in one batch gives you mush. Around the tenth call you will start hearing the same stories again, and that is how you know you can stop.
Three things to avoid.
First, do not pitch. The moment you describe your idea, the person switches from telling the truth to being nice.
Second, do not ask "would you." Would you use this, would you pay for this, would you tell a friend. People are terrible at predicting their own behavior, and they are generous with imaginary money.
Third, do not count compliments. "That sounds cool" is not data. Stories, numbers, and names are data.
What do you do with the answers? Look for patterns. If eight of twelve people have paid for a fix and still hate it, you have found something. If most of them shrug, be honest with yourself. Plenty of companies close because they built something nobody was waiting for, which is the heart of why startups fail. Changing the idea now costs you a week. Changing it after launch costs a lot more.
For the bigger picture on turning what you learn into small tests, The Lean Startup and Running Lean are the two I would read next. Both take about 15 minutes as summaries.
Before you launch
Print this list. Circle the six or seven customer discovery questions that fit your idea, and book your first call this week. Not next month, when the product is "almost ready." This week, while changing your mind is still cheap.
You will feel a pull to skip this and keep building, because building is fun and talking to strangers is uncomfortable. I feel it every time. Go talk to them anyway. Fifteen conversations will teach you more about your market than another three months alone with your laptop.
And if you want to keep reading while you wait for people to reply, here are the best books for founders and a guide on how to sell a product people want.
For 15 minute nonfiction book summaries of bestselling books, check out sumizeit.com

