·3 min read
MVP vs Prototype: What You Need First
Founders mix these up constantly. It matters because building the wrong one wastes time and money.
TL;DR Comparison
| Prototype | MVP | |
|---|---|---|
| Purpose | Test the idea | Test the business |
| Users | Internal / testers | Real paying customers |
| Functionality | Looks real, doesn't work | Works, maybe not pretty |
| Goal | "Do people understand this?" | "Will people pay for this?" |
| Timeline | Days to weeks | Weeks to months |
| Cost | $500 - $2,000 | $2,000 - $15,000 |
What is a Prototype?
A prototype is a visual representation of your product. It looks like the real thing but doesn't actually work. Think clickable Figma mockups or static HTML pages.
Use a prototype when:
- •You're not sure if users understand the concept
- •You need to pitch to investors or partners
- •You want to test different UX approaches
- •You're validating before spending on development
What is an MVP?
An MVP is a working product with just enough features to solve ONE problem for real users. It's functional, not polished. The goal is to learn if people will pay, not to impress them.
Use an MVP when:
- •You've validated the idea and know people want it
- •You need real user feedback, not opinions
- •You want to generate revenue quickly
- •You're ready to iterate based on actual usage
Decision Tree
Do you know if people want this?
No:Build a prototype first. Test the concept.
Yes:Move to the next question.
Have you talked to potential users?
No:Talk to 10 people. Then decide.
Yes:Move to the next question.
Are you ready to charge money?
No:Build a prototype. Get more validation.
Yes:Build an MVP. Start making money.
The Right Order
- •Talk to users (free)
- •Prototype to test understanding ($500 - $2k)
- •MVP to test willingness to pay ($2k - $15k)
- •Iterate based on real feedback
Most founders skip straight to MVP and waste money building something nobody wants. Don't be that founder.