How to Validate Demand Without Asking "Would You Use This?"

“Would you use an app that does X?” is one of the most common questions founders ask when trying to validate an idea, and it’s also one of the least useful. Almost everyone says yes. It costs nothing to imagine a convenient future, and most people are naturally inclined to be encouraging, especially to someone excited about their own idea. If you’ve relied on this question and gotten reassuring answers, it’s worth knowing that reassurance and real demand are not the same thing.

Here’s how to validate demand by asking better questions.

Why Hypothetical Questions Fail

A hypothetical question asks someone to predict their own future behavior, which people are notoriously bad at, especially about a product they haven’t actually used. There’s no cost to answering yes, no real decision being made, and no consequence if the prediction turns out to be wrong. This is the same weakness discussed in interest is not demand — anything that costs the respondent nothing tends to produce inflated, unreliable answers.

Ask About the Past, Not the Future

The single most useful shift you can make is to stop asking people to imagine the future and start asking them to describe the past. Instead of “would you use an app that helps you manage bookings?”, ask “tell me about the last time you had to manage a booking — what did you actually do?”

Past behavior is a far better predictor of future behavior than a hypothetical opinion, because it’s grounded in something real that already happened, not something the person is guessing about on the spot.

Useful Question Patterns

Ask about frequency and cost

“How often does this come up for you?” and “how much time or money does dealing with this currently cost you?” reveal whether the problem is significant enough to justify a new solution, rather than a minor annoyance.

Ask about existing workarounds

“What are you using today to deal with this?” often surfaces spreadsheets, manual processes, or competitor tools — evidence that the problem is real enough that people are already spending effort on it.

Ask what they’ve already tried

“Have you looked for a solution to this before? What did you find?” tells you whether this is an active, searched-for problem or one people haven’t thought to solve yet.

Ask about the last time it went wrong

“Tell me about the last time this really went badly” surfaces specific, vivid detail that a general question rarely produces, and specific detail is usually a stronger signal than a general impression.

Delay mentioning your idea

Hold off on describing your product until after the person has described their current situation in detail. Introducing your solution early anchors their answers to what you want to hear rather than their actual experience.

A Before-and-After Comparison

Weak Question	Stronger Alternative
“Would you use an app that does X?”	“Tell me about the last time you dealt with X.”
“Do you think this is a good idea?”	“What are you using today to solve this?”
“Would you pay for this?”	“How much does the current problem cost you, in time or money?”
“Do you have this problem?”	“How often does this come up, and how do you usually handle it?”
“Does this sound useful?”	“What have you already tried to fix this?”

Turning Interview Answers Into Evidence

Once you’ve collected several of these behavior-focused conversations, look for patterns rather than treating any single answer as conclusive. Consistent, specific complaints about the same workaround, or the same wasted time, across multiple independent conversations is much stronger evidence than a handful of polite hypothetical yeses. This pattern-matching approach connects directly to how to prove demand for a startup idea, where repetition and consistency across tests matter more than any single data point.

From Better Questions to Real Validation

Asking better questions doesn’t just improve your interviews — it changes what you build. A specific, painful, frequently occurring problem uncovered through past-behavior questions gives you a much sharper starting point for an MVP than a vague sense that “people seemed interested” ever could.

Frequently Asked Questions

Why is "would you use this app?" a bad validation question?

It's a hypothetical question that costs the respondent nothing to answer positively. Most people are naturally agreeable and will say yes to be polite, regardless of whether they'd actually adopt the product if it existed.

What should I ask instead of "would you use this?"

Ask about their current behavior and past actions instead of hypothetical future ones — how they solve the problem today, what they've already tried, and what it costs them. Behavior-based questions are far more predictive than opinion-based ones.

How do I know if a question I'm asking is leading?

A leading question suggests the answer you want to hear, often by mentioning your solution before the person has described their own experience. If your solution comes up before they've explained their current process, the question is likely leading.

Can I ever ask direct questions about my product idea?

Yes, later in the conversation, once you've heard about their current process and problem unprompted. Introducing your idea after listening, rather than before, keeps their earlier answers uncontaminated by what you're hoping to hear.

What's the single best question for validating a product idea?

There's no single best question, but asking someone to describe, in detail, the last time they encountered the problem — what they did, how long it took, what it cost them — tends to reveal more real signal than any hypothetical question about a future product.