Experienced tech startup founder (since 2013) and software developer (since the 1900s), helping non-technical founders test the market by helping build an MVP, specialising in two-sided markets. --- MVP = Minimum Viable Product, but most people screw up the *Minimum* part. The "M" means: as little as possible while still being useful. It’s not "everything your customer might want" or "a polished product with all features." It’s the cheapest, fastest thing you can build to validate a core assumption. Examples: - Bad MVP: A full-featured app with user accounts, payment, onboarding, notifications, etc. - Good MVP: A no-code landing page with a "Buy" button that just collects emails to test interest. Why focus on M? Because you're trying to learn fast. The more you build, the more you waste if your core idea is wrong. Strip it back until it feels uncomfortable — then go even leaner. --- MVP “M” Checklist: 1. Does it solve *one* core problem? → Not two, not five. One. 2. Can you build it in under 2 weeks? → If it’s taking months, it’s probably not minimum. 3. Can you fake or shortcut some of it? → Use no-code, manual steps, or duct tape behind the scenes. 4. Does it skip “nice-to-haves”? → No login system, no design polish, no notifications—unless absolutely core. 5. Does it let you test your riskiest assumption? → Usually: “Do people even want this?” 6. Can you throw it away without crying? → Emotionally and financially low-stakes = good MVP.

💻 Website

https://sharetribe.jayenashar.org/