If I pay someone to build my software, do I own it?

By Ranjit Bhinge, founder of Blur Studio · Updated · 8 min read

Short answer: Not automatically. In the United States, a contractor who writes code usually owns the copyright until a signed written document transfers it to you, so paying the invoice is not enough. What matters is the wording: an assignment moves ownership to you, while a license only lets you use the code. This is practical information, not legal advice, and other countries have different rules, so ask a lawyer before you rely on it.

Ranjit Bhinge

You paid a developer to build your software and you want to know whether you own it and whether you can take it to someone else.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Most owners assume that if they paid for software, they own it. Often that is true in practice, because nobody ever argues. But the law does not work that way by default, and the day you fall out with your developer, or want to switch to a new one, the paper matters more than the payment. Here is how to check, what the contract must say, and what you should be handed when the job ends. I am not a lawyer, and this is not legal advice. Where the stakes are high, pay for an hour of a lawyer's time.

The default rule: who owns code when nothing is written down

Under US copyright law, the person who creates a work is its author and starts as its owner. There are two main exceptions, and neither is automatic for a contractor.

  • Employees. A work made by an employee within the scope of their job is a "work made for hire", and the employer is treated as the author (17 U.S.C. sections 101 and 201(b)). If your developer is your employee, you usually own what they build on the job.
  • Commissioned work. For an independent contractor, the law lists nine kinds of commissioned work that can be a work made for hire if both sides sign a written agreement saying so: a contribution to a collective work, part of a film or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, and an atlas. Custom business software does not clearly sit in that list. So for most contractor-built software, the usual route is a written assignment, not a work-made-for-hire label.

An assignment is a transfer of ownership. The same law (section 204) says a transfer of copyright ownership is not valid unless it is in writing and signed by the owner, in this case the developer. No signed paper, no transfer. The practical result: if you hired a freelancer or agency, paid them, and never signed an ownership clause, they may still hold the copyright. What you are then allowed to do with the code you paid for, such as changing it or handing it to someone else, is a question for a lawyer in your country.

Outside the US the rules differ, and what applies to you depends on where you and your developer are based. Treat everything on this page as a starting point for a conversation with a lawyer, not a ruling.

Assignment versus license: the difference that decides everything

AssignmentLicense
What you getOwnership of the codePermission to use it on stated terms
Can you hire someone else to change it?YesOnly if the license allows it
Can you sell the business with it?YesOnly if the license is transferable
Can the developer reuse it for others?Not the parts you own, unless you agreeYes, often
Words to look for"assigns all right, title and interest""grants a license", "non-exclusive", "retains ownership"

A license is not bad by itself. Many good products are sold that way, including ready-made software subscriptions, and it can be cheaper. The problem is only when you think you bought ownership and the contract says license.

The five clauses that decide ownership

Read your contract, or the draft you are about to sign, and look for these five. If any is missing, ask for it in writing.

  1. An assignment clause. It should say the developer assigns to you all rights in the work they create for you, including code, designs, documentation and database structure. Look for the word "assigns", not "licenses".
  2. When ownership passes. The cleanest wording is "on payment", or "on creation, with payment due". Be wary of "on completion of all phases", because a dispute mid-project can leave you owning nothing yet.
  3. Pre-existing and third-party code. Developers reuse their own tools, and most modern software includes open-source parts (code that its authors share publicly under a license). Those are not assigned to you, and they should not be. They should instead be licensed to you in a way that lasts, cannot be withdrawn, and lets you use them as part of the finished product. Open-source licenses vary: the choosealicense.com summary shows that some require source code to be made available when you distribute the software, so ask which ones are in your build.
  4. Who else touched the code. If the developer uses subcontractors, ask for a promise that they have signed over their rights to the developer, who can then pass them on to you. Add AI coding tools to this question (see below).
  5. Handoff duties. Ownership you cannot reach is no use. The contract should require the developer to give you the source code, the accounts, the credentials and a setup note at the end, not just the running app.

What about code that AI wrote

If your developer used an AI coding tool, or you built part of the app yourself with one, ownership gets a second layer. The US Copyright Office published a report in January 2025 on whether AI output can be protected. Its conclusion was that, with technology generally available today, prompts alone do not give a person enough control over the output to make them its author. In plain words: code that an AI wrote from your instructions, with no real human editing, may not be protectable by copyright at all in the US. Human choices, edits and the way the pieces are arranged can still be protected.

That does not mean you cannot use or sell the software. It means the legal protection against copying may be thinner than you expect, and "who owns the code Claude wrote" does not have a simple answer. Two practical steps help. First, ask your developer in writing whether AI tools were used, and which ones. Second, read the AI tool's own terms for what they say about the output. If you built the app in an AI app builder, export the code so you hold a copy outside that tool. My comparison of an AI app builder versus hiring a developer covers the other trade-offs.

A worked example (made-up names and terms)

A landscaping company, Green Row, pays a freelancer $18,000 to build a quoting and scheduling app. The one-page agreement says: "Developer grants Client a non-exclusive license to use the software for Client's business. Developer retains all intellectual property." Two years later Green Row wants a new developer to add invoicing. What now?

  • The words "non-exclusive license" and "retains all intellectual property" mean Green Row never got ownership.
  • The license says nothing about changing the code or giving it to a new developer, so Green Row may need the original freelancer's permission.
  • The fix is cheap if you do it early: a short signed addendum assigning the code to Green Row, plus the repository and logins. It is expensive if you wait until there is a fight.

If the freelancer has vanished, see what to do when a developer leaves and you do not have the code.

The handoff checklist: what you should hold at the end

  • The full source code in a repository (the project folder that stores the code and its change history) under an account you own. GitHub's documentation describes how a repository can be transferred to a new owner, who can then manage its contents and settings straight away.
  • Hosting, database, domain and payment accounts in your company's name, with you as the owner and the developer as a user.
  • A list of every third-party service and key the app uses, and which are paid for by whom.
  • A setup note that lets a new developer run the app from scratch in about a day.
  • A copy of the database and the files.
  • A list of the open-source and third-party components, and their licenses.
  • The signed assignment, stored somewhere you can find it in five years.

My guide on who owns your website code and how to check access shows the same idea for a website, and how to move an AI-built app to production covers handing a prototype across safely.

Red flags in a developer contract

  • "Developer retains all intellectual property" with only a license to you.
  • Ownership passes only when the whole project is finished and accepted.
  • The app runs on hosting or a database account in the developer's name, with no promise to transfer it.
  • You get a running app but no source code ("compiled only").
  • No mention of open-source or third-party parts.
  • A big upfront fee, no staged handover.

A good contract does not have to be long. It has to be clear about these things. If you are comparing options, the guides on choosing a custom software development company and build versus buy help you decide whether you need to own the code at all.

Do you need to own it?

Sometimes the right answer is no. If the software is a tool your business uses but is not what you sell, a license from a vendor you trust may be cheaper and safer than owning code you must maintain. If the software is part of what makes your business different, or you plan to sell the business, owning it matters, and so does being able to prove it.

How I'd approach this

I would never start a build without a signed paper that says who owns what, and I would ask for it before the first payment, not after the last one. For custom code, I want the assignment, the handoff list above and the accounts in the client's name. That is how I work: Blur Studio's terms say that, unless the proposal says something different, you own the code and the work you pay for, once it is paid. I also hand over a written Owner's Manual at the end of a project. Where a project starts from a ready-built core that I license, I spell out which parts are licensed and which are your owned customizations, so there are no surprises.

If your current contract is unclear, do not wait for a dispute. Write to the developer, ask them to sign a short assignment and handoff, and book an hour with a lawyer to check the wording. That small cost is cheap insurance against paying twice.

Questions people ask

If I paid the invoice in full, do I own the code?

Not necessarily. In the US, copyright transfers only through a signed written document, or by an employment relationship. Payment alone may not give you ownership, and what you can do with the software then depends on the contract and your country's law. Check the contract for an assignment clause.

What is the difference between owning the code and having a license?

Ownership lets you change the code, hire anyone to maintain it, and sell it with your business. A license lets you use it on the terms in the contract and no more. Look for the words "assigns" versus "grants a license".

Do I own code that an AI assistant (a chatbot such as Claude or ChatGPT) wrote?

The rules are still developing. The US Copyright Office said in January 2025 that prompts alone do not make you the author of AI output, though human edits and arrangement can be protected. Read the AI tool's terms about output and ask a lawyer if the code is central to your business.

Can my developer reuse the code they wrote for me?

Only if the contract allows it. If you hold an assignment, the parts built for you are yours, but developers usually keep their general tools and know-how. Ask for a clause that separates your custom code from their pre-existing tools.

What should a developer hand over when the project ends?

The source code, the accounts for hosting, database, domain and payments in your name, a list of third-party keys and licenses, a setup note, a database copy and the signed assignment. See taking over software from a developer who left for what to do if they do not.

Do I need a lawyer?

For a small project, a clear signed assignment and handoff list may be enough. For anything central to your business, or if you plan to sell it or raise money, an hour with a lawyer who knows your country's rules is worth paying for. This page is not legal advice.

More in this topic: Problem solving: custom software (22 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…