Free tool · 2 minutes
Plan your MVP
Tick the features you think you need. The planner sorts them into MVP must-haves and version 2, explains why, and gives you a week range and a one-page plan. No email needed.
1
What must users be able to do?
2
Tick everything you think you need
Your MVP plan · an estimate, not a quote
9–13 weeks to launch
ScopePrototypeSprint 1Sprint 2Sprint 3Sprint 4Launch
In the MVP 6
Sign-up and loginevery MVP needs it
The core workflowevery MVP needs it
Basic admin viewevery MVP needs it
Analyticsevery MVP needs it
Email notificationsevery MVP needs it
Paymentsyour users need it to book or buy something
Version 2 3
Chat or messaginguseful later, not needed to prove the idea
iPhone and Android appsa web app works on phones; build apps once people use it
Reviews and ratingsuseful later, not needed to prove the idea
How this is worked out
Sign-up, the core workflow, a basic admin view, analytics and emails always go in the MVP. Other features go to version 2 unless your core workflow depends on them: payments if users book or buy, uploads if they create, messaging if they connect, a reporting dashboard if they track work. Apps join the MVP only if the product only makes sense on a phone. You can move any card yourself. Weeks add rough effort per feature plus 4 weeks for scoping, prototype and launch; the range is 0.8× to 1.15×. Assumptions to confirm on a call.