Prototype vs MVP: What You Actually Need First

The terms "prototype" and "MVP" get used interchangeably in startup conversations. They're not the same thing, and confusing them leads to building the wrong thing at the wrong time.

What a prototype is

A prototype is a tool for answering a specific question before committing to a direction. It's designed to be thrown away.

A clickable prototype (built in Figma or similar) lets you test user flows and UI decisions without writing code. A coded prototype lets you validate a technical approach — can this API do what we need, does this algorithm perform at scale — without building a full product.

The key property: prototypes are disposable. The goal is learning, not shipping.

What an MVP is

A Minimum Viable Product is the smallest version of your product that delivers real value to real users. It's designed to be iterated on.

An MVP is production software. It has auth, error handling, monitoring, and enough polish that users can actually use it. It's minimal in scope, not minimal in quality.

The common mistake

Teams often build what they call an MVP when they actually need a prototype. They write production-quality code to answer questions that a two-day Figma prototype could resolve. They spend six weeks on something they should have validated in six days.

The reverse also happens: teams build a throwaway prototype and then try to iterate it into production. Prototype code has no tests, no architecture, no error handling. Iterating it toward production is slower and more painful than starting clean with the validated design.

A useful decision rule

Build a prototype when you're not sure what to build. Build an MVP when you know what to build and need to start learning from real usage.

The order matters. Most projects benefit from a lightweight prototype phase — even a few days of mockups — before committing to MVP development. The questions answered in that phase shape every subsequent decision.

What this means for budget

A clickable prototype typically takes 2–5 days. A coded prototype for a specific technical question might take 1–2 weeks. An MVP for a well-specified product is typically 6–12 weeks.

Spending 5 days on a prototype before a 10-week MVP build is almost always worth it. It's insurance against building the wrong thing.