Yes, I agree that is the point of building a product. The one catch there, is when you have a client paying for development there are compromises and time to m

Yes, I agree that is the point of building a product. The one catch there, is when you have a client paying for development there are compromises and time to market considerations to which can affect having a product available to the wider audience. In our case, we were working both with the client we were building the product for initially and also we had prospected a number of other clients and were trying to get an MVP out that solved the problem and then iterate. However, that didn't work for the primary client and a number of things he wanted in his MVP were not good general product market fit, which made it harder for us to manage the timing & expectations. So while it was overall less expensive initially out of my pocket, the timeline was dictated/dominated by the client and special features they needed which took away from making a generic product that we could've had in the hands of others faster. Which in the end meant we had more product/development churn then if we had gotten the more generic 80% MVP out for a wider audience. That's what I meant by we could've focused on general product first.