MVP development guide: types, process, costs and timelines

MVP development is the process of building the smallest version of a product that tests whether real customers want it, before you spend the full budget. Eric Ries, author of The Lean Startup, measures an MVP by how much it teaches you, not by how little it contains. A coded software MVP takes roughly 3 to 16 weeks, and some MVPs need no code at all.

That distinction matters. In CB Insights’ 2026 analysis of startup shutdowns, poor product-market fit was a cause in 43% of cases, ahead of bad timing. This guide covers what an MVP is (and isn’t), five types you can build, a step-by-step process, what MVP development costs in the USA, UK, Australia and India in 2026, and what to measure once it’s live.

What is a minimum viable product?

A minimum viable product (MVP) is the smallest version of a new product that lets you learn whether customers want it, for the least effort. In a 2009 blog post, Eric Ries described it as the version that collects “the maximum amount of validated learning about customers with the least effort.”

Validated learning means evidence from what real customers do, such as signing up, paying or coming back, rather than what they say in a survey. Ries also warns that an MVP isn’t about creating minimal products for their own sake. It’s an experiment, and the product is only as big as the experiment needs.

The term gets mixed up with three others. Here’s how they differ:

Why does MVP development matter?

MVP development matters because the most expensive mistake in software is building the wrong thing well. Testing demand first protects the money you’d otherwise spend on features nobody uses.

The latest failure data backs this up. In March 2026, CB Insights analysed 431 venture-backed companies that shut down since 2023 and identified reasons for 385 of them. Running out of capital topped the list at 70%, but CB Insights calls that the final cause rather than the root problem. The more telling causes were poor product-market fit (43%), bad timing (29%) and unsustainable unit economics (19%).

Product-market fit is the point where a product satisfies a market that wants it badly enough to pay and keep using it. An MVP is the cheapest way to find out how far you are from it.

This isn’t only a startup problem. An established business launching a customer app or a new service faces the same risk. The UK Government’s service manual applies the same idea to public services: its alpha phase exists to test the riskiest assumptions with prototypes, and alphas tend to last 6 to 8 weeks.

If you have an idea and aren’t sure which assumption to test first, tell us about it and we’ll suggest the cheapest way to check it.

What types of MVP can you build?

There are five common MVP types, and only two of them need much code: concierge, Wizard of Oz, landing page, single-feature and no-code prototype MVPs. Pick the type that tests your riskiest assumption fastest, not the one that looks most like the finished product.

Concierge MVP

A concierge MVP delivers the service by hand, openly, to a small group of customers. You learn exactly what they need and whether they’ll pay, before automating anything.

Say two founders in Pune (a hypothetical example) want to build an app that matches small restaurants with relief kitchen staff. Instead of writing code, they run the matching themselves over WhatsApp for four weeks with 15 restaurants and charge a ₹500 booking fee. If restaurants rebook and pay, the app is worth building. If they don’t, the founders have spent a month rather than ₹10 lakh.

Wizard of Oz MVP

A Wizard of Oz MVP looks automated to the customer, but people do the work behind the scenes. Zappos started this way: according to a 2012 Fortune interview, founder Nick Swinmurn photographed shoes in local stores in 1999, put them online, and bought each pair at full price when an order came in.

Landing page MVP

A landing page MVP, or smoke test, describes the product on a single page with a sign-up, waitlist or pre-order button, then sends a small amount of paid traffic to it. Ries writes that a simple AdWords smoke test would have shown how bad one of his own early feature ideas was.

Single-feature MVP

A single-feature MVP is real, working software that does one job well: the job that delivers the core value. Everything else waits. This is what most people picture when they say MVP development, and it’s the right choice once demand is proven but you need to test whether the product keeps people coming back.

No-code prototype MVP

A no-code MVP uses tools such as Bubble, Glide or Softr, or a clickable Figma prototype, to put something usable in front of customers without custom code. It’s fast and cheap, but you’ll likely rebuild it once it works.

How does the MVP development process work, step by step?

MVP development follows seven steps: define the problem, find the riskiest assumption, set a pass mark, choose the MVP type, scope it, build and launch to a small group, then measure and decide. At Inwentions, those steps sit inside our discover, plan, design, build and launch process.

1. Define the problem and the customer. Write one sentence: who has the problem, how often, and what it costs them today.
2. Find the riskiest assumption. Ask what must be true for the product to work. Usually it’s “people want this enough to pay”, not “we can build it”.
3. Set a pass mark before you build. For example, 40 of 200 trial users still active in week four, or 25 paid pre-orders.
4. Choose the MVP type that tests that assumption fastest and cheapest.
5. Scope it with MoSCoW and write the Must haves down as user stories.
6. Build and launch to a small group, ideally people who match your target customer and aren’t friends or family.
7. Measure, learn and decide whether to persevere, pivot or stop.

How do you scope an MVP with MoSCoW?

MoSCoW is a prioritisation method that sorts every feature into Must have, Should have, Could have and Won’t have this time. The Agile Business Consortium, which maintains the DSDM agile framework that uses MoSCoW, calls the Must haves the Minimum Usable SubseT and recommends they take no more than 60% of the effort, with Could haves around 20%.

That 60% ceiling is a useful test for MVP scope. If your Must haves fill the whole budget, there’s no contingency, and any delay lands on something essential. Cut until the list is uncomfortable, then cut once more.

For the hypothetical restaurant app above, the Must haves might be a shift posting form, a list of available staff and a confirmation message. Ratings, in-app chat and payroll export are Won’t haves for now. Writing these as user stories with acceptance criteria in a short software requirements document makes every quote you collect comparable. If you’d like a second opinion on what belongs in your first version, ask us to review your scope.

How long does MVP development take and what does it cost?

A coded MVP takes roughly 3 to 16 weeks and, in published 2026 pricing guides, costs from about A$15,000 for a lean prototype in Australia to $150,000 for a larger build with a US firm. A non-code MVP can run in days for the cost of your time and a small ad budget.

These are the ranges firms in each market published for their own work in 2026:

For comparison, A$40,000 is roughly $27,600 and ₹6 lakh is roughly $6,300 at mid-2026 rates. The ranges aren’t for identical products, so treat them as a sanity check on quotes, not a budget.

Five things tend to move the number most: the number of platforms (a web app vs iOS and Android), integrations with other systems, payments, AI features, and compliance work for regulated data. If your MVP is a mobile app, our guides to app development cost and native vs cross-platform apps explain those choices in detail.

What should you measure after an MVP launch?

Measure the one behaviour that proves or disproves your riskiest assumption, against the pass mark you set before launch. Downloads and page views rarely prove demand. Repeat use and payment do.

Four measures cover most MVPs:

• Activation: the share of sign-ups who complete the core action once, such as posting a first shift.
• Retention: the share still active after four or eight weeks. This is the strongest signal you’ll get.
• Conversion: the share who pay, pre-order or upgrade.
• The Sean Ellis test: ask users how they’d feel if they could no longer use the product.

The Sean Ellis test has a well-known benchmark. In a 2018 First Round Review article, Superhuman founder Rahul Vohra explained that 40% of users answering “very disappointed” signals product-market fit, and that Superhuman scored 22% when it started measuring.

Numbers tell you what happened; interviews tell you why. Talk to five to ten users, including the ones who left. Then decide: persevere if you hit the pass mark, pivot (change one fundamental part of the plan, such as the customer or the problem) if you learned something promising, or stop if the demand isn’t there.

What are the most common MVP development mistakes?

The most common MVP development mistakes are building too much, launching without a pass mark, and treating the MVP as a cheap first version rather than an experiment. Each one burns budget without producing a clear answer.

• Building the whole wish list. If Must haves exceed 60% of the effort, the MVP isn’t minimal.
• No pass mark. Without a target set in advance, any result can be read as success.
• Testing with friends. Friends and family are kind. Strangers who match your customer profile are honest.
• Skipping viability. Minimal doesn’t mean broken. Payments, logins and data handling must work and feel trustworthy.
• Ignoring data rules. Check which privacy laws apply before you collect personal data: UK GDPR in the UK, the Privacy Act 1988 in Australia (which exempts some small businesses), state laws in the US, and India’s Digital Personal Data Protection Act 2023, which is being phased in.
• No budget for what comes next. An MVP produces a list of changes. Keep money aside to act on it.

What to do next

Write down your riskiest assumption and the cheapest MVP type that would test it. If a concierge or landing page test can answer it, run that first. You’ll learn more in two weeks than in two months of planning.

When you’re ready for a coded MVP, a one-page brief with your user, problem, Must haves and pass mark is enough to start a useful conversation. Inwentions handles app development and custom software development for clients in the USA, UK, Australia and India, from discovery through launch. Request a quote for your MVP and we’ll reply with questions, a suggested scope and a realistic timeline.