Building

What an MVP should and should not include

An MVP that is too big wastes money and delays learning. One that is too small cannot be sold. This guide explains what a first version of a SaaS product must include, what can wait and how to decide which is which.

By the Twarx Micro SaaS Boutique team5 min read

Minimum viable product is one of the most misused phrases in software. To some people it means a rough prototype. To others it means a full product with a few features removed. Neither is quite right, and the confusion costs founders money in both directions.

A useful definition is this: the smallest version of the product that solves the core problem well enough that the right customers will use it and pay for it. Each word matters. Smallest, because every extra feature costs time and delays learning. Solves, because a product that only half works teaches you nothing. Pay, because a product nobody can buy is still an experiment.

Start from the one job

Every good micro SaaS does one job for one kind of customer. Before listing features, write down that job in a sentence, and describe the moment a customer gets the result they came for. Everything in the MVP should exist to get customers to that moment, reliably and without help.

Walk through the path from first visit to that moment, step by step. Each step needs to be in the product. Anything that does not sit on that path is a candidate to leave out, however good an idea it is.

What the core must do

The core job should be done properly, not partially. If the product produces a report, the report should be accurate and usable. If it handles bookings, bookings should not get lost. Customers forgive a product that does little. They do not forgive one that does its main job badly.

That often means the core is deeper than founders expect, while everything around it is thinner. It is better to handle the main task fully, including the common exceptions and mistakes, than to offer five features that each work for the simplest case only.

The foundations you cannot skip

Some parts of a SaaS product are invisible in a demo but essential once real customers arrive. Leaving them out does not make the MVP smaller. It makes it unfinished, and they are usually harder to add later than to build in from the start.

  • Sign-up, login and password reset that work reliably.
  • Billing that can take payment and handle cancellations.
  • Each customer's data kept separate from every other customer's.
  • Backups that have been tested by restoring them.
  • Error tracking, so you hear about problems before customers do.
  • A simple admin view so you can see and support customers.

What to leave out

Most MVPs grow too large through reasonable-sounding requests. Each one makes sense alone, but together they double the build and push back the moment you learn whether the product works. A useful habit is to ask of every feature: would a customer refuse to buy without it?

If the answer is no, it waits. Customers will tell you after launch which of these matter, and the list is usually different from what anyone predicted.

  • Integrations with tools only some customers use.
  • Detailed reporting and dashboards beyond the essentials.
  • Settings and options for cases you have not seen yet.
  • Native mobile apps, when a web app that works well on phones will do.
  • Several pricing plans, when one will let you start selling.
  • Features requested by one prospect who has not committed to buy.

Signs your MVP is the wrong size

An MVP is too big if the scope keeps growing, if the launch date keeps moving because of features unrelated to the core job, or if you cannot explain in one sentence what the first version does. The cost is not just money. Every extra week without real users is a week without the information you need most.

An MVP is too small if customers cannot complete the core job without your help, if you cannot charge for it, or if it is so rough that people judge the idea by the bugs. A product launched too thin teaches you little, because you cannot tell whether people left because of the idea or the execution.

How to decide what goes in

Write every proposed feature on a list and put each one into one of three groups: needed for the core job, needed to sell and run the product safely, and everything else. The first two groups are the MVP. The third is the list you revisit after launch with real usage in front of you.

Then agree the scope in writing before the build starts, including what is out. When new ideas arrive during the build, and they will, add them to the later list unless they change whether customers can complete the core job. This keeps the build focused without losing the ideas.

Plan for what happens after launch

An MVP is the start of a product, not a finished one, so build it with the next step in mind. That does not mean building features early. It means making sure you will be able to learn from the first customers and act on what they tell you.

Before launch, decide what you will measure. For most products that is a short list: how many visitors sign up, how many reach the result the product promises, how many pay and how many are still using it after their first month. Set up simple analytics for those steps and nothing more. A handful of numbers you read every week is more useful than a dashboard nobody opens.

Plan to talk to early customers as well. Numbers show you where people get stuck, and conversations tell you why. Keep a running list of requests and complaints, note how many customers raised each one, and use that list when you decide what to build after the MVP. The features that rise to the top are often not the ones that were cut from the first version, which is exactly why they were worth leaving out.

The short version

A good MVP does one job properly, includes the unglamorous foundations that let you charge customers and keep their data safe, and leaves out everything a customer would not refuse to buy without. Decide the scope in writing before you start, protect it during the build and let real customers decide what comes next. The aim is not a small product for its own sake, but the fastest honest answer to whether people will pay for what you have built.

Have an idea worth testing?

Tell us the problem and who has it. We will reply with how we would validate it and what an MVP could look like.