Who owns the code a software development agency writes for clients?

Ownership of agency-written code depends on the contract. Copyright starts with the author, work made for hire is narrow for custom software, and most agreements use an assignment clause while the agency keeps background IP. Confirm the actual contract and consult counsel before assuming either side owns it.

Who owns the code a software agency writes for clients?

It depends on the contract. Under copyright law, the person who writes code is its author unless the work is a "work made for hire", and for an agency's outside contractors that status is narrow. Most agencies and clients instead settle ownership with an assignment clause in the statement of work, and agencies commonly keep their pre-existing frameworks and tooling as background IP.

For a referral partner, the practical point is that client deliverables and the agency's internal records are different layers. This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

What the rules actually say

The Copyright Act defines a work made for hire in two ways: a work prepared by an employee within the scope of employment, or a specially ordered or commissioned work that falls in one of nine listed categories and is covered by a signed written agreement saying it is a work made for hire. Custom software does not clearly fit those nine categories, which is why many contracts do not rely on the label alone.

The Copyright Office's Circular 30 explains the same two routes in plain terms: for a work made for hire the employer or commissioning party is the author. Where a work is not made for hire, ownership starts with the creator and moves by a signed transfer, which is why assignment clauses matter.

ConceptWhat it means in a software engagement
Employee workCode written by the agency's employees is owned initially by the agency, then passed to the client only if the contract says so
Contractor workFreelancers or offshore partners own their code unless an assignment or qualifying agreement says otherwise
Assignment clauseA signed transfer of rights to the client, often on payment
License clauseThe client gets rights to use the code, while the agency keeps ownership
Background IPFrameworks, libraries, scripts and templates the agency owned before the engagement

How it applies in common partner situations

SituationWhat to checkTypical outcome to confirm
Client paid for a custom buildAssignment wording and timing, such as on paymentClient owns the deliverable code; agency keeps background IP
Agency reuses its own frameworkBackground IP carve-out and any license-backFramework usually stays with the agency
Subcontractors helpedWhether each one signed an assignment to the agencyGaps can leave ownership unclear
Fixed-fee vs time-and-materialsWhether ownership passes at delivery or at final paymentDiffers by contract
Open-source componentsLicense terms of each componentGoverned by its own license, not the agency's

Note the licensing implication: the code in a client's repository is usually the client's concern, not an agency asset to license.

What an agency may still hold that is its own

Ask whether the statements of work keep internal frameworks, tooling and process records with the agency. These can include:

  • Delivery playbooks, estimation models and sprint retrospectives.
  • Internal ticket histories showing how the agency scopes, prioritizes and resolves work.
  • Design systems and component libraries retained as background IP.
  • Hiring, onboarding and code-review guidelines.
  • Proposals and internal pricing logic that identify no client.

Records that reveal a client's product, source code, credentials or customers are not in this list without that client's consent.

Questions to ask your counsel or the agency

  • Do our master agreement and standard SOW assign deliverables to clients, and when?
  • Which materials are listed as retained background IP?
  • Did every freelancer sign an assignment to us?
  • Does confidentiality cover our internal tickets that mention client work?
  • Could a licensee of our process records see client identifiers, and how would they be redacted?

Where this fits in a referral

Agencies with 50+ full-time employees at peak (contractors excluded), years of project history in Jira, Git and a PSA tool, and a clean separation between client deliverables and internal process material are the realistic candidates. See who qualifies for the baseline and the company fit checker for a preliminary screen. SourceX reviews rights with the agency, and nothing is shared without a signed agreement.

Related ownership questions follow the same pattern: pentest reports separate client findings from methodology, translation memories can be client-paid yet agency-held, and property management records default to the owner. Roll-ups can use the buy-and-build sectors guide to apply this check to every add-on.

How partner rewards work

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed.

Next step

If you know an agency that meets the baseline and has clear contracts, register as a partner and make the introduction. This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Is software always a work made for hire?

No. The statute recognizes employee work within the scope of employment and specially commissioned works in nine listed categories with a signed written agreement. Custom software often does not clearly fall in a listed category, so contracts usually use an assignment instead of relying on the label.

Does the client automatically own code after paying?

Not automatically. Ownership passes according to the contract. Some agreements assign rights on payment, some on delivery, and some only license the code. Reading the assignment and payment clauses is the only reliable way to know.

What is background IP in an agency contract?

It is material the agency owned or developed before or apart from the engagement, such as frameworks, libraries and templates. Contracts often carve it out so the agency keeps ownership and grants the client a license to use it inside the deliverable.

Can an agency license its internal project records?

Possibly, if the records are its own and contain no client-identifying or confidential material. Process records such as estimation models and delivery playbooks are more likely to be the agency's. Counsel should confirm against its client contracts.

What happens when freelancers wrote part of the code?

Without a signed assignment from each freelancer, ownership can stay with the individual, which can leave gaps in what the agency can pass to a client. Agencies should confirm every contributor signed an assignment.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment