The Conversation That Happens Every Week
Founder: "We need an MVP. But also something we can test with users. And it should be like a prototype but with real functionality."
Us: "You need a prototype."
Founder: "No, an MVP."
This confusion costs founders months and money. Let me fix it.
The Definitions (That Actually Matter)
Prototype
A visual simulation. It looks like the product. It doesn't work like the product.
- Clicking buttons shows animations
- Forms submit but don't save
- Pages navigate but aren't real
Purpose: Test UX, get visual feedback, show investors.
Time to build: Days to 2 weeks.
Cost: $2,000-$10,000.
MVP (Minimum Viable Product)
A real product with minimum features. It works. It just does the bare minimum.
- Auth works
- Core feature works
- Payments work (if applicable)
- Data persists
Purpose: Test if users will pay for a solution.
Time to build: 6-12 weeks.
Cost: $15,000-$50,000.
Beta
A launched product in testing. Real users, real data, iterating based on feedback.
- All MVP features plus some polish
- Limited users (invite-only or waitlist)
- Active feedback collection
Purpose: Find edge cases, refine UX, build community.
Time to build: MVP + 4-8 weeks.
Cost: $25,000-$80,000.
When to Use Each
Use a Prototype When:
- You need investor demos
- You're testing UX concepts
- You want to visualize before building
- You're pitching to raise money
Use an MVP When:
- You want to test if users will pay
- You need a real product for early customers
- You're ready to start getting revenue
Use a Beta When:
- Your MVP exists and works
- You want controlled growth
- You're collecting user feedback
- You need to find bugs with real users
The Mistake We See Constantly
Founders hire us to build an "MVP" but really need a prototype.
They don't have a product idea. They have a concept they want to visualize.
Then they're shocked when the "MVP" costs $30,000 and takes 10 weeks.
The fix: Know what you need before you talk to developers.
A Real Example
Concept: Project management tool for freelance designers.
What the Founder Thought They Needed
"MVP" with task management, team collaboration, file sharing, and client portals.
What They Actually Needed
First: A prototype to show 10 designers and ask "would you pay $20/month for this?"
If yes: Build an MVP with ONE feature (task tracking).
If no: Pivot or abandon before spending $40,000.
How We Handle This
When founders come to us, we ask:
- "What decision will this help you make?"
- "What's the fastest, cheapest way to make that decision?"
- "Is that a prototype, MVP, or beta?"
Usually the answer is "I don't know" or "whatever you recommend."
That's when we help them figure it out. Because the wrong choice costs more than the right choice.
The Decision Framework
Ask yourself:
"If this existed and worked perfectly, would I learn something new?"
If no: You don't need to build anything. You need more thinking.
If yes, but low confidence: Build a prototype. Fast and cheap.
If yes, and some confidence: Build an MVP. Real and tested.
If yes, and high confidence: You probably already have users. Consider beta.
The Honest Take
Most founders need a prototype first.
Most founders ask for an MVP.
This mismatch leads to expensive experiments that could have been cheap.
Before you hire developers, know what you're building and why. The question isn't "what should we build?" It's "what do we need to learn?"
The answer determines what to build.
Want help figuring out what you actually need? We offer free scoping calls where we help founders clarify their product strategy before writing any code.
