Great question (and approach). I'm _kinda_ a non-hacker (started as a designer, now do a bit of front-end coding, etc).
The mutual respect thing (as aggieben says) is huge. The best way to approach this is to put in the line what you're going to do. How are you going to contibute AT LEAST your fair share in the early stages of the project. Not "When we're ready to talk to VCs, I'm the guy!" or "I'll talk to lawyers so you don't have to!", but "Here's the stuff I'm going to do EVERY DAY while you code."
Hopefully you have a good story to tell there. I've found that most people (who aren't hackers or designers) really DON'T, when it comes right down to it... But every business is different.
If you can't commit an equal share of the work (which is likely-- project management is not a fulltime job for a team of 2-3-- and it's honestly a burden for good hackers on teams of this size), then put something else on the line. Money is a good start.
If you don't have money and you don't have "buidling" skills, then I'm hard-pressed to understand how you could motivate "builders", other than the promise of "If you guys manage to build something great, I'll help make it successful".
The big problem is that it's hard to build something great (which is why a lot of people advocate for bring in biz ppl when and if you manage to pull that off).
The mutual respect thing (as aggieben says) is huge. The best way to approach this is to put in the line what you're going to do. How are you going to contibute AT LEAST your fair share in the early stages of the project. Not "When we're ready to talk to VCs, I'm the guy!" or "I'll talk to lawyers so you don't have to!", but "Here's the stuff I'm going to do EVERY DAY while you code."
Hopefully you have a good story to tell there. I've found that most people (who aren't hackers or designers) really DON'T, when it comes right down to it... But every business is different.
If you can't commit an equal share of the work (which is likely-- project management is not a fulltime job for a team of 2-3-- and it's honestly a burden for good hackers on teams of this size), then put something else on the line. Money is a good start.
If you don't have money and you don't have "buidling" skills, then I'm hard-pressed to understand how you could motivate "builders", other than the promise of "If you guys manage to build something great, I'll help make it successful".
The big problem is that it's hard to build something great (which is why a lot of people advocate for bring in biz ppl when and if you manage to pull that off).