Name the riskiest assumption, scope the smallest version that tests it, use a simple stack and bought services, build in short cycles, launch to a small group of first users, and measure what they do. Decide from the evidence whether to keep going, change direction or stop.
This is the main guide in our MVP series. The guide on the MVP development process sets out the weeks from idea to launch.
What an MVP is, and is not
Eric Ries, in his 2009 guide to the minimum viable product, defines it as the version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least effort. Our glossary entry on the minimum viable product gives the short version.
An MVP is not a cheaper version of the full product, a prototype nobody uses, or a launch with every corner cut. It is the smallest thing real users can use that tells you whether the idea works.
Step 1: Name the riskiest assumption
Every idea rests on assumptions. Write them down and pick the one that, if wrong, kills the idea:
- Problem: do enough people have this problem, badly enough?
- Solution: will they use this way of solving it?
- Value: will they pay, or change how they work?
- Reach: can you find them at a cost that works?
Step 2: Scope the smallest test
List every feature you imagine, then keep only those needed to test the riskiest assumption with real users; the rest goes on a later list. Sometimes the smallest test is not software at all: a landing page, a manual service behind a simple form, or a clickable prototype. When it is software, aim for a scope you can build in weeks, not months; Clutch's software pricing guide puts the typical full custom software project at about 13 months, which is what an MVP avoids.
Step 3: Choose a simple stack
Pick technology your team knows and can change quickly, and buy what is not your idea: login, payments, email, hosting. Scale is a problem to have later. Keep the code, domain and accounts in your own name from day one, so the MVP can grow or be handed over.
Step 4: Build in short cycles
Build in cycles of a week or two, each ending in something you can click through. Test the main task with a few real people before launch. Keep quality high where users touch the product and simple everywhere else.
Step 5: Launch to first users
Launch to a small group you can talk to: early customers, a waiting list, a community. Watch what they do, talk to them weekly, and make it easy to report problems. The aim is evidence.
Step 6: Measure and decide
The Lean Startup's principles describe the core loop as Build-Measure-Learn: turn ideas into products, measure how customers respond, then learn whether to pivot or persevere. Measure behavior, not opinions: sign-ups that come back, tasks completed, payments, referrals.
Then decide: keep going and build the next feature, change direction, or stop. Stopping early is a good result; CB Insights' 2026 analysis of 431 venture-backed shutdowns, among the 385 whose reasons it found, put running out of capital at 70%, and testing early is how to spend capital on what works.
Common MVP mistakes
The faults we see most:
- Too many features, so the MVP takes as long as a full product.
- No riskiest assumption, so nothing is really being tested.
- Measuring compliments instead of behavior.
- Launching to everyone before learning from a few.
- Over-building for scale before anyone uses it.
Conclusion
To build an MVP, name the riskiest assumption, scope the smallest version that tests it, use a simple stack and bought services, build in short cycles, launch to first users you can talk to, and measure behavior to decide whether to continue, change direction or stop. An MVP is for learning, as Eric Ries defined it.
PromotEdge International is an international strategy, technology, marketing and design company, and our delivery team is in India. Our MVP team scopes, designs, builds and launches first versions, and our marketing for startups helps find the first users.
The guides in this series
This is the main guide in our MVP series. Each guide below goes deeper on one part and links back here.
- MVP development process: the weeks from idea to launch, phase by phase.
Facts we rely on: see our company facts for what we state about ourselves and where each fact comes from.