What belongs in an MVP, and what is quietly killing your runway

The hardest part of an MVP is the list of things you agree not to build.

The short answer

An MVP should contain signup, one complete core workflow, payments and analytics — nothing else. In India that is ten to sixteen weeks. Anything justified by 'we will need it eventually' belongs in phase two, because the first fifty users will change what eventually means.

Key takeaways

  • One user type, one workflow, one paid plan. Everything else is phase two.
  • Ship billing in the MVP — a product that cannot charge has not been validated.
  • Instrument activation from release one or you will be guessing at the roadmap.
  • Reserve a third of the budget for the two months after launch.

Nearly every MVP scope we are sent could lose forty percent of its features without losing anything a first customer would notice. The features are not bad ideas. They are just answers to questions nobody has asked yet.

The four things an MVP must have

  1. 01Signup and onboarding that gets a stranger to the point of value without a call.
  2. 02One complete workflow — end to end, properly, for one user type.
  3. 03Payments. A product nobody has paid for is a prototype with good manners.
  4. 04Analytics on activation and the core loop, so week four tells you something.

The things that always get cut

  • A second user role, before the first one has anyone in it.
  • A settings page with fourteen toggles, when the defaults have never been tested.
  • Integrations requested in sales conversations that have not closed.
  • A mobile app alongside the web app in the same release.
  • An admin dashboard beyond what support genuinely needs on day one.

Twelve weeks, honestly

WeeksWhat happensWhat you get
1–2Definition, architecture, core flow designScope and prototype
3–8Build in three sprints, billing includedStaging URL each fortnight
9–10Private beta with 10–30 usersFindings and fix list
11–12Fixes, launch page, tracking, go liveA product taking payments

If your timeline says twenty-four weeks, the scope contains a phase two. Find it and move it.

Questions people also ask

It is scoped on the one workflow you are building, and it should include payments and analytics — those are what make it a validation rather than a demo. If a quote is very low, check whether billing is in it. Keep back roughly a third of your budget for the eight weeks after launch, which is when you learn what to build next.

Keep reading

Related

What this connects to

Rather have this answered about your own account?

Send us what you have. We will look at it properly and write back with what we would change, in the same plain terms as the page you just read.