An MVP is the smallest version of a product which real users can use, built to test whether a problem is worth solving. MVP stands for minimum viable product, a term popularised by Eric Ries in 2009. In 2026, VirtuoLab indicates €1,000 to €3,000 for a landing page with a waiting list. A simple web app costs €5,000 to €10,000, and an app with login €10,000 to €20,000. Step 1 is a sharp problem statement, followed by a scope cut back to one core action. A web app built with Next.js is the usual MVP format, because a web app runs on every phone without app store review. For example, a booking tool tested with the first 20 users can launch within 3 to 6 weeks. Finally, the exact price follows after a free intake call with VirtuoLab.
What is an MVP?
An MVP is the smallest version of a product which real users can use to solve one specific problem. The term was defined by Eric Ries, author of The Lean Startup, in a blog post in 2009. According to Ries, an MVP lets a team collect the maximum amount of validated learning about customers with the least effort. The key word is learning: an MVP exists to test assumptions, not to impress. First, an MVP differs from a prototype, which only shows how a product could work. Second, an MVP differs from a full product, which covers every edge case and every user group. For example, a booking tool for physiotherapists, built with Next.js and tested with 20 users, may support only bookings and email confirmations. Payments and a mobile app can wait. Viable still matters, though. The core workflow must be reliable, secure and pleasant enough for users to come back in 2026.
Why should a startup begin with an MVP?
An MVP is a low-cost way for a startup to find out whether customers want the product before the money runs out. CB Insights analysed 431 VC-backed startups which shut down since 2023, and identified the reasons for 385 of the shutdowns. Running out of capital appeared in 70% of the cases, and poor product-market fit in 43%. CB Insights adds a sharp nuance: running out of capital is almost always the final cause of death, not the root problem. In other words, many startups spend the budget on a product without enough demand. An MVP reverses the order: first proof of demand, then the full investment. Additionally, a working MVP gives investors more evidence than a pitch deck, because the MVP produces real usage data. For example, 50 people on a waiting list say something, but 50 users who return every week say much more.
How do you build an MVP step by step?
Building an MVP is a cycle of five steps, from a sharp problem statement to a measurable launch. Step 1 is the problem statement: one sentence describing who has which problem, for example physiotherapists who lose time on phone bookings. Step 2 is scoping. List every feature idea, keep only the features needed for the core action and park the rest. Step 3 is the user flow: sketch the shortest route to the core action. Then test a clickable prototype with 5 to 10 users from the target group. Step 4 is building in short sprints, with a working demo after each sprint. Finally, step 5 is launch and measurement with Google Analytics or PostHog. Define in advance which numbers prove success, for example the share of sign-ups who complete the core action within 7 days. In practice, the scoping step saves the most money in 2026, because every feature which stays out costs nothing to build, test or maintain.
What does an MVP cost in 2026?
An MVP costs between €1,000 and €25,000, depending on the type, according to VirtuoLab price indications for 2026. First, a landing page with a waiting list costs €1,000 to €3,000 and takes 1 to 2 weeks. Second, a simple web app costs €5,000 to €10,000 and takes 3 to 6 weeks. Third, an app with login, user accounts and a database costs €10,000 to €20,000 and takes 6 to 10 weeks. Finally, a cross-platform mobile app built with React Native or Flutter costs €15,000 to €25,000 and takes 8 to 12 weeks. Running costs come on top: hosting an app back end typically costs €50 to €500 per month. A mobile MVP also needs store accounts, at €99 per year for Apple and €25 once for Google. In practice, the biggest saving comes from a smaller scope, not from a cheaper developer. The exact fixed price follows after a free intake call with VirtuoLab.
Should an MVP be a web app or a mobile app?
A web app is the right MVP format for most startups, because a web app runs on every device without app store approval. Phones matter here: according to StatCounter, phones generated about 65% of web traffic in the Netherlands in September 2026. A web app built with Next.js serves phone users as well and can work as a progressive web app, with an icon on the home screen. A cross-platform or native mobile app makes sense when the core feature depends on the phone itself: the camera, GPS tracking, Bluetooth or offline use. For example, a fitness tracker which logs workouts in the gym fits a mobile app, while a B2B planning tool fits a web app. A mobile MVP costs more: €15,000 to €25,000 with React Native or Flutter, plus store fees from Apple and Google. Additionally, every release passes app store review. A common route is to launch a web app first and add a mobile app once users ask for one.
Which mistakes make an MVP fail?
The most common MVP mistake is building too much before talking to users. Poor product-market fit played a role in 43% of the startup shutdowns in a CB Insights report from 2026. First, too many features: every extra feature delays the launch and blurs the test. Second, waiting for perfection: an MVP launched after nine months is no longer minimal. Third, launching without measurement. Without analytics and user interviews, a startup cannot separate success from noise. Fourth, a tech stack without room to grow. A no-code prototype is fine for validation, but a product with paying customers needs code which the startup owns and can extend. Finally, unclear ownership: the source code, the domain name and accounts with Apple, Google or Stripe belong to the startup, not the developer. For example, five short interviews per week with target users can reveal more than a month of extra development. In practice, the fix is a smaller scope, an earlier launch and weekly contact with real users.
How does VirtuoLab build an MVP?
VirtuoLab is a software agency in Papendrecht which builds MVPs for startups at a fixed price agreed upfront. The process has four steps. Step 1 is a free intake call and a scope, in which the feature list is cut back to the core. Step 2 is design and validation with clickable screens, tested with 5 to 10 users from the target group. Step 3 is building and testing in short sprints, with a demo of working software after every sprint. Step 4 is launch and support, including hosting, monitoring and the next iteration. All code is written by VirtuoLab itself, so the founder talks directly with the developer instead of an account manager. In 2026, the stack is React, Next.js, TypeScript, Node.js and PostgreSQL, with React Native or Flutter for mobile apps. Finally, after delivery, the startup owns the source code and the data. For example, investors and a future in-house team can then continue without permission from VirtuoLab.
Frequently asked questions
How long does it take to build an MVP?
Building an MVP takes 1 to 12 weeks, depending on the type, according to VirtuoLab indications for 2026. A landing page with a waiting list takes 1 to 2 weeks. A simple web app takes 3 to 6 weeks, and an app with login takes 6 to 10 weeks. A cross-platform mobile app with React Native or Flutter takes 8 to 12 weeks, partly because of app store review by Apple and Google. App review itself is usually quick: about 90% of submissions are reviewed within 48 hours, according to Apple. The biggest variable is not the code but the decisions. First, a clear scope before the start prevents rework. Second, quick feedback after each sprint demo keeps the planning on track. In practice, a founder who reserves a fixed hour per week for feedback helps the MVP launch on time.
Should I build my MVP with no-code or custom code?
No-code is a good choice for testing an idea quickly. Custom code is the better choice once the MVP needs to grow into a real product. Tools such as Bubble, Webflow or Glide let a founder build a clickable or even working version within days. The limits appear later. First, complex business logic. Second, performance as usage grows. Third, integrations and ownership of the code. Custom development with Next.js and PostgreSQL costs more upfront: from €5,000 for a simple web app, according to VirtuoLab indications for 2026. In return, the code belongs to the startup and can be extended without a rebuild. For example, a marketplace where sellers manage payouts, roles and listings tends to hit no-code limits early. A practical route starts with a landing-page test which collects the first 100 people on a waiting list. A custom MVP follows once demand is proven.
What happens after the MVP launches?
The period after launch is the real start of an MVP: a cycle of measuring, learning and improving. First, collect usage data: which screens users visit, where users drop off and how many return after a week. Usage data becomes visible with Google Analytics, PostHog or Plausible. Second, talk to users, because short interviews explain the numbers. For example, interviews with 5 users who dropped off can explain a weak sign-up rate. Third, decide per sprint: improve the core feature, add the most requested feature or change direction. In practice, hosting and monitoring continue in the background. An app back end costs €50 to €500 per month, according to VirtuoLab indications for 2026. A pivot is not a failure but the purpose of an MVP. As described by Eric Ries in 2009, the MVP is a tool for validated learning, and the learning starts on launch day.