MVP Development: From Idea to a Product Real Users Can Try

Prices are in US dollars. Euro and pound figures in parentheses are approximate, rounded conversions. Quotes are issued in the currency of your contract.

Minimum viable product is the most used and least understood phrase in early-stage software. Founders hear it as "cheap version", agencies sell it as "phase one", and investors use it to mean "show me something". This guide is the one place that covers the whole of MVP development, from the first scoping conversation to the decision about version two, and links to the detailed posts on each step. If you read nothing else before you build, read this.

What is MVP development for?

An MVP exists to answer one question: will people use this, and come back? Everything else about it follows from that purpose. It must be complete enough that a user can get real value, otherwise the answer tells you nothing. It must be small enough to ship in weeks, otherwise you learn too late. And it must be measured, otherwise you launched a product, not an experiment. Our post on what an MVP is and what to leave out covers the definition in depth, and MVP vs prototype vs proof of concept explains how it differs from the two things it is most often confused with.

What are the phases of MVP development?

The full walkthrough, with what you are asked to decide at each step, is in the MVP development process, step by step.

How much does MVP development cost?

A focused single-platform MVP with one core feature costs $20,000 to $40,000 (€17,000 to €35,000, £15,000 to £30,000). A complete MVP with accounts, payments, notifications and an admin panel costs $40,000 to $80,000 (€35,000 to €70,000, £30,000 to £60,000). Marketplaces, products with complex integrations and regulated products sit at $80,000 to $150,000 (€70,000 to €130,000, £60,000 to £110,000). The number is driven by screens, user roles, integrations and platforms, not by how good the idea is. How much MVP development costs breaks those bands down line by line, and what a 20k, 50k and 150k budget buys shows what each band looks like as a product.

How long does it take?

Eight to sixteen weeks from kickoff to a release that real users can try. Discovery and design take the first two to four of those. The things that stretch the timeline are slow decisions, scope added mid-build, partner integrations with unknowns and app store review. How long an MVP takes has the phase-by-phase breakdown and the list of what adds months.

Who should build it?

You have four options: a technical co-founder, freelancers, an agency, or no-code tools with your own hands. Each is right for a different founder. A solo non-technical founder with a validated idea and a budget is usually best served by an agency that has shipped MVPs before, because the cost of a wrong first build is a second first build. A funded team with a strong technical lead may be better hiring. Three posts cover the decision:

• How to choose an MVP development company, the checklist and the questions that expose a team that only ships features.
• Outsourcing MVP development, a verdict by founder situation.
• What a fixed-price MVP package should include, and what it usually hides.

If you are weighing no-code, no-code vs custom development gives the honest cases for each.

What goes into the first release?

One user type, one core journey, done completely. The commonest scoping mistakes are a second user role, social features, multiple platforms, advanced settings and integrations that could be done by hand for the first hundred users. The scoping method we use scores every candidate feature on whether it is needed for the core journey, whether it tests a real assumption and whether it can be faked. Only features that pass the first test and at least one of the others make release one. How to scope an MVP walks through it with an example.

Does the type of product change the approach?

Yes, in predictable ways. A SaaS MVP needs billing and tenancy from day one. An AI MVP should use hosted models and spend its budget on the workflow around them. A B2B MVP is won with five design partners rather than five hundred sign-ups. A marketplace has two sides to recruit and a chicken-and-egg problem to solve by hand first. We have a guide for each:

• How to build a SaaS MVP
• How to build an AI MVP without training a model
• B2B MVP vs B2C MVP
• How to build a marketplace app

When is an MVP the wrong move?

Sometimes. Regulated products that cannot ship incomplete, markets where a strong incumbent sets the bar for "minimum", and hardware-dependent products often need something bigger than an MVP or something smaller than one, such as a concierge service or a pilot. MVP vs MLP vs full product covers the cases where skipping the MVP is the right call.

What happens after launch?

The MVP's job starts at launch, not before it. The first 90 days are for measuring activation and retention, talking to the users who stayed and the ones who left, and deciding what version two is. Four to eight weeks in, the numbers usually point clearly at one of three outcomes: build on, pivot, or stop. The posts that cover this stage:

• How to test an MVP with real users
• Which metrics to track after launch
• When to build version two
• Rebuild your MVP or keep building on it

Why do MVPs fail?

Rarely because of engineering. The usual causes are building for an unvalidated problem, scoping a full product and calling it an MVP, launching without measurement, and treating the MVP as the finish line. Why MVPs fail lists the nine mistakes we see most and the fix for each. If you have not validated yet, start with how to validate a startup idea before writing code.

How 7L approaches MVP development

MVP development at 7L runs inside the Startupper Program: vision and validation, functional prototype, minimum viable product, market entry, scale. Discovery is where we earn our fee, because the feature we talk you out of is usually worth more than the ones we build. Teams are in New York, London and Athens, and the code is yours from the first commit. If you have an idea and want a number and a timeline for it, tell us what it does.