If you are looking for a tech co-founder, I am going to tell you why you've had a hard time finding people like me; why we've probably said no to you, and what you can do to change the situation. As is always the case in business when you are stuck, you need to understand the situation from the other person's perspective in order to get what you want. Our perspective may not be right, and I am going to say some cold, harsh stuff, but I think you will feel enlightened if stand in our shoes for a minute. For starters, I'm assuming you aren't making an amateur mistake.
Why nerds don't go looking for "non-technical" co-foundersIt may or may not surprise you to discover that when nerds (or technical founders, or future-CTOs or whatever you want to call us) decide to start a company, we don't go looking for a "business" expert. Startup business just isn't that complex. It is time-consuming, but not complex. What is complex, usually, is the technology: you need to build something reliable, scalable, easy to use and awesome. Believe me when I say that's fucking hard. And you usually need to do that for way less money than a big company would spend. That's the kind of shit alpha-nerds live for. Rightly or wrongly, we don't go looking for someone with MBA to help us build a startup, especially if the people we meet with MBAs have less of clue about the market than we do (which is the case surprisingly often). I'm not saying there's nothing you can offer. What I'm saying is that if you do have something to offer, you need to prove it.
You might have nothing to offer
You might think you have a lot to offer, but nerds don't see it that way: we don't need non-nerds to found a company, start building product and get our first users. I know that the classic company founding team is two people: one "builder" and one "seller", presumably the nerd and the business expert. But if you look at some of the best tech companies, the "seller" was often actually a technical person who learned to sell and learned the basics of running a business. The classic tech company founding team is more accurately described as a super-nerd (the builder) and a regular nerd (the seller). But I know, you've still got something we don't: a brilliant idea! There's two problems with that: 1. we also have great ideas, and 2....
Your brilliant idea is worthless
I know it sounds cold when I say your idea is worthless, but look at the companies that have come out of the last few decades of startups. They have either been simple ideas (e-bay, amazon, etc), copycats (facebook), or the ideas have been technical (google, heroku, etc), and let's face it, only a nerd could come up with a technical idea. Moreover, unlike you, nerds know what ideas can and can't be built. Don't get me wrong, ideas are not easy, and they are great starting points, but startups don't win on ideas: they win on execution. The value of the idea is that if everyone is invested in it and understands it, the team can work together cohesively. There's no better way to sour your team's enthusiasm for a project than to have "them" build "your" idea, and there's no better way to turn off a potential tech co-founder than to say "I have a great idea for a company, I just need someone to build it" (yes, I've heard this. A lot.). Sometimes companies do get started this way, but it's a sure sign of an unhealthy company that will be lucky to continue to be functional. If you want to find a tech cofounder, develop a relationship with them first, and then build the idea with them. One other note about ideas is that they often change in the face of your first product release and its response from the market, so your super-brilliant idea is probably going to change anyway. (If that's news to you, read up on the lean startup methodology).
What can you do about it?
If you aren't friends with any nerds who can build a business with you, you are not out of luck. Some common suggestions I've read are:
- Learn to code yourself. This might work if you are young and ambitious. It will certainly have the benefit of helping you speak the language, understanding technical problems, meeting other nerds and so on. I would certainly applaud the effort of learning to code, but let's face facts: you can't become your own technical cofounder unless your technical needs are very simple or you are willing to put serious time into it. There's more to being a CTO than "coding" and you are unlikely to get a deep understanding for technology by taking a crash course in Ruby.
- Outsource for your prototype. This actually works sometimes, but it will cost you and it's not as easy as it sounds. Outsourcing (whether on- or off- shore) requires that someone on your team has a clue about what's going on technically. You really need to be in touch with the technical team every day. Make sure you understand their technologies and, more importantly, their methodologies. If that sounds excessive, talk to anybody who's tried outsourcing. Keep in mind that even if you go with this strategy, you'll usually need to find a CTO and have them prove themselves before anyone will give you significant funding, which means you are going to need a plan to pay for this before you even approach a VC.
- Build your connections. Trust me: nerds will look at your linkedin profile. If we don't see hundreds of contacts (including at least as many VCs, angles, and potential customers as we have) we won't keep talking to you. Why should we?
- Accomplish something. What better way to prove to nerds that you are worth working with than to have done something successful in the past? If your resume is full of school and jobs rather than accomplishments, then you need to work on your resume. Try joining an early-stage startup, or helping a startup raise money. If you can do that, you will have awesome nerds knocking down your door. If you can't do that, at least try writing a successful blog, or running a meetup.