4 ms·

Two Non-Tech Co-Founders...??

3 points by jaypreneur 15y ago

So, is this a bad idea? Some quick background: 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. 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.... 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. 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. 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) 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. 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. 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? 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. Any and all advice here is appreciated. Thanks!

Zaronian 15y ago
It's not the most popular move, but it can totally work in the right industry if you hustle. If you're trying to build Facebook, stop now. But if you're working on something sales heavy, B2B, with complicated legal/marketing hoops or in other words, more business-y needs than killer tech skill needs, then by all means make a run for it. I started my company with another biz guy and it worked out. We hustled like crazy, got sales before there was a product, gave design/coding our best shot and eventually got lucky enough to find a tech co-founder who could tell that we were legit. It's not the easiest road, but it'd doable if you are in the right space with the right person. GL
willpower101 15y ago
imho, if you are successful, you will reach a point where the needs of the business will eventually outpace a non-hacker's ability to consume and learn fast enough. Keep your friend on, but start looking for a coder as a full time co-founder. And don't be stingy with equity. Vest him in with graduated steps up to 33.3%. Is the easiest way to find someone of quality.
jaypreneur 15y ago
Thank you both for the fast replies. I appreciate it. I guess I have a decision to make. Ultimately, I'm trying to build something with some complex features. It seems it might, as willpower put it, eventually outpace his ability to consume and learn fast enough. It isn't business-y as much as it is an internet platform for a lot of users (social network aspects, but not a social network persay). Bleh. I'm not trying to be stingy with equity or anything by not wanting him on if he can't contribute, but the reason for me thinking of now changing my mind is the following: 1. He's a good friend. I want him to stay that way. If it's truly hard for him to keep up, I don't want to then get need someone better to jump on board later. Then what does he do? 2. Say he doesn't bother doing the technical side. I'm not sure where else he'd fit in terms of skills. He's not terribly artistic/design inclined. And while I don't doubt his business skills, I have immersed myself in business and marketing books, went to school for business, and am far more energetic/passionate as a salesmen. It is why if he did know the technical side, his personality and skills would complement my own. 3. Well... I feel like lists always need at least 3. Unfortunately, I started the numbering before realizing that I didn't have a third thing to say, ha. So, it's actually more just about team dynamics and what he'd even have to do than dealing with equity or something. Since, honestly, I've been doing everything but the back-end side just fine (not progressing quickly as I'd like due to my full time job, but I digress) on my own and expect to continue handling all of that. Oh man. I feel terrible. I was just so excited when I thought about the idea of us working together and finally have a partner who could perhaps handle the technical end. I neglected to fully realize how difficult a role I was putting in his hands as someone with no technical experience. One last thing. Since as of now it seems like I made the wrong decision and want to back out of it. Would you think this is a reasonable thing to say: I'm sorry to say this, but I was thinking more about the ability for either of us to learn to code the back-end and I think it'd be tough to get up to speed fast enough starting from scratch like this. And all our other strengths overlap, so it'd be hard to really split roles up, so I don't think it's a good idea to partner up on this. You seemed excited about starting something and why not keep with it, even it's not with this idea? Just brainstorm some ideas on your own, bounce them off me, and still go through with it. We can help each other along the way. I don't know. I'll say something like that to him. Let me know if it comes off terrible. Since I feel terrible.