There are startups which I think can live without techie co-founders. It is my proposition that if your idea does not solve a core engineering problem then the need to bring in a technical co-founder diminishes. You can get away with hiring the talent as employees rather than as co-founders. Sure, you may need some help in putting together a demo/mockup, but that can be outsourced or done on contract.<p>Here are a few examples of startups that I think don't require technical co-founders because they are not that difficult to build (that is different from saying they don't need any technical help). AirBnB, CardPool, Fanvibe.
The danger of NOT bringing on a technical co-founder is that you're then dealing with a different type of developer/tech person. This technical person is generally the type that gets (or could get) paid good money.<p>So as Travis mentions in his comment, if you don't have lots of cash on hand, you could run into problems. There is really no shortage of jobs available to developers, and chances are many jobs out there will pay much better than what you can afford to pay at your startup. Unless you find the perfect person who doesn't mind making less than he/she probably could and is still 100% dedicated, you'll probably have a high turnover rate.<p>In contrast, you can generally assume that a co-founder is going to give you 100% all the time as they theoretically have a lot of skin in the game.<p>In many startups, you probably don't <i>need</i> a technical co-founder, but you probably <i>should</i> have one anyway.
Seems to me, though, that if you're not bringing a technical co-founder, you'd better be bringing cash to the table. A technical co founder can exchange time for code. Without them, you need some other medium, which is invariably cash (or connections to cash).