

"We need an MVP" – we hear this a lot. But usually they actually need a prototype. Or vice versa.
The difference isn't semantics. It can mean months of work and five-figure amounts. So yeah, this is important. Grab a coffee. ☕
| Prototype | MVP | |
|---|---|---|
| Goal | Validate idea | Validate market |
| Users | Internal team, selected testers | Real customers |
| Functionality | Fake it till you make it | Must actually work |
| Timeline | 1-3 weeks | 6-12 weeks |
| Cost | €5-15k | €20-80k |
When the basic assumption is still unclear:
A prototype is a hypothesis machine. It shows what something could be – without the effort of actually building it.
When you know WHAT you want to build and want to test IF it works:
An MVP is the minimum complete product. Not finished, but functional.
MVP doesn't mean "quick and dirty". It means:
"Let's quickly add X" – this sentence has ruined more MVPs than anything else. It's the dino-killer of product development. 🦕💥
A real MVP has:
| Your Situation | Recommendation |
|---|---|
| Idea still vague, budget tight | Prototype |
| Pitch to investors | Prototype |
| Internal alignment needed | Prototype |
| Idea validated, ready for market | MVP |
| Paying beta customers in sight | MVP |
| Competition pressing, time-to-market important | MVP |
Prototype → User Tests → MVP
Not either/or. The sequence matters:
This sequence costs a bit more than jumping straight into MVP. But it prevents you from building 8 weeks in the wrong direction.
Unsure what you need? We'll figure it out in 30 minutes. Free, no sales pitch. Promise – pinky swear. 🤞