> For the complete documentation index, see [llms.txt](https://milaforge.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://milaforge.gitbook.io/home/founding/prototype-vs-mvp.md).

# Prototype vs MVP

Learn the difference between a prototype and an MVP, when to use each, and what you actually need before investing in full product development.

### What is a prototype?

A **prototype** is a quick representation of a product idea.

I use a prototype when I need to answer questions like:

* Does this user flow make sense?
* Does the interface feel right?
* Do users understand the concept?
* Is this idea worth exploring further?

A prototype can be a Figma design, clickable mockup, or even a partially working application.

It does **not** need to be production-ready like an MVP.

### What is an MVP?

An [**MVP (Minimum Viable Product)**](#what-is-an-mvp) is a working version of the product that delivers its core value to real users.

The important distinction is that an MVP is not simply a more complete prototype. It is software that users can actually use to solve the problem the product is intended to solve.

For example, if I am building a marketplace:

* **Prototype:** users can click through a simulated process of finding and booking a service.
* **MVP:** users can actually find a service, book it, and complete the core transaction.

### Prototype vs MVP

|                     | Prototype                    | MVP                                      |
| ------------------- | ---------------------------- | ---------------------------------------- |
| Main purpose        | Test an idea or experience   | Test a real product with users           |
| Usually functional? | Not necessarily              | Yes                                      |
| Real users?         | Sometimes                    | Yes                                      |
| Production-ready?   | No                           | Not necessarily                          |
| Main question       | "Does this idea make sense?" | "Will people actually use this product?" |

### Which one should I build?

I would start with a **prototype** when the biggest uncertainty is the product concept, user experience, or workflow.

I would build an **MVP** when the core concept is sufficiently understood and the important question is whether real users will use and value it.

The mistake I try to avoid is building an MVP when a prototype would answer the question more cheaply—or spending months polishing a prototype when the real uncertainty can only be answered by putting a working product in users' hands.

The goal is not to build the smallest product possible. It is to build the **smallest thing that can answer the most important unanswered question**.

If you are unsure whether your idea needs a prototype or an MVP, [contact me](/home/welcome/contact.md) and I can help determine what should actually be built.