Customer Discovery
Customer Interview Questions for SaaS Validation
Use these customer interview questions to validate SaaS pain points, workflows, buying intent, alternatives, and MVP scope.
Overview
Customer interviews are not sales pitches. They are a way to understand how people work today, what costs them time, what they have already tried, and whether the problem is important enough to change behavior.
The best questions are specific and behavior-based. Avoid asking if someone likes your idea. Ask what happened last time they had the problem, what they did, who was involved, and what the outcome cost.
Questions about the workflow
Start with the current process before mentioning your product. You want the customer to describe the workflow in their own words. This reveals language, friction, handoffs, tools, and hidden constraints.
- Walk me through the last time this happened
- What tools or documents did you use
- Who else was involved
- Where did the process slow down
- What happens if this task is missed
Questions about pain and cost
Pain needs weight. A task can be annoying without being valuable enough for SaaS. Ask about time, missed revenue, customer experience, staff workload, and risk so you understand whether the pain can support pricing.
- How often does this happen
- How much time does it take each week
- What mistakes happen when it goes wrong
- Does it affect revenue or customer retention
- Who notices when the problem is not solved
Questions about alternatives
Alternatives show what the customer values. If they already pay for software, your job is to understand what is missing. If they rely on manual work, your job is to understand why no tool has replaced it yet.
- What have you tried already
- Why did that not solve the problem
- What do you like about the current workaround
- What would make switching worth it
- What systems would a new tool need to fit around
Questions about buying intent
Buying intent is sensitive, so ask plainly and respectfully. You are not trying to force a yes. You are trying to learn whether the problem belongs near a budget and whether the customer can imagine adopting a solution.
- Who would approve a tool for this
- What would a fair price depend on
- Would you try a simple first version
- What would make this not worth paying for
- Can I follow up with a prototype or mockup
How to use Customer Interview Questions for SaaS Validation
Start with one narrow customer
The most useful way to apply this page is to pick one customer segment before you generate or validate anything. A broad audience creates broad answers. A narrow buyer makes the pain, pricing, competitors, and MVP scope easier to judge. Instead of saying small businesses, choose a specific operator such as independent accountants, home service contractors, med spa owners, property managers, or freelancers with repeat client work.
Write the pain in customer language
Before using ProblemToMVP, write the problem the way a customer would say it. Avoid polished startup language at this stage. A phrase like we keep losing approved change orders is more useful than a phrase like contractor revenue optimization platform. Plain language helps the report stay grounded in a real workflow and makes the next validation step easier.
Compare alternatives before you build
Every SaaS idea competes with something. Sometimes the competitor is another product. Sometimes it is a spreadsheet, a shared inbox, a template, an assistant, or a process nobody likes but everyone understands. Strong validation means comparing your MVP against those alternatives and asking whether the buyer has a clear reason to switch.
Turn the report into a test
The report should lead to an action, not just another idea saved in a notes app. Use the output to write interview questions, draft a landing page, create a simple mockup, contact prospects, or offer a manual pilot. If the first test does not create a stronger signal, revise the niche, pain point, pricing, or MVP scope before writing more code.
Keep the first version intentionally small
A good SaaS MVP does not need every feature a mature product would have. It needs enough value to test the main promise with a real user. Keep setup short, avoid complex integrations at the beginning, and focus on the one workflow that proves the customer cares. If the product needs months of building before anyone can react to it, the scope is probably too large for an MVP.
Use evidence to choose the next step
After you test the idea, look for behavior instead of compliments. Did someone ask for access, share real workflow details, agree to a follow-up, import data, invite a team member, or discuss price? Those signals are more useful than polite feedback. If the evidence is weak, the right move may be to narrow the customer, change the pain point, or compare a different opportunity before building further.
FAQs
How many customer interviews should I do?
Five to ten interviews in one narrow segment can reveal patterns. More may be needed if the answers are inconsistent.
Should I show mockups during the first interview?
Usually not at the start. First learn the workflow. Show a mockup later if you need feedback on a specific solution.
What questions should I avoid?
Avoid leading questions like would you use this. Ask about past behavior instead.
How do I know if the interview went well?
You should leave with clearer language, real examples, current workarounds, and a better sense of urgency.