What is an MVP (minimum viable product)?
A minimum viable product (MVP) is the smallest working version of a product that real users can use, and ideally pay for, so you can test whether it solves their problem before investing in the full build. It does one core job well and leaves everything else for later.
Updated
| Clickable prototype | MVP | Full product | |
|---|---|---|---|
| Works with real data? | No: simulated screens | Yes | Yes |
| Purpose | Test the idea and the flow | Test demand and usage | Scale and serve all users |
| Typical time (Mjengo Corporate) | 1–2 weeks | 8–12 weeks for a mobile app | Ongoing |
| Starting cost (Mjengo Corporate) | From KES 25,000 | From KES 350,000 for a mobile app | Depends on scope |
Why build an MVP first?
Most new products are built around assumptions: that customers have the problem, that they will pay, that they will change their habits. An MVP tests those assumptions with real users for a fraction of the cost of a full build.
For founders in Kenya, an MVP also makes conversations with investors and partners concrete. A working product with early users is far easier to back than a pitch deck.
How do you scope an MVP?
- Write down the one problem the product solves and for whom.
- List every feature you imagine. Then cut everything that is not needed to solve that one problem.
- Keep the features that let a user complete the core job end to end, including payment if payment is the test (in Kenya that usually means M-Pesa).
- Design a clickable prototype of that flow and put it in front of target users before building.
- Build only what the prototype proved. Measure usage from day one.
- Decide what to build next from the data, not from the original feature list.
Common MVP mistakes
- The "minimum" keeps growing. Every extra feature delays the moment you learn something.
- "Minimum" becomes "broken". An MVP should be small, not unreliable. Users judge what they see.
- No measurement. If you cannot see what users do, the MVP cannot teach you anything.
- Skipping the prototype. Testing a clickable design first is far cheaper than finding out after the build.
How Mjengo Corporate builds MVPs
We start every MVP with a UI/UX blueprint (from KES 25,000, 1–2 weeks) so you can test the core flow first. A mobile app MVP for Android and iOS starts from KES 350,000 (≈ US$2,700) and typically takes 8–12 weeks, including the backend, an admin dashboard and M-Pesa integration. Web-based MVPs and internal systems usually start lower.
Frequently asked questions
What is the difference between an MVP and a prototype?
A prototype simulates the product so you can test the idea and the flow; it does not work with real data. An MVP is a working product that real users can use, so you can test real demand and behaviour.
How much does an MVP cost in Kenya?
At Mjengo Corporate a mobile app MVP for Android and iOS starts from KES 350,000 (about US$2,700) and takes 8–12 weeks. A clickable prototype to test the idea first starts from KES 25,000.
How long should it take to build an MVP?
Most MVPs should launch within two to three months. If the plan takes much longer, the scope is probably bigger than a minimum viable product.
