How to find product–market fit: conversations with the right people, asked in the right way

Why conversations with your ICP should be the foundation of product development

Many founders start building with the belief that if they create an excellent product, the market will naturally respond. Unfortunately, this assumption rarely holds. Even a perfectly designed solution does not guarantee that customers will buy it, because people do not make decisions based solely on features or technical quality. They make decisions based on how they assess risk, the effort required to change their current workflows, and whether the promised benefits are relevant enough to justify that change. The only way to understand these factors is by talking to people who genuinely represent your ideal customer profile. Not industry acquaintances, not general audiences, but those who live the exact problems, processes, and constraints your product is meant to address. To gain real insights from these conversations, it is not enough to simply talk; one must also ask the right questions.

Focus on barriers, problems, and risks rather than trying to validate your idea.

People often assume they would buy the ideal version of a product, but their actual decisions usually look very different. This is why, in conversations, it is far more valuable to explore the obstacles they see rather than the features they find interesting. When someone tells you what might stop them from adopting a new solution: concerns about time, integration, fit, reliability, or internal approval, you are getting information that most founders overlook. If you understand these barriers early and address them directly, you gain an advantage over competitors who focus only on what their product does well. Solving or mitigating perceived risks is often more decisive than adding another improvement. A product that answers real concerns will always perform better in the market than one that merely appears better on paper.

Put your ego aside and ask for every flaw, weakness, and objection.

As a founder, you rely on confidence to build momentum and communicate your vision. But in conversations with potential customers, confidence can easily become a filter that prevents you from hearing what truly matters. Instead of seeking confirmation that your idea is strong, ask explicitly for every weakness, concern, and limitation they see, both in your concept and in the category as a whole. This approach not only reveals how your audience perceives your product but also highlights what they pay attention to, what creates doubt, and which objections you will need to address later through your product, messaging, or onboarding. People rarely share their genuine concerns spontaneously; they share them when they feel invited to do so. These insights are often the difference between building something customers like and something they trust enough to adopt.

Understand what keeps customers with their current solution.

Even if your product is objectively better, it does not automatically replace the existing option. Switching constantly involves effort, uncertainty, and disruption, and many aspects you consider superior may not be significant enough for the customer to justify the transition. This is why it is essential to understand what they appreciate in their current solution: what works well, what they rely on, and what they would recommend to a colleague. These elements create strong “anchors” that hold them in place. If you are unsure, you risk presenting a value proposition that does not resonate or asking customers to relinquish something they consider essential. By going deep into the strengths of the existing alternative, you gain clarity on what you must preserve, what you must exceed, and where your product must offer something meaningfully different.

Why founders must temporarily set aside their ego to uncover real insights

Founders need a strong ego to inspire teams, attract talent, and push a vision forward. But during market conversations, that same ego can limit what you learn. If you focus on defending your idea or highlighting its strengths, you may overlook concerns that customers may not express directly unless asked. By directing the conversation toward the advantages of the current solution and the weaknesses of your own idea, you reach the deeper fears and doubts that actually influence purchasing decisions. Ultimately, your goal is not for customers to like your product; your goal is for them to buy it. Understanding their objections and hesitations is the most effective way to make that possible.

A simple structure for interviews that leads to honest, actionable answers

To run conversations that generate meaningful insight rather than polite feedback, you can follow a structure that reflects how customers genuinely think about change:

1. Start with what they like in their current solution

This helps you understand what they value, what they rely on, and what they are unwilling to lose. These insights form the baseline that any new solution must respect.

2. Move to the problems they see with adopting something new

Explore the risks, barriers, and concerns related to switching in general and to your specific idea. This includes operational challenges, internal processes, uncertainty, cost, integration, or anything they fear might go wrong. It is essential to treat these concerns seriously, as they often outweigh the potential benefits. Then ask about potential risks and concerns related to your future product/service.

3. Only then ask about the ideal solution

After they have described what they appreciate and what they fear, they can now articulate what a genuinely valuable alternative would look like. Ask what they feel is missing today, how these gaps affect their work, and which outcomes would be meaningful enough to justify change. Explore how they currently compensate for the shortcomings of their existing tools and what would make that workaround unnecessary. Answers at this stage tend to be far more realistic and actionable because they are grounded in the context you already understand.

Why this approach leads you closer to real product–market fit

Product–market fit does not come from guessing features or validating assumptions. It stems from understanding how customers make decisions and shaping your product around their reality, rather than your expectations. When you learn what they value today, what they fear in switching, and what they would genuinely find better, you reduce uncertainty and build a product that aligns with real-world behavior. And in B2B especially, this alignment is what turns interest into adoption and conversations into revenue.