"while doing little to no work yourself. "
Why that assumption?
Added:
"I can most likely figure out whatever it is that you do with a bit of time and elbow grease."
Have you? Or are you just assuming that as well?
Why that assumption?
Added:
"I can most likely figure out whatever it is that you do with a bit of time and elbow grease."
Have you? Or are you just assuming that as well?
About the second one, I was actually paraphrasing something I heard Max Levchin state at one of his talks years ago. Not sure how much it's worth, given his partnership with Thiel.
Even though we really shouldn't feel this way, a lot of us developer sorts wrestle with the idea that we're the only ones ever really working, specifically in the pure development phase of a project.
Granted, I'm sure everybody feels that way at least once during a given venture. I've forced myself to stop thinking that way, but it seems a fairly human thing to think.
If the technical person does not execute on the MVP, the idea guy mostly out only lost time-to-market. On the other hand, if the technical person delivers, he/she is now "all-in" before the idea person typically contributes meaningful execution-value towards the business.
Its probably most fair to view the first "execution" contributors (technical team building MVP) as the first investors in the business, and therefore should be recognized with more favorable terms (equity distribution). If the idea person can create actual execution value in tandem with the MVP, then an initial 50/50 split is fair.