I'm basically in the same situation. Here is the solution I found that is working for me. I'm assuming you have a clear vision for your product/service. You're going to have to take the lead on owning the product, there's no getting around this. There's almost no chance you're going to find a co-founder that's going to handle the product/development, etc while you focus on marketing. I've tried and each time has ende…
I will have to disagree on this, this advice is only good if your sole purpose is to make a quick buck. If you want to start a long term solid business than I suggest you treat people like humans and not like cheap interchangeable pieces as this post suggests. Think of it this way, since you are not the one developing the application how much will you know about all its inner workings? When you will have customers an…
Here's the thing: Building anything ends up being a very iterative process. From my personal experience, by the time one moves from the prototype/beta phase upwards of 90% of the original code/design base is thrown away, redone, etc. Since what I'm really looking for here is the first-cut that allows for the validation of the idea and the on-boarding of the first few (hundred-)thousand users, I think there could be some advantages to a little shorter-term thinking; if-and-only-if that means I'm able to deliver that first cut to market sooner than if I were to focus on the stability of the team upfront.
Don't get me wrong, I'm still wavering on my opinion of this (hence this entire thread). But I am really enjoying / appreciating the various methodologies.