Customer Insights: How to Discover What Your New Market Truly Needs

When you build a product for a new market, the hardest part is figuring out what customers really want and need. That is the entire foundation for everything that follows — product design, roadmap prioritization, go-to-market strategy.

Most candidates stumble here because they treat customer feedback as a checklist of feature requests instead of a source of insight. They miss the subtlety: customers don’t always know what they want, and what they say is often a symptom, not the problem.

Your actual job is to discover the underlying needs, motivations, and behaviors that drive purchase decisions. Without that, you are building guesses, not products.

The stakes of shallow customer research

I have watched thousands of PMs and founders dive into customer feedback without a framework. The pattern is consistent:

• They start by collecting feature requests or complaints.
• They treat every request as equally important.
• They try to satisfy every voice, leading to a sprawling backlog.
• They launch features that nobody uses or that solve the wrong problem.
• The product fails to gain traction or misses its business targets.

This is what the recruiter wants to know when they ask: How do you determine what customers want and need in a new market? They want to hear that you go beyond surface-level feedback to uncover the core drivers of customer behavior. That you connect those with business implications. That you make product decisions with accuracy and confidence.

Three pillars of customer insight for new markets

The process has three pillars:

1. Research with intent and structure. Use a mix of qualitative and quantitative methods to gather data. Don’t start with surveys of thousands — start small, focused, and expand as you learn.

2. Interpret feedback to find patterns and root causes. Customers rarely articulate their real needs directly. They describe workarounds, frustrations, or desired outcomes. Your job is to decode these signals.

3. Categorize and prioritize based on impact and frequency. Not all needs are equal. Some are niche but critical, others are common but low impact. You need a way to group and rank them to make trade-offs.

This is not a checklist exercise. It requires curiosity, discipline, and a mindset that treats customer insights as hypotheses to be tested, not facts to be implemented blindly.

How to start customer research in a new market

Step 1: Begin with a small, focused sample

You never start by surveying thousands of users in a new market. That is a recipe for noise, not clarity.

Instead, start with 10 to 20 carefully selected users who represent your target segments. These can be current customers, prospects, or even users of competing products.

At Pragmatic Leaders, when we launched a new learning product, we began by interviewing 15 users from diverse backgrounds — students, working professionals, and coaches. This helped us understand the different contexts and needs before scaling up.

Step 2: Use qualitative interviews to uncover behaviors and motivations

Ask open-ended questions about how users currently do their jobs, what frustrates them, and what workarounds they use.

Avoid yes/no questions or leading questions like "Would this feature resolve your problem?" because users tend to say yes to please you without real conviction.

Instead, ask:

• "Walk me through the last time you tried to solve this problem."
• "What tools or processes did you use?"
• "What was hard or frustrating about it?"
• "Have you tried any alternatives?"
• "What would make this easier or better?"

These questions reveal latent needs — the real "job" the user is hiring your product to do.

Step 3: Supplement with surveys for scale and validation

Once you have qualitative themes, design surveys with focused questions to validate patterns at scale.

Keep surveys short and targeted — users will abandon long forms.

Use quantitative data to identify how widespread a need or pain point is, and segment responses by user type or behavior.

Step 4: Conduct competitive and market research in parallel

Understand how competitors solve similar problems and where gaps exist.

Market research helps size the opportunity and informs positioning.

But your primary source remains your customers.

How to interpret and categorize customer feedback

Look beyond feature requests to the underlying problem

Customers rarely say, "I want feature X." They say, "I’m frustrated because I have to do Y manually."

For example, a customer might ask for a "duct tape" to hold a CD case. But what they really want is a solution that prevents their CDs from breaking or getting lost.

You need to decode these requests into core needs:

• What is the job the customer is trying to get done?
• What obstacles do they face?
• What outcomes do they value?

Group feedback into themes

Categorize customer inputs into buckets such as:

• New ideas (unmet needs, new workflows)
• Existing ideas (requests to improve current features)
• Priority requests (features requested by many users)

This helps you see where demand clusters.

Quantify frequency and impact

Count how many users mention each theme, and estimate the business impact of solving it.

A feature requested by 5% of users but critical to retention may trump one requested by 30% but with low impact.

Use frameworks like "Jobs to be Done" or "Mom Test" to avoid biases

The Jobs to be Done framework encourages you to understand the real tasks customers hire your product for.

The Mom Test teaches how to ask questions that avoid false positives from polite or biased answers.

How to make product decisions based on customer insights

Align insights with business objectives

Not every customer request fits your strategy or market opportunity.

Your job is to balance customer needs with business goals and technical constraints.

Prioritize problems, not solutions

Focus on the core problems that, when solved, unlock value for many users.

Avoid jumping to solutions too early.

Use data to validate assumptions and measure impact

After building features, track metrics that show if you solved the problem.

Iterate based on real user behavior.

Document and communicate your rationale

Make your prioritization decisions transparent by linking them to customer insights and business impact.

This builds trust with stakeholders.

Common mistakes to avoid

Test yourself: The New Market Launch

Where to go next

• Develop your user research skills: User Research Methods
• Learn how to prioritize product features: Prioritization Frameworks
• Understand market sizing and competitive analysis: Market and Competitive Research
• Practice translating insights into roadmaps: Roadmap Planning

PL alumni now work at Flipkart, Razorpay, PhonePe, Swiggy, Amazon, and 30+ other companies.