What Is an MVP?

MVP stands for Minimum Viable Product, the smallest functional version of a product that delivers real value to its intended users. It is not a prototype, a mockup, or a landing page. It works, it solves a real problem, and it is designed to be shipped to real users as quickly as possible so you can learn from how they actually use it.

The concept was popularised by Eric Ries in The Lean Startup and has since become the standard approach for building software products under conditions of uncertainty. The core premise is straightforward: you do not know exactly what users want until they use your product. An MVP lets you find out cheaply, quickly, and with minimal risk before committing to a full build.

An MVP is defined as much by what it intentionally excludes as by what it includes. The goal is to identify the one core problem the product solves, the thing that makes someone say 'yes, this is worth using', and build only that. Advanced features, polished dashboards, and secondary workflows can all come later once you have validated the core loop.

What separates a successful MVP from a failed one is almost always scope discipline. Teams that try to include too many features end up shipping late, overspending, and still not knowing if the core idea works. Teams that focus ruthlessly on the essential user journey ship faster, learn faster, and build better products as a result. At Toggle, we scope aggressively from day one and ship production-ready MVPs in 2 weeks.