Should an Indian startup run design thinking before building its MVP?

The question comes up in almost every founder conversation we have in Pune and Bengaluru: "We have the idea and a small engineering team. Should we just build the MVP, or do design thinking first?" The honest answer is that design thinking and an MVP are not alternatives. Design thinking decides what the minimum viable product should be; the MVP tests whether people will adopt it. Skipping the first step does not save time, it moves the learning to a more expensive place.

Why do so many Indian startups build the wrong thing first?

India's startup base is now very large. The Commerce and Industry Ministry reported more than 2.23 lakh DPIIT-recognised startups as of 31 March 2026, with over 55,200 recognised in FY26 alone, a 51.6% rise on the previous year. In a written Lok Sabha reply in early 2026, the Minister of State for Commerce said 6,789 recognised startups had been categorised as closed or dissolved.

Closures have many causes, but one is consistent across markets. CB Insights' long-running analysis of startup post-mortems finds "no market need" cited in roughly 35% of failures, ahead of running out of cash or being out-competed. The product worked; nobody needed it enough to change their behaviour and pay.

The pattern starts early. At a Samsung Solve for Tomorrow 2026 design thinking workshop run with IIT Delhi in Greater Noida in June, student participants described the same reflex: assuming an idea is good because it sounds innovative, and learning instead to "validate whether a problem actually exists before attempting to solve it." Founders with funding and a dev team are not immune to the reflex; they simply pay more for it.

What does design thinking change about the MVP?

Design thinking, in the five-stage form most teams use, front-loads three things that a build-first MVP leaves to chance: who the user actually is, what job they are trying to get done, and which part of that job is painful enough to pay for. The MVP that comes out the other side is usually smaller, not bigger, because the team has dropped features that interviews showed nobody asked for.

How long does design thinking take before an MVP?

Far less than most founders fear. Three formats cover almost every early-stage situation we see in India:

1. One-day problem framing. Founders and the first two or three hires write the problem statement, map assumptions, and rank them by risk. Output: a list of the five assumptions that would kill the company if wrong, and a plan to test each one.
2. Five-day discovery sprint. Monday to Friday: map the problem, interview users, sketch solutions, build a clickable prototype, and put it in front of five to eight real users. We describe the full agenda in our guide to running a 5-day discovery sprint for B2B SaaS.
3. Two- to four-week discovery. For regulated or multi-stakeholder markets such as healthcare, lending, government or K-12 education, where the buyer, the user and the approver are different people and each needs a separate round of interviews.

Compare that with the two to four months a small team typically spends building a first version. Even the longest discovery format finishes before a build-first team has its first demo.

When is it reasonable to skip design thinking and just build?

Design thinking is not a ritual, and there are cases where a build-first MVP is the faster route to the same learning:

• You are the user. A team of chartered accountants building a GST reconciliation tool for CA firms already has the empathy data; it should still test pricing and workflow with peers, but a full discovery is overkill.
• The model is proven and you have distribution. If you are bringing a working category to a new Indian segment and already have the channel, the risk is execution, not need.
• The build is cheaper than the research. A no-code landing page with a payment link can be live in a day. Where that is true, the landing page is the prototype.

Outside those cases, especially for B2B products sold to enterprises, hospitals, banks or schools, the people who will use the product rarely sit in the founding team, and assumptions about their day need to be checked before code is written.

How do you know the discovery worked?

A discovery has done its job when the team can answer four questions with evidence rather than opinion: which segment feels the problem most, what they do about it today, what they would stop doing if your product existed, and what they said when shown a price. If any answer is still a guess, the MVP scope is still a guess. We covered the metrics that make this measurable in does design thinking actually deliver ROI for Indian product teams?

One more signal: the MVP backlog should shrink after discovery. If the feature list grew, the sprint produced ideas, not decisions.

How Qodequay runs this with early-stage teams

Our design thinking consulting practice in Pune runs problem-framing days and five-day discovery sprints for founders and product teams, then hands the validated scope to our own engineering teams or yours. We build products ourselves too, including Abhigyaan, our VR learning platform deployed in 1,350 Maharashtra Zilla Parishad schools reaching 1.5M+ students, so the discovery output is scoped for engineers, not a slide deck. Qodequay is ISO 9001:2015 and ISO 27001:2022 certified. Book a 30-minute discovery call to scope a sprint for your idea.