Lakhlani International
Business & Technology

Before You Build: How to Define Your Customer and the Problem Worth Solving

The most expensive mistake in a new venture is building something carefully that nobody needs. It happens to talented teams with good technology, because enthusiasm for a solution can run ahead of evidence about the problem.

This article explains what research says about how often that happens, and offers a practical way to define the customer and the problem, and to test both, before significant money is committed. It addresses the first problem listed on Lakhlani International's Business Strategy page: a business idea that lacks a clearly defined customer and problem.

What the failure data says

CB Insights analysed 101 post-mortems written by founders and others about failed startups. The most frequently cited reason was lack of market need, appearing in 42% of cases. Running out of cash was cited in 29%, and having the wrong team in 23%. Being outcompeted (19%), pricing or cost problems (18%) and lacking a business model (17%) followed. Companies often named more than one reason, so the percentages do not add to 100.

Treat the numbers with care. The sample is small, the reasons are self-reported, and the companies were mostly technology startups. Even so, the pattern is instructive. Several of the other reasons, such as poor pricing and an unclear business model, are close relatives of the same underlying issue: not understanding the customer and their problem well enough.

Start with a specific problem statement

A useful problem statement is narrow enough to test. Try to complete these sentences in plain language:

  • →Who has the problem? (A specific type of person or organisation, not "businesses".)
  • →When does it arise? (The situation or trigger.)
  • →What is the problem? (Described in the customer's words.)
  • →What do they do today? (The current workaround or competing option.)
  • →What does it cost them? (Time, money, risk or frustration.)

The fourth question matters most. If customers have no current workaround and are not spending time or money on the problem, the problem may not be urgent. If they already pay for an imperfect solution, you have evidence that the problem is real.

Choose a narrow first customer segment

"Everyone who might benefit" is not a customer. A narrow first segment lets you learn faster, speak more precisely and build for a clear need. Useful ways to segment include:

  • →By situation: customers who have just experienced a specific event or change.
  • →By role: the person who feels the problem and the person who pays may differ.
  • →By size or type of organisation: a ten-person business and a ten-thousand-person group rarely buy the same way.
  • →By current solution: people using a spreadsheet, a competitor or nothing.

Choosing a narrow segment is not a permanent decision. It is a way to find out whether your problem statement holds in one place before spreading effort across many.

Climb the evidence ladder

Not all evidence carries equal weight. A useful ladder, from weakest to strongest:

The evidence ladder

  1. Your own belief or an expert's opinion: a starting hypothesis only.
  2. Customers say the problem exists, in conversation: the problem is recognised.
  3. Customers describe specific recent incidents and what they did: the problem is real and current.
  4. Customers use a workaround or spend time or money on the problem: the problem has a cost.
  5. Customers commit, by pre-ordering, paying a pilot fee or signing an agreement: the solution has demand.

Many ventures stop at level 2 because compliments are easy to collect. Moving up requires asking about past behaviour rather than future intentions, and, eventually, asking for commitment.

This fits the approach on the capability page, which refers to customer, market and positioning hypotheses to validate. A hypothesis is a statement you intend to test, with a clear idea of what result would change your mind.

Write hypotheses you can fail

Turn the problem statement into testable hypotheses, each with an evidence threshold agreed in advance.

Hypothesis, test and evidence

  • →Owners of small clinics lose significant time to appointment no-shows. Test: interview a set of owners and ask about the last month. Evidence that would support it: most describe recent, costly incidents. Evidence that would weaken it: few mention it unprompted.
  • →They would pay for a fix. Test: offer a paid pilot. Evidence that would support it: several commit. Evidence that would weaken it: interest but no commitment.

The examples above are placeholders to show the format, not research findings. Define in advance what number of conversations and what proportion of positive responses you will treat as meaningful, and write it down before you start so that you do not reinterpret ambiguous results favourably.

Warning signs

  • →You describe the customer as a broad category.
  • →You can explain your technology better than the customer's problem.
  • →Customers praise the idea but do not change behaviour.
  • →You cannot name what customers use today.
  • →You are adding features to attract customers who are not yet engaged.

An illustrative scenario (hypothetical)

Consider a hypothetical founder building an analytics tool for "small businesses". Early conversations are positive, but no one commits. The founder narrows to independent physiotherapy clinics and learns, through interviews about the previous month, that missed appointments are frequent and that owners currently manage reminders by hand. Two clinics agree to a paid pilot for a simple reminder workflow, which is quite different from the original analytics idea.

The pivot came from specific evidence rather than from a new concept. This scenario is invented for illustration and does not describe any client.

When outside input helps

Founders are often too close to their idea to test it neutrally. An outside view can challenge assumptions, help frame the strategic question and structure the evidence to collect. Lakhlani International's capability work starts by defining the strategic question and desired decision, then reviews the customer, market, operational and financial inputs supplied. The page is explicit that it cannot guarantee a commercial outcome; what it offers is clearer assumptions and defined validation milestones.

To sharpen an early-stage idea, explore the Startup Acceleration capability. For the foundations of strategy, start with the guide to what business strategy is.

What is business strategy?

The foundations this article builds on: diagnosis, guiding policy and coherent action.

Read the foundational guide

Startup Acceleration

Support for early-stage ventures sharpening the problem, the customer and the evidence before committing budget.

Explore Startup Acceleration

Frequently asked questions

How do I know if my business idea solves a real problem?

Look for evidence of behaviour, not just opinion: customers who recently experienced the problem, describe what they did and already spend time or money on a workaround. Willingness to commit, such as a paid pilot, is the strongest signal.

How narrow should my first customer segment be?

Narrow enough that you can describe their situation precisely and reach a meaningful number of them. If you cannot picture a specific person and their week, the segment is probably too broad.

How many customer interviews are enough?

There is no universal number. Decide in advance what pattern would convince you, and continue until answers begin to repeat. A small number of well-chosen interviews about recent behaviour beats many casual chats.

What is the difference between a customer and a user?

The user experiences the product, while the customer pays for it. They can be different people with different priorities, so test the problem and the buying decision with both.

Is product-market fit the same as having customers?

Not exactly. Having customers shows some demand. Product-market fit usually implies a repeatable pattern: a defined segment that adopts, keeps using and recommends the product at acceptable cost. Define what it means for your business with measurable signs.

When should I pivot?

When your tests repeatedly fail to find the evidence you set as a threshold, and you have a specific, better-supported alternative to try. Pivoting on a hunch repeats the original mistake.

References

  • →CB Insights. The Top 20 Reasons Startups Fail (2018, 101 post-mortems). https://www.cbinsights.com/research/startup-failure-reasons-top/
  • →Lakhlani International. Business Strategy capability page. https://lakhlaniinternational.com/capabilities/business-strategy

Related articles

Business & Technology

Setting Up a BFSI or Fintech GCC in Mumbai: A Strategy Guide for Financial Services Leaders

Mayank N Lakhlani

Thinking of a BFSI or fintech Global Capability Centre in Mumbai? Compare cities, understand Maharashtra's GCC policy, and plan mandate, model and talent.

Read article→

Business & Technology

Mumbai's $300 Billion Ambition: A Business Strategy Guide for Companies in the Mumbai Metropolitan Region

Mayank N Lakhlani

How NITI Aayog's MMR roadmap and Maharashtra's GCC policy shape growth decisions for Mumbai businesses, and how to turn them into a practical strategy.

Read article→

Business & Technology

Doing Business Across Delhi NCR: A Strategy Guide for Companies Spanning Delhi, Gurugram and Noida

Mayank N Lakhlani

Delhi, Gurugram and Noida have different economic identities. Learn how to plan location, talent, funding and growth strategy across Delhi NCR.

Read article→

Business & Technology

Agentic AI in GCCs: Governed Automation That Survives Past the Pilot

Mayank N Lakhlani

India's Global Capability Centres are increasingly where enterprise AI work gets built. The Nasscom-Zinnov 2026 report puts India at about 28% of global GCC AI talent, second only to the US. That makes GCC leaders natural sponsors of agentic AI: systems that plan and take actions toward a goal rather than only answering prompts.

Read article→

Business & Technology

The Technology Blueprint for a New India GCC: Stack, Engineering Organisation, Security and DPDP Readiness

Mayank N Lakhlani

By the time a Global Capability Centre has a mandate and a location, the practical question is what to build first. Hiring engineers without a technology plan creates a centre that works hard and delivers inconsistently, with standards that differ by team and a security posture nobody has reviewed.

Read article→

Business & Technology

Captive GCC, Build-Operate-Transfer or Outsourcing: Choosing Your India Operating Model

Mayank N Lakhlani

Once a company decides it needs engineering capacity in India, a second question arrives quickly: should it build a captive Global Capability Centre, use a partner to build and run one before handing it over, or outsource the work entirely? Each route has defensible reasons behind it. The mistake is choosing by habit, cost headline or a vendor's pitch rather than by the nature of the work.

Read article→

Enjoyed this article?

Explore more ideas, research, and perspectives from the Knowledge Hub — or start a conversation with us.