Skip to content
dvnt.io

Resources · glossary

MVP (minimum viable product)

The smallest version of a product that genuinely solves a user's problem and lets you check whether anyone will use it. Not a prototype, and not a version stripped of quality.

Also called
  • MVP
  • minimum viable product
  • first product version
  1. 01

    What an MVP really means

    That the product does one thing and does it well. The scope is narrow, but what is there works and can be shown to a customer. An MVP that crashes or loses data doesn't test the idea; it tests patience.

  2. 02

    Why build one

    To test an assumption before you spend the whole budget. The most expensive project is the one that finds out after a year that it was solving a problem nobody had.

  3. 03

    How it affects cost

    An MVP usually costs a fraction of the full product's budget, but it isn't simply a slice of it. The architecture has to support growth, or the saving turns into a rewrite from scratch.

  4. 04

    What it gets confused with

    A prototype (which handles nothing and only shows the idea) and a proof of concept (which checks technical feasibility). Of the three, only an MVP reaches real users.

In practice

Related terms

  • Project estimateAn estimate of a project’s effort and cost made before it starts, based on what is known about the scope at that moment. It is not a price promise — the less is known, the wider its range should be.
  • Build vs buyThe decision between building your own solution and buying a ready-made one. It is settled on costs over time and on whether the process is the company's advantage or just a necessity.

← All terms

15 minutes. No sales pitch.

A term in a proposal sounds foreign? In 15 minutes we explain what it means for your project.