Validating

Why "would you use this?" fails as idea validation

"Would you use this?" feels like validation but predicts almost nothing. Here is why the question fails and what a real demand signal looks like instead.

"Would you use this?" is one of the most common questions founders ask to validate an idea, and one of the least reliable. It measures a stated opinion about a hypothetical, which costs the person nothing and overstates what they will actually do. People say yes to be kind and to picture a more organized version of themselves. Real validation is not a yes on a survey, it is a real person doing something that costs them time, money, or reputation before the product exists. The question that predicts demand is not "would you use this" but "what are you already doing about this problem right now."

The question feels like research. It is closer to flattery with a clipboard.

Spend an hour in any founder community and you will watch the same move on repeat. Someone describes an idea, links a short survey, and asks the crowd if they would use it. The yeses roll in, the founder feels validated, and the build begins. Months later the product launches to silence. The problem was not the idea. The problem was the question.

Is "would you use this?" a good validation question?

No. It is a comfortable question, which is different. It asks a person to predict their own future behavior about something that does not exist yet, while being watched by the hopeful founder who built it. Almost everyone answers kindly, and almost none of them are lying on purpose. They just have no skin in the answer, so the answer means very little.

Why does "would you use this?" overstate demand?

Three things stack up. People want to be nice, so they round up. People imagine an idealized version of themselves who finally gets organized, eats well, and adopts your tool. And the question has no cost, so saying yes is free. A free yes is the cheapest currency on earth. You can collect a thousand of them and still not have a single customer.

What is the difference between stated and revealed preference?

Stated preference is what people say they want. Revealed preference is what they actually do when it costs them something. The entire history of failed products lives in the gap between the two. People say they will exercise and buy the gym membership they never use. They say they will switch tools and never do the migration. Validation that only collects stated preference is measuring the wrong half of the human.

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

Stop asking about the future and start asking about the past. The future is where people are generous. The past is where the truth already happened. Ask what they are doing about this problem today. Ask what they have already tried, and what they spent, and what they rigged together because no clean answer existed. A person who has duct taped a bad fix for a problem has shown you a real wound. A person who says your idea sounds useful has shown you good manners.

How do you know if validation is real?

It cost the other person something. That is the whole test. A pre order, a deposit, a signed letter of intent, a paid pilot, a migration off a tool they already use, or proof they already pay to solve the problem badly. A reservation with a refund button is softer, an email signup is softer still, and a survey yes is barely a signal at all. Rank your evidence by what the other person stood to lose. The more it cost them, the more it counts.

Key takeaways

  • "Would you use this?" measures a free, kind, hypothetical yes that overstates real demand.
  • People answer about an idealized future self, not the self who will actually decide.
  • Stated preference is what people say, revealed preference is what they do when it costs them.
  • The better questions point at the past: what have you already tried, spent, or hacked together.
  • Real validation is a costly act before the product exists, not a yes on a form.

FAQ

Is "would you use this?" ever useful?

It is fine for gathering language and framing, never for a build decision. Treat the answer as a hypothesis to test, not proof.

What is a better validation question than "would you use this?"

Ask "what are you doing about this problem right now, and what has it cost you." Past behavior predicts far better than predicted behavior.

Are surveys useless for startup validation?

Surveys are good at describing opinions and bad at predicting purchases. Use them to learn how people talk, not to decide what to build.

What counts as a real demand signal?

An action that costs the person time, money, or reputation before your product exists. A deposit beats a pre order, a pre order beats a signup, a signup beats a survey yes.

Why do founders keep asking "would you use this?"

Because it feels like progress and it usually returns good news. It protects the idea instead of testing it, which is exactly why it is dangerous.