Startup & Growth

What an MVP Is, and What It Definitely Is Not

Not a cheap version of the product and not a prototype. An MVP is an experiment with a hypothesis — and most of the value is in what you agree not to build.

Purushottam Kumar Suman
Purushottam Kumar Suman
Founder & CEO, Drema AI
8 min read
Diverse group discussing startup ideas in a creative office

The term has been diluted until it means 'version one, but rushed'. That reading produces the two failure modes we are most often asked to rescue: a nine-month build of unvalidated features, or something assembled so carelessly that traction forces an immediate rewrite.

01

It is an experiment with a hypothesis

An MVP tests one belief your business depends on. Write the belief down as a sentence — 'clinics will pay ₹8,000 a month to cut appointment no-shows' — and the scope follows from it. Without a stated hypothesis there is no principle for deciding what to leave out, and everything ends up in.

If you cannot state the hypothesis in one sentence, you cannot scope the MVP.

02

Viable means someone would actually use it

The minimum is real. A signup form measures curiosity, not demand. To learn whether people will pay, the thing has to do the job well enough that using it is a rational choice, which means one workflow done properly rather than five done partially.

03

Cut breadth, not quality

The right reduction is scope: fewer features, fewer user types, one platform, one segment. The wrong reduction is care: no error handling, no tests, no thought about data structure. Breadth is recoverable later; a foundation you have to replace at the moment of traction is the expensive kind of shortcut.

Cut: featuresOne workflow, done completely
Cut: audiencesOne segment, not everyone
Keep: real paymentsWillingness to pay is the test
Keep: analyticsThe whole point is learning
04

Instrument it, or you learn nothing

An MVP without analytics is a launch, not an experiment. Decide before building what signal would confirm or refute the hypothesis, and instrument for exactly that. Teams that skip this end up interpreting the result through whatever they already believed.

05

Six to ten weeks, or rescope

If a proposed MVP will take six months, it is not one. That is a product build wearing the label to avoid a difficult prioritisation conversation. When we see a six-month scope, we work backwards to the smaller thing that would answer the question first.

06

Be willing to accept the answer

The uncomfortable outcome is the valuable one. If the evidence says no, that is a year and a great deal of money saved, and it is worth more than another phase of building in hope. Agreeing in advance what result would make you stop is what makes the experiment real.

1
Hypothesis, written down
6-10 wks
Or it is not an MVP
Real money
The only convincing signal
Purushottam Kumar Suman
Written by
Purushottam Kumar Suman
Founder & CEO, Drema AI

Founder and CEO of Drema AI. Builds AI systems, SaaS platforms and industry software — and writes about what actually survives production.

CTA Background

Got a problem like this one?

Bring it to a call with a founder.You will get a straight answer, including when the answer is no.

View Our Work
AI-First Engineering
Secure & Scalable
Built to Deliver Impact