What is an MVP?
A Minimum Viable Product is the simplest version of your product that tests whether anyone actually wants it. Build less, learn faster, iterate based on real user feedback — not assumptions.
MVP: The Definition
A Minimum Viable Product (MVP) is the most basic version of a product that can be released to early users to validate a core business hypothesis. It includes only the features absolutely necessary to test whether people want what you're building — and nothing more.
The concept was popularized by Eric Ries in The Lean Startup (2011), building on ideas from Steve Blank's customer development methodology. The key insight: instead of spending months building a full product based on assumptions, launch something minimal, collect feedback, and iterate.
The MVP formula:
Famous MVP Examples
Dropbox
2007MVP: A 3-minute explainer video
Drew Houston didn't build cloud storage first — he made a video showing how it would work. The video went viral on Hacker News, driving 75,000 signups overnight. The product didn't exist yet. The video validated demand before writing a single line of storage infrastructure.
Lesson: You can validate demand without building the product. Sometimes a video, landing page, or mockup is enough.
Zappos
1999MVP: Photos of shoes from local stores
Nick Swinmurn took photos of shoes at local stores and listed them online. When someone ordered, he'd buy the shoes at the store and ship them. No inventory, no warehouse, no shoe partnerships. Just a website and a camera.
Lesson: Test the core hypothesis manually before building infrastructure. If people will buy shoes online (the hypothesis), the logistics can come later.
Airbnb
2007MVP: Air mattresses on the founders' floor
Brian Chesky and Joe Gebbia rented air mattresses in their apartment to conference attendees who couldn't find hotel rooms. Three guests, three air mattresses, a homemade breakfast. Revenue: $240/night. The entire hotel industry disrupted by a weekend experiment.
Lesson: Start impossibly small. Your MVP should make you slightly embarrassed — if it doesn't, you've over-built.
Buffer
2010MVP: A two-page landing page
Joel Gascoigne created a landing page describing Buffer (social media scheduling), with a pricing page. When visitors clicked 'Plans and Pricing,' they saw the plans. When they clicked a plan, they saw: 'We're not quite ready yet — leave your email.' 120 signups validated the idea in a week.
Lesson: A landing page with a pricing page tests willingness to pay, not just interest. It's the cheapest possible product-market fit test.
Spotify
2006MVP: Desktop app with piracy-level convenience
Spotify's MVP was a desktop app that let you search and instantly play any song — legally. No social features, no playlists, no podcasts. Just 'type a song name, hear it immediately.' The core value proposition, stripped to its essence.
Lesson: Your MVP should nail one thing perfectly. Spotify didn't try to be a social network or podcast platform — they made music search instant.
How to Build an MVP (7 Steps)
Identify your core hypothesis
Every MVP tests a hypothesis: 'People will pay for X because they have problem Y.' Write this down explicitly. If you can't state the hypothesis in one sentence, your MVP scope is too broad.
Define the smallest test
What's the absolute minimum you need to build to test your hypothesis? It's usually less than you think. A landing page, a video, a manual process behind a simple UI — anything that tests whether people want this.
Set success criteria before building
Define what success looks like: '50 signups in the first week' or '10 people willing to pay $X.' Without pre-defined criteria, you'll rationalize any result as a success.
Build it in days, not months
An MVP that takes 3 months to build isn't minimal. If your MVP takes longer than 2-4 weeks, you're over-scoping. Cut features until it fits in 2 weeks. The features you cut can come back after validation.
Launch to a small audience
Don't launch to everyone. Find 50-100 people who match your target user profile. Personal emails, niche communities, Product Hunt. Quality feedback from 50 target users beats vanity metrics from 5,000 random visitors.
Collect feedback from day 1
Set up a feedback channel before you launch — not after. A voting board lets early users tell you what's missing, what's broken, and what to build next. This turns your MVP users into co-designers of the product.
Iterate based on data, not guesses
Use feedback votes, usage data, and conversion metrics to decide what to build next. Don't guess — let your users tell you. The MVP is just the starting point; the feedback loop is what makes it work.
Your MVP Needs a Feedback Loop
An MVP without a feedback mechanism is an experiment without results. Collecting user feedback from day 1 is what transforms a guess into a product.
Voting board
Let early users submit feature requests and vote on what to build next. The votes tell you exactly what's missing and what matters most. Set up in 2 minutes with Features.Vote.
Learn morePublic roadmap
Show users what you're planning to build based on their feedback. A public roadmap builds trust and gives early adopters a reason to stick around through the rough MVP phase.
Learn moreIterate fast
Use vote data and usage metrics to decide what to build in each sprint. Ship weekly. The MVP is the starting point — the feedback loop is the engine that drives iteration.
Learn more6 Common MVP Mistakes
Building too much
The most common mistake. Your MVP has 47 features, took 6 months, and you're still not sure if anyone wants it. An MVP with too many features isn't minimal — it's just a product you're scared to ship.
No feedback mechanism
Launching an MVP without a way to collect user feedback is like running an experiment without recording results. You learn nothing. Set up a feedback board before launch so users can tell you what to build next.
Perfecting the wrong things
Spending 3 weeks on animations when you haven't validated that anyone wants the core feature. Polish is for after validation. Your MVP should be ugly but functional — beautiful but useless is worse.
Targeting everyone
An MVP for 'everyone' helps no one. Pick a specific niche — the narrower, the better. Solve one problem for one type of user exceptionally well. You can expand later.
Ignoring willingness to pay
Lots of people will say 'cool idea!' Few will pay money. Your MVP should test willingness to pay, not just interest. Buffer's genius was showing a pricing page before the product existed.
No success criteria
If you don't define what 'success' looks like before launching, you'll interpret any result as positive. Set specific, measurable targets: X signups, Y conversions, Z feedback submissions.
"Shout out to FeaturesVote! Integration was done in under a minute"
Alexandre Negrel,
Founder at Prisme Analytics
Frequently Asked Questions
Still not convinced?
Here's a full price comparison with all top competitors
Is it lacking a feature you need?
Chances are, we're already working on it. Check our roadmap
Okay, okay! Sign me up!
Start building the right features today ⚡️