What is an MVP, in plain English?
By Bonaventure Ogeto, Founder and CEO, Mctaba Labs
Published
An MVP, or minimum viable product, is the smallest version of your product that a real customer can use and pay for, built to find out whether the business works. It does one job from start to finish. It is not a demo, a design, or a cheap copy of the full product you imagine.
It is easy to picture an MVP as a smaller, cheaper version of the big product in your head. Fewer screens, fewer features, the same dream at a discount. That picture leads to first versions that take months and teach their owners nothing.
An MVP is not a small product. It is a test that happens to be a product. Once you see it that way, the question changes from "what can I afford to build?" to "what is the least I must put in front of a customer to learn whether this business works?"
What does MVP actually mean?
MVP stands for minimum viable product. The term became common through Eric Ries's book The Lean Startup, where the point of a first version is learning: you build the least you can, put it in front of real customers, measure what they do, and decide what to build next from that evidence.
Take the two words one at a time.
Minimum means you leave out everything that is not needed to answer your question. Not "everything we cannot afford". Everything.
Viable means that what remains truly works for the customer. They can come in, do the one job and get the result. If you are selling, they can pay. A product that does half a job is minimum but not viable, and it will teach you only that broken things do not sell.
A useful picture: you want to help people cross a river. The full product is a bridge. Half a bridge is not an MVP, because nobody crosses on half a bridge. A small boat is. It is slow and it carries one person at a time, but it gets a paying customer to the other side, and by the end of the week you know how many people want to cross and what they will pay.
How is an MVP different from a prototype or a demo?
These words get used as if they were the same. They are not, and a developer will quote you very differently for each.
| Compared on | What it is | Who uses it | What it tells you |
|---|---|---|---|
| Mock-up | Pictures of screens | You and a designer | Whether the idea is clear |
| Prototype | Screens you can click through, with nothing real behind them | A few people you sit beside | Whether people understand how to use it |
| Demo | A working slice shown by you | An audience watching | Whether people are interested |
| MVP | A working product that does one job from start to finish | Customers on their own, with their own money | Whether people will pay and come back |
| Full product | Many jobs, many kinds of user | Everyone | Nothing new, if you skipped the steps above |
The line that matters is between the demo and the MVP. Everything above that line is used with you sitting beside the user. An MVP is used when you are not there, by people who owe you nothing. That is what makes its evidence worth more than any amount of praise for a prototype.
What does an MVP look like for a business in Kenya?
Here are three made-up examples to show the shape. None is a real company.
A chama contributions tracker. The dream is an app with loans, dividends, statements and a group chat. The MVP is a page where the treasurer records who has paid this month, and each member gets an SMS or WhatsApp message with their balance. Members still pay to the treasurer's M-Pesa line as they do today. The question it answers: will a treasurer pay a small monthly fee to stop arguing about who has paid?
Grocery delivery for one estate. The dream is a marketplace with riders, live tracking and hundreds of vendors. The MVP is a WhatsApp number, a price list sent every morning, one mama mboga, one rider, and payment on M-Pesa at the gate. There is no code at all. The question: will households in this estate order three times a week and pay a delivery fee?
Fee reminders for small private schools. The dream is a full school system with report cards and timetables. The MVP is a simple web page where the bursar uploads the fee list, and parents get a reminder with the school's Paybill and their child's admission number. The question: do reminders bring fees in earlier, and will the school pay for that?
Notice what the three share. Each does one job for one kind of customer. Each takes or tracks real money. And each leaves the hard, expensive parts to a person and a phone until the idea has earned the right to be automated.
How do I decide what goes into my MVP?
Use the sheet below. It fits on one page, and you can hand it to whoever builds for you.
1. Write the one sentence the MVP must make true.
[One kind of customer] can [do one job] and [get one result], and pays [how] for it.
For the chama example: "A chama treasurer can record this month's contributions and every member sees their balance, and the chama pays a monthly fee by M-Pesa."
2. List every feature you have imagined. All of them. Get them out of your head and onto paper.
3. Put each one through three questions.
- Can the customer finish the job without it? If yes, cut it.
- Can I do it by hand for the first fifty customers? If yes, do it by hand.
- Will the customer notice it is missing in the first week? If no, cut it.
4. Sort what survives into three columns.
| Build now | Do by hand for now | Later |
|---|---|---|
| The one job, start to finish | Sign-up and onboarding (you do it on a call) | Second kind of user |
| Taking or recording payment | Reports (you send a PDF on Friday) | Dashboards and charts |
| The message the customer receives | Support (your own WhatsApp) | App store versions |
5. Write the pass mark. For example: "Ten treasurers use it for two months running and six of them pay." Write yours before anything is built.
If the "Build now" column has more than five lines, you are still describing the bridge. Go round again.
What is an MVP not?
A few things get called MVPs and are not.
It is not a broken version of the full product. Ten features that each half work teach you nothing. One feature that fully works teaches you a great deal.
It is not an excuse for carelessness with money or data. If your MVP holds people's phone numbers, ID details or payments, you owe them the same care as a finished product. Keep less data instead of protecting it badly.
It is not a pitch. If the only people who have seen it are friends, judges at a competition and potential investors, it is a demo. Put it in the hands of a stranger who has the problem.
It is not permanent. Much of an MVP gets rewritten once you know what customers do with it. That is the plan working, not money wasted. You paid to find out what to build properly.
How do I know when my MVP has done its job?
When it has answered the question you built it to ask. That can go three ways.
Customers use it, pay and come back without being chased. You have a business to grow, and their requests tell you what to add next.
Customers use it but will not pay, or pay once and vanish. The problem is real but the offer is wrong. Change the price, the promise or the buyer before you add a single feature.
Nobody uses it, even after you have put it in front of the right people yourself. The problem is not painful enough. This is disappointing and also the cheapest moment you will ever have to find out.
What an MVP never does is finish. If you catch yourself saying "it just needs one more feature before we show customers", you have stopped running a test and gone back to building the bridge.
What does this mean for the build?
It changes what you ask a developer for. Instead of "build me an app like the big ones, but simpler", you arrive with one sentence, a short "Build now" column and a pass mark. That is a job someone can price, finish and be held to. It is also a job you can check with your own eyes: either a treasurer can record a payment and a member gets the message, or not.
It changes what you spend on, too. The effort goes into the one flow and the payment step, because those are where customers decide whether to trust you. Everything else stays as plain as it can be. If you want to see how a first version is scoped with a builder, the page on MVPs for founders walks through it.
Key takeaways
- An MVP exists to answer a question about your business, not to impress anyone.
- It must do one job from start to finish for a real customer, including taking the money.
- A prototype shows an idea. An MVP is used by people who do not know you.
- Write the one sentence the MVP must make true, then cut every feature that sentence does not need.
- Do by hand anything a customer cannot see. Automate it once it hurts.
- Decide before launch what result means carry on, change or stop.
Frequently asked questions
- What does MVP stand for?
- It stands for minimum viable product. Minimum means the fewest features you can get away with. Viable means it still does the whole job well enough that a customer gets the result they came for and is willing to pay for it.
- Does an MVP have to be an app?
- No. It can be a website that works on a phone, a WhatsApp number with a person behind it, a USSD menu or a spreadsheet you run by hand. Pick whatever your customers already use. An app in a store is often the slowest and most expensive way to begin.
- Can an MVP look ugly?
- It can look plain, but it cannot be confusing or feel unsafe. People in Kenya are careful about where they send money, so the payment step and anything that touches their balance must look trustworthy and work every time. Spend your polish there and nowhere else.
- Is an MVP the same as a beta version?
- Not quite. A beta is usually a nearly complete product being tested for bugs before a wider launch. An MVP comes earlier and asks a bigger question, which is whether anyone wants this at all. Many MVPs are thrown away or rebuilt once that is answered.
- What comes after the MVP?
- You read the result against the pass mark you set. If customers paid and came back, you add the next most requested thing and fix what you were doing by hand. If they did not, you change the customer, the promise or the price before you spend on more features.
Sources
- The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, Eric Ries (book, 2011). Checked on 19 November 2026.
- The Mom Test: How to Talk to Customers and Learn If Your Business Is a Good Idea When Everyone Is Lying to You, Rob Fitzpatrick (book, 2013). Checked on 19 November 2026.
