Glossary · Custom software

MVP

An MVP (Minimum Viable Product) is the first version of a piece of software with only the essential features, used right away to learn what to improve.

MVP in practice

MVP stands for Minimum Viable Product. It is the smallest version of a piece of software that already solves a real problem and that you can put in the hands of the people who will use it. It is not a mock-up or a demo: it really works, but it only does what is essential.

Starting from an MVP reduces the risk of spending months and budget on features nobody ends up using. You see early whether the idea holds up, gather feedback from colleagues and clients and invest in the parts that prove useful. It is the most prudent way to approach custom software.

Example: an estate agency wants complete management software for properties, viewings, contracts and commissions. The MVP starts with the property list and the viewings calendar, used by the whole office. After a few weeks of use it becomes clear what is really needed next: perhaps client reminders, rather than the commissions module that seemed urgent.

The typical mistake is inflating the MVP until it is no longer minimal: pick a single process and a single group of users. The opposite mistake is building it so provisionally that it has to be redone from scratch: the foundations, such as the database and logins, should be designed properly from the start. We go into more detail on our custom software page.