Here's my current strategy as a 'business guy' trying to get the attention of good hackers. Note: it's not working.<p>- Understand the languages we'll be using and build as much I can. The ugly truth is that it's very slow going.<p>- Distinguish myself from other 'business guys.' I ran BD for a design and launch firm that worked with successful, high exit startups. We also ran a major demo conference. Doesn't have much of an effect- maybe my story is a dime a dozen in this town.<p>- Genuine respect for engineering. I truly don't want to abstract away engineers like so many companies. I've seen a major startup with 100% technical roots drive off a cliff because they focused on "UX," marketing, partnerships, etc., realize the product they were launching was buggy and unlikable, scramble to rewrite everything and unsurprisingly fail. I believe it's critically strategic your team build consumer products they're actually using. Don't steamroll your engineers. Duh. Elevate them so they are the heart of your company? Takes commitment but will pay off- especially through your B and C rounds.<p>- Etc. Basically, everything I can to make sure the DNA of our partnership is centered on raw technical initiative and isn't simply a means to an end.<p>There's a stereotype of the dominant businessperson and workhorse engineer. And it does happen- I've met quite a few teams with this dynamic. Personally, I don't want it. The smartest guy in the room rarely exhibits the submissive personality and I'm looking for an equal.<p>On a tangent, I want founders and scrappy engineer/entrepreneurs to understand how to treat sales/BD people. I have a string of experiences getting excited about working for a young company before the founders try and get me to do the work on straight commission. The insult doesn't bug me, but I walk because it shows me you're not ready to run a relationship business.