Stanford Grad Sues Snapchat Claiming They Stole His ‘Million Dollar Idea’
betabeat.com
betabeat.com
Implementors: beware 'idea guys' with inflated senses of their own value, and who may not have the skills/staying-power for all the detail and drudge work ahead.
Unless Brown is a total fraudster, I'd guess there was some legitimate contribution but then early falling-out. (The complaint identifies a contentious phone call in mid-August 2011 as the turning point.)
Assignment agreements and founder-vesting schedules exist for these kinds of cases... but given the speed and informality of today's ventures, can arrive too late to save teams from ugly court disputes.
If (to your description) you consider the idea/logo 10% of the work then that's what it is worth.
Imho, the correct way to compensate not-really-founders is with a convertible note for the market value of their services times an appropriate risk multiple, or, if you can afford it, cash. (I have actually done this.)
If I was asking someone to do logo and design work for free (and just that) I'd offer something like 10% of net income with a end of life maximum at $35,000. That would allow them to potentially receive much more cash than the time they invested. It also establishes an upper bound to prevent someone for getting 1% of a billion dollar company because they wrote some html a few decades ago.
It's a risk-reward on both sides. Companies die off all the time. The vast majority of people that do work 'for a percentage' are going to get nothing.
With all that said, cash is always easier
It seems to me the skill-set you start with at the beginning of a startup will be significantly smaller and narrower than what you have at the end of a startup.
Without code you don't even have a pig to put lipstick on.
Adding:
I_HAVE_THE_CODEZ && AttractingUsers && RetainingUsers &&
AttractingTalent && DoingPayroll && GettingOfficeSpace &&
HavingARolodex && KnowingSalaries &&
KnowingProductManagement && KnowingSales &&
OhCrapWeveGotAConferenceComingUp && OurRockstarJustLeft &&
*everything*
[Note: I'm a "developer"... ]http://whartoniteseekscodemonkey.tumblr.com/
Always good for a laugh
Deleted comment
Being a good chef doesn't make you a good restaurant manager. Entirely different skillsets.
http://en.wikipedia.org/wiki/Howard_Schultz#Career
ETA: and how about McDonald's? [1]
"Believing that the McDonalds' formula was a ticket to success, Kroc suggested that they franchise their restaurants throughout the country. When they hesitated to take on this additional burden, Kroc volunteered to do it for them"
http://en.wikipedia.org/wiki/Ray_Kroc
Regardless of his business ethics, I think Kroc had a lot of experience by that time he ran across McDonalds and had some value to add. He wasn't just along for the ride.
I think if the idea is so amazing, convince someone to put up enough money to pay prevailing wages for the coding.
*Update: After a couple replies I went from "pretty sure" - to absolutely sure in the other direction - Based on the YC application it is safe to say Drew was a coder when he applied to YC, apologies and thanks for the corrections.
I could just as easily say, if your not an attorney...you have no business starting a company, whether tech or otherwise. Talk about opening a restaurant and not knowing how to cook, we are talking about forming a business without knowing how to structure it, registering IP, drafting your own agreements, or ensuring the business remains compliant with Federal, State and local laws.
However, the truth is you can hire general counsel or retain a law firm to handle the legal issues for your company, in much the same way a business owner can hire coders to code, or contract graphic designers to create a logo. Very rare is the individual who can have an idea, develop it, form the business, market the business/product, design the product packaging, develop the company website, sell the product, and fight on going litigation.
As I'm sure many people will point out, Drew already had a demo of the product [1]
You can start a tech company without knowing how to code, but Dropbox is not the example.
Other qualities non-technical co-founders can bring: money, social/sales/pitch skills, outsider opinions (from not having possible preconceived notions of generally accepted technical limitations), industry experience or experience in general.
Also, I hope it is clear I'm not saying technical co-founders can't bring any/all of the above.
But really it's nonsense.
There have been countless fantastically executed products that we've seen on Show HN, however many (if not most) were based upon either a too-common idea, or a poorly considered idea.
Without a good idea, the best work in the world is all for naught. Simply dismissing it is ridiculous when most of the people reading these posts sit spinning their wheels doing nothing because they can't think of a good idea to implement.
Counterexample: Steve Jobs.
Read the text in front of you, on your computer screen. Note the word "code":
>> I am starting to think, rightly so, that if you don't code ... you have no business starting a tech company.
>> Counterexample: Steve Jobs.
> Sure, he didn't know as much as Woz but still brought a lot to the table.
Wake up and smell the Cappuccino -- the topic is whether Jobs could code. Jobs could not code. End of story.
I speak as someone who knew Jobs personally, and who (along with everyone else) noticed that he couldn't code.
http://www.quora.com/How-high-were-Steve-Jobs-skills-in-codi...
Answer: "nonexistent."
http://bexhuff.com/2010/03/should-product-managers-know-how-...
"Steve didn't ever code. He wasn't an engineer and he didn't do any original design, but he was technical enough to alter and change and add to other designs." -Woz
You could do it with audio too. You could do it with GPS coords. You could do it with any data feed. Photo sharing is just huge right now.
This strikes me as different than what happened with Facebook.
I think what your really getting at is a verbal agreement is still enforceable. As is always the case in law the answer is: "maybe."
In order to be enforceable certain agreements/contracts MUST be in writing to be enforceable. It is a contract principle known as "Statute of Frauds", but despite the name has absolutely nothing to do with fraud. Some examples include contracts for the sale of real estate, contracts that will take more than a year to perform, and I think marriage agreements.
Although you are most likely correct, the verbal agreement might be enforceable here, but it is certain the Defendant's attorneys will argue the Statute of Frauds applies; therefore, since the agreement is not in writing it is unenforceable. To speculate on how a Judge would rule on this preliminary matter would be inappropriate without benefit of all the evidence obtained through discovery.
>but it is certain the Defendant's attorneys will argue the Statute of Frauds applies; therefore, since the agreement is not in writing it is unenforceable.
>To speculate on how a Judge would rule on this preliminary matter would be inappropriate without benefit of all the evidence obtained through discovery.
Presumably Mr. Brown can prove he had a claim on the SnapChat/Picaboo source code and make the same argument.
In US contract law, oral contracts are just as legal binding as the ones written down.
"helped with the UI. " hahaha. Did he code it?