How to plan an MVP: build the smallest thing that proves your idea

A minimum viable product (MVP) is the smallest version of your product that delivers real value to real users — enough for you to learn whether the idea works. Done well, it saves you months and a lot of money. Done badly, it's either a bloated first version or a half-finished product nobody wants to use.

Start from the core job

Ask: what is the one job a user hires this product to do? For a booking platform, it's "find an available time and book it." Everything that doesn't directly support that job — reviews, loyalty points, chat, dark mode — can wait.

Map the single main journey

Write down each step a user takes from arriving to getting value. For example:

1. Lands on the homepage
2. Searches for a service near them
3. Views a provider
4. Picks a time
5. Enters details and confirms
6. Gets a confirmation email

That's your MVP. Build that journey well and cut almost everything else.

Sort features into three buckets

• Must have: without it, the core journey doesn't work.
• Should have: makes it better, but people could live without it for a few months.
• Later: nice ideas that depend on the product working first.

Be ruthless. Most first versions have too many "must haves."

Fake what you can

Admin tools, matching logic and reports can often be done manually behind the scenes at first. If ten orders a day come in, a person can handle them. Automate once volume makes it necessary.

Decide what you want to learn

Every MVP should answer specific questions: Will people sign up? Will they come back? Will they pay? Set up simple analytics and decide in advance which numbers will tell you to keep going, change direction, or stop.

Plan for version two

Build the MVP on a solid foundation — secure logins, a proper database, clean code — so you can grow it rather than throw it away. "Minimum" should describe the feature list, not the quality.