Getting feedback before you launch: what to ask, who to ask, when to stop

Every founder we work with has done some version of this: shown their idea to a handful of people, got a few encouraging nods, and filed it under validated. And look, we get it. When you've been living inside your idea for weeks or months, any positive signal feels like oxygen. But here's the thing - most of those nods aren't feedback. They're politeness.

Unstructured feedback from the wrong people is worse than no feedback at all, because it gives you confidence without evidence. You end up building something that your mates think sounds cool, rather than something your actual users would pay for. And that's a very expensive mistake to discover after launch.

Unstructured feedback is noise. Structured feedback from the right people is signal.

So before you launch - before you even build, ideally - you need a proper approach to getting input that actually changes your decisions. Not a full-blown research methodology, mind you. Just some discipline around three questions: who do I ask, what do I ask them, and when do I stop asking?

Your mum thinks it's brilliant (that's the problem)

The single biggest mistake founders make with pre-launch feedback is asking people who have no reason to be honest with them. Friends, family, colleagues - they all want to be supportive. Which is lovely, but completely useless when you're trying to figure out whether strangers will hand over money for what you're building.

The people you need to talk to are target users - people who actually have the problem you're solving, right now, and who are currently doing something about it (even if that something is a messy spreadsheet or a string of WhatsApp messages). These are the people whose behaviour will tell you something real. If someone doesn't recognise the problem you're describing, they're not your audience, and their opinion - however well-intentioned - will steer you wrong.

Where do you find them? Wherever they already congregate. Industry forums, LinkedIn groups, Reddit communities, Slack channels. It takes a bit of graft, but five conversations with genuine target users will teach you more than fifty with people in your existing circle. And yes, it can feel awkward to cold-approach strangers. But most people are surprisingly willing to talk about their problems - especially if you're not trying to sell them something yet.

Stop asking questions that invite applause

Here's a question that sounds useful but isn't: "What do you think of my idea?" It practically begs for a compliment. And you'll get one, because people are nice, and then you'll walk away feeling great while learning absolutely nothing.

The questions that generate real signal are the ones that focus on the person's existing behaviour, not your solution. Rob Fitzpatrick's The Mom Test is the best short guide on this, and it boils down to a simple rule: talk about their life, not your idea. A few examples of what that looks like in practice:

• "How are you dealing with [problem] right now?" - This tells you what you're actually competing with. Sometimes the answer is a competitor's product. More often, it's inertia, or a cobbled-together workaround that's just about good enough. Both are useful to know.
• "What's the most annoying part of that?" - You're looking for emotional specificity here. Vague frustration is common. Specific, repeated pain points are gold. If three different people independently mention the same friction, you've found something worth building around.
• "Have you looked for a better solution? What happened?" - This reveals whether the problem is painful enough to motivate action. Someone who's actively searched and come up short is a far better signal than someone who shrugs and says "Yeah, it's a bit annoying I suppose."

Notice what's missing from those questions: any mention of your product. That's deliberate. The moment you pitch, you stop learning and start selling - and people respond differently to a sales pitch than they do to a genuine conversation.

When to stop listening

There's a less obvious failure mode with pre-launch feedback, and it's this: never stopping. Some founders get so hooked on the research phase that it becomes a form of procrastination. Just a few more interviews. Just one more survey. I want to be really sure before we commit. At some point, you're not de-risking. You're just avoiding the scary part.

So how do you know when you have enough? A useful rule of thumb: when the surprises dry up. In the first few conversations, almost everything you hear will be new. By conversation eight or ten, you'll start predicting what people say before they say it. That pattern repetition is your cue. You're not going to reach certainty - that's not how this works - but you can reach a point where the broad shape of the problem is clear and you're hearing more confirmation than contradiction.

For most early-stage products, somewhere between 8 and 15 target-user conversations will get you there. Not a huge number. But they need to be the right conversations, properly structured, with people who genuinely match your intended audience.

What about conflicting feedback?

It will happen. One person wants the feature you were planning to cut. Another thinks your core proposition is solving the wrong problem entirely. And suddenly your clear picture looks like a mess again.

When feedback conflicts, resist the urge to average it out into something bland that pleases nobody. Instead, look for patterns beneath the surface. Often, contradictory feedback is actually two different user segments talking. One group might want a quick, lightweight tool. Another might want depth and customisation. That's not conflicting feedback - that's a segmentation insight, and it should sharpen your thinking about who you're building for first, not muddy it.

And sometimes, honestly, one person is just wrong. Not every piece of feedback deserves equal weight. Someone who perfectly matches your target user and has spent money trying to solve this problem? Their input counts for more than a casual observer's.

Build the habit early

The founders who do this well don't treat pre-launch feedback as a box to tick. They treat it as a discipline that carries through the entire life of their product. Because the market doesn't stop having opinions after you launch - and your ability to hear those opinions clearly, without flinching or filtering, is one of the biggest advantages you can have.

Getting this right before you build a thing will save you time, money, and the particular heartbreak of launching something nobody asked for. Getting it wrong - or skipping it entirely - is how good ideas end up as expensive lessons.

Five honest conversations with the right people will teach you more than five thousand polite ones with the wrong people.

If you're not sure whether you've got enough signal to move forward - or you want help structuring your pre-launch research so it actually informs what you build - book a discovery call with us. It's 30 minutes, no obligation, and you'll come away with a clearer sense of what you know, what you don't, and what to do next.