MVP stands for minimum viable product: the smallest version of your product that tells you whether your idea works. Not half a product, and not a prototype that only exists in a slide deck, but a working first version that real users can use.

What does MVP actually mean?

The three words say it all:

  • Minimum: only what is needed to solve the core problem. Everything that "would be nice" waits.
  • Viable: it has to work and deliver value. A user should be able to solve their problem with it.
  • Product: it is live and in use, so you learn from real behaviour instead of opinions.

Why does an MVP matter?

Most software projects don't get stuck on code; they get stuck on assumptions. You think you know what users want, spend months building a full package, and only discover at launch that half of it goes unused. An MVP turns that around:

  • You learn faster. Within weeks you see how real users interact with your product.
  • You invest less up front. You pay for the core first, and only then for additions that have proven their value.
  • You have something to show. A working product convinces investors, partners and first customers far better than an idea on paper.
  • You reduce risk. If the idea doesn't work, you find out after a small investment instead of a large one.

What belongs in an MVP, and what doesn't?

The hardest part is choosing what to leave out. A useful rule of thumb: include only what you need to deliver the main promise to your user.

In

  • The one core action it's all about, such as booking an appointment, placing an order or finding a home.
  • Login, if users need to save something.
  • A simple admin area, so you can manage data without a developer.
  • A way to measure whether it works.

Not yet

  • Extensive settings, reports and export features.
  • Support for every edge case.
  • Features you want to have "for later".

MVP examples

A delivery platform can start with one city, one kind of product and payment on delivery. A booking app can launch with one type of appointment and an email confirmation. An AI service can first do one task well before more are added. At Woonbot, for example, everything revolves around one core: helping home seekers find the right listings faster.

MVP versus prototype

A prototype shows what something could look like. An MVP actually works. With a prototype you test whether people understand the idea; with an MVP you test whether they use it and are willing to pay for it.

Getting an MVP built

At Gain Impact we usually build an MVP in 4 to 8 weeks, for a fixed price of typically €3,000 to €5,000. Here's how it works:

  1. Getting acquainted. We discuss your idea, your audience and your main goal.
  2. Defining scope. Together we decide what goes into the first version. You get a concrete plan, a fixed price and a timeline.
  3. Building and testing. You see a working version every week and give feedback straight away.
  4. Launching. We take the product live and stay available for the next step.

Want to know what the next steps cost? Read how much it costs to build an app, or see our process.