The most expensive mistake with an app idea isn't building it badly — it's building too much before you find out whether anyone wants it. That's what an MVP is for. But let's first clear up what the term means, because it gets thrown around often and explained rarely.
What an MVP actually is
MVP stands for minimum viable product. Taken apart:
- Product — something real, that works. Not an idea, not a pitch, not a drawing.
- Minimum — reduced to one job: your first customer's main problem. One flow, built end to end.
- Viable — good enough that someone can use it today and tell you, through their actions, whether your idea is worth anything.
In short: the simplest version of your app that a real customer can use right now. The term comes from the lean-startup movement and stuck because it fixes an old problem: people would build in secret for a year, launch, and discover nobody wanted the product. The MVP flips the order: first you learn whether the idea holds, then you invest.
A concrete example: you want an app where a barbershop's clients book their own appointments. The MVP doesn't need payments, loyalty points, notifications and user profiles. The MVP is: the client sees the free slots, picks one, gets a confirmation. That's it. If people use it, the rest gets added step by step.
What an MVP is NOT
- Not a sketch or a mockup — those show what it will look like, but can't be used.
- Not a pitch demo — a video or a slide deck doesn't validate your idea; only real usage does.
- Not a bad product — "minimum" refers to how many features it has, not how well it works. The little it does must work flawlessly.
- Not necessarily an AI-built prototype — that's often the step before. If you already have one in Lovable, v0 or Bolt, I've written separately about how to take it to production.
If your MVP doesn't make you blush a little, you've built too much.
What your first MVP should NOT include
- Every "nice to have" feature — add them once you have users asking for them.
- Pixel-perfect design — clean and clear is enough to validate.
- A native App Store app from day one — a web app works on any phone and launches in days, not months.
- A sophisticated admin panel — at the start, "administration" can be you with a simple table behind the scenes.
How long it takes and what it costs
A typical MVP is ready in 1–3 weeks. With me, the first version is free — I build it so you see something real before you invest anything. If the idea proves itself and you want more, most projects land between €500 and €2,500, with the price agreed clearly up front. I've detailed the numbers in what an app costs for a small business.
How you know the idea is validated
Not by likes and friends' opinions — friends lie kindly. By facts:
- Someone uses it a second time without being asked.
- Someone recommends it of their own accord.
- Someone is willing to pay — even a small amount is a huge signal.
If none of these signals shows up after a few weeks, you've learned cheaply that the idea needs a change — that's exactly the value of an MVP. An idea that "failed" with €0 invested is a win, not a loss.
The questions everyone asks me
MVP or prototype — what's the difference? A prototype shows the idea (and can be built with AI tools); an MVP is used by real customers. The usual road is: idea → prototype → MVP → product. I cover that whole road.
Do I need to be technical to launch an MVP? No. You describe the problem in your own words; turning it into an app is my job.
What happens after the MVP? If the signals are good, we add what users ask for, step by step. If not, we adjust the idea — or stop, with your wallet almost untouched.
Next step
Tell me the idea in two or three sentences, like you'd tell a friend. I'll answer honestly whether an MVP can test it, what the first version would contain — and I'll build it free.