Build log/SaaS

What goes into a SaaS MVP, and what waits

An MVP is the smallest product someone will pay for, not the smallest product you can build. Here is what belongs in the first release and what can wait for real users.

The short answer

  • Include what a paying customer needs on day one: sign-up, the core workflow, billing and a way for you to support them.
  • Leave enterprise features, integrations and mobile apps until customers ask for them.
  • Instrument the MVP from the start, so the second release is decided by data.

Minimum, but viable

The point of an MVP is to learn whether people will pay, as early and cheaply as possible. That means it has to be good enough for a real customer to use for real work. A demo that only works when you drive it teaches you very little.

What belongs in the first release

  • Sign-up and login, with password reset and email verification.
  • Workspaces, so a customer can invite their team. Adding multi-tenancy later is expensive.
  • The core workflow: the one job your product does better than a spreadsheet.
  • Billing: plans, a trial and a way to take payment. Charging from day one is the strongest signal you will get.
  • An admin console, so you can see accounts, fix data and help customers without a developer.
  • Analytics and logging, so you know what people actually use.
  • A marketing site that explains the product and can be found.

What can wait

  • SSO and enterprise controls, until an enterprise customer asks and will pay for them.
  • A public API and integrations, until customers tell you which systems matter.
  • Mobile apps, unless the core job happens away from a desk.
  • Usage-based pricing, until you know which usage customers value.
  • White-labelling, until a reseller is waiting for it.

Build the foundations properly

Some things are cheap to do right at the start and painful to change later: the data model, how tenants are separated, how permissions work, and how deploys happen. An MVP can be small without cutting these corners.

Decide the second release with data

Every MVP should ship with product analytics and a short list of questions it is meant to answer. The second release is then planned from what customers did, not from a backlog written before anyone used it.

Scope yours. The MVP scope builder lets you sort features into now and later.
Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.