Back to all posts
Buyer's Guide7 min read·October 25, 2026

Who Owns the Code When You Hire a Software Agency?

TB
ThynkBlox Team
Engineering

Who owns source code in outsourced software development?

Ownership depends on the written agreement and the law that applies to it, so do not assume that paying an agency settles the question. Before development starts, agree in writing which intellectual property transfers to your business, which components you receive permission to use, and when those rights take effect. Establish access to the code repository from the start, then document who controls the accounts and what happens when the engagement ends.

Treat ownership and access as separate requirements. Ask for both a clear agreement and a practical way to continue the project with another team.

What should the ownership agreement cover?

Ask for an explicit intellectual property assignment covering the custom work you are buying. Have a lawyer check its wording, scope, timing, and formal requirements under the applicable law rather than relying on a general promise that “the code is yours.”

Define the deliverables beyond application code. Your requested scope should include custom designs, database structures, automated tests, documentation, and instructions for building and releasing the software.

Use a schedule like this to make the discussion concrete:

ItemWhat to agree
Custom application codeWhich rights transfer, to which legal entity, and when
Designs and documentationWhich editable originals and supporting materials are included
Existing agency componentsWhat the agency retains and what permission your business receives
Third-party componentsWhich licenses apply and what obligations need review
Incomplete workWhat you receive if the project ends before completion
Work by subcontractorsHow the agency documents its authority to transfer the agreed rights

Avoid leaving “project materials” undefined. Name what another developer would need to understand, maintain, and extend the product.

When should intellectual property transfer?

Make the transfer trigger explicit. Discuss whether ownership transfers as work is created, after each paid milestone, or after final payment. These are terms to negotiate, not assumptions to leave until delivery.

If transfer depends on payment, define which payment triggers which rights. Ask what happens to a completed, paid milestone if a later milestone is disputed.

Also agree on your permission to test and operate the software before the final transfer. Put the treatment of rejected work, cancelled features, and unfinished development in writing.

Ask the agency to explain how it obtains the necessary rights from employees and subcontractors. The legal requirements for a valid transfer can vary by jurisdiction, so take legal advice on them.

Why should repository access start immediately?

A repository stores the project's source code and change history. Access lets your team inspect what has been delivered, but repository access alone does not establish copyright ownership.

Request that the project repository sit within an organisation account your business controls. Give the agency access through individual accounts, with permissions appropriate to each person's work.

Before development begins, agree that:

  • Your business has an administrator who can manage access.
  • Project work reaches the agreed repository regularly.
  • Your team can download the source and inspect its history.
  • Instructions explain how to build, test, and release the application.
  • Access and handover terms remain clear if an invoice is disputed.

If the agency proposes using its own repository, ask how you will receive ongoing access and a complete transfer. Make that arrangement part of the agreement.

Can you own every component in the application?

Separate custom work from existing components. Ask the agency to identify reusable code it already owns before including that code in your project.

For anything the agency retains, request written permission broad enough for your intended use. Discuss whether your business and future suppliers may operate, copy, modify, and maintain it, and whether that permission continues after termination.

Third-party software needs separate review. An agency's assignment of custom work does not replace the licenses governing third-party components. License obligations depend on the component and how it is used or distributed.

Request an inventory of dependencies, commercial tools, fonts, images, and other licensed materials. Ask who pays for renewals and whether a change of supplier affects your ability to use them.

For more background, read open-source software: pros and cons.

Who should control the accounts?

Ask your business to hold the primary accounts for services essential to operating the product. Include the domain, hosting, application distribution, billing, analytics, and other services the project needs.

Use business-controlled contact details and recovery methods. Invite the agency through its own accounts rather than sharing one person's login.

Record the following for each service:

  • The account owner and a backup administrator
  • Who pays the bill and receives renewal notices
  • Who controls recovery and authentication
  • What access the agency needs
  • How access will be removed or transferred

If a service must remain under the agency's account, agree on the reason, exit process, and any limits before choosing it. Ask the agency to demonstrate the proposed transfer route rather than leaving it as a handover promise.

Access decisions also deserve a security review; see data security in modern applications.

What should happen when the engagement ends?

Write the exit arrangement while both parties are planning a successful project. Cover an ordinary completion, an early cancellation, and a change of supplier.

Specify the handover materials, delivery method, responsible person, and any agreed assistance fees. Include:

  • Complete source code and available change history
  • Editable designs, tests, and technical documentation
  • Build and release instructions
  • An inventory of services and software licenses
  • A record of unfinished work and known defects
  • A secure process for transferring credentials and removing access

Agree separately on the return or deletion of your business data and confidential materials, subject to applicable obligations.

Make a handover exercise part of acceptance: ask someone outside the delivery team to build and run the application using the supplied materials. Use documentation best practices in software projects to shape that requirement.

What would a clear arrangement look like?

Consider an illustrative project for a customer booking application.

The buyer requests assignment of the custom booking logic, interface designs, tests, and documentation. The agency identifies an existing utility library it intends to retain and proposes a continuing license that permits maintenance by another supplier. Third-party packages appear in a separate inventory for review.

The repository and operating accounts sit under the buyer's control. Each milestone identifies its deliverables and transfer trigger. The exit schedule covers paid work, incomplete work, documentation, and transition assistance.

This is a discussion outline, not a contract clause. Have the final agreement checked against the actual project and applicable law.

What common mistakes should you avoid?

Treating payment as the ownership clause. Ask for express terms identifying the work, rights, recipient, and transfer trigger.

Accepting a final download as the whole handover. Request history, editable materials, tests, and instructions as well.

Assuming everything is custom. Identify retained agency materials and third-party components before approving their use.

Leaving accounts with an individual. Establish business-controlled administration and recovery.

Waiting until termination to discuss access. Agree on the exit process before development starts.

Use these points alongside the questions in how to choose a software development agency.

What are the frequently asked questions?

Does paying the invoice mean I own the code?

Do not rely on payment alone. Ask a lawyer to confirm how the agreement and applicable law establish your rights, including when any assignment takes effect.

Can an agency reuse code from my project?

Make your expectations explicit. Separate custom work assigned to your business from retained tools, reusable components, and confidential materials. Have the agreement define permitted reuse.

What if I am buying a subscription product?

Ask for the product's license and exit terms. A subscription purchase may provide access to software without transferring ownership of its source code.

What should I ask before signing?

Ask: “If we appoint another developer, what rights, code, accounts, and documentation will they need, and how will we receive them?” Require a written answer reflected in the agreement.

Ownership also depends on who writes the code, so ask the subcontracting questions before you sign.


*This post is general information, not legal advice. Consult a qualified lawyer about your agreement. Last reviewed: October 2026.*

Leaving an agency? See the handover checklist for what to receive and how to prove it works.

*Planning a software build? Start a conversation about the scope, access, and handover your project needs.*

Ready to build?

Let's turn these ideas into your next product.

Start your project