So, is this a bad idea?<p>Some quick background:<p>I came up with an idea. I researched potential competitors, talked to potential customers, and overall got good feedback. So, I went along working out features (as well as refining down to MVP) and started designed a pretty detailed wireframe. I consider myself a business/design co-founder. I feel I have a good eye for design and user experience. I'm learning to code the front-end now. Unfortunately, those skills can only get me so far.<p>So, I decided to ask a friend of mine (who is also non-technical) if he wants to do this with me. The idea I had in my head is the following....<p>I could outsource, but then I have no one to update/maintain anything. Though I guess at that point, I would have an MVP and (hopefully) customers and could get a tech co-founder on board.<p>I could do it myself. But then I spread myself thin everywhere, take longer to accomplish everything, and likely can't really do a professional level job. The outcome is the same as above. I get MVP out there and (hopefully) customers and could get a tech co-founder on board.<p>Then there is hustle hard to try to get a tech co-founder without an MVP. Difficult. (I have to try though... so perhaps I should have tried that first? I'm not just trying to be the "idea guy" or anything. I know I need to bring more value to the table than that)<p>Ultimately, all the above issues show one glaring weakness. How do I even know this tech co-founder won't be a huge problem? From what I understand and believe, your relationship with a co-founder is just as important as their skill sets. You need to get along, share a vision, have trust... it's not easy to find this person. If you can find them at all.<p>Fortunately, my friend and I do have a good relationship, work well together, trust one another, and so on. If he was technical, I'd have IMMEDIATELY went to him. But unfortunately who doesn't know any coding, but he's willing to learn to become technical co-founder. An additional plus is we're both in the a position to go at this full time.<p>However, what can I expect here? Is it a bad idea? He's a smart guy and learns quickly. But I know there's a lot to learn... there are those with years of experience out there. So, is it setting myself up for failure/problems?<p>I am just second guessing myself here. While I'd feel bad to "take it back" because we're good friends. I would rather do that now, before we get started working on it, then down the road when we realize it was a mistake. To be honest, the reason I am second guessing myself is because maybe I'm underestimating my ability to find a technical co-founder? Or even underestimating my ability to "do it all" I suppose.<p>Any and all advice here is appreciated. Thanks!