Customer Discovery Questions for SaaS Founders

SaaS discovery interviews look similar to any other customer discovery conversation on the surface, but the underlying dynamics are different. Purchases often involve more than one person, sales cycles stretch over weeks or months, and the value of the product usually shows up gradually through repeated use rather than in a single first impression. Generic discovery questions miss these dynamics. Here are the questions that account for them.

Understand Who’s Actually Involved in the Decision

Before diving into problem questions, map out who’s involved in adopting a tool like yours at the organizations you’re talking to.

“Who else would be involved in deciding to try or buy something like this?” This surfaces whether you’re talking to the end user, the budget holder, or someone with influence but no final say — and tells you whether you need to interview more than one role to get a full picture.

“How have similar tools been adopted here in the past?” This reveals the realistic approval process — informal team decision, procurement review, IT sign-off — which shapes both your sales approach and your MVP’s requirements.

Understand the Current Workflow in Detail

“Walk me through how your team currently handles this, step by step.” SaaS problems are often embedded in a broader workflow involving multiple tools and handoffs. A detailed walkthrough reveals where your product would actually fit, and where it might create new friction instead of removing it.

“Which parts of that process are manual, and which are already automated?” This tells you what you’re actually competing with — not necessarily another SaaS product, but often a spreadsheet, an email chain, or a partially automated internal tool.

Understand Recurring Value, Not Just Initial Interest

“If this worked well, how would you know a month from now?” SaaS products need to prove ongoing value, not just a good first impression. This question surfaces what “success” looks like over time for the person you’re talking to, which matters more than their reaction to a demo.

“How often would your team realistically use something like this?” Frequency of use directly affects both perceived value and pricing tolerance. A tool used daily justifies a different price and urgency than one used quarterly.

Understand Budget and Existing Spend

“What are you currently spending — in tools, time, or headcount — to deal with this?” This is far more revealing than asking “would you pay $X.” Understanding existing spend tells you what budget category your product would compete for and what price range is realistic.

“What would need to be true for this to be an easy yes for budget approval?” For B2B SaaS especially, this question gets at the real, often unspoken criteria — ROI proof, security review, integration requirements — that determine whether interest converts into a purchase.

A SaaS-Specific Question Set

Question	What It Reveals
“Who else would be involved in this decision?”	Buying committee and stakeholders
“Walk me through your current workflow.”	Where the product fits, real competition
“How would you know this worked, a month from now?”	Definition of ongoing value
“What are you currently spending on this problem?”	Budget category, realistic pricing
“What would make this an easy approval?”	Purchase criteria and blockers

Avoiding the Enthusiastic-Insider Trap

A common SaaS discovery mistake is relying too heavily on interviews within your own network — former colleagues, industry contacts, people who already like you. These conversations tend to be more forgiving and less representative of a typical buyer’s real decision process. Balance them with conversations reached independently of your existing relationships, following the broader principle covered in how to validate demand without asking “would you use this?”.

From SaaS Discovery to MVP Scope

Once you understand the real workflow, the buying process, and the recurring value your target customers need to see, you’re in a much stronger position to scope an MVP that fits into an existing decision process — rather than one that requires you to invent a new budget category or convince an entirely new buying committee from scratch.

Frequently Asked Questions

How is SaaS customer discovery different from consumer app discovery?

SaaS products often involve multiple stakeholders in a buying decision, longer sales cycles, and value that shows up gradually through repeated use rather than a single moment of delight. Discovery questions need to account for this, asking about budget approval, team impact, and ongoing use, not just first impressions.

Should I interview the end user or the budget holder for a B2B SaaS idea?

Both, and separately if possible. End users can tell you about day-to-day pain and workflow, while budget holders can tell you about approval process, existing spend, and what would justify a purchase decision. Their answers are often quite different.

What's a good question to test willingness to pay for a SaaS product?

Ask what they currently spend, in money or time, solving the problem today, and compare that to what a reasonable price for your solution would need to be. Direct "would you pay $X" questions are far less reliable than understanding existing spend.

How do I validate a SaaS idea with a long sales cycle?

Focus discovery on understanding the approval process itself — who needs to sign off, what evidence they'd need to see, and how long similar purchases have taken in the past — rather than expecting a fast validation signal like you might get from a consumer product.

What SaaS discovery mistake do founders make most often?

Interviewing only enthusiastic early adopters within their own network, who tend to be more forgiving of a rough pitch and unrepresentative of a typical buyer's actual decision process.