MVP (minimum viable product) is the simplest product that lets a team test whether users want what they are building — with enough quality that feedback reflects real demand, not UX frustration.

How it works

Teams identify one core job-to-be-done and strip everything else. A B2B workflow tool might launch with a single integration and manual onboarding behind the scenes. A consumer app might test one loop — create, share, return — before adding social features or monetization layers.

The MVP produces measurable signals: activation rate, week-one retention, conversion to paid, or sales cycle length. Those metrics guide the next build priorities. Founders often confuse “minimum” with “embarrassingly incomplete.” If users cannot complete the core task, you learn nothing useful about market fit.

Investors at seed stage typically ask what hypothesis the MVP tested and what changed after the first cohort — not how many features shipped. A focused MVP also makes it easier to explain what you learned when pivoting, which preserves credibility in the next fundraise.

Why it matters

• Founders: Speed to learning beats perfection. Budget and runway go further when you validate demand before scaling headcount or infrastructure.
• Investors: MVPs de-risk technical and market assumptions cheaply. Strong retention on a narrow product suggests room to expand; vanity launches with no repeat usage usually pass.

Common mistake

Building an MVP that is really a v1 roadmap in disguise — too many features to isolate which ones drive value, too slow to ship, too expensive to pivot.

Related ideas

See also product-market fit, beachhead, iteration cycles, and launch.