Lakhlani International
Research

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

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.

This guide explains what applied research is, how it differs from nearby activities, what a sound engagement defines before it starts and what it can and cannot promise. It reflects how Lakhlani International's Research & Innovation page describes its approach, and it does not claim any laboratory, facility or result that the page does not state.

A working definition

Lakhlani International's FAQ defines applied research as investigating a defined practical problem to inform a decision, product, process or venture. Three parts of that sentence do the work.

  • →A defined practical problem. The question is specific enough to investigate. "Is there a market for this?" is too vague. "Will operations managers at mid-sized food processors pay for this monitoring approach at a price that covers delivery cost?" is a question that can be tested.
  • →To inform a decision. The output is not a report for its own sake. It helps someone decide whether to build, buy, partner, pivot or stop.
  • →A product, process or venture. The focus is practical outcomes, not new knowledge for its own sake.

How it differs from related activities

Applied research compared with nearby activities

  • →Basic research. Purpose: extend general knowledge without a specific application in mind. Typical output: scientific findings and publications.
  • →Applied research. Purpose: answer a defined practical question to support a decision. Typical output: evidence, a synthesis and a recommendation.
  • →Product development. Purpose: build and refine a product to a specification. Typical output: a working product.
  • →Market research. Purpose: understand customers, competitors and demand. Typical output: market insight.
  • →Innovation consulting. Purpose: structure how an organisation explores and evaluates new ideas. Typical output: frameworks, plans and decisions.

In practice they overlap. A single engagement might include applied research on technical feasibility, market research on demand and consulting on how to decide. The useful distinction is whether the work is organised around a decision and an evidence standard.

What a sound engagement defines up front

The capability page states that a sound engagement defines four things.

  1. The question. What exactly are we trying to find out?
  2. The evidence standard. What would count as convincing evidence, and what would not?
  3. The validation method. How will we collect it, and is the method proportionate to the stakes?
  4. The decision. What choice will the findings inform, and who makes it?

If any of the four is vague, research tends to wander. Teams collect interesting facts that do not settle the question.

The three tests every idea faces

A useful way to organise questions comes from Tim Brown of IDEO, whose book Change by Design (2009) describes innovation as the balance of three criteria.

  • →Feasibility: can we build or deliver it with the technology and capabilities available?
  • →Desirability: do the intended people want it enough to use or buy it?
  • →Viability: can it sustain a business, with a workable model and economics?

The Lakhlani International page names a specific problem: technical feasibility and market demand being conflated. Separating these tests is often the single most valuable step, because a technically excellent idea can still lack demand, and a desired idea may be impossible to deliver profitably. The companion article on why feasibility is not demand goes deeper.

Staging: how mature is the idea?

Researchers and engineers often describe progress in stages. NASA's Technology Readiness Levels, for example, run from TRL 1, where basic principles are observed, to TRL 9, where a system has been proven in operation. The scale was designed for aerospace, and other sectors adapt it, but the principle is useful anywhere: different stages need different evidence. An early concept needs proof that the idea is plausible. A prototype needs testing in realistic conditions. A near-product needs evidence of reliable delivery and demand.

Matching the validation method to the stage is what the page means by "proportionate validation methods". A heavy test on an immature idea wastes money, while a light test on an expensive decision wastes the chance to avoid a costly mistake.

What you should expect to receive

Per the capability page, an engagement can produce:

  • →A research question and hypothesis register.
  • →A proposed validation plan and evidence criteria.
  • →A synthesis of findings, uncertainties and limitations.
  • →A decision brief outlining options and next experiments.

Notice that the last item is a decision brief, not a verdict. The recommendation takes one of three forms: proceed, revise or stop, with a rationale.

What it cannot promise

The page is candid on three points.

  • →Not every project produces a commercial product. Research may show that an idea needs revision or should not proceed. A credible process records negative and inconclusive findings as well as positive ones.
  • →Technical testing needs the right resources. It can be part of a project where suitable facilities, qualified specialists, methods and budgets are agreed. Nothing here implies that every engagement includes laboratory work.
  • →Evidence has limits. Findings come with uncertainties and alternative explanations, which a good synthesis states.

A negative result is a useful result. It can save a team the cost of building something nobody wants or cannot deliver.

An illustrative scenario (hypothetical)

Consider a hypothetical founder with a prototype sensor that can detect a quality problem in packaged goods. The engineering results are promising, and the founder wants to raise money to build a full product.

A structured approach starts with the decision (invest in building the product or not), and breaks the question into three. Feasibility: does the sensor work reliably in real factory conditions? Desirability: do quality managers see this problem as costly enough to change how they work? Viability: could the price cover the cost to serve? Evidence criteria are set before testing. The founder discovers that the sensor works, but that most target factories already catch the problem at an earlier stage, so only a narrow segment would buy. The recommendation is to revise: focus on that segment before building more. This scenario is invented for illustration and does not describe any client.

Where to start

Write one sentence describing the decision you face, and one describing what evidence would change your mind. If you cannot write the second sentence, you are probably not ready to design the research, and drafting it is a useful first step.

If you would like to discuss a research question, validation programme or potential venture partnership, the Research & Innovation capability sets out how the work runs, and the partnerships page covers working with Lakhlani International on a venture basis.

Research & Innovation

A research question and hypothesis register, a validation plan with evidence criteria, a synthesis and a decision brief.

Explore the capability

Technical feasibility is not market demand

Why promising ideas fail when they are tested late, and how to test the riskiest assumption first.

Read the next article

Venture partnerships

For research collaboration, joint development or a venture partnership rather than a one-off study.

Explore partnerships

Contact Lakhlani International

For a research question or potential project, start with a conversation.

Go to contact

Frequently asked questions

What does applied research mean?

Applied research investigates a defined practical problem to inform a decision, product, process or venture. It focuses on answering a specific question with evidence, rather than expanding general knowledge.

What is the difference between applied and basic research?

Basic research aims to extend general knowledge without a specific application in mind. Applied research starts from a practical problem and aims to inform a decision about it.

Will every research project produce a commercial product?

No. Research may show that an idea needs revision or should not proceed. A credible process records negative and inconclusive findings as well as positive results.

Can applied research include technical testing?

It can, where suitable facilities, qualified specialists, methods and budgets are agreed for the project. It should not be assumed, and any claim of facilities needs to be confirmed with the provider.

How do I know if my idea needs research before development?

If a build or investment decision depends on assumptions you have not tested, such as demand, technical performance or economics, research is probably worth doing first. Match the effort to the cost of being wrong.

What should I prepare before discussing a research project?

Bring the problem statement, current evidence, the decision you want to inform, available resources, and any confidentiality or intellectual-property considerations.

References

  • →Lakhlani International. Research & Innovation capability page. https://lakhlaniinternational.com/capabilities/research-innovation
  • →NASA. Technology Readiness Levels. https://www.nasa.gov/technology/technology-readiness-levels/
  • →Brown, T. Change by Design: How Design Thinking Transforms Organizations and Inspires Innovation (2009).

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

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

Mayank N Lakhlani

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.

Read article→

Enjoyed this article?

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