Who Owns the Code When a Developer Builds It for You?

You paid for the software, so you own it. That feels obvious, and it's the assumption almost every small-business owner walks in with. It's also, under US law, often wrong. This is one of those quiet gaps that never matters until the day it matters enormously, when a developer moves on, a relationship sours, or you go to sell your business and a lawyer asks who actually owns the code. Let's make sure that day goes well for you.

We build custom software and we assign every bit of it to our clients, so we have no reason to soften this. Here's exactly how ownership works and the exact clause to insist on.

The default rule that catches people out

Under US copyright law, the person who creates a work generally owns it. There's an exception called 'work made for hire,' but it works differently than the name suggests. For an actual employee building software as part of their job, the employer owns it automatically. For an independent contractor, which is what most freelancers and agencies are, work made for hire only applies if there's a signed written agreement saying so, and even then only for certain categories of work. Software commissioned from a contractor doesn't reliably fall into those categories on its own.

The practical upshot: if you hire an outside developer and there's nothing in writing about ownership, the developer can legally own the code you paid to have built. You might have a license to use it, or you might have nothing but a handshake. Neither is ownership.

The exact clause to look for

You don't need to be a lawyer to check for this. You need the contract to contain an assignment, not just a 'work made for hire' label. Look for language along these lines:

Developer hereby assigns to Client all right, title, and interest in and to all deliverables, including all intellectual property rights, upon Client's payment. To the extent any deliverable does not qualify as a work made for hire, Developer irrevocably assigns it to Client.

Two things make that clause do its job. First, the word assigns, not just 'work made for hire,' because the assignment is the belt-and-suspenders that works even when work-made-for-hire doesn't. Second, upon payment, which is fair to both sides: you own it once you've paid for it. If the contract only says the work is 'work made for hire' and stops there, ask for the assignment sentence to be added. Any honest developer will. None of this is legal advice, and copyright rules can turn on details specific to your situation, so have a lawyer review the actual language before you sign anything that matters.

Owning the code isn't the same as owning the keys

Even with a perfect assignment clause, you can still be stranded if the practical pieces live in the developer's accounts. Make sure you also get and control:

• The source code itself, delivered to you, not just a running app you can't edit.
• The code repository (like GitHub) under your account or ownership.
• The hosting, domain, and any third-party service accounts in your name.
• Any documentation and credentials a new developer would need to take over.

Ownership on paper plus access in practice is what real control looks like. Missing either one leaves you dependent on the developer's goodwill. If you're vetting a developer now, this belongs on your list of questions to ask before hiring.

This isn't a reason to distrust developers

It's worth saying plainly: most developers who retain ownership by default aren't being sneaky. Often nobody wrote anything down and the law filled the gap. And there are legitimate cases where a developer reuses their own general tools or libraries across clients, which is fine as long as your specific software is assigned to you. The point isn't suspicion. It's that ownership is too important to leave to assumption. Put it in writing and the whole issue disappears.

How we handle ownership

Our model is simple and it's in every contract: when you hire us for custom software and AI, you own all of it. The code is assigned to you on payment, you get the source and the repositories, and every account, domain, and login is set up in your name from the start. No licensing you back your own software, no exit fees, no lock-in. That's our practice, not the industry standard, which is exactly why we're telling you to demand the clause from whoever you hire. If a developer won't put your ownership in writing, believe what that tells you.