How to Get Feedback on a Business Idea Before Building It

Most founders think they've validated their idea when they've only collected opinions. Here's how to get feedback that actually tells you whether your idea is worth building.

Most founders think they've validated their idea when they haven't. They've collected opinions. And opinions, however well-intentioned, are not the same thing as validation. The distinction matters because acting on opinions rather than genuine feedback is one of the most reliable routes to building something nobody uses. CB Insights looked at 431 venture-backed companies that shut down from 2023 onwards and could pin down why 385 of them failed. Poor product-market fit accounted for 43%, and two thirds of those never found a market at all. The vast majority of those founders spoke to people before they built. They got feedback. It just wasn't the right kind.

Why most feedback is useless

The feedback most founders collect falls into one of three traps: The politeness trap: friends, family, colleagues, and even casual acquaintances are motivated to be encouraging. They don't want to crush your enthusiasm. So they tell you it sounds great. That's kindness, not feedback. The hypothetical trap: even well-meaning strangers will tell you what they think they'd do, rather than what they actually do. People systematically overestimate their own likelihood of trying new things and paying for new products. The leading question trap: most founders, consciously or not, pitch their idea when they're supposed to be gathering feedback. By that point the person being asked is responding to the pitch, not evaluating the idea independently.

What genuine feedback actually looks like

Genuine feedback tells you something you didn't already know. The most valuable signals are: Unprompted recognition of the problem: when you describe the problem you're solving, without mentioning your solution, and the person immediately says "yes, that's genuinely annoying, I deal with that all the time." Specific, detailed complaints about existing solutions: people who genuinely have a problem can tell you exactly what's wrong with how they currently solve it. Behavioural evidence over stated intentions: watch what people do, not what they say they'd do. Willingness to pay, tested directly: not "would you pay for this?" but "I can give you access now for £X a month. Do you want to sign up?"

How to structure feedback conversations properly

Talk to the right people: your target customer is not your network. It's the specific person who has the specific problem you're solving. Start with their world, not your idea: begin every conversation by understanding how the person currently handles the problem you're solving. Don't mention your idea at all initially. Introduce the idea late and loosely: when you do mention your idea, describe it as a concept you're exploring rather than something you're committed to. Listen for hesitation as much as enthusiasm: the most useful feedback often comes in the pauses, the qualifications, the "well, it depends" moments. Ask about money every time: before you end every conversation, ask directly what someone would expect to pay for a solution to this problem, and whether they'd pay it today.

The limits of conversation-based feedback

Conversations are an essential starting point. But they have a ceiling. The fundamental problem is that people cannot accurately predict their own behaviour, especially around new products. They don't know how they'll actually use something until they use it. This is why the most valuable feedback you can get on a business idea comes from putting something real in front of people. When someone uses a real product, their behaviour tells you things no conversation ever could. Where they hesitate. Where they go instinctively. Whether they come back. Whether they'd pay.

How to get real product feedback before committing to a full build

Bluprint's Prototype Sprint builds a real, fully functional digital product in five days from £750, something you can put in front of your target users this week and start collecting the kind of feedback that actually tells you whether to invest in building further. Traditional app development in the UK costs between £20,000 and £250,000. HM Treasury tells its own departments to assume software projects cost more than the first estimate. Its Green Book guidance on optimism bias sets the upper adjustment for developing software and systems at 200% on capital cost and 54% on duration, and tells appraisers to start at that upper bound rather than work up to it. Most of that money is spent before anyone has tested whether the core idea works. Spending £750 to find out first is not a compromise. It's the smarter sequence.

What to do with the feedback you collect

Weight behaviour over words: what people do matters more than what they say. Look for patterns, not outliers: one person who loves it and one person who hates it tells you nothing. Patterns across multiple users tell you something real. Separate "interesting" from "valuable": people finding your product interesting is not the same as finding it valuable enough to use regularly or pay for. Be willing to hear what you don't want to hear: the founders who build successful products are the ones who take negative feedback seriously rather than explaining it away.