The importance of MVP

As we've told in a previous post, user feedback is one of the most important aspect of successful SaaS startups. Since it's so important, we should start getting users feedbacks as soon as possible, right?
That's when the MVP - Minimum Viable Product - concept gets in place.

MVP does NOT mean to quickly put a low quality product for users to test it. Your MVP should be strong enough to offer value with high quality, but simple enough to release fast and start iterating over it, based on feedbacks.

Take a look at the first released version of bkper:

What helped us quick release the first version:

- Simple authentication and authorization
- No fancy style, just framework defaults
- Handmade logo
- No mobile, add-ons or other clients
- No charts, geolocation or any other cool feature, just the very basic ones
- No language support.

What helped us create a strong base to evolve:

- Build on top of a big PaaS/IaaS provider, in our case, Google Cloud Platform
- Functional and Unit automated tests coverage throughout the entire product
- Clear separation of business and client responsibility through REST API
- Apply security standards and protocols like OAuth2

The same screen from above as it is nowadays:

As we continue to grow, we deliver features in a MVP manner. All add-ons, libraries, mobile clients and any other features are rapidly released and further evolved based on feedbacks. Sometimes we even decide to kill some feature or module after first iterations.

This way we ensure that we always drive the most valuable features to our users, with high quality, as fast as possible, with a lower cost.