Who owns the code? Copyright and contracts when you pay for custom software
Why paying for development does not by itself transfer copyright, how the work-made-for-hire rules treat employees and contractors differently, and what your contract needs instead.
You paid for the software, so you own it - that assumption is wrong often enough to sink deals, acquisitions and product launches. Under US copyright law, the creator is the default owner, and paying an invoice is not the same as owning the copyright. This article summarises the US Copyright Office's own material - its "What is copyright?" page and Circular 30 on works made for hire, both read on 20 November 2026 - for buyers of custom development. It is general information, not legal advice.
The default: the creator owns the copyright
Copyright law gives the owner a set of exclusive rights and the power to authorize others to use them. By default the author - the person who wrote the code - holds those rights. Payment alone does not move them. Ownership changes hands through specific legal routes, and the Copyright Office is blunt that the work-made-for-hire concept "can be complicated and has serious consequences" for both sides.
Employees: the straightforward case
When a work is prepared by an employee within the scope of their employment, it is a work made for hire and the employer is considered the author and owner from the start. Whether a situation qualifies is judged by the facts in existence when the work is created. Code written by your own employees as part of their job is the clean case.
Contractors: where "work for hire" clauses overpromise
For independent contractors, a commissioned work counts as a work made for hire only if two conditions both hold: the parties expressly agree in a written instrument signed by both of them, and the work is commissioned for use in one of nine statutory categories. Those categories, listed in 17 U.S.C. section 101, are use-based, not a list of media types: contribution to a collective work, part of a motion picture or other audiovisual work, translation, supplementary work, compilation, instructional text, test, answer material for a test, or atlas. Ordinary standalone software commissioned from a contractor usually matches none of those uses, and then a "work for hire" sentence in the contract does not transfer copyright by that route. But the test is the commissioned use, not the label "software": a specific arrangement can fall within a category - code commissioned as a contribution to a collective work, for example - so treat borderline arrangements as fact-specific, not automatically excluded. Where work made for hire does not apply, ownership moves by assignment, and 17 U.S.C. section 204(a) is the formality: a transfer of copyright ownership, other than by operation of law, is not valid unless it is in writing and signed by the owner of the rights conveyed or their authorized agent. Your contract should contain that written assignment explicitly, covering the code, related materials and the rights to modify and distribute.
Registration and enforcement
The Copyright Office notes that registration - or a refusal - is necessary to enforce copyright through litigation; the requirement it describes applies to US works. If ownership matters to your business, registering the work and keeping the chain of signed agreements is what makes the right usable, not just theoretical.
A buyer's checklist
Before signing: does the contract include an express written copyright assignment from every person or company who will write code, not just a work-for-hire clause? Are subcontractors covered the same way? Who owns pre-existing code and libraries the vendor brings in, and what license do you get? After delivery: do you have the signed documents on file and the source in your own repository?
What to keep in mind
This article covers US law as described by the US Copyright Office; other countries assign initial ownership differently, so have the contract checked under the law that governs it. Open-source components in your codebase keep their own licenses regardless of what your contract says. And the nine-category analysis above reflects Circular 30's summary of the statute - edge cases belong to a lawyer, not a blog post.