--- title: "What Is an MVP? Minimum Viable Product Explained Simply" description: "What an MVP (minimum viable product) is, what it is not, examples like Dropbox and Airbnb, the types of MVP, and how to build your own with AI." source: "https://flowmaps.app/guides/what-is-an-mvp" --- # What Is an MVP? Minimum Viable Product Explained Simply ![Tuan Hoang](https://flowmaps.app/team/tuan-hoang.jpg) By [Tuan Hoang](https://www.linkedin.com/in/tuan-hoang-188b4756/), Founder of Flowmaps Published 3 November 2026 · 6 min read An MVP, or minimum viable product, is the smallest version of your product that real people can use and that teaches you whether the idea works. It does one main job well enough that someone would use it, pay for it or come back to it. It's not a demo, and it's not the finished product. It's the first real step, built to learn as fast as possible. The term was made popular by Eric Ries in _The Lean Startup_ (2011). The idea is simple: instead of building for a year and hoping, you build the smallest useful thing, put it in front of people and let what they do decide what you build next. ## What "minimum", "viable" and "product" mean - **Minimum**: only what's needed for the main job. Everything else waits. - **Viable**: it actually works and solves the problem. A broken or confusing app teaches you nothing, because people leave before you learn anything. - **Product**: real people can use it, not just look at it. Most beginners get "minimum" right and forget "viable". An app with five half-working features is worse than an app with two that work well. ## What an MVP is not | An MVP is not… | Because… | | ----------------------------- | ---------------------------------------------------------------------------------- | | A prototype | A prototype shows how something could look. An MVP is used by real people. | | A beta of the full product | A beta is the whole product with bugs. An MVP is a small product on purpose. | | The cheapest possible version | Cheap but broken isn't viable. Small is the goal, not sloppy. | | Version 1.0 forever | It's the start of learning. What you build next depends on what people do with it. | ## Famous MVP examples - **Dropbox** started with a short video showing how file syncing would work, before the product was finished. The sign-up list grew overnight, which showed people wanted it. - **Airbnb** began when the founders rented air mattresses in their own apartment to people visiting a conference in San Francisco. One web page, a few guests, real money. - **Zappos** tested whether people would buy shoes online by posting photos of shoes from local stores. When someone ordered, the founder bought the pair at the store and shipped it. None of these had the features their products are known for today. Each one answered one question: do people want this? ## Types of MVP | Type | What it is | Good for testing | | ---------------------- | -------------------------------------------------------------------- | -------------------------------------- | | **Landing page** | A page that explains the product, with a sign-up or pre-order button | Whether people are interested at all | | **Video or demo** | A short video of how it will work (like Dropbox) | Whether the idea makes sense to people | | **Concierge** | You do the work by hand for the first customers | Whether people pay for the result | | **Single-feature app** | A real app that does only the main job | Whether people use it and come back | With AI app builders, the single-feature app has become the easiest type. What used to take a developer months can now be a working app in days. That makes the "minimum" part even more important: when building is cheap, it's tempting to build everything. ## How to build an MVP with AI, in five steps 1. **Write the problem in one sentence**: who has it, and what they're trying to get done. 2. **Find the one main job** your app must do to solve it. For a booking app, that's booking. For a habit tracker, ticking off today. 3. **List the features, then cut.** Keep only what the main job needs, plus the basics every app needs (accounts if data is saved, payments if you charge from day one). Our [MVP feature list guide](https://flowmaps.app/guides/mvp-feature-list) has three example lists, and the free [app feature list generator](https://flowmaps.app/tools/app-feature-list-generator) writes a first one from your idea. 4. **Build one feature at a time** in an AI builder like [Lovable](https://flowmaps.app/lovable), [Bolt](https://flowmaps.app/bolt) or [Claude Code](https://flowmaps.app/claude-code), and test each one before the next. Read [how to build an app without coding](https://flowmaps.app/guides/how-to-build-an-app-without-coding) for the full path. 5. **Put it in front of real people** as soon as the main job works. Watch what they do, not just what they say. Building for phones? See [how to create a mobile app without coding](https://flowmaps.app/guides/how-to-create-a-mobile-app-without-coding). A phone-friendly web app is usually the fastest MVP, even if you want a store app later. ## How do you know your MVP worked? Decide before you launch what "worked" means, so you can't talk yourself into it afterwards. For example: - 10 people sign up from one post - 3 of the first 20 users come back the next week - 2 people pay, even a small amount If it worked, build what people ask for most. If it didn't, talk to the people who tried it: was it the problem, the solution or the way you explained it? Changing direction after an MVP isn't failing. It's what the MVP is for. (And if you've read that "90% of startups fail", see our [startup statistics fact-check](https://flowmaps.app/guides/startup-statistics-fact-check) for where that number really comes from.) ## Plan the MVP so you can keep building The MVP is the first version, not the last. The features you leave out are still part of the plan; they just come later. [Flowmaps](https://flowmaps.app/) keeps that whole plan on one map: what's in the MVP, what's next and what's for later, with a build prompt for each feature. When your first users ask for something, you move it up instead of starting a new plan. Browse the [example maps](https://flowmaps.app/examples) to see MVPs other people planned, or read about [spec-driven development](https://flowmaps.app/guides/spec-driven-development) to turn each feature into clear instructions for your AI builder. ## Frequently asked questions ### What does MVP stand for? MVP stands for minimum viable product: the smallest version of a product that real people can use, and that shows whether the idea is worth building further. ### What is an example of an MVP? Airbnb's first version was a simple web page renting air mattresses in the founders' apartment during a conference. Dropbox started with a demo video. A modern example: a booking app that only lets customers book and pay, without reviews, reminders or a mobile app yet. ### How many features should an MVP have? Usually three to six. Enough to do the main job and the basics around it, like signing in or paying. If your list is longer, check whether each feature is needed for the main job. ### What is the difference between an MVP and a prototype? A prototype shows how a product could look or work, often without being usable. An MVP is a working product real people use. You might build a prototype to test a design, and an MVP to test whether people want the product. ### How long does it take to build an MVP? With AI app builders, a simple MVP can work within days to a few weeks, depending on the app. Planning the features first is what keeps it short: most delays come from building things that weren't needed yet. ### How much does an MVP cost to build? Built yourself with an AI app builder, often less than $100 a month: the builder's plan (around $20–25 a month) plus a domain name. Hiring an agency costs far more. The biggest cost is usually your time, which is why a short feature list matters. ## Plan your app with Flowmaps Describe your idea, get a map of every feature and a build plan for your AI builder. Free to start. [Start free](https://flowmaps.app/login?new=1)