An MVP is not a prototype. A prototype tests whether something can be built. An MVP tests whether someone will use it — and specifically, whether the core hypothesis that justifies building the full product is correct.

The hypothesis framework

Every MVP should be testing one specific hypothesis. Define what a positive result looks like before you build. Teams that fail to do this interpret any user engagement as validation and any lack of engagement as an execution problem, rather than as data.

What to include and what to cut

Include the minimum flow that allows a real user to attempt the core action. Cut everything that does not help test the hypothesis: admin panels, notification systems, settings pages, help centers.

Timelines

A real MVP should take 4 to 10 weeks to build. The AI Sprint format compresses this further: 5 to 10 days to a deployable prototype using Claude Code and modern tooling.

The most common MVP failures

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

1. Item 1
2. Item 2
3. Item 3

Unordered list

• Item A
• Item B
• Item C

Text link

Bold text

Emphasis

^Superscript

_Subscript