{"id":687,"date":"2019-08-12T16:00:49","date_gmt":"2019-08-12T10:30:49","guid":{"rendered":"https:\/\/www.hestabit.com\/blog\/?p=687"},"modified":"2021-10-14T13:21:46","modified_gmt":"2021-10-14T07:51:46","slug":"mvp-is-great-but-what-about-minimum-viable-segment","status":"publish","type":"post","link":"https:\/\/www.hestabit.com\/blog\/mvp-is-great-but-what-about-minimum-viable-segment\/","title":{"rendered":"MVP Is Great, But What About Minimum Viable Segment?"},"content":{"rendered":"

To ideate and build a product that can penetrate a billion-dollar market and enthuse millions of customers is a glorious feeling for any entrepreneur, and a great goal indeed.\u00a0<\/span>For such goals, your minimum viable product (MVP) and the selection of your minimum viable segment (MVS) should be fundamentally sound. <\/span><\/p>\n

So what are those steps<\/h2>\n

Building a Minimum Viable Product (MVP) is certainly one of them. It\u2019s a smart way to validate your business model, by launching a version of the product having minimum features, without compromising on its viability. <\/span><\/p>\n

But to make your MVP even more effective, shouldn\u2019t there be a Minimum Viable Segment (MVS), say, an initial customer base? It can further streamline your development<\/a> process and get you more traction in the initial days. <\/span><\/p>\n

Where do Startups go wrong?\u00a0<\/strong><\/h2>\n

Startups at times are unable to look beyond their MVP, maybe because they focus more on the product, which is why their search for a <\/span>\u2018Product-Market Fit\u2019<\/span><\/i> doesn\u2019t end. <\/span><\/p>\n

They go hammer and tongs to dominate the market. They paint the market with broader strokes and fail to identify their Minimum Viable Segment. Many would argue that it\u2019s a natural progression to not look for a specific market segment when launching a product and target customers<\/a> aggressively instead. This is how you can serve a multitude of market segments and customers\u2019 expectations. Right? <\/span><\/p>\n

This may seem to be enterprising in the beginning, but gradually it starts pulling the development team in different directions, leading to much chaos.<\/span><\/p>\n

The hardest part is to decide what not to do or which feature not to implement. – Steve Jobs<\/i><\/p><\/blockquote>\n

It applies to customers and market segments as well. If you think about it, every product is built keeping certain customer personas in mind. These personas should serve as the template for your Minimum Viable Segment. Though you mustn\u2019t confuse this segment with early adopters. You can learn more about customer personas here<\/a>.\u00a0<\/span><\/p>\n

It comprises of customers who are most likely to buy your product, for the price you set and in the way you imagined\/designed. It\u2019s a fragment of your target market, small enough to get covered quickly and yet generate decent revenue to make the business model sustainable. <\/span><\/p>\n

Pandering to MVS is like playing the game of darts from close quarters \u2014 the chances of hitting the bullseye become more realistic. <\/strong><\/h3>\n

So how big should that initial segment be? Well, it\u2019s a million-dollar question. If we take a SaaS product into consideration, 1000 customers is a decent number to start with. For instance, if a product is targeting restaurants, then the minimum viable segment can be 1000 Italian restaurants in a particular region. This can give you an insight into customers who have similar tastes and expectations, therefore propelling your competitive advantage. <\/span><\/p>\n

It\u2019s about pandering to the similar needs and pain points<\/h2>\n

To simply put it, in an ideal MVS, a set of customers will share similar needs and pain points. So the idea is to trace such customers and gradually build a small segment for your MVP. <\/span><\/p>\n

Your product is not the features you build, but the \u2018Needs\u2019 it caters too. It\u2019s an important realization, as customers don\u2019t think in terms of features, but in terms of pain points. \u00a0<\/span><\/p>\n

When there is a pool of consumers who are looking for similar solutions, referencing one another becomes a lot easier. People are able to build a healthy community where self-learning is encouraged. Such a community can save you a lot of time and money, as you won\u2019t need to stretch your support team, at least during the initial days of your product. <\/span><\/p>\n

Now just imagine a pool of consumers who are facing different issues with the product and you are providing solutions accordingly. Do you think people will be able to reference one another that easily? <\/span><\/p>\n

Don\u2019t confuse MVS with Vertical Market<\/h2>\n

Choosing a Vertical, say Financial Services as your initial segment isn\u2019t the smartest thing to do, as it\u2019s too broad. It\u2019s important to break down that vertical further, say into Banking, Brokerage, Insurance, etc., to discover a set of potential customers having the same requirements. <\/span><\/p>\n

MVS requires iterations, just like MVP<\/h2>\n

You should remain in the \u2018Calibration Mode\u2019 while figuring out your MVS. If you have zeroed in on a segment, do you think all customers in that segment have the same requirements? You need to keep iterating until you get the answer. Interviewing customers<\/a> will help you with this. So the bottom line is, you need to keep refining your MVS. \u00a0<\/span><\/p>\n

There is more to it<\/h2>\n

Some factors which you may overlook while zeroing in your MVS: <\/span><\/p>\n