MVP vs Full Product
What to include in a first version and what can wait.
Build an MVP when you need to test whether users want the product, or when budget and time are limited: include only the features needed for the core use case. Build a fuller first version when you are replacing an existing system that people already depend on.
- An MVP tests demand; it is not a cheap full product.
- Internal systems that replace spreadsheets need enough features to replace them.
- Plan version 2 before launching version 1.
What belongs in an MVP?
The features a user needs to complete the core task once, from start to finish. Accounts, payments and admin tools are included only if that task needs them.
What can wait?
Advanced settings, secondary user roles, extensive reporting, integrations that can be done manually at first, and polish on screens rarely used.
When is a full product the right start?
When replacing an existing tool. Staff will not switch to a system that covers half of what the spreadsheet did.
Frequently asked questions
How much does an MVP cost?
A custom web platform starts from €1,500 and a custom mobile app from €2,300. See our mobile app cost guide for details.