Who Owns the Code? IP Ownership Clauses in Software Employment and Contractor Agreements

When a company hires a developer or brings on a contractor to build software, everyone assumes the company owns what gets built. That assumption is frequently wrong, and the gap between assumption and legal reality is where expensive disputes are born. IP ownership in software depends almost entirely on what the written agreement says — and whether one exists at all.

Why Default Rules Are Not Your Friend

In the United States, copyright in an original work belongs to its creator by default. Software is a copyrightable work. So unless something in writing transfers that copyright — or qualifies the work as a "work made for hire" — the person who wrote the code owns it.

For employees, the work-made-for-hire doctrine under the Copyright Act generally gives employers ownership of works employees create within the scope of their employment. But "scope of employment" is not limitless. Code a developer writes at home, on personal equipment, solving a problem unrelated to their job duties may fall outside that scope entirely.

For independent contractors, work-made-for-hire applies only to a narrow list of categories defined by statute — and custom software does not automatically qualify. A contractor who writes your entire product on a fixed-fee contract may own that code unless the agreement contains an explicit written assignment of copyright. A signed contract with a payment schedule but no IP assignment clause leaves ownership with the contractor.

What an IP Assignment Clause Actually Does

An IP assignment clause transfers ownership of intellectual property — copyright, patent rights, trade secrets — from the creator to the company. It is not the same as a license. A license lets the company use the work; an assignment transfers title.

A well-drafted assignment clause will typically:

• Cover work product created during the engagement, whether or not it happens on company time or equipment
• Define "work product" broadly enough to include documentation, algorithms, and inventions, not just finished code
• Include a present-tense assignment ("hereby assigns") rather than a promise to assign later, which matters if a dispute arises before the paperwork is complete
• Contain a power of attorney provision so the company can record the assignment with the USPTO or Copyright Office without chasing down a former contractor

Patent rights require separate attention. Copyright protects the expression — the code itself. A patent, if obtained, protects the underlying invention. Even if a contractor assigns copyright, patent rights to an invention they conceived may still belong to them unless the agreement explicitly assigns those as well.

The "Prior Inventions" Carve-Out

Many employment agreements include a schedule where new hires list inventions they made before joining the company. This carve-out protects the employee from inadvertently signing over work they did before the job started. From the company's perspective, it also establishes a clean record: everything the employee creates going forward belongs to the company, and there is a documented baseline of what was carved out.

Founders who later become employees of their own company after a funding round sometimes discover they forgot to carve out their pre-incorporation inventions — and technically assigned them to the company that did not yet exist, or to a subsequent employer. Getting this list right at the time of signing matters far more than most people realize.

State Law Variations

Several states — California, Delaware, Illinois, Minnesota, North Carolina, and Washington among them — limit how broadly an employer can claim rights over work an employee does on their own time with their own resources, unrelated to the employer's business. These statutes override contract language that reaches too far. If your workforce spans multiple states, your agreement template should be reviewed against the laws of each state where employees work, not just where the company is incorporated.

What Happens Without a Written Agreement

When there is no written IP agreement — or the agreement is silent on ownership — the parties are left arguing about intent, industry custom, and default legal rules. Courts have found contractors retained ownership of software even after being paid in full, because no assignment was ever executed. The company had a license implied by the circumstances, but it could not stop the contractor from selling the same work to a competitor, and it could not obtain a patent on the invention without the contractor's cooperation.

Fixing ownership after the fact requires a written assignment signed by the original creator. If the relationship has soured, that signature can be difficult or expensive to obtain.

Practical Takeaways

• Never assume employment or payment alone transfers IP ownership — get a signed agreement with an explicit assignment clause before work begins
• Treat copyright and patent rights as separate: an agreement that addresses one may be silent on the other
• For contractor agreements, confirm the assignment is present-tense and covers both copyrights and patent rights to inventions conceived during the engagement
• Ask every new hire to complete a prior inventions schedule at the time of signing, and keep a copy on file
• If your team works across multiple states, verify that your agreement template complies with each state's employee invention statutes
• When acquiring a company or its software assets, confirm that the target's IP was properly assigned up the chain from every contractor and founder who contributed to it

This guide is general education, not legal advice, and does not create an attorney–client relationship. For your specific situation, talk to a registered patent attorney.