ProductBeginner6 min read

Minimum Viable Product (MVP)

An MVP is the smallest version of your product that delivers real value to early users and generates validated learning. The goal isn't a 'crappy first version' — it's the fastest path to proving whether customers will pay for your solution. 74% of startups fail because they build something nobody wants.

Also known asMVPMinimum Loveable ProductMLPPrototypeFirst Version

Challenge a friend Browse library

The Trap

The trap is building too much. Founders spend 6-12 months building a 'complete' product before showing it to a single customer. By then, they've burned through runway and assumptions. Dropbox's MVP was a 3-minute demo video — it validated demand before writing a single line of code.

What to Do

Define the ONE core problem you solve. Build only the features needed to test if users will pay for that solution. Launch within 4-6 weeks. Your MVP should be embarrassingly simple — if you're not embarrassed by v1, you launched too late.

Formula

MVP Scope = Core Value Proposition − Everything Else

In Practice

Buffer originally tested demand for a social media scheduling tool with just a two-page website. Page 1 explained the features. Clicking 'Pricing' led to Page 2, which said 'Hello! You caught us before we're ready.' Users entered their email to join a waitlist. Once they saw strong conversion rates, they built the actual product. Their MVP was literally nothing but HTML.

Pro Tips

01
The best MVPs don't need code. Zappos started by photographing shoes at local stores and listing them online — when someone ordered, the founder walked to the store and bought them.
02
Set a HARD deadline of 30 days for your MVP. Constraints breed creativity.
03
Your MVP should have exactly ONE metric: 'Did they use it more than once?'

Myth vs Reality

Myth

“MVP means minimum effort”

Reality

The V stands for Viable — it must actually work well enough that early adopters see value. A buggy, confusing product isn't a valid test of your idea.

Myth

“You need to build it before validating”

Reality

The best MVPs aren't built at all — they're landing pages, demo videos, concierge services, or Wizard of Oz tests that simulate the product.

Try it

Run the numbers.

Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.

🧪

Scenario Challenge

You want to build a tool that uses AI to generate personalized meal plans. Your co-founder wants to spend 4 months building the AI engine, recipe database, and mobile app before launch. You have $50K in savings and no external funding.

Industry benchmarks

Is your number good?

Calibrate against real-world tiers. Use these ranges as targets — not absolutes.

MVP Build Time

Initial version of early-stage SaaS

Elite (Fast execution)

1-4 weeks

Good

1-2 months

Average

3-4 months

Critical (Over-engineering)

6+ months

Source: Y Combinator

Real-world cases

Companies that lived this.

Verified narratives with the numbers that prove (or break) the concept.

👟

Zappos

1999

success

Nick Swinmurn wanted to sell shoes online but didn't know if people would buy shoes without trying them on. Instead of building inventory and a warehouse, he took photos of shoes at local stores, listed them online, and when someone ordered, he physically went to the store, bought the shoes, and shipped them. Zero inventory, zero warehouse, maximum learning.

MVP Cost

$0 inventory

Time to First Sale

~2 weeks

Validation

People DO buy shoes online

Eventual Acquisition

$1.2B (by Amazon)

You don't need to build the final version to test the hypothesis. Zappos validated 'will people buy shoes online?' for essentially $0.

Decision scenario

The Feature Creep Crisis

You're 3 weeks into building your MVP. Your designer wants to add 'just one more feature' — social sharing. Your developer says it'll add 2 weeks. You have $15K left and a demo day in 4 weeks.

Budget Remaining

$15,000

Time to Demo

4 weeks

Core Features

80% done

Social Feature

0% done

Decision 1

Adding social sharing would make the demo look more polished — but it means cutting testing time to 1 week instead of 3 weeks.

Add social sharing — investors at demo day expect polishReveal

Social sharing ships buggy. The core product crashes during the demo because you only had 1 week of testing. Two investors pass because of reliability concerns.

Testing Time: 3 weeks → 1 weekBug Risk: Low → High

Ship core features only — spend 3 weeks testing and polishing the essentialsReveal

The demo is simple but rock-solid. Investors appreciate that you focused on the core value proposition. One investor says: 'I love that you know what matters and what doesn't.' You get a $100K check.

Testing Time: Stays at 3 weeksDemo Reliability: High

🛠️