Who Owns the Code Your Contractor Wrote?

A founder hires a freelance developer, pays the invoice, and assumes the company now owns the software. That assumption is often wrong. Under U.S. copyright law, the person who writes code is presumed to own the copyright in it unless one of a narrow set of legal exceptions applies. Paying for the work is not one of those exceptions.

This matters because the code is frequently the most valuable asset a startup has. If ownership is unclear, it can slow down a fundraising round, sink an acquisition, or leave you unable to stop the same contractor from selling a near-identical product to your competitor.

The employee rule does not cover most contractors

Copyright law has a doctrine called work-for-hire that automatically gives an employer ownership of copyrightable work an employee creates within the scope of employment. Founders hear this term and assume it protects them whenever they pay someone to build something. It does not work that way for independent contractors.

For a contractor's work to qualify as work-for-hire, two things have to be true at the same time. First, the work has to fall into one of a small number of statutory categories, things like a contribution to a collective work, a translation, or a supplementary work. Custom software generally does not fit any of these categories. Second, even if it did fit, the parties need a signed written agreement, made before or at the time the work begins, that expressly states the work is made for hire. Most freelance arrangements fail on the first requirement alone. That means the label "work-for-hire" in a contractor agreement often does nothing at all for software, no matter how clearly it is written.

What actually transfers ownership

Because the statutory work-for-hire category rarely applies to code, the reliable path is a written assignment. An assignment is a separate legal act: the contractor, who owns the copyright the moment the code is written, expressly transfers that ownership to your company. This is not a formality. Without an effective assignment, the developer retains rights in the code even after being paid in full, and your company holds, at best, an implied license to use it for the purpose the parties originally discussed.

An implied license is a shaky foundation for a company asset. It can be narrower than you think, limited to the specific use the contractor understood at the time, and it says nothing about your ability to modify the code, sublicense it, or stop the contractor from reusing it elsewhere. If you are raising capital or negotiating a sale of the business, buyers and investors will ask for a clean chain of title on your intellectual property. "We have an implied license from a contractor we haven't talked to in two years" is not an answer that closes a deal.

Get the agreement right before the work starts

A written agreement should be signed before the contractor writes a single line of code, not after. At a minimum it needs:

• An express, present-tense assignment of all copyright and related rights in the work product to the company, not a promise to assign later.
• A description of the work broad enough to cover revisions, iterations, and related materials such as documentation and design files, not just the initial deliverable.
• A waiver, where applicable, of any moral rights the contractor might otherwise assert.
• Confirmation that any pre-existing code or libraries the contractor brings into the project are either licensed to you on terms you can live with or excluded from the deliverable entirely.
• Cooperation language requiring the contractor to sign further documents if you ever need to register the copyright or prove the chain of title.

That last point about pre-existing and third-party code is its own risk. A contractor who drops open source components into your product without disclosing the license terms can create obligations you never agreed to, including a requirement to release your own code publicly under certain licenses. The firm has written separately about that risk; see our piece on open source license risk if your product includes any third-party or open source code.

Where this fits with your broader contracts

Ownership language should not live only in a general services agreement. If you use a statement of work for each project, the assignment clause needs to appear in both documents or be clearly incorporated by reference, because a mismatch between the master agreement and the individual statement of work is a common source of disputes. Our overview on how these documents relate to each other, MSA vs. SOW, walks through how to structure that relationship.

It is also worth remembering that this issue is not limited to outside contractors. Founders, advisors, and even early employees who write code before formal employment paperwork is in place can create the same gap in ownership. If your company has multiple founders contributing code or other IP before formation documents are finalized, review our article on the founder's agreement, which addresses how ownership of pre-formation work should be handled.

North Carolina and Pennsylvania

Copyright ownership and the work-for-hire doctrine come from federal law, so the analysis is the same whether your company is based in Charlotte or in the Philadelphia area. What differs is the state law that governs the underlying contract, including how a court in North Carolina or Pennsylvania might interpret ambiguous assignment language or resolve a dispute over whether an agreement was properly formed. That is a reason to have the contract reviewed by counsel licensed in the state whose law will govern it, not a reason to treat the copyright question itself differently between the two states.

If your company has been operating on verbal agreements or template contracts pulled from the internet, the fix is usually straightforward: audit who wrote what, and get signed assignments from anyone who does not already have one on file, including past contractors if you can still locate them. Our intellectual property practice reviews contractor and developer agreements for founders who want to know where they stand before a fundraising round or exit forces the question. You can reach the firm through our contact page to schedule a review.