2. Business requirements are a two-way street. Many non-technical folks have a hard time sufficiently describing their business requirements, and even more simply don't have the skill and patience required to work with a technical resource to turn business requirements into functional and technical requirements. You can't blame a technical resource for this shortcoming.
3. In today's market, good developers who are eager to make money generally have no shortage of employment and contracting opportunities. In certain geographic areas of the United States, experienced developers can easily make six figures annually. Outside of the United States, it's not difficult to find freelance developers earning far in excess of the average local wage. Unless you have a personal relationship with a developer and a co-founder relationship grows organically out of that relationship, it's naive to believe that a developer willing to work for you on an equity-only basis is going to be the cream of the crop.
In short, there's a reason there are so many non-technical founders running around like chickens with their heads cut off looking for a technical co-founder: very few good developers want to take your 1 am call so that they can do all the work for free while you sleep.
I was very lucky that the contractor I am working with is one of the best developers I have ever worked with. He really feels like part of the company, and knows the product inside out. Of course the weakness is that if I can't afford to pay him any more, there's nothing I can do with the site if I need to fix something etc.
But in the end, yes, you have to deal with the dillema: hire or take someone on board, share the responsability and the earnings.
The big reason to not have a cofounder is because 100% of a two million dollar business can be life changing. Half of that is more like a feather in your cap.
Paul Graham and VC firms are looking for billion dollar businesses. 5% of such a company shared here and there doesn't matter so much. But those sorts of businesses present shitty expected value to a founder. You want full ownership of a higher probability bet.
My opinion is that it depends on what your startup's value proposition is.
If you're building Groupon, the example's Sampleboard, or any startup where the development work is standard, I'd say the technical cofounder isn't essential.
He/she can prevent contractors from pulling a fast one, but you're being too biased - most contractors will build to specs, probably not as polished or complete, but more than enough for an MVP.
OTOH, if your startup's value proposition depends on leveraging new technologies, or a complex stack, or delivering something where tech is critical, you need the technical founder/cofounder.
I've seen a Groupon clone founded by a lawyer of all things :) and the outsourcing work was shoddy but the first technical hires patched it up.
Well, Thank God the ideas man is getting his rest, I guess.
Don't fall for this. Really, get yourself a technical co-founder. Amaze him. You can call him in the middle of the night, telling your new idea. Next day, he will already had done dissecting it and have a technical spec ready. Or any other crazy stuff that you want and he will say simply "No". You have no idea how useful is a "No" in a start-up. And so on, and so on...you get the picture.
PS. I am using a neutral "he" here.