Future Hypothesis in Customer Interviews: Stop Asking Would You Use This

"Would you use this?" is the most expensive cheap question in startup discovery.

It costs the customer nothing to say yes. It costs the founder months if they believe it.

The future hypothesis mistake happens when a founder asks someone to predict whether they would use, buy, pay for, switch to, or care about a product that does not yet exist. The answers are usually optimistic, vague, and detached from the customer's real constraints.

Why future answers feel so good

Future questions produce clean sentences:

"Yes, I would definitely use that."

"I could see myself paying $20 per month."

"That would be really helpful."

Those answers are emotionally satisfying because they sound like demand. They also arrive quickly. A founder can ask ten people and collect ten encouraging predictions in a week.

The problem is that real adoption is full of friction. The customer may need approval. They may already have a workaround. They may dislike switching tools. They may agree in principle but never feel enough pain to act. They may have no budget. They may simply be trying to be supportive.

A Reddit thread about validating SaaS ideas makes the practical point founders often rediscover: asking about past behavior is a stronger indicator than asking people to speculate.

The better evidence is behind the past

Instead of asking:

"Would you use an AI meal planner?"

Ask:

"Tell me about the last time you planned meals for the week. What did you actually do?"

Instead of:

"Would you pay for a tool that summarizes sales calls?"

Ask:

"Have you ever paid for a tool, contractor, or internal process to improve sales call review?"

Instead of:

"If this existed, would you switch?"

Ask:

"What would have to go wrong with your current setup before you would consider switching?"

Past behavior has texture. It contains dates, workarounds, people, tools, budgets, and consequences. It can be checked. It can surprise you.

Future intent floats.

What if the product does not exist yet?

Founders often defend future questions by saying, "But they cannot talk about using my product because it does not exist."

Correct. That is why you should not ask about your product first.

Ask about the problem space. Your product is only one possible response to that problem. If the customer has never tried to solve the problem, never searched for alternatives, never complained to a coworker, never hacked together a workaround, and never spent money or time on it, then their future enthusiasm is weak evidence.

The sequence is:

1. Find the last real incident.
2. Understand the workaround.
3. Ask what made the workaround tolerable or painful.
4. Ask whether they have tried to improve it.
5. Only then test whether your product direction matches the reality you found.

How to handle willingness to pay

"How much would you pay?" is a future hypothesis with a dollar sign.

Better payment questions look backward or ask for a real commitment:

• "What have you paid for in this area before?"
• "Who approved that spend?"
• "What budget did it come from?"
• "What made the purchase worth it?"
• "Would you be willing to prepay for a manual version we deliver next week?"

The last question is no longer a pure hypothetical because it asks for present action. The moment the cost becomes real, the signal improves.

How Vera trains this

In Vera, future-hypothesis questions trigger fake-positive customer behavior. The AI customer may respond warmly and vaguely: "Yeah, I could see myself trying that." The founder hears something pleasant, but the truth score drops because no hidden evidence was earned.

To uncover useful facts, the founder has to ask about concrete history: past behavior, current workaround, payment history, and constraints.

That is the habit real discovery depends on. Stop asking people to predict the future. Ask them to narrate the past.