06 - Customer Discovery Interviews: How to Talk to Users and Discover What They Really Need

https://youtu.be/WFKguOEvAc8

Every startup begins with uncertainty.

You may have a vision, a strong idea, a prototype, or even a working product.

But there is one thing you don't know until you talk to real customers: whether your assumptions actually match their reality.

This is where customer discovery interviews become one of the most important tools for a founder.

Customer discovery is not about selling your product.

It is about listening.

It is about understanding how people actually work, what frustrates them, what they have already tried, what those problems cost them, and what happens when those problems remain unsolved.

For me, this is one of the most important disciplines in building a startup because it forces us to step away from our assumptions and get closer to reality.

Don't Build in a Vacuum

One of the easiest mistakes for a founder is to spend months building something without speaking to enough potential customers.

As a technical founder, it is especially easy to fall into this trap.

You can spend weeks designing architecture, selecting technologies, building APIs, creating interfaces and adding features.

Everything may look impressive.

But there is a fundamental question that remains unanswered:

Does anyone actually need this?

A product can be technically excellent and still fail because it solves a problem that customers don't consider important.

Customer discovery helps answer that question before we spend too much time and money building.

Customers Reveal Problems We Cannot See From Our Laptop

Founders naturally create assumptions about their customers.

We imagine how they work.

We imagine what frustrates them.

We imagine what they would pay for.

We imagine which features they need.

But imagination is not evidence.

A real customer may have a completely different workflow.

They may not even describe the problem in the way we expected.

They may already have a workaround.

They may consider something we thought was critical to be completely unimportant.

And sometimes they reveal a much bigger problem that we hadn't even considered.

That is the real value of customer conversations.

They expose the gap between what we think is happening and what is actually happening.

Customer Discovery Is Not a Sales Meeting

One of the biggest mistakes founders make during interviews is trying to sell their product.

They introduce themselves.

They explain the company.

They demonstrate the product.

They show the features.

Then they ask:

"Would you use this?"

This sounds like customer research, but it often produces misleading answers.

People are generally polite.

They don't want to discourage you.

They may say:

"That's a great idea."

But a compliment is not validation.

The real question is not whether someone likes your idea.

The real question is whether they have experienced the problem strongly enough to take action.

Talk About Their Life, Not Your Product

The best customer interviews focus on the customer's existing world.

Ask about their workflow.

Ask about their daily activities.

Ask what takes too much time.

Ask where mistakes happen.

Ask what they find frustrating.

Ask what they currently do when the problem occurs.

Ask what happens when the problem isn't solved.

The objective is to understand their life before introducing your solution.

This changes the conversation completely.

Instead of asking:

"Would you use our AI platform?"

you might ask:

"How do you currently find information when you need something from your organization's internal documents?"

That question can reveal much more.

Ask About What Actually Happened

One of the most useful principles in customer discovery is to focus on past behavior rather than future intentions.

People are not very good at predicting what they will do in hypothetical situations.

If you ask:

"Would you use this application?"

you may get a positive answer.

Instead ask:

"Tell me about the last time you experienced this problem."

Now you are discussing something that actually happened.

You can ask what they did.

Who was involved.

How long it took.

What tools they used.

How much it cost.

What went wrong.

What they did afterward.

Past behavior gives you evidence.

Future intentions give you opinions.

For startup validation, evidence is far more valuable.

Open-Ended Questions Create Better Conversations

Avoid turning an interview into a questionnaire.

Questions that can be answered with "yes" or "no" usually don't give you enough context.

Instead, use prompts such as:

"Tell me about..."

"Walk me through..."

"What happened the last time...?"

"How do you currently handle...?"

"What did you try before?"

These questions encourage customers to tell stories.

And stories contain information.

You learn about their environment, their priorities, their frustrations and the workarounds they have created.

Sometimes the most valuable insight comes from something the customer says casually while explaining how they currently work.

Listen More Than You Talk

A useful rule for customer discovery is the 80/20 principle.

Try to spend roughly 80% of the conversation listening and only 20% asking questions.

Your job is not to impress the customer.

Your job is to understand them.

This can be difficult for founders because we are naturally passionate about our ideas.

When a customer describes a problem, we immediately want to explain how our product could solve it.

Resist that temptation.

Keep listening.

Ask another question.

Go deeper.

Let them finish.

Sometimes silence is extremely valuable.

If you stop talking for a few seconds, people often continue explaining their thoughts.

And those additional sentences can contain the most useful information in the entire conversation.

Don't Lead the Customer to the Answer

Another common mistake is asking questions that already contain your assumption.

For example:

"Don't you think manually preparing reports is frustrating?"

The question itself suggests the answer.

Instead ask:

"How do you currently prepare your reports?"

Then listen.

If the process is genuinely frustrating, the customer will tell you.

Neutral questions are much more valuable because they allow reality to emerge naturally.

Your goal isn't to prove your hypothesis.

Your goal is to discover whether your hypothesis is correct.

Compliments Are Not Validation

Founders love hearing:

"This is a great idea."

It feels encouraging.

But compliments are not the strongest signals.

Look for behavior.

Did the customer actually experience the problem?

Did they spend money trying to solve it?

Did they create a spreadsheet because existing software wasn't sufficient?

Did they hire someone to handle the problem manually?

Did they spend several hours every week dealing with it?

Did they build their own internal tool?

Did the problem cause lost revenue or customers?

Those are much stronger signals.

Behavior is usually more trustworthy than enthusiasm.

Talk to the Right People

Another important part of customer discovery is selecting the right people to interview.

Not everyone is your customer.

If you are building a solution for manufacturing companies, talking primarily to people who have never worked in manufacturing may give you interesting opinions but very little useful validation.

If you are building an enterprise finance product, talking only to individual consumers won't tell you enough about enterprise workflows.

The people you interview should actually experience the problem you are investigating.

This sounds obvious, but it is surprisingly easy to get wrong.

Founders sometimes interview people who are convenient to reach rather than people who are relevant to the problem.

Convenience is not the same as customer relevance.

Ask About the Last Time They Experienced the Problem

One of my favorite customer discovery questions is:

"Tell me about the last time you faced this problem."

This question forces the conversation into reality.

Instead of discussing hypothetical scenarios, you get a specific event.

You can then ask:

What happened?

What did you do?

How long did it take?

Who helped you?

What tools did you use?

What was frustrating?

How much did it cost?

What happened afterward?

These follow-up questions can reveal the actual economics and severity of the problem.

Ask What They Have Already Tried

Another powerful question is:

"What solutions have you tried already?"

This question can reveal enormous amounts of information.

Maybe they use Excel.

Maybe they use WhatsApp.

Maybe they have an internal application.

Maybe they hire people to perform the task manually.

Maybe they use an expensive enterprise platform.

Maybe they have tried several products and abandoned all of them.

Every workaround tells you something.

If customers are already spending money, time or effort trying to solve a problem, that can be a strong indication that the problem matters.

Ask What Isn't Working

Once you understand the current solution, ask:

"What works well?"

and:

"What doesn't work?"

This helps you identify the gaps in existing solutions.

You may discover that the customer isn't looking for something completely new.

They may simply want one frustrating part of their existing workflow to disappear.

That can be a much more focused startup opportunity.

Ask How Much the Problem Costs

Another important question is:

"How much time or money does this problem cost you?"

The answer can completely change how you think about the opportunity.

If a customer spends ten minutes every month dealing with an issue, the problem may not be particularly valuable.

If they spend four hours every week, the situation is different.

If the problem costs the company lakhs of rupees every year, the opportunity becomes even more interesting.

The cost isn't always financial.

It can also be lost productivity, delayed decisions, lost customers, compliance risk or employee frustration.

Ask What Happens If the Problem Isn't Solved

This is another question that can expose urgency:

"What happens if you don't solve this problem?"

If the answer is:

"Nothing really. It's just a little inconvenient."

you may not have a strong startup problem.

But if the answer is:

"We lose customers."

"We miss deadlines."

"Our employees spend days doing this manually."

"We lose significant revenue."

"We can face compliance penalties."

then the problem has much higher stakes.

Understanding consequences helps distinguish a genuine pain point from a minor inconvenience.

From Conversations to Insights

Customer interviews are valuable, but the conversations themselves aren't the final outcome.

The real value comes from what you do with the information afterward.

After every interview, capture detailed notes.

Don't just write:

"Customer doesn't like the current process."

That is too vague.

Instead document:

What problem did they describe?

How frequently does it occur?

What workaround do they use?

How much time does it consume?

How much money does it cost?

Who is affected?

How do they feel about it?

What solutions have they already tried?

What happens when the problem isn't solved?

These details turn conversations into usable product intelligence.

Look for Patterns, Not Individual Stories

One customer story is interesting.

Five customers describing the same problem is much more significant.

This is where patterns begin to emerge.

Imagine you interview ten finance managers and six independently mention that they spend several hours every month manually reconciling invoices across different systems.

Now you have something much stronger than one person's opinion.

You have a recurring pattern.

Patterns help you determine which problems deserve attention.

They also help prevent founders from overreacting to a single unusual customer.

Turn Conversations Into Clear Problem Statements

Instead of keeping dozens of disconnected interview notes, turn recurring insights into specific problem statements.

For example:

"Small business finance teams spend several hours every week manually reconciling invoices across multiple systems, resulting in lost productivity and delayed payments."

That statement is much more useful than:

"Users don't like accounting."

A strong problem statement gives your product team something concrete to solve.

It can become a compass for your MVP.

Let Customer Discovery Shape Your MVP

Once patterns become clear, use them to determine what you build first.

Don't create an enormous list of features.

Start with the most important pain points customers repeatedly describe.

If customers consistently struggle with one particular workflow, solve that workflow extremely well.

If another feature sounds interesting but customers don't care about it, deprioritize it.

This is one of the biggest benefits of customer discovery.

It prevents product roadmaps from being driven entirely by founder assumptions.

Customer Discovery and AINexLayer

This approach is particularly relevant to how I think about building AINexLayer.

Enterprise AI creates enormous possibilities.

But there are countless things we could potentially build.

The challenge isn't finding another AI capability.

The challenge is identifying where organizations have meaningful problems that AI can solve better.

For example, an organization may have thousands of documents but employees struggle to find the right information.

Another organization may have large amounts of business data but struggle to turn it into useful insights.

Another may have repetitive processes that consume significant employee time.

These are not merely technology opportunities.

They are customer problems.

And the right way to understand them is to talk to the people experiencing them.

Customer discovery helps us understand what organizations actually need rather than simply building what we think they should need.

If you want to experiment with AINexLayer and explore how AI can be applied to real business problems, you can try it at app.ainexlayer.com → Try AINexLayer.

Start With Five to Ten Interviews

You don't need to interview hundreds of people to begin learning.

Start with five to ten carefully selected customers.

The objective isn't statistical perfection.

The objective is depth.

Have meaningful conversations.

Ask follow-up questions.

Look for contradictions.

Pay attention when several people describe the same problem independently.

Then adjust your questions based on what you're learning.

The interview process itself should evolve.

Your first few conversations may reveal that your original assumptions were wrong.

That's a good outcome.

It means the process is working.

Quality Matters More Than Quantity

Ten shallow conversations aren't necessarily better than five deep ones.

The goal isn't to collect as many responses as possible.

The goal is to understand the problem deeply.

A single detailed story can reveal a workflow that you never considered.

A single customer can explain why existing solutions fail.

A single conversation can completely change your product direction.

That is why founders should focus on the quality of the conversation rather than simply counting interviews.

Customer Discovery Is an Ongoing Process

Customer discovery doesn't stop once you launch the MVP.

Your understanding of customers should continue evolving.

As you gain users, you learn more.

As the market changes, new problems appear.

As customers use your product differently than expected, new opportunities emerge.

As your company grows, your customer base becomes more diverse.

The best startups maintain a continuous feedback loop between customers and product development.

Listen → Learn → Build → Measure → Listen Again

That loop can become one of the most powerful systems inside a startup.

The Best Founders Listen

There is a tendency to think that great founders are great because they have extraordinary ideas.

Ideas certainly matter.

But I believe another skill is equally important.

The ability to listen.

The best founders aren't necessarily the people who talk the most about their vision.

They are often the people who spend the most time understanding the reality of the people they are trying to serve.

They listen without immediately defending their idea.

They accept uncomfortable feedback.

They change their assumptions.

They recognize patterns.

And they allow customers to influence what gets built.

That requires humility.

And humility is one of the most valuable startup skills.

What I Take Away From Customer Discovery

For me, customer discovery is ultimately about replacing assumptions with evidence.

Instead of saying:

"I think customers need this."

we ask them.

Instead of saying:

"I think this problem is painful."

we investigate what it costs them.

Instead of saying:

"I think they will pay."

we look for evidence of willingness to pay.

Instead of building for months and hoping customers appear, we involve customers in the learning process from the beginning.

This doesn't eliminate startup risk.

Nothing can.

But it can dramatically reduce the risk of building something nobody wants.

Don't Ask Customers to Validate Your Idea

Ask them to describe their reality.

That small change in mindset can completely transform customer discovery.

Don't walk into the conversation trying to prove that you are right.

Walk in trying to discover where you might be wrong.

Don't ask:

"Would you use my product?"

Ask:

"Tell me about the last time you faced this problem."

Don't ask:

"Do you think this is a good idea?"

Ask:

"What are you doing today to solve it?"

Don't ask:

"Would you pay for this?"

Ask:

"How much are you currently spending to solve the problem?"

The difference is enormous.

The Real Startup Advantage

Customer discovery may not look glamorous.

There is no funding announcement.

No impressive product demo.

No viral launch.

No big headline.

It may simply be a founder sitting across from a customer and asking questions.

But those conversations can determine whether the company builds something valuable or spends years solving the wrong problem.

The best founders don't assume they understand the customer.

They work relentlessly to understand them.

They replace opinions with evidence.

They replace assumptions with stories.

They replace features with problems.

And they use those insights to build products that customers actually need.

That is why I believe customer discovery interviews are not just another startup exercise.

They are one of the foundations of building a startup that matters.

Try AINexLayer

If you are exploring how AI can solve real problems across enterprise knowledge, data, analytics and business processes, you can experiment with AINexLayer here:

Try AINexLayer → app.ainexlayer.com

Take a real problem from your organization, explore the workflow, and see where AI can create practical value.