An MVP (Minimum Viable Product) is the simplest version of a product that can give you a real answer to one core question: will people use this and pay for it? Not in words, in behavior. A typical MVP for a business idea can be built in 8-12 weeks with a budget of €15,000-€40,000, and it must be functional enough that the first real users go through the whole path - from signup to payment.
This article breaks down how to define an MVP, what to cut from scope, how to get to real user testing in 12 weeks, and which mistakes to avoid.
What an MVP is NOT
The biggest confusions around MVPs:
- Not a prototype. A prototype is a visual mockup, it doesn’t run. An MVP is a working product.
- Not “a bad product fast.” A bad product tests whether users tolerate a bad product - which is the wrong hypothesis.
- Not half the plan. Not “the same product, but smaller.” It’s a distilled version - only what’s needed to test the main hypothesis.
- Not “we’ll launch without payment.” Without payment, you only test “will people try it for free.” Which is almost always “yes.”
What an MVP ACTUALLY must be
Three criteria for a good MVP:
- A user can go through the full path. From first encounter with the product to payment (or main goal). No detours, no manual interventions in the background.
- The main hypothesis is testable. After 4 weeks of use, you have clear numbers that confirm or disprove the leading assumption.
- It can be modified quickly. If the numbers say “turn right,” you must be able to do it in 1-2 weeks, not 6 months.
How to define scope - the “one hypothesis” test
The biggest beginner mistake: trying to build the whole product as “MVP.” A real MVP tests one main hypothesis.
Exercise: for every feature you’re thinking of including, ask:
“If I remove this functionality, can I still test the main hypothesis?”
If the answer is “yes” - remove it from the MVP. Put it in “v2.”
Typical mistake: a team building a marketplace for freelancers decides the MVP must have chat, reviews, payment system, multiple user roles, a mobile app, and an admin panel. A real MVP: a simple listing where a freelancer can post a service, a client can order, and both sides are manually connected via email. A thousand times cheaper, tests “do freelancers have quality offers for clients” - which is the leading hypothesis.
12-week plan: week by week
This is our actual process for most MVPs:
Week 1-2: Discovery and definition
- Conversations with 5-10 potential users
- Definition of the main hypothesis
- Feature list, split into MVP and v2
- Concrete success metrics (how many signups, how many activations, how many payments)
- Written brief with scope and deadline
Week 3-4: Design and architecture
- UX design of main paths (3-5 screens)
- Visual design of brand identity
- Technical architecture (stack, database, API)
- Launch environment plan (hosting, domain, email)
Week 5-10: Development
- Backend development (3-5 weeks in parallel)
- Frontend development (4-6 weeks in parallel)
- Weekly demo presentations with the client
- Gradual integration of all parts
Week 11: Testing
- Internal testing (QA + client)
- Beta testing with 5-10 external users
- Bug fixes and polish
Week 12: Launch
- Production environment setup
- Measurement tools (analytics, error tracking)
- First real users
- Marketing/communication (basic)
After the 12 weeks - a month of testing, then a decision: pivot, scale, or close.
What an MVP costs
Honestly, depends on the product type. Typical ranges:
| MVP type | Cost (€) |
|---|---|
| Marketing landing + simple signup portal | 8,000 - 15,000 |
| Web app with login, profiles, and payments | 15,000 - 35,000 |
| Mobile app with backend | 20,000 - 45,000 |
| Marketplace or complex platform | 30,000 - 80,000 |
These prices cover Discovery, design, development, testing, and launch. They don’t cover marketing, founder salaries, or money for actual marketing testing after launch.
5 most common MVP mistakes
1. Scope creep. “Just one more feature.” If the MVP takes 6+ months, you’re very likely building a product, not an MVP.
2. No payment from day 1. A free version doesn’t test willingness to pay. Even €5 symbolic is enough to filter out “just trying it” users.
3. No success metrics. “We’ll see how it goes” is not a plan. Define upfront: 100 signups in the first 4 weeks, 20% activation, 5% paying conversion.
4. Optimizing before validation. “It has to scale to a million users.” No, it has to be good enough for 100 users. Scaling comes after proven demand.
5. Not talking to users after launch. Numbers say what, but not why. Conversations with the first 20-50 users reveal where to actually pivot.
When an MVP pays off, and when it doesn’t
Pays off when:
- You have a hypothesis you need to test before a bigger investment
- You have a user base ready to try (or a path to reach them)
- You have a budget for testing + marketing
- You’re ready to say “this won’t work, we’re closing it” if the data says so
Doesn’t pay off when:
- You already know demand exists (e.g. an internal tool 50 people already need) - just build the full version
- The market is defined by regulation (medical, financial sectors) - MVPs often can’t legally function
- You only get one shot (one large client who expects a final product)
Frequently asked questions
What if the MVP shows the idea doesn’t work? That’s the biggest value of an MVP - you learned for €25,000 what you’d otherwise learn for €250,000 a year in. Going back to the drawing board isn’t failure, it’s risk reduction.
Can we extend the MVP into a final product? Yes, if the architecture is set up well. That’s key - a good MVP isn’t “throwaway code,” it’s a foundation that’s gradually built upward.
Who from our team should be involved? The product owner (the person who makes decisions), one or two future users for testing, and someone who understands the business system (finance, operations, sales - depending on product type).
How soon after launch should we make a decision on continuing? Typically 4-8 weeks after launch. Less than 4 weeks isn’t enough data. More than 8 weeks means you don’t have clear metrics or are refusing to hear what the data says.
Thinking about an MVP?
Book a free Discovery call. We help you distill the idea into a testable MVP, define success metrics, and propose a plan that goes from idea to real users in 12 weeks.
Reach out at [email protected] or through the form on our homepage.