Customer Interview Questions: 40 Examples for Discovery, Retention, and Pricing Research
A practical bank of 40 customer interview questions for discovery, retention, and pricing research.
The fastest way to improve customer interviews
Most interview guides fail for one reason: they ask for opinions, predictions, or summaries instead of concrete past behavior.
A strong customer interview question does three things:
- anchors on a real event
- stays neutral
- gives you an obvious path for follow-up
If you need help structuring the full guide around these questions, start with How to Write a User Interview Guide That Produces Better Insights. This post focuses on what to ask in the room.
How to use this question bank
For a 30-minute interview, prepare 6–8 primary questions, not 20. Pick one research goal per study. Discovery, retention, and pricing each need different evidence.
Use this fallback prompt whenever an answer is vague:
Can you walk me through the last specific time that happened?
That one probe will usually get you better data than adding more top-level questions.
40 customer interview questions by research goal
| Goal | Question | Strong follow-up prompts | Common mistake to avoid |
|---|---|---|---|
| Discovery | 1. Tell me about the last time you tried to solve this problem. | What triggered it? What did you do first? | Asking whether the problem matters |
| Discovery | 2. What was happening that made this feel urgent? | Why then and not earlier? | Accepting urgency at face value |
| Discovery | 3. How are you handling this today? | What tools, workarounds, or people are involved? | Ignoring non-product alternatives |
| Discovery | 4. What is most frustrating about your current approach? | What takes the most time? What breaks most often? | Asking for a feature wishlist |
| Discovery | 5. Who else is involved when this problem comes up? | Who influences the decision? Who feels the pain? | Treating one user as the whole buying group |
| Discovery | 6. What have you already tried? | Why did you try that option? What happened next? | Skipping failed attempts |
| Discovery | 7. What made those options good enough or not good enough? | What was missing? What was surprisingly useful? | Leading toward your product category |
| Discovery | 8. How do you decide this problem is worth solving? | What metric, cost, or risk matters? | Assuming the problem is strategic |
| Discovery | 9. What happens if you do nothing? | Who notices? What gets delayed or lost? | Asking only about best-case outcomes |
| Discovery | 10. What would a better outcome look like in practice? | What would change in your day or workflow? | Asking for abstract success criteria |
| Discovery | 11. When did this problem first become noticeable? | What changed in your team, process, or goals? | Missing the context shift |
| Discovery | 12. How often does this happen? | Tell me about the last two times. | Accepting frequency estimates without examples |
| Discovery | 13. What part of this process feels hardest to control? | Where do mistakes or delays show up? | Staying too high-level |
| Discovery | 14. If you could remove one step, which would it be? | Why that step? What depends on it? | Turning the interview into solution design |
| Retention | 15. Think about the last time you got value from the product. What happened? | What were you trying to do? What result did you get? | Asking if they are satisfied |
| Retention | 16. What keeps you coming back? | Which moments are genuinely useful versus just routine? | Confusing habit with value |
| Retention | 17. When does the product fit naturally into your workflow? | What happens before and after you use it? | Ignoring surrounding context |
| Retention | 18. Have there been times you almost stopped using it? | What caused that? What changed your mind? | Only interviewing active promoters |
| Retention | 19. What feels harder than it should after signup? | Where did you get stuck most recently? | Focusing only on onboarding week one |
| Retention | 20. Which features do you rely on most? | What job do they help you complete? | Equating usage with importance |
| Retention | 21. Which parts do you ignore or avoid? | Why are they not useful: too confusing, irrelevant, or too much work? | Defending low-use features |
| Retention | 22. What would make you look for an alternative? | What would be the first warning sign? | Asking directly about churn likelihood |
| Retention | 23. How would your work change if this product disappeared tomorrow? | What would you replace first? | Assuming they have no substitute |
| Retention | 24. Who would notice first if you stopped using it? | You, your manager, or your customers? | Missing team-level dependency |
| Retention | 25. What expectations did you have that were not met? | When did you realize that? | Asking only about bugs |
| Retention | 26. What made you trust this product enough to keep using it? | Was it reliability, support, results, or something else? | Treating trust as only a brand question |
| Retention | 27. What changed between your first week and now? | What became easier, harder, or more valuable? | Missing how value evolves over time |
| Pricing | 28. Tell me about the last time you paid for a tool like this. | Who approved it? What was compared? | Asking what they would hypothetically pay |
| Pricing | 29. How do you usually evaluate whether a tool is worth the cost? | What budget, ROI, or risk threshold matters? | Asking for a single price point too early |
| Pricing | 30. What alternatives are you comparing against? | Internal build, manual work, competitor, or doing nothing? | Ignoring the do-nothing option |
| Pricing | 31. What would make this feel expensive? | Which missing outcomes would break the value equation? | Treating price sensitivity as fixed |
| Pricing | 32. What would make this feel cheap in a bad way? | What would you assume was missing? | Assuming lower price always helps |
| Pricing | 33. How is budget approved for tools like this? | Who owns the budget? What evidence do they need? | Interviewing users only, not buyers |
| Pricing | 34. When in the buying process does price become a serious factor? | At shortlist, procurement, or renewal? | Discussing price without purchase context |
| Pricing | 35. What costs matter besides subscription price? | Setup, migration, training, switching, compliance? | Forgetting total cost of adoption |
| Pricing | 36. Have you ever chosen a more expensive option? Why? | What made the premium feel justified? | Assuming cheapest wins |
| Pricing | 37. Have you ever rejected a cheaper option? Why? | What concerns made it feel risky? | Missing trust and implementation concerns |
| Pricing | 38. What pricing model feels easiest to explain internally? | Seat-based, usage-based, tiered, annual? Why? | Testing pricing pages instead of buying logic |
| Pricing | 39. At renewal time, what would you review to decide whether to continue? | Usage, outcomes, team adoption, support? | Asking only about initial purchase |
| Pricing | 40. What result would need to be true for this to feel worth paying for? | How would you measure that result? | Asking if they see value in general |
Three follow-up prompts that consistently work
Good follow-ups are short and specific:
- What happened right before that?
- Can you give me a recent example?
- How did you decide what to do next?
These work because they pull people out of generalities and back into actual behavior.
Mistakes that ruin otherwise good questions
The biggest mistake is asking future-tense questions in discovery or pricing research: Would you use this? Would you pay for this? Those answers are usually optimistic and low-confidence.
The second mistake is stacking questions: How do you solve this, how often does it happen, and how frustrating is it? Ask one thing at a time.
The third mistake is failing to probe. The first answer is usually a headline, not evidence. The useful insight often shows up in the second or third layer.
Final tip
A question bank is not an interview script. Choose the few questions that match the decision you need to make, then listen closely enough to go off-script when something important appears.
If you need to decide whether interviews are even the right method, see When to Use Surveys vs Interviews for Product Decisions.