Lakhlani International
Research

Technical Feasibility Is Not Market Demand: Why Promising Ideas Fail When They Are Tested Late

A team spends a year proving that something can be built. The prototype works, the benchmarks are strong and the demo impresses visitors. Then the product reaches customers and the response is polite indifference. Nothing was wrong with the engineering. The question the engineering answered was not the question that decided the outcome.

This pattern is common enough that Lakhlani International's Research & Innovation page names it as one of the problems it addresses: technical feasibility and market demand being conflated. This article explains why the two get confused, what the failure data suggests, and how to test each before committing large budgets.

Three different questions

Tim Brown of IDEO, in Change by Design (2009), describes innovation as the balance of three criteria, which are useful because each asks a different question.

Feasibility, desirability and viability

  • →Feasibility. Question: can we build or deliver it with available technology and capabilities? Typical evidence: prototypes, performance tests, technical risk assessments.
  • →Desirability. Question: do the intended people want it enough to use or buy it? Typical evidence: observed behaviour, commitments, willingness to pay.
  • →Viability. Question: can it sustain a business with a workable model and economics? Typical evidence: unit economics, pricing tests, cost to acquire and serve customers.

An idea can pass one and fail another. A technically brilliant product may solve a problem nobody prioritises. A highly desired product may be impossible to deliver at a price customers will pay. Only an idea that satisfies all three is likely to become a business.

What the failure data suggests

CB Insights analysed 101 post-mortems from failed startups. The reason cited most often, in 42% of cases, was no market need. Running out of cash was cited in 29% and having the wrong team in 23%. Companies often gave several reasons, so the percentages do not add up to 100. The sample is small, the reasons are self-reported and the companies were mostly technology startups, so treat the figures as indications rather than rates.

They still point to a consistent lesson. Failure often traces back to demand and economics, which are exactly the questions that engineering success does not answer.

Why teams conflate the two

Several forces push in the same direction.

  • →Capability bias. Technical teams are good at testing technical questions, so that is what gets tested.
  • →Visible progress. A working prototype feels like proof. Market evidence feels slower and less certain.
  • →Friendly feedback. People who like the founder or the demo offer encouragement, which is not the same as intent to buy.
  • →Confirmation bias. Teams pay more attention to evidence that supports the idea. Research on published science shows how strong this tendency can be: Daniele Fanelli's 2010 study found that positive results are reported far more often in some fields than others, which he links to bias. Teams inside companies are not immune.
  • →Sunk cost. The more that has been spent on the build, the harder it is to ask whether anyone wants it.

Start with the riskiest assumption

Every idea rests on assumptions, and the sensible order of testing is by risk and by cost.

  1. List the assumptions the idea depends on across the three criteria.
  2. For each, estimate how likely it is to be wrong and how expensive a wrong answer would be.
  3. Test first the assumption that is most likely to be wrong and most costly if so, using the cheapest method that gives reliable evidence.

Often the riskiest assumption is about demand, and the cheapest test is a conversation or a small paid pilot, not a larger build. The capability page describes this as selecting proportionate validation methods.

Testing desirability

Start with behaviour, not opinions.

  • →Problem interviews about the past. Ask people to describe the last time they faced the problem, what they did and what it cost. Past behaviour is more reliable than predictions.
  • →Observation. Watch how the work is done today, including workarounds.
  • →Small pilots or manual versions. Deliver the outcome by hand to a few customers before automating it.
  • →Commitments. Pre-orders, paid pilots or signed agreements are stronger than compliments or informal interest.

The Business Strategy article on defining your customer and the problem offers an evidence ladder from opinion to payment.

Testing feasibility

Feasibility tests should aim at the specific technical risks that could sink the idea.

  • →Write down the performance the product must reach in real conditions, not ideal ones.
  • →Build the smallest prototype that tests the hardest technical risk first, not the easiest.
  • →Test under realistic conditions, including messy data, variable environments and real users where relevant.
  • →Record what you could not test and why.

The capability page notes that technical testing can be part of a project where suitable facilities, qualified specialists, methods and budgets are agreed. It does not assume every project includes it.

Testing viability

  • →Estimate the cost to deliver and serve one customer, with assumptions listed.
  • →Test pricing with real prospects, not only surveys.
  • →Estimate how customers would be found and what that costs.
  • →Check that the sums work at realistic volumes, not only at best-case volumes.

A concept can be desirable and feasible yet fail because each customer costs more to win and serve than they will pay.

Set evidence criteria before testing

Agree in advance what would count as support, what would count as weakening evidence and what you will do in each case. For example: "If at least a defined number of target customers agree to a paid pilot at the proposed price, we proceed to build the minimum version. If fewer, we revise the segment or the offer." Writing the thresholds beforehand protects against reinterpreting ambiguous results favourably. The page lists evidence criteria as part of the validation plan.

Warning signs

  • →The team can describe the technology better than the customer's problem.
  • →Nobody outside the team has used the prototype in real conditions.
  • →Feedback is positive but nobody has committed money or time.
  • →Success is defined as launching, not as customers keeping and paying for the product.
  • →Negative findings are explained away.

An illustrative scenario (hypothetical)

Consider a hypothetical team that has built a document-processing tool using a new technique that extracts data accurately from messy scans. Benchmarks are excellent. They plan a full product launch.

Separating the three tests exposes the risk. Feasibility is strong. Desirability is unproven: they have spoken to few buyers. Viability is unclear because the tool's processing cost per document is high. The team interviews fifteen prospective buyers about their last document backlog, offers three a paid trial and prices the processing cost per document. Two buyers commit, but only at a price below the team's cost. The finding is a revise recommendation: reduce processing cost or target a higher-value document type before building more. This scenario is invented for illustration and does not describe any client.

When outside perspective helps

Teams close to a technology often find it hard to design tests that could prove them wrong. An outside perspective can help frame the question, set evidence criteria and document findings and limitations. Lakhlani International's capability produces a research question and hypothesis register, a validation plan, a synthesis and a decision brief. It does not promise that every project will result in a commercial product.

To discuss a research question or validation programme, the Research & Innovation capability sets out what an engagement covers, and the contact page reaches the team. For the foundations, the guide to what applied research is covers the definitions.

Research & Innovation

A hypothesis register that separates feasibility, desirability and viability, with evidence criteria set before testing.

Explore the capability

What is applied research?

The introduction to this series: definitions, staging and what an engagement can and cannot promise.

Read the introduction

Define your customer and the problem

An evidence ladder from opinion to payment, from the Business Strategy series.

Read the guide

Contact Lakhlani International

For a research question or validation programme, start with a conversation.

Go to contact

Frequently asked questions

What is the difference between technical feasibility and market demand?

Technical feasibility asks whether something can be built or delivered. Market demand asks whether enough people want it enough to use or buy it. Each needs its own evidence, and passing one does not imply passing the other.

Why do startups fail even when the technology works?

Common reasons include lack of market need, running out of cash, the wrong team and unworkable economics. In CB Insights' analysis of 101 post-mortems, no market need was cited most often, though the sample is small and self-reported.

How do I test demand without building the product?

Talk to target customers about their recent behaviour, observe how they work today, deliver a manual version of the outcome to a few customers, and ask for commitments such as paid pilots or pre-orders.

What counts as strong evidence of demand?

Behaviour and commitment: customers who already spend time or money on the problem, or who agree to pay for a pilot. Compliments and informal interest are weak evidence.

When should I test feasibility first?

When the main risk is whether the technology can work at all, and testing demand would be meaningless until you know. Test whichever assumption is riskiest and cheapest to check first.

Should evidence criteria be set before or after testing?

Before. Agreeing thresholds in advance reduces the temptation to reinterpret ambiguous results in favour of the idea.

References

  • →CB Insights. The Top 20 Reasons Startups Fail (2018, 101 post-mortems). https://www.cbinsights.com/research/startup-failure-reasons-top/
  • →Brown, T. Change by Design: How Design Thinking Transforms Organizations and Inspires Innovation (2009).
  • →Fanelli, D. "Positive" Results Increase Down the Hierarchy of the Sciences. PLOS ONE (2010). https://pmc.ncbi.nlm.nih.gov/articles/PMC2850928
  • →Lakhlani International. Research & Innovation capability page. https://lakhlaniinternational.com/capabilities/research-innovation

Related articles

Research

Preparing for an Applied Research Partnership in India: A Brief Template and What the 2025 RDI Scheme Signals

Mayank N Lakhlani

Indian businesses and founders considering research and innovation work have had a new public policy to watch since mid-2025. This article explains what the Research Development and Innovation Scheme says on its face, what is not yet clear from the public sources reviewed here, and how to prepare a clear brief for any research partnership, whether or not public financing is involved.

Read article→

Research

How to Write a Research Question, Hypothesis Register and Validation Plan

Mayank N Lakhlani

Most research projects that disappoint were never really designed. They started with a topic ("explore the market for this"), collected material and ended with a long document that did not settle anything. The cure is to design the research around a decision before collecting any evidence.

Read article→

Research

Proceed, Revise or Stop: How to Make Staged Decisions on an Early-Stage Idea

Mayank N Lakhlani

The hardest decision in innovation is rarely whether to start. It is whether to continue. Money has been spent, people are invested and the evidence is mixed. Without an agreed way to decide, teams tend to drift: extending a project because stopping feels like failure, or abandoning it because of one discouraging result.

Read article→

Research

What Is Applied Research and Innovation Consulting? How It Differs from Basic Research and Product Development

Mayank N Lakhlani

Many new ventures start with a strong belief: a technology that should work, a market that should want it, a way of operating that should be cheaper. Belief is a fine place to begin and a poor place to commit large budgets. The gap between "should" and "does" is where applied research earns its keep.

Read article→

Enjoyed this article?

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