4 Reasons Why MVP’s are a good idea for a startup

Are MVPs (i.e., creating Minimally Viable Products) a good idea for startup companies? Or for existing companies that want to create a new product or service?

Yes, absolutely! Why? I want to answer this “Why” question in this post. This idea is important and appropriate before I get into the short series of posts I mentioned in a previous post: Can non-geek startups get suitable software solutions.

First, what is an MVP? MVP = Minimally Viable Product

An MVP is the idea that you can create and release or sell a very, very small product with very few required features. This small product makes it faster and easier to get the product into the market, and to get proof of whether the concept in the product actually works or not…i.e., are customers willing to pay for it or not.

This idea applies not only to creating a new product from scratch, but also applies to adding new features to an existing product, as well as companies that provide services as opposed to products.

Now the question is, why should you do this? I see 3 reasons why:

  1. Cheaper – It takes less money, as well as effort and mental energy, to create a much smaller product
  2. Quicker – It takes less time to create the much smaller product.
  3. Last Risk – You risk less money, which then puts less money
Given those 3 reasons why, you can then realize additional benefits from executing an MVP:
  1. Faster to market – You can create the product and get it into customers hands sooner. This is often important when customers tastes and preferences change very quickly these days, and your competition is often reacting much quicker to your same customers changing preferences.
  2. Make money sooner – You are able to start earning money soon because of the two benefits above.
  3. Quick proof of the concept – You are able to learn if you’re product is any where close to hitting the mark as a result of the “Faster to market” and “Make money sooner” ideas above. The idea is that if you make any money at all, you can then figure out that you might actually have something good.

To execute an MVP is much, much easier and cheaper than creating a full blown product that has so many features that you “think” are necessary for the first version. But keep in mind the problem with creating an MVP is the tough decisions you have to make to strip away the fluff and figure out what really is minimally viable and a must-have to release the product.

We apply this idea to many projects in custom software solutions we create for our customers. Those projects are often situations where the customer wants to start a new line of business in an existing, well established company. Additionally, they are also often new companies or individuals starting a new company that wants to create a new product or service.

The solutions we create end up being small custom desktop applications or a new custom web application. Often enough, we end up continuing to modify and extend the solution over time, or the customer grows sufficiently that they can take over maintenance and improvement of the product in-house.