All articles

Handoff

Who owns the code? IP basics for software founders

August 19, 2026 · 2 min read

Who owns the code? IP basics for software founders. ProductScott, Handoff.

Here is a fact that surprises many founders: paying someone to build your software does not automatically make you the legal owner of it. Intellectual property rules are not common sense, and the gap can cost you. This is a plain-English primer, not legal advice, so confirm specifics with a lawyer.

The short answer

Ownership of code depends on your agreement, not just on who paid. Without an explicit IP assignment in your contract, a contractor may legally retain rights to what they built. Put ownership in writing before work starts, and you avoid an ugly surprise later.

Why "I paid for it" is not enough

  • Contractors are not employees. Work made by employees within their job often belongs to the employer by default; work by independent contractors frequently does not, unless assigned in writing.
  • Defaults vary. The rules differ by jurisdiction and situation, so relying on "obviously it's mine" is risky.
  • Open-source and third-party components. Your product may include code under licenses with their own terms; you should know what is in it.

The practical upshot: get it in writing, do not assume.

What to put in your agreement

  • An IP assignment clause. All work product, code, designs, assets, is assigned to you (or your company).
  • A statement on pre-existing and third-party code. What the developer is bringing in and under what license.
  • Confidentiality. Protecting your idea and materials (see how to protect your software idea).
  • Deliverables and access. Tied to the practical ownership of code and accounts (see own your code and accounts).

Legal ownership vs practical ownership

There are two layers: the legal right to the IP (your contract) and the practical ability to use it, the code, accounts, and documentation in your hands. You need both. Owning the rights but not having the runnable code, or vice versa, still leaves you stuck.

A product simulation is delivered to cover the practical side, runnable code, database, and documentation that are yours, and you should pair any build engagement with a clear IP assignment so the legal side matches. Together, that is real ownership.

Building something you want to fully own? Start a project, and get the IP terms in writing.

Frequently asked

If I pay for it, don't I automatically own it?

Not necessarily. Depending on the arrangement and jurisdiction, a contractor may retain ownership of code they wrote unless your agreement explicitly assigns it to you. Get an IP assignment in writing; do not assume.

What is an IP assignment clause?

A contract clause stating that all intellectual property created for you, code, designs, and related work, belongs to you. It is the simplest way to make sure 'I paid for it' actually means 'I own it.'

Have an idea or a problem to solve?

ProductScott engineers it end to end: documentation, a working codebase, and a runnable mock database, delivered in weeks.

Start a project