Cautionary tale: A friend and his co-founders developed a product and then sold it (and their company) to a large company with the agreement that they would get a percent of sales of "their" product. Their product (call it "Product A") sold for something like $20K a license. What the acquiring company did was to bundle it with their own $20K product ("Product B") only now they charged $40K for Product B and gave away Product A (when purchased with Product B) so they wouldn't have to pay the product creators their cut.<p>Happy ending: My friend and his colleagues eventually got their money in arbitration.
Your wording is very vague but I'm going to assume when you say 'your firm wants your home-project', you mean they want to buy it, rather than they are demanding you hand it over under some kind of IP rights squabble.<p>Do you want cash and/or stock for the sale? Or, do you want a %age of future royalties of the sale (that might tricky if they want to incorporate it into a bigger product). (Or a combination of both cash/stock and %age)<p>Do you want to remain involved in the project, or even moved into the team that would continue to work on this? If so you should get that contractually agreed as part of the sale.<p>How much do you feel the project is work, and separately, how much has the company indicated they are willing to spend? If it is more than, say, $20k I would go and see a lawyer to draw up the contractual issues. Less then $20k, you can probably do this on your own given the amount is small. You could also incentivize the lawyer to negotiate on your behalf in return for a %age of the sale - particularly worthwhile if you are not a good negotiator. It's also a 3rd party, so none of the mind games that could be used against you by negotiating with your own boss/boss's boss/etc comes into play.<p>You might be wise to incorporate the project into a company, transfer the IP to the company and then sell them the company.<p>You should also review your code to make sure you are not using any OS code that has an incompatible license with selling the code.<p>Perhaps you could provide more answers and people could advise you better.
Depends on how you view the sale. If you are fully transferring rights I would just sell it to them, with the price set at 100 dollars an hour for however many hours you estimate you worked on it. If you plan on retaining rights I would ask for 20-30% of that first figure plus 10-20% of revenue generated(with some stipulation on what that number is if they give it away as a value add).
I think the question here is, how big is the company? Depending on how small or large the company is depends on everything.<p>If they are a small company, they probably would not be able to afford a large cash deal, and would probably try to sell you with royalties rather than a big cash payment.<p>A medium sized company, a nice chunk of cash and small royalties if any.<p>And a large company - it's an all cash deal.<p>I would go for a lump sum cash payment if you can take it, and if you can add royalties on top, more power to you. But again like previously stated, that can be a fishy area.<p>You are in an employee relationship, so you will never be able to audit books, or verify things that a normal founder would be able to easy reference check.<p>Get as much UPFRONT cash as you can. Consider royalties as a "bonus".<p>My 2 cents.
The most important piece: if you did it once, you can do it again. Remember this.<p>Now the details:<p><a href="http://en.wikipedia.org/wiki/Work_for_hire" rel="nofollow">http://en.wikipedia.org/wiki/Work_for_hire</a><p>You should read your contract with them. As a rule of thumb, if you are in an "innovative" job, that is you were hired to invent, than they might have a claim.
Nevertheless, if you want to keep the job you will have to settle, but they don't know it? or do they? I don't know the details... Can the project run at all w/o you? Are you essential to maintaining it? You can negotiate anything. Cash, future share of an exit/profits etc. Look at their demand as a starting point of the negotiations.
I'm not expert, but there's a couple of things you could investigate:<p>Licensing: You could license it and then get a flat fee per license sold. This gets around the problem that someone mentioned about getting a % of revenue and then having the company bundle the product. Also, then you should sign you to a non-compete, which they should pay you for, so that you don't undercut them.<p>Sell outright: Figure out how much the software is worth, come up with a revenue model and then sell it for 3x sales, or something like that.
i was in the exact same situation in a few cases, even not too long ago, just on the other side. i was the ceo.<p>we are in webapp development, so basically everything related to that belongs to the company.<p>now, one of the guys did a really cool tool in his freetime and showed it to us a couple of weeks later.<p>my first question to him was: how much do you want for it? even though this really had no connection to any of the things we did at the time, not even the plans we had for the future.<p>still, we agreed on the price and he got paid out immediately.<p>exactly one month later a client came with somewhat similar needs for his website, so we sold it without any update.<p>since the the sales price was quite above the aquisition cost, and we had to do no work on it, the guy got a compensation later to become 50/50 with the company in that subject.<p>me buying stuff from co-workers happened many times, i think it's great when a company has an offer or an opportunity for you, other than your regular job.<p>it might not change a thing during workdays, though. :)<p>anyway, i suggest you go for it, try to get best offer you can get, but if you name the price make sure you don't look like a fool by settling in a fraction of your first offer, so price it right!<p>we'll try to help you if you ask :)
Presumably you have, in place, an employment agreement and an Intellectual Property agreement. You should review them and, if necessary, discuss the situation with a lawyer who is experienced in this sort of thing. You also need to know what your employer's intention is. If your "home-made project" was not excluded in your employment/IP agreement they may feel they already own the product.
based on what i understand, though most of the people might not agree with me<p>1. if you are developing something, even tough as side project on your offtime, it is usually own by the company you work for (it will be on your employment contract most of the time)<p>2. On the other hand, if you think you can make money on your project, and based on what i heard in_California<p><a href="http://en.wikipedia.org/wiki/Non-compete_clause#Exceptions_-_valid_non-compete_agreements_in_California" rel="nofollow">http://en.wikipedia.org/wiki/Non-compete_clause#Exceptions_-...</a><p>Non-compete agreements are automatically void as a matter of law in California, except for a small set of specific situations expressly authorized by statute.<p>3. but the company is going to argue that you get the idea of developing the side project based on your current project<p>4. so at the end its a matter of getting what you want from the company vs. making the situation into a terrible one.<p>You can ask for promotion with more money, or options and even run the project as a stake holder.<p>that all depends on how you and your company react to each other.
You left out some important information.<p>Are they trying to force you to give them your home-made/side project as they believe they are entitled to the software due to your employment? Or, are they interesting in purchasing the product?
Did you work on it at anytime during work hours or on work computer or other property?<p>Are they offering to buy it from you or just claim that it belongs to them because you are an employee.<p>I don't have any answers, but these questions are important.