The most valuable part of this article is in footnote #2:<p>"This could make sense if Mr. Business Guy had a MUCH better understanding of the market needs, the product capabilities, and the process required to build a product that evolved over time. Developing this skillset turns Mr. Business Guy into Mr. Product Guy, and makes him a much more attractive cofounder."
Oftentimes "technical co-founder" is a euphemism for an employee willing to work for deferred compensation. In my experience, it says that a "business guy" has an idea but no money, which causes me to doubt the "business" part, or at least infer that the "business" part is in selling the idea to people who will work for free.<p>Then again, I don't trust founders who won't invest their own money in their idea(s).
Tyler makes some great points. I remembering in this video (<a href="http://ycombinator.posterous.com/y-combinators-graham-doesnt-see-bubble-in-tec" rel="nofollow">http://ycombinator.posterous.com/y-combinators-graham-doesnt...</a>) Paul talks about the co-founders and how they really look at the relationship vs the idea...
What should a technical person look for in a business guy? Connections? What else? I've worked with "idea guys" who don't seem to bring much to table and that has (probably unfairly) biased my perception on the value of an idea. I'd love to know what other skills to look at from the business side.
What do you technical people think of business/idea guys that teach themselves how to code and begin working on their ideas themselves? Do you find it makes the business guy easier to work and communicate with?