SaaS User Interviews: The Questions That Reveal What to Build Next
User interviews are the most direct path from user behaviour to product decisions. But most user interviews generate polite, unusable feedback because the questions are wrong. The specific questions that reveal what users actually need, the interview format that produces honest answers, and how to synthesise interviews into product decisions.
The Question Design Problem
User interviews generate bad data when they ask the wrong questions: hypothetical questions (‘would you use a feature that…’), leading questions (‘don’t you think it would be useful if…’), and opinion questions (‘what do you think of the product?’). These questions produce socially acceptable answers rather than genuine insight because they invite the respondent to speculate about future behaviour, agree with the interviewer’s framing, or give positive feedback to avoid an uncomfortable conversation. The questions that generate useful product data are behaviour-based (what have you done?), specific (what happened the last time you encountered this problem?), and outcome-oriented (what were you trying to accomplish when you hit that obstacle?). Behaviour-based questions produce honest answers because they ask about things that actually happened, which are harder to misrepresent than hypothetical opinions.
What to Ask at Each Stage
Pre-build discovery interviews: understanding the problem space
The goal of pre-build discovery interviews is to validate the problem hypothesis before committing development resources. Questions: ‘Walk me through your typical [workflow related to your product category]. How does that usually go?’ / ‘What is the most frustrating part of that process for you?’ / ‘When was the last time that frustration caused a real problem for you? What happened?’ / ‘Have you ever tried to solve that problem? What did you try? Did it work?’ / ‘What would need to be different for that problem to no longer affect you?’ These questions reveal whether the problem is real, how frequently it occurs, and what users have already tried — without the interviewer mentioning a product or solution.
Post-launch user interviews: understanding value delivery
The goal of post-launch user interviews is to understand which features are delivering value, which are confusing, and what is missing. Questions: ‘Can you show me how you typically use [Product] in a typical week?’ / ‘Walk me through the last time you used [specific feature]. What were you trying to accomplish? Did you achieve it?’ / ‘Is there anything you expected [Product] to do that it does not do?’ / ‘If you had to remove one thing from [Product] and could only keep everything else, what would you remove?’ / ‘If you could add one thing to [Product] that would make it significantly more valuable for you, what would it be?’ The last two questions are particularly effective at separating features that are genuinely valued from those that are used but not essential.
Churn interviews: understanding why users leave
The goal of churn interviews is to understand the specific reasons users cancel and whether those reasons are addressable. Questions: ‘When you made the decision to cancel, what was the primary reason?’ / ‘Was there a specific moment or event that led to that decision?’ / ‘Was there anything [Product] could have done differently that might have changed your decision?’ / ‘What are you using now instead, and how is that going?’ / ‘If [Product] added [specific improvement], would you consider coming back?’ Churn interviews are the most emotionally uncomfortable interviews because they involve explicit feedback that the product has failed to deliver. They are also the most valuable: the specific reasons for cancellation identify the changes that would have the highest impact on retention.
🔗 Related reading on sasolutionspk.com
Bubble SaaS Customer Interview Guide
SA’s complete guide to running customer interviews for SaaS product founders — templates, questions, and synthesis frameworks for each interview type.
Bubble SaaS Product-Market Fit
How user interview insights feed into the product-market fit measurement framework — from discovery to the 40% ‘very disappointed’ test.
From Conversation to Action
Count the themes
After 5+ interviews, list every specific pain point, missing feature, and workflow friction mentioned. Count how many times each appears across the interviews. Themes mentioned by 3 or more users in 5 interviews are validated signals that should influence the product roadmap. Themes mentioned once are individual experiences that belong in the backlog but not the next sprint.
Extract the exact language
The specific words users use to describe their problems are the most effective raw material for landing page copy, email subject lines, and product naming. A user who says ‘I am always chasing clients for sign-off’ is giving you the headline for a workflow feature. Note and preserve exact phrases from each interview.
Identify the one-thing insight
In most sets of 5-8 user interviews, one insight emerges that is both surprising and consistent: something that users consistently do differently from how the product assumes they behave, or a use case the product was not designed for that users are consistently attempting. The one-thing insight is the highest-value output of the interview process and often points directly to the highest-impact product change.
Q: How do I recruit users for interviews after launch?
Three sources work reliably: (1) an email to all active users asking for 20 minutes in exchange for a $20 Amazon gift card or a month of free subscription — response rates are typically 5-15% of the users emailed; (2) a personal message from the founder to the 10-15 most engaged users (highest usage, longest tenure, or most interaction with support) — response rates are 40-70% for genuinely personal messages; and (3) the exit interview email sent to churned users, asking for a brief conversation before the cancellation is processed — response rates of 15-25% are typical for a personal, specific ask from the founder.
Q: How long should a user interview be?
45 minutes is the SA standard for post-launch user interviews: long enough to cover the core questions with room for follow-up, but short enough that the participant’s attention and energy remain fully engaged throughout. Pre-build discovery interviews work well at 30 minutes if kept tightly focused on a single workflow area. Churn interviews are often shorter (15-20 minutes) because the conversation has a specific focus and the participant’s motivation to engage is lower than that of an active user being interviewed.
Q: Should I take notes during user interviews or rely on recording?
Both. Record every interview (with explicit consent at the start of the call) so that you can review specific moments and extract exact quotes accurately. Take real-time notes on the observations that stand out in the moment — the user’s emotional reaction to a specific question, a surprising statement, or a moment of confusion — because these observations are harder to reconstruct from a recording alone. Review the recording within 48 hours while the interview is fresh, before the details fade and before the next set of interviews begins.
Ready to Build Your MVP?
SA Solutions builds MVPs in weeks using Bubble.io. Start with a free audit or scope your build in 48 hours with a Discovery Sprint.
