For many (most?) startups, for many (most?) MVPs, in many (most?) domains -- yes, with a million caveats -- the "non-technical cofounder" can likely figure it o

For many (most?) startups, for many (most?) MVPs, in many (most?) domains -- yes, with a million caveats -- the "non-technical cofounder" can likely figure it out what's needed to hack together a simple product, get a handful of real users using it, and then go from there. In my case, all I had done was make HTML/CSS websites with a bit of PHP. But I didn't let "I need a technical cofounder" and "I'm just the business guy" stop me from figuring out how to build v0.1 myself and get it out. I had never touched a server before. I had never built a web app with a MVC stack before. I had zero experience with command-line prior. I didn't have any formal technical training. But I just started coding and built it myself, and from there was able to attract a great technical cofounder and early team. And 10 years later, we sold it for $100M. I'm not saying this to brag. I'm proud that "I figured it out" with duct tape but I realize that I had the good luck that it all worked out. But I worry that other guys like I was are sitting there thinking 'Shit, everyone says I need a technical cofounder'. Well, maybe not. Go try to build it yourself. Especially in the age of co-pilot and decades of StackOverflow - for most apps, you can figure it out. No one take this the wrong way. I'm just trying to potentially inspire some bright person out there to try it themselves, and building the first simple version yourself might be the missing step in attracting a REAL technical person or at least validate your hypothesis.