Software IP Assignment Agreement: What Developers Must Sign

byAlex Solo10 min read

Maya pays a freelance developer $18,000 to build the first version of her app. The code is delivered, the invoice is paid, and the product goes live. Six months later, an investor asks a simple question: does the company actually own the software?

That question can make your stomach drop. Paying for code feels like it should mean you own it, but under US copyright law, that isn't always how it works.

The good news is that this can usually be fixed with the right paperwork. A clear software IP assignment agreement or IP assignment agreement can help make sure your business owns the code, can keep building on it, and won't hit avoidable issues during fundraising, a sale, or a dispute with a developer.

Do You Own Software Just Because You Paid For It?

No, paying a developer's invoice doesn't automatically mean your business owns the copyright in the software.

Under the US Copyright Act, copyright usually starts with the person who creates the work. For software, that generally means the person who writes the source code owns the copyright at first, unless there's a written agreement or a specific legal rule that changes that position.

This is where many businesses get caught. You may have paid for:

  • the developer's time
  • a working product
  • a set of deliverables
  • a license to use the code

But that isn't always the same thing as owning the copyright in the code itself.

If you only have an invoice, email trail, or statement of work, you might have an implied license to use the software for the project. That can be useful, but it may not let you:

  • modify the code freely
  • sell or license the product to customers
  • transfer the software to a buyer
  • stop the developer from reusing parts of the code elsewhere
  • prove clean ownership to investors

That's why a software ownership agreement or code assignment agreement should be signed before work starts where possible. If the work is already done, you can still use a confirmatory assignment to tidy up ownership, but it's usually easier while everyone is still on good terms.

What Is A Software IP Assignment Agreement?

A software IP assignment agreement is a written contract where the developer transfers ownership of specified intellectual property rights to your business.

For a software project, this usually focuses on copyright in the code and related materials. It may also deal with inventions, documentation, designs, databases, APIs, configuration files, scripts, confidential information, and other project assets.

A strong agreement should make clear:

  • Who is assigning the rights - usually the individual developer or the development company that actually owns the work.
  • Who is receiving the rights - usually your company, not you personally.
  • What is being assigned - such as source code, object code, documentation, UI designs, technical specifications, test scripts, and project files.
  • When ownership transfers - for example, as the work is created, when payment is made, or when deliverables are accepted.
  • What is excluded - such as the developer's pre-existing tools, frameworks, templates, or general know-how.

The word assignment matters. A license gives you permission to use something. An assignment transfers ownership. If your business needs to own the product so it can commercialize, raise capital, grant customer licenses, or sell the business later, you'll usually want an assignment rather than just a software license.

You should also check that the person signing has the right to assign the IP. If your developer used subcontractors, employees, or offshore team members, your agreement should require them to secure all necessary assignments from those people too.

What Must A Developer Sign To Transfer Code Ownership?

A developer should usually sign a software IP assignment agreement, or a software development agreement that contains clear software development agreement IP ownership terms.

The right document depends on timing. If you're about to start the project, it's often cleaner to include the assignment inside the main development agreement. If the code has already been delivered, a separate assignment may be the better fix.

Before Work Starts

Before the developer begins, your contract should cover both the commercial deal and the IP position. That means it should address scope, fees, milestones, support, confidentiality, acceptance testing, and ownership.

For IP, look for clauses that say the developer assigns to your business all rights, title, and interest in the deliverables, including copyright, once created or once paid for. Your attorney can tailor the timing to match your payment structure and bargaining position.

After Code Has Already Been Delivered

If you've already received code, don't panic. You may still be able to get a short IP assignment signed.

Start by collecting:

  • the original proposal or statement of work
  • invoices and proof of payment
  • emails or messages discussing ownership
  • repository access records and commit history
  • a list of deliverables you received
  • details of any open-source or third-party libraries used

Then ask the developer to sign a confirmatory assignment that clearly identifies the project and transfers the relevant IP to your company. If the relationship is tense, get help before sending anything. The way you frame the request can affect whether the developer cooperates.

Employee Developers

If the developer is your employee, copyright ownership can work differently under the Copyright Act's work made for hire rules. Code created by an employee within the scope of employment may be owned by the employer from the start.

Even so, many companies still use employee invention and IP assignment clauses because state law, job scope, side projects, and timing can create gray areas. Your state's rules can affect these clauses, so it's worth getting them tailored.

What Clauses Should A Software Ownership Agreement Include?

A software ownership agreement should clearly identify the software, assign the relevant IP, deal with third-party materials, and protect your access to the working code.

Here's a practical outline you can use as a starting point. This isn't a finished legal document, and a lawyer should tailor it before you use it.

  1. Parties - write the legal names of your company and the developer or development company.
  2. Project Description - describe the software, product, module, app, website, integration, or platform being built.
  3. Deliverables - list what must be delivered, including source code, object code, documentation, credentials, design files, test files, build scripts, and deployment materials.
  4. Assignment Of IP - state that the developer assigns all rights, title, and interest in the deliverables to your company.
  5. Timing Of Transfer - say whether rights transfer on creation, payment, acceptance, or another milestone.
  6. Source Code Access - require delivery of current, complete, buildable source code and repository access.
  7. Pre-Existing Materials - identify tools, libraries, templates, frameworks, and reusable code the developer already owned before the project.
  8. License To Pre-Existing Materials - give your business the rights it needs to use any excluded materials as part of the software.
  9. Third-Party And Open-Source Components - require the developer to disclose these components and comply with their license terms.
  10. Developer Warranties - have the developer promise that they created the work or have the rights needed to transfer it.
  11. Confidentiality - protect your product plans, source code, customer information, business data, and trade secrets.
  12. Further Assurances - require the developer to sign extra documents if needed to confirm ownership later.

You may also need clauses covering support, bug fixes, security, service levels, moral rights where relevant, payment disputes, and termination. For confidential technical information, the federal Defend Trade Secrets Act may also be relevant, especially if you want to preserve trade secret protection around source code, algorithms, data models, or product architecture. If the agreement governs trade secrets or confidential information, it should include the DTSA whistleblower immunity notice required by 18 U.S.C. Section 1833(b)(3), or cross-reference a compliant policy, especially for employee, contractor and consultant agreements.

How Should You Deal With Libraries, Tools And Pre-Existing Code?

You should separate code your business owns from materials the developer brings to the project, then make sure you have the rights you need to use the full product.

Most developers don't write everything from scratch. They may use:

  • open-source libraries
  • commercial SDKs
  • internal templates
  • reusable authentication modules
  • UI components
  • deployment scripts
  • testing tools

That isn't automatically a problem. In fact, it can save you time and money. The risk isn't knowing what sits inside your product or what rules apply to it.

For example, Jordan's SaaS startup pays a contractor $25,000 to build a customer dashboard. The contractor delivers the dashboard, but later Jordan learns that a key reporting feature uses a library with license terms that don't fit the startup's planned enterprise product. The company now has to replace that component before a customer rollout, which delays launch by six weeks.

A good contractor software rights clause should require the developer to disclose third-party materials before delivery, or at least before they're included in production code. You'll also want a schedule that lists each component, its license type, and any restrictions that matter to your business.

For the developer's own pre-existing tools, you have two main options:

  • Assignment - the developer transfers ownership of those materials to your company. This is less common for reusable tools because developers often need them for other clients.
  • License - the developer keeps ownership, but gives your company a broad enough license to use, modify, host, maintain, and commercialize your software.

Don't leave this to assumptions. If the developer is allowed to keep using generic know-how and tools, say so. If your product needs exclusive ownership of a particular module, say that too.

What If The Developer Refuses To Sign After The Work Is Done?

If a developer refuses to sign after delivery, your first step is to review what you already have and work out your practical leverage.

Don't start by threatening legal action. Start with documents and access.

  1. Gather The Paper Trail - collect contracts, proposals, statements of work, invoices, payment records, emails, messages, and repository activity.
  2. Check Existing Terms - look for wording about ownership, licensing, deliverables, confidentiality, subcontractors, open-source software, and payment milestones.
  3. Confirm Access - make sure your company controls repository access, hosting accounts, admin credentials, domain accounts, cloud services, and deployment pipelines.
  4. Map What You Need - list the exact rights you need, such as ownership of custom code, a license to tools, or a release of claims after final payment.
  5. Make A Commercial Proposal - offer a simple, fair assignment that matches what both sides likely expected when the project began.
  6. Get Help If There's Resistance - if the developer says they own the code, demands extra money, or threatens to disable access, speak with a licensed attorney quickly.

Your options will depend on the contract wording, payment status, who wrote the code, whether subcontractors were involved, and the law of the state governing the contract.

If you're heading into fundraising or a sale, this issue becomes more urgent. Investors and buyers often ask for an IP chain-of-title review. They may want to see signed agreements from founders, employees, contractors, and key vendors showing that your company owns or can legally use its core technology.

Where possible, fix the issue before due diligence begins. A clean assignment signed today is usually much easier than explaining a gap later.

Frequently Asked Questions

Can A Developer Keep Reusing Code They Wrote For My Business?

It depends on your contract. If the code was assigned exclusively to your company, the developer usually shouldn't reuse that same custom code. If the agreement excludes reusable tools or general know-how, they may be able to keep using those parts.

Registration isn't required for copyright to exist, but it can be valuable. For US works, registration with the US Copyright Office is generally needed before filing a copyright infringement lawsuit, and timely registration can affect available remedies.

Should The Agreement Cover Trademarks And Product Names Too?

Usually yes, if the developer is creating names, logos, icons, or brand assets. Trademark rights are different from copyright, and federal trademark registration is handled by the USPTO, so these items should be addressed separately.

Can I Use A Free Template For A Code Assignment Agreement?

You can, but be careful. Free templates often miss project-specific issues like source code access, open-source libraries, developer tools, subcontractors, and timing of ownership transfer.

Key Takeaways

  • Paying a developer doesn't automatically mean your business owns the software copyright.
  • A software IP assignment agreement transfers ownership, while a license only gives permission to use the code.
  • Your agreement should deal clearly with source code, deliverables, pre-existing tools, third-party libraries, open-source components, confidentiality, and trade secret notices.
  • If the code has already been delivered, you may still be able to fix the gap with a confirmatory assignment.
  • State law, contract wording, employee status, and subcontractor involvement can change the answer, so get tailored help where the stakes are high.

If you'd like help with developer IP assignments, software ownership clauses, source code access terms, DTSA trade secret notices, or a confirmatory assignment for code you've already received, you can reach our team at (888) 449-8437 or team@sprintlaw.com. Where legal services are required, they're provided by licensed US lawyers at ElevateNext US, LLC, a trusted US law firm, through the Sprintlaw platform.

Alex Solo
Alex SoloCo-Founder

Alex is Sprintlaw's co-founder and a legal technology leader. He holds law and media degrees from the University of Sydney and has been recognized by Australasian Lawyer, Lawyers Weekly and the Sydney Young Entrepreneur Awards for his work building Sprintlaw and improving access to business legal support.

Need legal help?

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Keep reading

Related Articles

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.