Software code ownership guidePaying for custom software does not mean you own the code.

In the United States, whoever writes the code owns it unless a signed contract says otherwise. Here is what to put in writing, which accounts belong in your name and what to ask before you sign.

By Shay McGill, CTO of Lagom Tech Solutions · Updated · 5 min read

By default, the developer owns the code.

This guide is general information about US law, not legal advice. Every contract and situation is different. Have a lawyer review your contract before you sign it.

Under US copyright law, the author of a work owns the copyright as soon as it is written. For software, the author is whoever writes the code, or the company that employs them.

Paying for the work does not change that on its own. If your contract says nothing about ownership, the developer may still own the code you paid for. You may only have an implied right to use it.

Why "work made for hire" rarely covers an outside developer.

Many software contracts call the work a "work made for hire." That phrase has a specific legal meaning, and it covers less than people expect.

Work made for hire covers two cases. The first is work an employee does as part of the job. The second is commissioned work in a short list of categories set by the Copyright Act, with a signed agreement.

Software written by an outside contractor rarely fits that list. So a contractor's code is often not work made for hire, even when the contract uses the phrase.

The answer is a written assignment of intellectual property. In plain terms, the developer agrees to transfer their rights in the code to your company. A transfer of copyright has to be in writing and signed to count.

Careful contracts use both: work-for-hire language, plus an assignment as a backup in case the first does not apply.

When does ownership change hands?

Many contracts assign ownership on payment. That is fair to both sides: the developer keeps the rights until paid, and you get them when you pay.

Read how that works with milestone payments. Ownership should pass for each part as you pay for it, not only at the very end. Otherwise a dispute over the last invoice can leave you without rights to anything.

Also check what happens if the project stops early. You should own whatever you have paid for, and be free to have someone else finish it.

What about code the developer already had?

Developers rarely start from a blank page. They reuse their own templates, components and tools, and they build on open-source libraries. That is normal, and it can keep your cost down.

Say an HVAC shop hires a developer for a dispatch board, and the developer reuses a scheduling component from earlier work. The shop usually gets a license to that component, not ownership of it. Make sure that license is:

  • Perpetual: it does not end when the project or the relationship ends.
  • Irrevocable: the developer cannot take it back later.
  • Royalty-free: there is no ongoing fee to keep using it.
  • Transferable: it goes with the software if you sell the business.
  • Open to other developers: you can hire someone else to change and maintain it.

Open-source code comes with its own licenses. Permissive licenses, such as MIT and Apache 2.0, ask for little more than credit. Copyleft licenses, such as the GPL, can require you to share your source code if you distribute the software.

Ask for a list of the open-source components and their licenses. It is a fair request, and a careful developer keeps one.

The accounts matter as much as the code.

Owning the copyright helps little if you cannot reach the code. Software lives in a handful of accounts, and each one should belong to your company.

AccountWhat to check
Code repositoryThe online account that stores the code and its history. Your company owns it and adds the developer as a member.
Hosting and databaseThe servers and database your software runs on. Billed to your company, with you as an owner or admin.
Domain nameRegistered in your company's name, with a company email address as the contact.
App-store accountsApple and Google developer accounts in your company's name, so your apps are published under your business.
Third-party servicesEmail, text messages, maps, payments and AI. Each one billed to you, with logins you control.

An app published under a developer's personal account can be slow and awkward to move later. So can a domain registered to someone's personal email.

Ask for documentation and admin access as well. That means an admin login for every system and a short guide to how the software is deployed. It also means a list of every service it depends on.

What happens if your developer disappears?

Developers change jobs, close their shops and get sick. Plan for it before it happens, not after.

Suppose the code sits in your repository and the accounts are in your name. If the setup is written down, another developer can learn it and pick up the work.

If the code lives only on the developer's laptop or in their accounts, you may have to start over. That is an expensive way to learn this lesson.

Picture a property manager whose tenant portal stops working on a Friday. With admin access and a deploy guide, a new developer can find the problem. Without them, the portal stays down while you hunt for passwords.

Questions to ask before you sign.

Bring this list to any developer, and then to your lawyer. Clear answers in writing protect both sides.

  • Does the contract assign all intellectual property in the custom code to my company?
  • When does ownership pass: with each payment, or only at the end?
  • What pre-existing code will you reuse, and what license do I get to it?
  • Which open-source components are included, and under which licenses?
  • Will the repository, hosting, domain and app-store accounts be in my company's name?
  • Will I get admin access and written documentation at launch?
  • If we stop working together, can another developer take over without your permission?
  • Is there anything I would still owe you after the project ends?

At Lagom Studio, you own the code, whatever you decide next. By default, we set up the hosting and code accounts in your company's name. The design from Discovery is yours to keep, too, even if you build with someone else.

To see what a build costs, read what custom software costs a small business or see full pricing. If you want to talk through a project before you sign anything, book a free problem review.

Questions

Common questions.

Who owns the code when you hire a freelance developer?

In the United States, the developer owns the copyright by default, unless a signed written agreement transfers it. Paying for the work does not transfer ownership on its own. To own the code, you want a written assignment of intellectual property in the contract. This is general information, not legal advice, so have a lawyer review your contract.

Does a work made for hire clause give me the software?

Not always. Work made for hire covers work by employees, and commissioned work in a short list of categories set by the Copyright Act. Software from an outside contractor rarely fits those categories. That is why careful contracts add a written assignment of intellectual property as a backup. Ask a lawyer to review the exact wording.

What is an IP assignment in a software contract?

It is a clause where the developer agrees to transfer their rights in the code to your company. It is often tied to payment, so ownership passes as you pay. It should cover the custom code written for you. Reused tools and open-source parts usually come with a license instead of ownership.

Should my hosting and app-store accounts be in my company's name?

Yes. The code repository, hosting, domain name and Apple and Google developer accounts should belong to your company, with the developer added as a user. If they sit in a developer's personal accounts, moving them later can be slow, and you may lose access if the relationship ends.

What if my developer reused their own code in my project?

That is common and usually fine. You typically get a license to those pre-existing parts rather than ownership. Make sure the license is perpetual, irrevocable, royalty-free and transferable. It should also let another developer change and maintain the software if you ever switch.

Do I own the code if I hire Lagom Studio?

Yes. With Lagom Studio you own the code, whatever you decide next. By default, the hosting and code accounts are set up in your company's name, so you can work with anyone later. The design from a Discovery engagement is also yours to keep, even if you build with someone else.

Tell us the problem

Want a straight answer for your business?

Tell us what eats your team's time. We'll tell you honestly what it would take to fix, and whether custom software is even the right answer.

30 minutes, no pitch deck. Or email info@lagomtechsolutions.com.