Who Owns the Code Your Freelance Developer Wrote? (It's Probably Not You)

Here's a scenario that plays out constantly: a founder pays a freelance developer or agency to build their product, the invoice gets paid, the product ships — and the founder assumes they own the code because they paid for it. In most jurisdictions, that assumption is wrong by default.

The default rule

Under copyright law in the US, UK, and most common-law countries, the person who creates a work — the developer who wrote the code — owns the copyright in it by default, even if they were paid to write it. There's one major exception: if the developer is your direct employee acting within the scope of employment, the work is usually automatically owned by the employer ("work made for hire" in the US, similar doctrines elsewhere).

Independent contractors — freelancers, agencies, most outsourced dev shops — are not employees. Paying an invoice creates a right to be paid for services. It does not, by itself, transfer ownership of what was created. Without an explicit written assignment, the developer retains the copyright, and you typically hold, at best, an implied licence to use what you paid for — not to own it, modify it freely, or stop them from reusing chunks of it elsewhere.

Why this actually matters

Most founders never notice this gap until it costs them something specific:

• Fundraising due diligence. Investors' lawyers check IP ownership of your core product. A missing assignment is a common deal-slowing finding in early-stage due diligence.
• An acquisition. A buyer needs clean title to the code they're acquiring. Gaps here get escrowed, discounted, or become a closing condition.
• A relationship breakdown. If a developer relationship ends badly, an implied licence can be disputed or revoked in ways an explicit assignment can't be.
• Reuse by the developer. Without an assignment, nothing stops a freelancer from reusing your core logic in a competitor's product, unless your contract separately restricts that.

What actually fixes it

An explicit, written IP assignment clause — either in the contractor agreement itself or as a standalone document — that states the developer assigns all right, title, and interest in the work product to you, effective on creation or payment. A few things worth getting right in the clause:

• Present assignment language ("hereby assigns") rather than a promise to assign later, which is weaker and can be harder to enforce
• Coverage of pre-existing IP the developer brings in — libraries, frameworks, their own reusable code — usually licensed to you rather than assigned, since they didn't create it for you specifically
• Moral rights waiver where relevant (matters more in the UK/EU than the US)
• Timing tied to payment or creation, so there's no gap where ownership is ambiguous

What to do if you've already got this gap

Go back and get a retroactive assignment signed for any developer or agency who built material parts of your product without one. This is far easier to fix now, with a cooperative relationship, than during a funding round or acquisition when the counterparty has leverage and a deadline.

Frequently asked questions

Does paying an invoice count as buying the code?

No. Payment creates an obligation to pay for services rendered — it doesn't by itself transfer copyright ownership. You need an explicit written assignment clause for that.

What about code written by an employee?

Work created by a genuine employee within the scope of their job is normally owned by the employer automatically under work-made-for-hire principles — this is the one case where the default rule favors the company, not the creator.

Does an NDA cover this?

No. An NDA protects confidential information from being disclosed — it says nothing about who owns IP that gets created. They're separate clauses serving separate purposes.

This article is general information about how these documents and obligations usually work. It is not legal advice on your specific situation, and reading it does not create a lawyer-client relationship. Laws referenced here change — verify current requirements before relying on this for a live decision.