1) I think you're too worried about the dev not being a "mobile dev." There really aren't any developers with 5 yrs experience on the currently dominant mobile

1) I think you're too worried about the dev not being a "mobile dev." There really aren't any developers with 5 yrs experience on the currently dominant mobile platforms b/c they haven't been around that long. Good developers can pick up new technologies at a reasonably quick speed. A web developer has some server/client experience. Good enough. 2) IMO you don't need to worry that the developer is more interested in a paying gig. Being treated as a valuable professional who is compensated for their time is not a bad angle to keep the dev's head in the game. Act grateful that he's helping you do something you consider important and then pay him. That can still go a long way. 3) I'm biased (because I'm a developer not a V.C.), but I'd say "what you can do beforehand" is mainly just getting the product as far along as possible. It sounds like you've already taken the leap of faith so just try to get to v1.0 quickly. Building a product and then selling it is not as unreasonable as some market pre-validation advocates say it is. 4) If you really have taken the leap of faith, act like it. You are going to build this product and sell it. You're just going to have some meetings to see if the V.C.'s want to come along for the ride. 5) To paraphrase Sh*t My Dad Says: "Son, let women figure out why they won't date you, don't do it for them." Applies here as well. In a less coarse example, when I was 25 and working at my first startup I was frantically trying to get all our ducks in a row before some big meetings with V.C.'s and potential enterprise clients. The CEO told me, "Don't worry about it. At some point you have to stand up and say what you have to say and let them challenge you on it. That's where we're at."