Book a call

A free MVP scope template that builds itself.

The short answer

Use this MVP scope template to sort every feature into must have, later or skip. It estimates the hours and cost as you go, then gives you a one-page scope to copy. There’s no signup, and nothing you enter leaves your browser.

Book a free callEstimate your cost

Reviewed by Anubhav Gupta, Bespoke Devs · Updated

Fill in your MVP scope template

Sort each feature. Be strict: can a customer pay and get value without it?
  • User accounts & loginEmail, Google sign-in, password reset · about 24 hours
  • Stripe subscriptionsPlans, checkout, billing portal, webhooks · about 32 hours
  • Admin dashboardManage users, content and payments · about 40 hours
  • Teams & rolesWorkspaces, invites, permissions · about 32 hours
  • AI featuresChat, generation, summaries, agents · about 48 hours
  • File uploadsImages, documents, storage · about 16 hours
  • Email notificationsTransactional emails and digests · about 16 hours
  • Analytics & reportsCharts, exports, usage stats · about 32 hours
  • Real-time chatMessaging, live updates, presence · about 56 hours
  • Marketplace payoutsStripe Connect, split payments · about 64 hours
  • Mobile appiOS + Android with React Native · about 160 hours
  • Multiple languagesTranslated UI and content · about 24 hours
Estimated build
260 hours
With a freelancer
$4,500–$10,000

This scope fits our $4,997 full-scale MVP, built in 15 days. The hours include base setup, design from scratch and a marketing site. These are estimates, not quotes.

Get a fixed quote →

What to include in an MVP

A useful MVP feature list is short. A first version usually needs only what lets someone try it, pay and get the main result.

  • The one core workflowThe single job customers would pay for. Everything else supports this.
  • A way to payIf you plan to charge, include billing so you learn from real purchases.
  • Accounts, if neededAdd login when the product has to remember the user.
  • Basic adminEnough to help customers without asking a developer.

What goes in the one-page scope

The MVP scope template copies as plain text, so you can paste it into an email, a brief or a contract draft. It has four parts.

  • Product typeSaaS web app, AI product, marketplace or simple tool. The type changes the base hours.
  • Estimated buildThe total hours for your must-have list, including base setup, design from scratch and a marketing site.
  • Must haveEvery feature you’re committing to for launch. This is the list a developer prices.
  • LaterFeatures you’ve decided to wait on. Writing them down stops them creeping back in during the build.

A worked example

Take a SaaS web app with user accounts (about 24 hours), Stripe subscriptions (about 32) and an admin dashboard (about 40) as must haves, and email notifications in later. That comes to about 260 hours once base setup, design and a marketing site are added. It fits under the 300 hours we can build in 15 days.

Now move a mobile app to must have. It adds about 160 hours on its own, which takes the total to about 420 and past that limit. Many first versions can wait on this one, so test the web version first and move mobile back to later.

Common scope mistakes

  • Copying a mature competitorTheir feature list took years. Pick the part your customers would pay for now.
  • Leaving “later” emptyIf nothing has moved to later, you probably haven’t made any hard choices yet.
  • Forgetting integrationsThe estimate here leaves out third-party services, so list them for whoever quotes the work.
  • Describing screens, not the jobSay what the customer needs to get done. A developer can then suggest a simpler way to do it.

Common questions

  1. They’re rough. They use typical build hours per feature and typical market rates, so a real quote depends on the details of your scope.

  2. Anything a customer could do without in their first month. Team roles, mobile apps, analytics and multiple languages often wait until people are paying.

  3. No. The tool runs in your browser and doesn’t send your selections to us. Only anonymous usage events are recorded.

  4. An MVP scope template is a short document listing what a first version will do at launch and what will wait. It gives you and your developer one agreed list to price and build against.

  5. It’s a good start, but not a full specification. Add the core workflow in your own words, any third-party services you need and any designs you already have. For more on choosing features, read our [MVP features guide](/saas-mvp-development/scope).

Keep reading

Start a project

Tell us what you’re building.

Takes under a minute. We come back with a scope and a fixed price.

  • Reply within 24 hoursA real person reads every brief.
  • Fixed scope, fixed priceYou get a written proposal, no hourly billing.
  • You own the codeFull ownership of code and assets at launch.
What are you building?
When do you want to launch?
Budget
Prefer email? [email protected]