You talked to some potential customers. They seemed interested. So now you're either about to spend six months building or you're paralyzed wondering if their interest was real.
The problem is simple: you can't tell the difference between "that's a cool idea" and "I would actually pay money for that."
Most validation advice won't help you figure it out.
People say yes to things they will never buy.
It's not lying. It's default politeness. Someone asks you "would you use this if it existed?" and saying no feels rude. Saying yes feels easy. You say yes and move on with your day.
A founder hears yes and thinks they found validation.
They didn't. They found politeness.
The gap between saying yes and actually changing your behavior is enormous. Most founders miss it because they're not listening for the right signals.
You need to know what you're actually listening for.
Real validation has a specific shape. It looks like inconvenience.
When someone genuinely needs what you're offering, they have already tried to solve the problem another way. They're using a workaround. They're spending money on a partial solution. They're doing manual work that takes hours every week.
That's the signal.
Not interest. Not enthusiasm. Inconvenience.
A founder with a real problem will describe their current solution first. Unprompted. They'll show you the spreadsheet they built. They'll tell you about the tool they're using that kind of works but costs too much. They'll mention the three hours a week they spend doing something by hand.
When you hear that, you've found something.
When someone just says "yeah that sounds useful," you haven't found anything yet.
Here's what else matters: specificity.
A real problem gets described with details. Names of the tools they're using now. Numbers. Specific workflows. Actual dollar amounts they're spending or losing.
A fake problem gets described in vague language. "It would be nice to have." "That could help with our process." "We'd probably use that."
Listen for the difference. It matters.
Another signal: they push back.
If someone truly cares about a solution, they won't just accept your idea as you describe it. They'll argue about it. They'll say "but what about this edge case?" or "that won't work because we also need this." They'll have opinions.
That's real engagement.
Generic interest produces generic responses. Real need produces friction.
Stop thinking of validation as a conversation.
Think of it as an invitation to change behavior.
Here's what actually works:
Find one person with the problem. Not ten. Not a survey. One real person who has experienced the exact problem you think you're solving. Describe it back to them. Use their words. Get them to nod and say "exactly, that's it."
If you can't find someone who experiences the problem you think you're solving, you don't have a problem worth solving yet.
Watch what they do now. Don't ask them what they do. Watch them do it. See the workaround. See the tool. See the hours. See the cost. See the frustration. That's your real data.
Ask them to do something hard. The strongest validation signal is someone willing to take action before your product exists. Not action in your product. Action in the real world.
Maybe they're willing to give you an hour of their time to teach you their process. Maybe they're willing to fill out a detailed survey about their current workflow. Maybe they're willing to get their team in a room to walk you through what they're doing.
People who aren't genuinely interested won't do that. People who are will.
Get them to commit to something. Before you build anything, get them to put their reputation or money on the line. Ask them to refer you to three other people with the same problem. Ask if they'd be a beta customer at a specific price point. Ask if they'd pay for a pre-sale of your solution.
Real interest means willingness to commit.
Not a big commitment. But a real one.
Sometimes you'll hear genuine inconvenience from one person and generic interest from five others.
That doesn't mean you're ready to build.
It means you found one person with a real problem. Now find two more.
If you can find three different people, who don't know each other, who are experiencing the exact same problem, who are all inconvenienced by their current solution, and who all show genuine interest in yours, you have something worth building.
If you can't find three, you don't.
It's that simple.
Sometimes you'll get mixed signals because the problem is real but your solution is wrong. Someone will describe the problem perfectly and then push back hard on how you're thinking about solving it. That's not a reason to stop. That's a reason to listen.
Adjust your solution based on what you learn. Then test again.
Sometimes you'll get mixed signals because you're asking the wrong people. You found someone interested but they're not your real customer. Keep looking.
And sometimes you'll get mixed signals because the problem isn't real. You'll be able to find one person who's frustrated but can't find others. You'll notice people use vague language when you ask them about it. You'll see that their current workaround works fine and they're not actually motivated to change.
That's the signal to stop.
Not because you failed. But because this idea won't work and you found out before you built it.
Validation isn't about collecting yeses.
It's about finding the specific person who will change their behavior because you solved their problem. Then figuring out how many of those people exist.
If you can find three, you've got something worth building.
If you can't, you've saved yourself six months.
Either way, you know before you start.
If you're trying to figure out whether to build this or move to the next idea, Acrein Lab exists exactly for this moment. We help you validate before you commit.
The right conversation at the right moment changes everything. Let's have it.
Talk to us