> what should my MVP contain so as to provide value and test market fit? This is a question you should be asking your prospective users/customers. Ask them wh

> what should my MVP contain so as to provide value and test market fit? This is a question you should be asking your prospective users/customers. Ask them what they need. If you're charging money, ask them what they'd pay for. If not, ask them what they'd need to see before using your OSS software. I like to frame it as "if I had a product that did this for you right now, would you pull out your credit card and sign up for it today?" Take what they tell you, look for commonalities and trends, and then use that to determine what should be in your MVP. Build the MVP, go back to the people who would pay for it, and get them to pay for it. That's generally how you build an MVP (IMO). Though its much harder to do than it sounds.