A minimum viable product (MVP) is the smallest version of a new product that real people can use, built so you can learn whether they want it before you spend more. Eric Ries, who popularised the term, defined it in 2009 as the version of a new product that lets a team collect the maximum amount of validated learning about customers with the least effort. The key word is learning. An MVP is a test, not a cheap finished product.
Why it matters for your business
Most founders we meet are excited and a little scared, and both are reasonable. The fear is spending a year and a large budget building something nobody pays for. An MVP shrinks that risk. You put a working core in front of real users in weeks or a few months, watch what they do, and decide what to build next based on evidence rather than hope.
It also forces a useful conversation. Writing down the one problem the product solves, and the one action that proves people value it, often shows that half the feature list can wait.
An example
A founder in Dubai wants an app connecting families with home tutors, with chat, video lessons, payments, ratings, a tutor dashboard and an admin panel. The MVP version: tutors listed by subject and area, a booking request, payment for the first lesson and a WhatsApp message to confirm. Video, ratings and the full dashboard wait.
If families book and come back, the founder has proof. If not, the founder learned that cheaply and can change course.
| Belongs in the MVP | Can usually wait |
|---|---|
| The one core action users came for | Extra roles and permissions |
| Sign-up and payment, if money is the test | Detailed analytics dashboards |
| Basic security and data protection | Social features and gamification |
| A way to hear from users | Every platform at once |
How to use it
- Write the riskiest assumption in one sentence: "Parents will pay upfront for a first lesson."
- Pick the smallest product that tests it with real users.
- Decide in advance what result counts as success.
- Cut every feature that does not serve that test. Keep quality where it matters: security, payments and the core flow.
- Launch, measure, talk to users, then decide what to build next.
If you are hiring outside help to build it, our guide to hiring an offshore development team covers what to check first. Founders with an idea and no tech team can work with our senior team from scoping to launch through Astra Team.
Frequently asked questions
How is an MVP different from a prototype?
A prototype shows how a product might look or work, often with no real data behind it. An MVP is a working product that real users can use for real, so you learn from their behaviour rather than their opinions.
How long does it take to build an MVP?
It depends on the scope, the platforms and the integrations, so be wary of a fixed number given before anyone has seen your idea. A tightly scoped MVP is usually measured in weeks or a few months, and cutting features is the main way to shorten it.
Who owns the code of my MVP?
You should, in writing, before work starts. When we build an MVP, the client owns the code, designs and accounts. Check any contract for ownership and access to the code repository before you sign.
Last reviewed 22 Oct 2026 by the Astrafolio team.