Skip to content
Free tool

MVP Scope Planner

Choose what you are building and the features you have in mind. The planner splits them into a first version and later, rates the complexity, and gives you a one-page plan to copy or send.

Optional. It goes at the top of the plan.

What are you building?

Platforms

Features

Suggested for this type of app. Move anything that is not essential to Later: it is the fastest way to launch sooner.

Accounts and admin

  • Sign-up and login
  • User profiles
  • Roles and permissions
  • Admin dashboard

Payments

  • One-off payments
  • Subscriptions and billing
  • Payouts to sellers

Content and data

  • Listings or catalogue with search
  • File and image uploads
  • Booking and calendar
  • Maps and location

Communication

  • Email notifications
  • Push notifications
  • In-app chat
  • Ratings and reviews

AI

  • AI assistant or chatbot
  • AI answers from your documents
  • AI content generation

Business

  • Reports and analytics
  • Integrations with other systems
  • Multiple languages
  • Offline mode

Your MVP plan

Medium first version

Typical build time: 4 to 8 weeks

First version
5 features
Later
2 features

Suggested stack

  • Web app: React or Next.js
  • Backend: a Laravel or Node.js API with a PostgreSQL or MySQL database
  • Payments: Stripe
  • Hosting: Vercel or a VPS

Answer these before building

  • Who is the first user, and what one job must they be able to finish?
  • Which roles exist, and what can each one see and change?
  • Which plans will you offer, and what happens when a payment fails?
  • How will you know the first version worked?
As text, ready to paste into a doc or email.

Get a second opinion on this plan

Send it to me and I will reply with what I would cut, what I would add, and what it would take. Free.

Only used to reply to you. Never shared.

What an MVP should include

A minimum viable product is the smallest version that lets real users complete the one job your product exists for. Everything else, from reviews to dashboards, can wait until people use the core. The most common reason a first version runs late is a feature list that was never cut.

How the planner estimates complexity

Each feature carries a weight based on how much work it usually takes: sign-in is small, in-app chat and seller payouts are large. Platforms add to it, because a mobile app needs store releases and device testing. The timeline is a typical range for a first version of that size, not a quote; a real estimate needs a conversation about the details.

Turning the plan into a build

Take the first-version list to whoever will build it and ask them to challenge it. If you would like a second opinion, send the plan with the form above and I will reply with what I would cut, what I would add, and what it would take.

Frequently asked

How long does it take to build an MVP?
Most first versions take somewhere between a few weeks and three months. The biggest factors are the number of features in the first version, whether it needs a mobile app, and integrations with other systems. The planner shows a typical range for the scope you choose.
Should my MVP be a web app or a mobile app?
If you are still testing whether people want it, a web app is usually faster and cheaper: no app store review, no installs, and one codebase. Build mobile first when the core experience depends on the phone, such as the camera, location or push notifications.
Is the planner free?
Yes. It runs in your browser and nothing is stored. The plan is only sent anywhere if you choose to email it, and then only to me.
Can you build the MVP for me?
Yes. That is what the Idea to launch service is for: a first version built quickly with AI-assisted development and reviewed by a senior engineer.

Want it built, not just planned?

Idea to launch: a first version in front of real users in weeks, built with AI-assisted development and reviewed by a senior engineer.

More free tools