By Rakibul Hasan, Moonlab
An MVP, or minimum viable product, is the smallest version of a product that solves one real problem for real users, so you can learn whether it is worth building more. It is not a rough prototype or a broken app. It is a small product that works.
This guide shows how to scope an MVP, what to cut, how long it tends to take and how to test it with users. It is for owners and founders in the US, UK and Europe who want to build an app or web tool without overspending. Timelines depend on scope and team, so treat ours as general guidance.
Start with one problem and one user
Write one sentence: who has the problem, what the problem is and how your product helps. If you cannot say it simply, the idea is not ready to build.
Talk to at least a handful of potential users before building. Ask how they solve the problem now, what it costs them and what they have tried. Their answers tell you more than a feature list.
Check whether you need to build anything yet
Often you can test the idea with something cheaper: a landing page, a form and a spreadsheet, or no code tools and manual work behind the scenes. If people will not sign up for that, they may not use an app.
Automation tools can stand in for a backend in early tests. See moonlab.space/guides/build-ai-agent-without-code and moonlab.space/guides/business-process-automation-guide for ideas.
Scope: the one core journey
Map the single journey that delivers value from start to finish. For a booking tool, that might be: pick a time, confirm, get a reminder. Build only that.
- List every feature you can imagine.
- Mark what the core journey cannot work without.
- Move everything else to a later list.
- Write what done looks like for each remaining feature.
What to cut
Cut anything that does not help test your main assumption. Common cuts for a first version are listed below.
- Several user roles, until one is proven.
- Native apps on every platform: pick one, or use a responsive web app.
- Custom admin panels: use the database's own interface.
- Social features, chat and ratings.
- Advanced reporting and settings.
- Perfect design polish, while keeping the product clear and usable.
Timeline and team
A tightly scoped MVP is often measured in weeks to a few months, not a year. The time depends on features, integrations and how fast you give feedback and decisions. Delays usually come from changing scope, not from coding.
Work in short cycles, with something to look at every week or two. Agree who makes decisions. A small team of a designer, a developer and you as product owner can be enough.
Test with real users
Put the product in front of real people early, even before it is finished. Watch them use it, without helping, and note where they get stuck. Five to ten sessions usually show the biggest problems.
Decide in advance what success looks like, such as how many users complete the main journey or come back. Choose measures that show real behavior, not just compliments.
Decide what happens next
After the test, choose one of three paths: improve and continue, change direction or stop. Stopping early is a good outcome if the evidence says so, because it saves money.
Plan for the basics even in an MVP: secure logins, backups, privacy compliance and error alerts. Keep the code in your own accounts, as in moonlab.space/guides/outsourcing-software-development.
A worked example and common mistakes
Here is a made-up example. A founder wants an app for local cleaners to find customers. His full idea has profiles, reviews, in app chat, payments, a calendar, a rating system and a mobile app for both sides. Built in full, it would take many months.
He applies the one core journey rule. The core is that a customer describes a job and a cleaner accepts it. For the first version he builds a simple web form for customers, a spreadsheet that receives requests, and a messaging group where a handful of cleaners claim jobs. He does the matching by hand. There is no payment feature and no chat; cleaners and customers talk by phone.
He runs this for four weeks with twenty customers in one town and tracks how many requests turn into completed jobs and how many customers book again. Only then does he decide what to build next. If completed jobs are low, he talks to customers to learn why before writing any code. If they are strong, the manual steps that hurt most, such as matching and reminders, become the first features.
A realistic plan after that is a small web app for requests and a simple cleaner dashboard, built in weeks, with payments added only when people ask for them. Avoid the mistakes below.
- Building for every user type at the start.
- Adding features because a competitor has them.
- Polishing design before checking anyone wants the product.
- No success measure, so any result looks like a win.
- Asking friends who are too polite to be honest.
- Skipping basics like backups and secure logins.
- Letting the developer own the code and hosting.
How to decide and what to do this week
Use these tests to decide whether a feature belongs in the first version. If the answer to the first question is no, the feature waits.
- Can the core journey work without it?
- Could it be done by hand for the first users?
- Would the first ten users notice if it were missing?
- Does it help test your biggest assumption?
- Does it add a new user type, platform or integration?
- Can you describe what done looks like in one sentence?
How Moonlab can help
We help scope and build MVPs, from simple automations to web apps. See moonlab.space/services/web-apps-and-saas, moonlab.space/services/app-development and moonlab.space/services/custom-build.
A free 30-minute automation audit at moonlab.space/contact is a good place to talk through your idea.
