Guides 3 min read

What is an MVP and how to build one in 12 weeks

A practical guide to building an MVP (Minimum Viable Product) in 12 weeks. How to define scope, what to cut, and how to actually test the idea with real users.

by Tsunami Digital Team May 13, 2026

An MVP is the simplest version of a product that can answer one question: will people use this and pay for it? Not in words, but in behaviour. A typical MVP can be built in 8-12 weeks on a budget of €15,000-€40,000, and must let real users complete the entire path - from signup to payment. The concept comes from Eric Ries’ Lean Startup methodology.

What an MVP is and is not

It is not a prototype (an MVP runs), not “a bad product shipped fast”, not “the same product, smaller”, and not free-only (without payment you only test “will people try it for free”).

A real MVP meets three criteria:

A user completes the full path from first encounter to payment, with no manual interventions.
The main hypothesis is testable - after four weeks, clear numbers confirm or disprove it.
It can be modified quickly. If data says “turn right”, you can in 1-2 weeks, not six months.

How to scope - the one-hypothesis test

The biggest beginner mistake is building the entire product as an “MVP”. A real MVP tests one main hypothesis. For every feature, ask: “If I remove this, can I still test the main hypothesis?” If yes, push it to v2.

A team building a freelance marketplace once decided their MVP needed chat, reviews, payments, multiple roles, a mobile app, and admin panel. A real MVP: a simple listing where freelancers post services, clients order, and connections happen manually via email. A thousand times cheaper, and it tests the leading hypothesis.

The 12-week plan

Weeks 1-2: Discovery. User conversations, hypothesis, MVP/v2 split, success metrics, written brief.
Weeks 3-4: Design and architecture. UX of main paths (3-5 screens), visual design, stack, launch plan.
Weeks 5-10: Development. Backend and frontend in parallel, weekly demos, gradual integration.
Week 11: Testing. Internal QA plus beta with 5-10 external users.
Week 12: Launch. Production setup, analytics, first real users.

After 12 weeks: a month of testing, then a decision - pivot, scale, or shut down.

Costs and common mistakes

Typical MVP ranges: landing plus signup portal €8,000-€15,000; web app with login and payments €15,000-€35,000; mobile MVP €20,000-€45,000; marketplace €30,000-€80,000. For broader context, see custom software cost in Croatia.

Avoid:

Scope creep. If MVP takes six months, you are building a product.
No payment from day one. Even €5 filters out “just trying” users. Stripe is fastest.
No success metrics. Define upfront: 100 signups in four weeks, 20% activation, 5% paying.
Optimising before validation. Build for 100 users, not a million.
No user conversations after launch. Numbers say what, conversations reveal why.

Frequently Asked Questions

What if the MVP shows the idea doesn’t work? That is the biggest value - you learned for €25,000 what you would have learned for €250,000 a year later.

Can we extend the MVP into a final product? Yes, with proper architecture. A good MVP is a foundation, not throwaway code.

When should we decide continue or stop? Typically 4-8 weeks after launch. Less is not enough data.

Thinking about an MVP?

Book a free Discovery call. We help distill the idea into a testable MVP, define success metrics, and propose a plan that takes you from idea to real users in 12 weeks.

Reach out at [email protected] or via the form on our homepage.

All articles