MVP scope builder
Pick the features for a first version and get a scope document to share.
FreeRuns in your browserNo signupUpdated 2026-11-05
The answers below are an example for a booking app. Replace them with your own.
Features: in the MVP, later, or not needed
Accounts and access
- Sign-up and loginEmail and password, email verification, password reset
- Social loginSign in with Google, Apple or Microsoft
- Roles and permissionsDifferent access for admins, staff and customers
- Team accountsInvite colleagues to a shared account
- Two-factor authenticationA second step at login for sensitive accounts
Core product
- DashboardAn overview screen of the user's key information
- Create, edit and list recordsThe main objects of the product, such as orders, projects or patients
- Search and filtersFind records by text, status or date
- File and image uploadsAttach documents or photos to records
- Calendar and schedulingAvailable times, bookings and a day or week view
- Messages or commentsConversations between users inside the product
- ExportDownload data as CSV or PDF
Notifications
- Transactional emailsConfirmations, receipts and password resets
- SMS or WhatsApp messagesReminders and alerts sent to a phone
- Push notificationsAlerts on a phone from a mobile app
- In-app notificationsAn alerts list inside the product
Payments
- One-off paymentsCard or wallet payment for a single purchase
- SubscriptionsPlans, recurring billing, upgrades and cancellations
- Invoices and receiptsTax-compliant documents sent to customers
Admin and operations
- Admin panelManage users, records and settings without a developer
- Product analyticsTrack sign-ups, activation and the success measure
- Audit logA record of who changed what, and when
- Help centre or support chatAnswers and a way to contact you
Integrations
- Calendar syncTwo-way sync with Google or Outlook calendars
- CRM or accounting integrationSend customers or invoices to another system
- Public API or webhooksLet customers connect their own tools
- Single sign-on for companiesSAML or OpenID login through a company directory
Content and reach
- Marketing site or landing pageExplains the product and collects sign-ups
- More than one languageTranslated interface, including right-to-left if needed
- Privacy policy, terms and cookie consentThe legal pages a live product needs
Every feature in the MVP should help prove the success measure. If it does not, move it to Later.
In the first version
9
Features in the MVP
Deferred
6
Written down for later
# ClinicBook: MVP scope ## The problem Small physiotherapy clinics take bookings by phone, which ties up reception and leads to missed appointments. ## Who it is for Patients who book appointments, and the reception staff who manage each day's schedule. ## How we will know it works Half of new bookings at our pilot clinics are made online within three months of launch. ## Platform and timing - Platform: Web app that works on phones - Target launch: Within 12 weeks of starting the build ## In the first version (9) ### Accounts and access - **Sign-up and login**: Email and password, email verification, password reset - **Roles and permissions**: Different access for admins, staff and customers ### Core product - **Dashboard**: An overview screen of the user's key information - **Calendar and scheduling**: Available times, bookings and a day or week view ### Notifications - **Transactional emails**: Confirmations, receipts and password resets ### Admin and operations - **Admin panel**: Manage users, records and settings without a developer - **Product analytics**: Track sign-ups, activation and the success measure ### Content and reach - **Marketing site or landing page**: Explains the product and collects sign-ups - **Privacy policy, terms and cookie consent**: The legal pages a live product needs ## Later, not in the first version (6) - Social login - Export - SMS or WhatsApp messages - One-off payments - Calendar sync - More than one language ## Assumptions to test - Patients will book online if it takes under a minute - Clinics will switch if it cuts phone calls at reception ## Open questions - Do clinics need to take a deposit at booking? - Which clinic will pilot the first version?
Paste the Markdown into Notion, Google Docs, GitHub or an email to a developer.
Before you share it
- Can you explain how each MVP feature helps the success measure?
- Could any MVP feature be done by hand for the first customers?
- Is every open question owned by someone, with a date to answer it?
About this tool
How it works and how to read the result.
Need this done for you?
Web app & SaaS development
SaaS products and web apps, from first version to scale.
See the serviceWhat it does
This MVP scope builder helps you decide what goes into the first version of a web or mobile app and writes it up as a document you can share. You describe the problem, the users and how you will measure success, then go through a list of common features grouped by area and mark each one as in the MVP, later or not needed. Add features specific to your product, the assumptions you want to test and the questions still open. The page produces a Markdown scope document that you can copy or download. It runs in your browser and nothing is sent anywhere.
How to use it
- Name the product and describe the problem in one or two sentences.
- Say who the first version is for and the one result that will show it works.
- Pick a platform and a target launch.
- Go through the feature list and mark each item MVP, Later or No.
- Add anything specific to your product, your assumptions and open questions.
- Copy or download the document and send it to everyone who needs to agree on it.
How to read the result
The example is ClinicBook, an online booking app for small physiotherapy clinics. The problem is that bookings arrive by phone, tying up reception and leading to missed appointments. Success is defined as half of new bookings at the pilot clinics being made online within three months of launch.
Nine features are in the first version: sign-up and login, roles so staff and patients see different things, a dashboard, calendar and scheduling, transactional emails, an admin panel, product analytics, a landing page and the legal pages. Six are deferred: social login, SMS reminders, online payments, calendar sync, export and a second language.
Two choices in the example are worth copying. Analytics is in the MVP, because without it there is no way to check the success measure. Payments are deferred, because patients can still pay at the clinic and the first thing to prove is that they will book online at all.
The document follows a fixed order: problem, users, success measure, platform and timing, features in, features later, assumptions and open questions. Read it back from the top. Each feature in the first version should connect to the problem or the success measure. If one does not, move it to later and see whether anyone objects.
A short MVP list is not the same as a small build. Calendar and scheduling, for example, hides a lot of rules about opening hours, staff availability and cancellations. Once the list is agreed, plan the build in phases with the project timeline calculator or get a rough range with the app development cost calculator.
When the scope is ready, our web app development service can turn it into a working first version.
Questions
Frequently asked.
What should an MVP include?
The smallest set of features that lets real users solve the problem and lets you measure whether they did. That usually means the core action, whatever accounts and permissions it needs, the emails that confirm it happened, and enough admin and analytics to run it and see the result. Everything else can wait until the first users tell you what they miss.
Why write down what is not in the MVP?
Because ideas you leave out come back in every meeting. A written later list shows they were heard and parked, not forgotten. It also gives the second version a starting point, ranked by what first users actually ask for.
Is an MVP the same as a prototype?
No. A prototype shows how something might work, often with fake data, and is used to test a design. An MVP is a working product that real users rely on, so it needs real accounts, real data and the legal basics, even if it does very little.
More in Business & pricing
Related tools.
- Website brief and RFP generatorAnswer a few questions and get a brief to send to web design agencies.
- Website launch checklistEverything to check before and after a website goes live, as a checklist.
- Website redesign checklistSteps to redesign a site without losing traffic: audit, redirects, launch, checks.
Your next move
Like what you see? Tell us about it.
A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.
India · Working with clients worldwide