Every startup CEO who is growing a scalable company should make sure that her startup owns the IP rights to work created by independent contractors. Failure to do so could seriously impact the value of the company, jeopardize the possibility of obtaining investment, and lead to legal liability for infringement and horrible embarrassment.
There are a few ownership concepts in intellectual property law that are critical to know.
1) Under copyright law, when an independent contractor creates an original work of authorship — like a logo or software application — the copyright automatically vests in the author of the work. There is an exception for works made for hire but it is very narrow and specific. See my previous post on the subject of the work for hire doctrine.
2) Patent rights are personal. They vest in the inventor. Corporations can’t be inventors.
3) Any trade secrets belong to the independent contractor unless specifically transferred. Potential trade secret protection can be lost if no reasonable measures of protection are taken to keep the information secret, like an NDA.
Consequently, a company must have a signed written agreement with the author/inventor that transfers the IP rights to the company.
An example of a super simple, proper assignment clause:
[NAME OF CONTRACTOR] hereby assigns and agrees to assign to [NAME OF YOUR COMPANY] all right, title and interest in and to the [NAME OF THE WORK] and all intellectual property rights therein.
The red words are critical. Courts have decreed the proper type of language and your contract should use it. The description of the work and the associated IP rights may be extensively defined. Some assignment clauses are fairly long and detailed but the critical words to effectively transfer the rights are in red.
Here are five CEO misbeliefs that I commonly see in my legal practice:
1) “My company paid for the work and so it owns the IP rights.”
This is the most common false belief that I see in my practice. The legal truth is counterintuitive. CEOs need to understand that they must take specific measures to own the IP rights for work that is created by independent contractors. They must have formal, written contracts if they want the company to own the IP rights. If the company wants to sell and sublicense the work — like software! — they must either have a full assignment of IP rights or a very broad license.
2) “The contractor says my company will own the IP rights and so my company owns the rights.”
Oral agreements are not sufficient to transfer IP rights. IP transfers must be in writing signed by the author/inventor.
3) “I have a NDA with the contractor and so my company owns the rights.”
A simple NDA does not transfer IP rights. You need an agreement with a specific assignment clause that transfers the rights.
4) “My contract says my company owns the rights.”
A clause that says that your company owns the rights but does not assign the rights does not legally transfer the rights. I see this mistake a lot with contracts drafted by the entrepreneur or pulled off the web.
The following is improper and will not transfer IP rights to your company!
[NAME OF COMPANY] will own all right, title and interest in and to the [NAME OF THE WORK] and all intellectual property rights therein.
5) “It doesn’t matter if my company owns the rights, I have a good relationship with the contractor.”
Frequently in the startup world, relationships fall apart. I’ve seen partnerships and oral agreements go awry. I’ve seen independent software developers threaten a startup’s customers with cease and desist notices for infringement because the startups didn’t have IP assignments or licenses for its customers. If your company is paying for the work, make sure it owns the IP rights by using a formal, written contract with the contractor that specifically assigns the rights.
Other related post:
Does Your Startup Own the IP Rights to Work Created by its Founders?
Jill Hubbard Bowman is an intellectual property lawyer and educator who helps startups protect their intellectual property and avoid legal liability.
The information provided in this legal blog is not intended as legal advice and does not create an attorney-client relationship. Please do not submit questions or comments seeking legal advice or submit confidential information through this blog. By communicating through this blog, you understand and agree that the information will not be treated as confidential and the publisher has no duty to keep it confidential.





{ 3 trackbacks }
{ 5 comments }
Your web page is really helpful to people like us. Your post is worthwhile to read and highly beneficial. Many thanks so significantly for sharing it up!
Must turn out to be a member of this site, superb post. Thought it was with google.
Many thanks very significantly for this entry. Searching forward to yet another 1.
What I want to know is why you didnt think to include the other side of this problem? There are so many things that youre missing here that I dont see how you could actually form an intelligent opinion on the subject. Its like you didnt even consider that there me be another side here. Im kind of disappointed.
Dayle,
It is really about trying to keep the length of posts manageable. This post is focused on a the perspective of a startup CEO, even software development company managers, who needs to make sure the startup owns the fundamental IP. I’ve done a number of posts that address issues regarding keeping your IP free of ownership claims (see Startup Basics) and carve out issues for software developers who need to protect the IP they want to reuse or resell (Who Owns the Rights to Custom Software).
Licensing that only gives some rights to customers is a complicated subject and more posts will be coming.
Heather and I will also be doing a free teleclass for software developers in a few weeks that will address how to deal with ownership in more complicated relationships.
Thanks for sharing.
Jill
Comments on this entry are closed.