Is a landing page an MVP?

A landing page can be the smallest test of demand, and Buffer called its two-page test an MVP. But it cannot show whether the product delivers value. Treat it as a demand test, not a product test.

How long should a landing page test run before I decide?

Long enough to reach your written stop condition with traffic that does not know you. Set the number before launch, not after you see the results.

How much does an MVP cost in India?

It depends on scope, integrations and design. At Gigzman, MVP development starts at ₹1,50,000 with a typical timeline of 6 to 12 weeks, and the final quote follows a written scope.

Can I skip the MVP and go straight to the full product?

You can, but if a negative result would not change your plans, you are not validating anything. An MVP that fails still does its job for a fraction of the full build's cost.

MVP vs Landing Page: What Each Can Prove for You

Before Buffer had any product code, Joel Gascoigne tested it with two web pages and a tweet. When he finally did build, the first version took 7 weeks of evenings and weekends, after he had told people it would take 1 week.

That gap is the whole MVP vs landing page decision. A landing page answers one kind of question in days. An MVP answers a different kind in weeks or months. By the end of this post you will know which question you are actually asking, what each test costs, and the signal that says it is time to build.

I'm Tarun, founder of Gigzman. We build MVPs for a living, so read this with that bias in mind. Even so, our own MVP page tells founders who have not yet described the idea to a potential user that building is premature.

MVP vs landing page: they answer different questions

Most posts on this frame it as "what should I build first?" That is the wrong axis. The better question is: what would change your mind? Each test below can change it about one thing, and only one.

The question you have	Cheapest test that answers it	What a yes looks like	What it cannot tell you
Does anyone have this problem badly?	Conversations with people in the market	They describe the pain before you do, and what they already pay to work around it	Whether they will pay you
Will they pay roughly this price?	A landing page with a real price and a waitlist	Strangers leave an email after seeing the price, some click a paid plan	Whether the product delivers
Is the output even wanted?	Doing the work by hand for five customers	They come back for a second round without being chased	Whether you can do it at scale
Does the product deliver, and do people return?	An MVP with one complete journey	Users reach the moment of value and come back	Whether you can reach them cheaply
Can you reach buyers again and again?	The landing page plus a repeatable channel	The same channel brings signups a second and third week	Anything about retention

Our own idea-to-MVP guide boils validation down to three questions: do people already spend money, time or effort on this, will they pay at roughly your price, and can you reach them repeatedly without burning cash? The first two are cheap to test without code. The third is the one founders skip.

What a landing page can prove (and what it can't)

Buffer is the cleanest example, and Joel wrote it up in Idea to Paying Customers in 7 Weeks. The first two pages only checked "whether people would even consider using the app". Then Joel added a pricing page between the two, so visitors had to pass through prices before leaving an email. People kept clicking through, and a small number clicked on paid plans. Only after that did he start building.

So a landing page can prove interest at a stated price. That is real evidence, and it costs days, not months.

What it cannot prove is that the product works. Giff Constable, a product practitioner who writes on validation, put it bluntly: he would still put up a landing page, "but not really as a test for value or market demand". The Spin by fryga team has a sharper line for it: "Conversion is a promise accepted; activation is a promise delivered".

If you do run a landing page test, make the signal honest:

Show a real price. A waitlist with no price only proves curiosity.
Make one specific promise. "Book a doctor in Gurugram in under a minute" can fail. "Healthcare made simple" cannot.
Ask for something that costs the visitor. An email after a pricing click beats a bare email box.
Use traffic that does not know you. Friends will sign up for anything you make.
Write the stop condition before launch. Decide what number would make you drop the idea, and write it down first.

What only an MVP can prove

Some questions cannot be answered by a page. Does the product do the job on real data? Do people get to the moment of value without you on a call? Do they come back next week?

Those need a working product, and the right MVP is smaller than most founders expect: signup to the moment of value, finished and working, not two features half-built. It also needs measurement from day one. On our MVP builds, events on activation, retention and drop-off go in before the first user does. An MVP you cannot measure is just a smaller launch.

An MVP is the right spend when one of these is true:

You have a clear hypothesis and need evidence for it.
You are raising and need something investors can use.
You have paying interest and nothing to sell yet.

The third one is the best place to be. It usually means a landing page, a pre-order or a manual pilot has already done its job.

The middle option most founders skip: do it by hand

Between the page and the product there is a cheaper test that tells you more than either: deliver the result yourself.

Paul Graham's essay Do Things That Don't Scale makes the case that the most common unscalable thing founders have to do at the start is to recruit users manually. His best example is Stripe, whose founders delivered "instant" merchant accounts to early users by signing them up for traditional merchant accounts behind the scenes.

For most ideas I see, a manual version for five customers answers "is the output even wanted?" faster than any build. If you are planning a tool that writes property listings, write the first twenty by hand and charge for them. If you are planning a booking app, take bookings on WhatsApp and a spreadsheet for a month. If nobody wants the hand-made version, they will not want the automated one.

Cost and time, side by side

Here is what each test costs when you buy it, using our published floors where we sell the thing.

Test	Typical time	Cost	Best for
Thirty conversations	Days	Nothing but your time	The problem question
Landing page you build yourself	Days	A domain and a page builder	Price and demand
Business website from an agency	3 to 6 weeks	From ₹45,000 at Gigzman	When the page must also sell and rank
Manual pilot for five customers	A few weeks of your time	Your time	Whether the output is wanted
MVP with one complete journey	6 to 12 weeks	From ₹1,50,000 at Gigzman	Delivery, activation, retention

Two notes. First, we do not publish a separate landing-page price, and for a pure demand test I would rather you build the page yourself this weekend than pay us. Second, the MVP row is a floor, not an average: integrations and design from scratch push it up.

Five checks before you pay anyone to build

Run these in order. If any answer is "no", the next step is a page, a conversation or a manual pilot, not a build.

Have you described the idea to potential users? If not, building is premature.
Have you written what result would make you stop? Teams that skip this step rarely stop.
Has a stranger accepted a real price? A pricing click, a pre-order or a paid pilot counts. A compliment does not.
Is your biggest risk delivery, not demand? If people clearly want it and the open question is whether it works, an MVP is the right test.
Can you name the one journey? One signup-to-value path, written in a sentence. If your brief has two products in it, cut one first.

That last point is common. Most MVP briefs we receive contain two products, and finding the one that matters is the highest-value hour of the engagement.

When I'd tell you to skip the landing page

A landing page is not always step one. Skip it when:

You already have paying interest. Someone has asked to pay and you have nothing to deliver.
The value is only visible in use. If the product's worth depends on how well it handles a user's own messy data, a page cannot show it. Run a tight MVP or a manual pilot instead.
You are raising and need a working demo.
The build is genuinely tiny. If a usable version takes a weekend, the weekend is your test.

How we approach it at Gigzman

We run four live products of our own on the same stack we build for clients, so we have made most of these mistakes on our own time. We do not take equity: we charge for the work, which means we will tell you to build less rather than more. Every MVP ends with a written scope of what is in and what is out, a working product on a real domain, an analytics dashboard for the few numbers that decide the next step, and the source code in your own repository from day one.

If the MVP fails, it did its job for a fraction of what a full build would have cost. If the honest answer is "build a landing page first", that is what we will say.

Your next step

Write down the one question that would change your mind, then pick the cheapest test in the table above that answers it. If that test is an MVP, tell us what you are building and we will come back with a plan, a timeline and a price within two working days.