The difference
| What to compare | Prototype | MVP |
|---|
| What it is | Screens and flows you can click through, without a working product behind them. | A launched first version that real users can use. |
|---|
| What it answers | Do people understand it, and does the flow make sense? | Do people actually use it, and would they pay for it? |
|---|
| Who sees it | You, advisers, investors and a few test users. | Real users, with analytics and a feedback loop. |
|---|
When a prototype comes first
- The flow is unclear and you want to change it cheaply before anything is built.
- The goal is to raise money, where a waitlist landing page or the first slides of a pitch deck may be the fastest proof.
- You are still choosing between two directions and need something to put in front of people.
When to go straight to the MVP
When the scope is already clear: one audience, one main job and the smallest set of features needed to learn. The MVP then carries its own analytics and feedback capture, so launch day produces evidence rather than opinions.
How we run it
We do not sell the two as separate projects. The first phase is chosen around what you already have: wireframes and user flows if the vision is clear, a Business Model Canvas and user-pain research if it is not, or a waitlist page if you are fundraising. Later phases move through high-fidelity product UI and a clickable prototype into the build. Because each phase is fixed-price with no deposit, you can stop after the prototype and keep everything produced.
The design side is on the product design page. If the question is how long the build takes, see how long it takes to build an MVP.