Can a company sell software I wrote for them if they never gave me a contract I was asked by companyA(UK) to rewrite their legacy application, which I have been doing for a year. CompanyA have made a deal to sell the application to CompanyB(USA). The deal will complete at some date in the near future. In the meantime, CompanyB have been bankrolling development (paying me). Neither companyA or CompanyB have given me me a contract or any letter of agreement. I am a freelance developer. I work from home on my own equipment, to my own schedule. I handle my own tax and I have one other client. CompanyA gives me broad direction (e.g. please write a bookings feature) I design the graphical user interface and architecture, and then implement the feature. As of now I have completely replaced the front-end, most of the back-end, and have added many features. I invoice CompanyB monthly as a software consultant and they have paid on time. I'd like to know: 1. Do I own the copyright to the software I have written. And if so does CompanyA have any right to sell the product to CompanyB without me signing it over? 2. Should I register or take other action to protect what I consider to be my original work? 3. What rights do CompanyB have, given that they have been paying me? Thank you
This answer to a related question sums up the relevant concepts regarding work for hire. Since, according to your description of your relationship to A, you are not an employee (Commun. for Non-Violence (CCNV) v. Reid 490 U.S. 730), and you do not a written agreement, under US law, this would not be a work for hire: thus you hold copyright to something. I presume Company A gave you the source code and you are rewriting it to fit some technical requirement, so you have been given permission by the copyright holder to create a derivative work. You do not gain copyright to the original code: you only hold copyright to what you wrote. You would therefore need the permission of the copyright holder (of the original program) to sell copies of the modified program (currently A, company B in the future once the transfer is complete). There isn't a special "signing-over" ceremony for permission to copy, but the situation you describe is very messy. Even without a written agreement, you do understand that they intend to make multiple copies of the resulting program which includes your contribution, and you have received something of value in exchange for your contribution. So, one would argue, you have at least given permission to copy your stuff, even without a piece of signed paper -- in hiring you, you have given them an implied license to use what they paid you to create. The unclarity would be in whether you transferred your property rights, or simply licensed them to use it. Hence the recommendation to get an IP attorney.
Defining the value of a privately held company is hard (tax returns don't provide a very informative basis because accountants will tend to under-value things like "goodwill" in order to avoid paying tax). However that doesn't matter for this stack, because the only legal question is: If I had some means of coming up with a number and presenting it, would it be legally acceptable to define that as their company value in a license? And the answer is: absolutely yes! You are pretty much entirely free to define terms in your license as you see fit. If you want to define "company value" as meaning "the annual gross salary paid to receptionists", go for it. (You would probably need to define what a "receptionist" is in this case).
Based on the contract language quoted in the question, and the facts stated there, it would seem that the employee owns the copyright on the software. It would seem that the software was not created &quot;during the course of employment.&quot; However, when the employee offers it to the employer free of charge, the employer may well want to own the copyright and any other related IP. The employer might want the employee to sign an agreement transferring the copyright. Or the employer might simply treat the software as belonging to the employer. Asserting and enforcing the copyright against the employer might be difficult. Insisting on even a token payment would help establish thst the copyright belongs to the employee, or gettign the employer to sign an acknowledgement of the ewmployee's copyright would have a similar, bnt even stronger effect.
Your question mixes up two different aspects of intellectual property. From a copyright point of view, it is perfectly legal to reproduce the features of a one piece of software in another. The functionlity of the software is not copyright (although the detailed look and feel of the user interface might be). However you ask if you, as an employee, can do this by &quot;looking into the code of software X&quot;. Presumably by doing this learn something of the organisation and algorithms used. Even if you avoid direct copying, you are likely to have learned trade secrets of your employer, and publishing these is at least a civil tort in the US, and in some states a crime.
&quot;Wholly unconnected with your employment&quot; means exactly that. Anything that is not connected to your functions or processes that you use in the course of your employment that your employer would have an interest in either protecting or marketing. Writing a book about software development If you are just a software developer, this would be fine unless you were talking about a process unique to your employer. If you worked in a publishing house that wrote software development books, this would be connected and must be disclosed to your employer. Releasing an open source piece of software not specifically aimed at the industry the company is in Again, this probably fine not to disclose since it would not be something you would develop as part of your employment, or under the umbrella of your company focus market. Release a commercial piece of software not specifically aimed at or competing with the industry the company is in Same as above. Honestly though the best policy is being open. If you come to your company with your idea and tell them that it doesn't have any applications in your industry and would like to develop it in your own time, they would have a much harder leg to stand on in a court case when they finally figured out how to apply it.
They certainly can make that a license term and revoke the license if you do not comply. However, revoking the license is all they can do to &quot;forbid&quot;. Or they could sue you for damages without revoking the license. That said, you are free to consult how to use their software so long as you do not hold a license so that you are not bound by the terms AND you do not break the law e.g. copyright. How to do it is up to you to figure. Maybe you could simply consult users that do have a license — on their premises and devices.
On what grounds would you sue? Contract Well, I think that you would struggle to find the necessary elements (see What is a contract and what is required for them to be valid?) In particular, you would struggle to prove that there was intention to create legal relations on their part and possibly on yours. Are you able to identify in your "back &amp; forth" a clear, unequivocal offer and acceptance? Without knowing the details of the "back &amp; forth": I was hoping that someone at $organization might be willing to write an article explaining what you do, the history of the organization and how it works appears on the face of it to be a request for a gift; not an offer to treat. Promissory Estoppel If you don't have a contract then it is possible (IMO unlikely) that they induced you by your actions to commit resources (your time in writing) in anticipation of a reward (them publishing what you wrote). To be estopped they would have to have known that you were writing the article in the expectation that it would have your organisation's name in it, that they did not intend for that to happen and that they allowed you to invest those resources notwithstanding. If you can prove all of that then you can require them to do what they promised. The big difficulty I see in this is did you tell them that a) you were writing the article, b) it would have your name in it and c) you expected it to be published in that form. Copyright If they publish the work or a derivative work without your permission you can sue for breach of copyright. As it stands, they probably have an implied licence to publish and you would need to explicitly revoke that. Options There are two reasons to go to court: Money Principle If you are going to court for money then this is at best a risky investment and at worst a gamble: balance your risk and reward carefully. If you are going to court for a principle then I simultaneously admire your principles and think you're an idiot. Make a deal Explain that the reason that you wrote the article was a) to support their fine publication and the fantastic work it does (even if you don't) and b) to garner good publicity for your organisation. You understand and admire their strong editorial stance (especially if you don't) but the article involved a considerable amount of work and could they see their way clear to give you a significant discount (~80%) on a full page ad facing the article.
The whole purpose of a patent is that the contents of the patent becomes public knowledge, in exchange for a time limited monopoly. Therefore you are allowed to do anything, since you are not just allowed but expected to examine the patent in order to improve on it, except that you need a license to sell or give away products implementing the patent as long as it is valid. The only thing to be careful about is that by publishing source code, you might be enticing others to infringe on the patent, so I'd recommend not to do that without advice of a lawyer. PS. With software, the interpretation of "making" software in patent law may be a bit surprising. There was a major case between Microsoft and AT&amp;T about that. The software developer isn't "making" the software. The build engineer putting everything together isn't "making" the software. The CD manufacturer making a million copies isn't "making" the software. The person installing it on their computer is the one who makes it.