mikealle233
That one man rose to power in government and obtained degrees, despite poor math and reading skills, doesn't surprise me much less outrage me.
Put another way:
Odds of getting sued: 1%
Max downside if he gets sued: What? 50k before he declares bankruptcy?
Ok, so risk adjusted cost of the "just fucking sue me" approach: $500.
$500 vs. $350,000...hmmm...tough choice.
You might say, well, it's not as though it's one or the other. You can request reasonable changes and not jeopardize the 350k.
Well, ya, I suppose so, but what are the odds that any request you make will kill the deal? If it's also 1%, then the expected cost is $3500.
That's still more expensive than the "just fucking sue me" approach. In reality, the odds of killing a deal over contract disagreements are much higher than getting sued.
Google has serious strategic problems going forward, and it seems the best Larry can do is make 25% of employee bonuses tied to chasing Facebook and ignoring investor questions.
Making a rags to riches die hard engineer CEO of a multi-billion dollar corporation may seem like a cute idea, but this won't end well.
I just find it peculiar how this entire HN community seems in love with the idea of giving away equity in exchange for money and advice, to hopefully increase the odds that your programming work will eventually turn into a big payday...but you seem completely standoffish about the idea of receiving equity in exchange for working on a product that already has proven traction, which would sky rocket the odds of your programming work eventually turning into a big payday.
In other words, you'd get the same increased odds of success that venture capital brings, but you'd be receiving equity instead of giving it away.
In one case, you're bitter about the prospect the person who increases your odds not putting in as many hours as you; in the other case, you gladly accept the prospect of a person increasing your odds but not putting in as many hours as you.
My question is why you're so fixated on hours of work, and instead aren't just look at it in terms of business opportunity where you can make a ton of money? Hours of work seems to be a bad, arbitrary metric to obsess over.
Groupon isn't successful because of its programming prowess. It's successful because of its sales, marketing and business development prowess. Groupon is a great example of a startup that's not that complicated in the technical department (or at least it wasn't when it started...now it's large enough to where it's justifiable to bring in programming all stars to make sure scalability, maintainability, etc. are in order).
So, as to why a developer should work for a proven MVP rather than building his own clone, the reason is simple...why is it more attractive to be an equity technical founder of Groupon vs. starting your own Groupon, if Groupon approaches you after it's already gained traction?
Absolutely, most startups fail because they build something that people don't want. That doesn't mean things like scalability and maintainability don't matter. It means you're putting the cart before the horse if you're worrying about those things before you even have a product that people want.
All you're really bringing to the table is the first 3 steps, and asking your technical co-founder(s) to handle the next 617 or so. It's better than just a "big idea", but not by as much as you're thinking.
Aren't your same gripes just as valid against venture capitalists? I mean, all they're giving you is money, and they're trying to take a huge chunk of equity while you have to worry about the next 617 steps?
Not necessarily. Offshore outsourcing of programming is quite cheap. The question is whether your MVP is so complex it warrants a $100/hour local programmer to handle that complexity. In many cases, it's not complex enough to warrant it, and paying $100/hour to a developer is inconsistent with building a MVP, because you're hiring a bells and whistles developer better suited to a large corporation with millions in profit at stake if the developer screws up. But, sure, if you're building something complex, you're shooting yourself in the foot by cheaply outsourcing.
"If you're willing to throw out the MVP code and have the new cofounder rewrite it, that might be something you could convince a developer to join up for -- but be prepared to "lose" the money for the initial MVP development."
That's exactly what I'm proposing. Who cares if you "lose" the money for the MVP development? If the MVP has shown traction, you haven't "lost" the money. You've paid cheaply for a traction proving MVP. That is money well spent, and now it's time to move onto the next level.
In any event, the idea that a developer would turn down an opportunity to be a founding equity member of a startup, which has a product that's already proven traction, because the MVP contained messy code is absurd. I'm not saying some developers wouldn't think that...I'm saying such developers are irrational.
"...but if you were looking for a partnership, I'd want to know what you'd spend your time doing."
Your attitude puzzles me. You have two hypothetical choices, if you were offered such a partnership.
1) Say no and continue to build software with a 90% chance of failure.
2) Say yes and build software with a 90% chance of success.
Even if the non technical cofounders sit on their asses and do absolutely nothing while you code all day, you'd be sitting on 33% equity in an already successful startup, when they took all the cash risk up front to prove the thing works. All you've got to do now is code and build on existing success. And you think that's an offer that you should scoff at?
In reality, the non technical cofounders wouldn't sit around and do nothing. This would be a group of people who've already proven they can go from zero to traction proving MVP on their own, and surely they'd continue to work in non-technical ways to make the product a success. I don't understand why you'd be so skeptical about what they'd do with their time, unless you think their success was dumb luck.
This won't work for immensely complex ideas, and it won't produce award-winning code, but it'll be good enough to create a minimum viable product and see if it has traction.
If it does get any traction, THEN they can worry about finding a programming partner, and the question of what they bring to the team will be clear -- a business that has already shown traction.