Many software projects fail not because they are badly built, but because they build too much, too soon. The MVP is the remedy: launch a reduced version fast, learn from real users, then extend what works.
What an MVP is not
Neither a mock-up nor a throwaway prototype: it is a live product, with accounts, payment and terms of use. A customer can sign up and pay. What is missing is everything that has not yet proved its worth.
Choosing the three features
Ask the question: “Which one would nobody pay without?” What's left after that sorting usually fits into three features. The rest — reports, options, fine-tuning — goes on the version 2 list, with no regrets.
What we keep for later
- Complex roles: at the start, two roles are enough
- “Just in case” integrations: we connect the three that are used every day
- Customisable settings: decide on the user’s behalf, adjust later
- The mobile app: a site that works well on a phone is enough to learn
Measure from day one
An MVP without measurement is just another hunch. Which pages are viewed, where people drop off, which features are used: those figures decide version 2, not opinions in a meeting.
And the price?
A well-scoped MVP is costed before it is built: with us, from 6,900.– for three features and three integrations, price fixed at the end of the scoping week. How it works →
Eramis →