If your startup builds software, the code your team writes is not automatically owned by your company. Neither is the design work, the algorithms, the database architecture, or the marketing content. Under US copyright law, the person who creates something owns it — unless a written agreement transfers that ownership to the business.
For most early-stage startups, this creates a serious legal problem that does not surface until it is too late: at a funding round, an acquisition, or a dispute with a departing co-founder. Investors and acquirers run IP due diligence as a standard step. If your company cannot prove it owns its own technology, the deal slows, the valuation drops, or the transaction collapses.
IP assignment agreements fix this by formally transferring ownership of intellectual property from individuals to the company. This article explains how these agreements work, who needs to sign them, and what happens when they are missing.
1. What Is an IP Assignment Agreement?
An IP assignment agreement is a written contract that transfers ownership of intellectual property — including source code, patents, copyrights, trade secrets, designs, and inventions — from a creator to another party, typically the company. In a startup context, the agreement ensures that everything your team builds becomes corporate property, not personal property belonging to the individual who built it.
These agreements go by several names depending on the context: Proprietary Information and Inventions Agreement (PIIA) for employees, Confidential Information and Invention Assignment Agreement (CIIA) for contractors, and IP Assignment Agreement or IP Transfer Agreement in general contract contexts. The name matters less than the substance: the agreement must clearly identify what is being transferred, confirm present ownership transfer (not a future promise), and be signed by both parties.
Our intellectual property legal services cover the full range of IP agreements for technology businesses, from founder assignments to contractor NDAs.
2. Who Needs to Sign One?
Co-Founders
Founders routinely begin building a product before formally incorporating the company. During that period, any code written, designs created, or inventions developed belong to the founder individually — not the company, which did not exist yet. At the time of incorporation, each founder must sign an IP assignment agreement transferring all pre-incorporation work to the newly formed entity. Skipping this step means the company may lack legal ownership of the core product it is trying to sell.
Employees
The US “work made for hire” doctrine under 17 U.S.C. § 101 provides some protection: works created by employees within the scope of employment can be treated as works made for hire, with copyright vesting in the employer. But this doctrine has important limits. It does not cover patents or trade secrets, and disputes frequently arise over whether work falls within the scope of employment — particularly for engineers who work remotely, build tools outside core hours, or contribute to personal projects using company resources.
A signed IP assignment agreement eliminates this ambiguity. Every employee who contributes to the product — not just engineers, but designers, writers, marketers, and product managers — should sign one before their first day of work.
Contractors and Freelancers
This is where startups make the most costly mistakes. The work-for-hire doctrine generally does not apply to independent contractors under US copyright law — unlike employees, contractors retain ownership of what they create unless a written agreement explicitly assigns that ownership to the company. A verbal understanding, a Slack message, or a scope-of-work document that describes the deliverable does not transfer IP rights.
Every contractor who touches your codebase, creates designs, writes content, or develops any company asset must sign a formal IP assignment agreement before work begins. This includes overseas contractors, one-time freelancers, and technical advisors who contribute even informally.
3. What the Agreement Must Include
A properly drafted IP assignment agreement covers more than a simple transfer of rights. Key provisions include:
- Assignment scope: The agreement must define what categories of IP are assigned — copyrights, patents, patent applications, trade secrets, trademarks, moral rights (where applicable), and any related rights. Vague language creates gaps.
- Present transfer language: The agreement should use language that transfers ownership immediately, not as a future promise. “Assignor hereby assigns” is a present-tense transfer. “Assignor agrees to assign” is a promise that courts have sometimes found unenforceable before the specific IP exists.
- Prior inventions carve-out: Employees and contractors may have pre-existing IP they want to retain. A clearly defined prior inventions schedule attached to the agreement protects the company from claiming ownership of work that predates the relationship, while protecting the individual from unexpected claims.
- Moral rights waiver: In some jurisdictions, creators hold moral rights that cannot be transferred — only waived. The agreement should include an explicit moral rights waiver where permitted by law.
- Confidentiality obligations: IP assignment agreements typically include confidentiality provisions covering proprietary information, trade secrets, and business strategy.
- Cooperation clause: The assignor agrees to assist with patent filings, execute additional documents, and support the company’s efforts to register or enforce the assigned IP.
4. The “Work Made for Hire” Doctrine and Its Limits
Some founders assume that paying someone for work automatically transfers IP ownership. This is incorrect under US law. The work-for-hire doctrine applies to employees working within the scope of their employment for certain copyright-eligible works. It does not apply to contractors (without a written agreement specifying work-for-hire status), to patents, or to work created outside a defined scope of employment.
Even for employee-created works, the statutory definition of “work made for hire” under the Copyright Act covers only nine specific categories of works when created by contractors under a written work-for-hire agreement. Software that does not fall into one of those categories requires an explicit IP assignment clause to transfer copyright ownership.
A technology contract lawyer familiar with IP law structures these agreements to account for both copyright and patent rights, identifies which works qualify for work-for-hire treatment, and fills the gaps with explicit assignment language where the doctrine does not apply.
5. What Happens Without a Signed Agreement
The consequences of missing IP assignments typically do not surface during the early startup phase. The problem appears when your company needs to prove ownership: at a Series A due diligence review, when preparing for an acquisition, or when a former contractor claims rights to code they wrote for you.
Investors have rejected funding rounds because a critical piece of the product was written by a contractor who never signed an IP assignment agreement. In those situations, the startup faces a choice: track down the former contractor, negotiate a retroactive assignment (often expensive), or remove and rewrite the disputed code. Acquirers face the same problem, and a title defect in IP ownership is one of the most common reasons technology M&A transactions are restructured or delayed.
Courts treat IP ownership disputes as contract disputes. Without a signed agreement, the company has no contract to enforce.
6. Retroactive IP Assignments
If your startup already has co-founders, employees, or contractors who contributed to the product without signing IP assignment agreements, you can address this retroactively. A retroactive IP assignment agreement transfers previously created IP to the company as of a specified date.
Retroactive assignments are valid under US contract law when the parties agree in writing. However, complications arise when the assignor is no longer contactable, when the assignor disputes the scope of what they created, or when the assignor has already assigned or licensed the same IP to a third party. The longer the delay, the harder and more expensive the fix.
For startups preparing for a fundraising round or acquisition, a technology lawyer can conduct an IP assignment audit — reviewing what has been signed, identifying gaps, and drafting retroactive assignments or alternative remedies for missing documentation.
Frequently Asked Questions
Does paying a contractor automatically give my company ownership of what they create?
No. Under US copyright law, contractors retain ownership of their work unless a written agreement explicitly assigns that ownership to the company. Payment alone does not transfer IP rights. You need a signed IP assignment agreement before work begins.
Can I use a template IP assignment agreement I found online?
A generic template may miss jurisdiction-specific requirements, fail to address patents separately from copyrights, or use future-tense assignment language that courts have found unenforceable in certain disputes. Templates also do not account for your specific IP categories, contractor relationships, or pre-existing work by founders. A technology lawyer drafts agreements tailored to your actual situation.
What is a prior inventions schedule and do I need one?
A prior inventions schedule is a list, attached to the IP assignment agreement, of any IP the employee or contractor created before joining the company and wants to exclude from the assignment. Including one protects the company from later disputes about scope and protects the individual from unexpected ownership claims on their pre-existing work.
What happens if a co-founder leaves before signing an IP assignment agreement?
If the departing co-founder created core product IP before signing an assignment agreement, they may retain legal ownership of that work. The company’s options include negotiating a retroactive assignment, seeking a license to use the IP, or in some cases, removing and rewriting the disputed material. This situation is significantly more difficult and expensive than getting the agreement signed at the outset.
Do non-technical founders and employees need to sign IP assignment agreements?
Yes. IP assignment agreements apply to any employee or contractor who creates work product for the company, including written content, marketing materials, brand designs, business strategies, and product documentation. Copyright protects these works, and ownership should be formally assigned to the company regardless of whether the creator is a developer.
When should my startup’s IP assignment agreements be signed?
Before work begins. For founders, IP assignments should be executed at or immediately after incorporation. For employees, the agreement should be signed before the first day of work, as part of the onboarding process. For contractors, the agreement should be signed before the engagement starts and before any deliverables are created.
Protecting Your Company’s Most Valuable Asset
Your technology is your business. If the people who built it never signed an agreement transferring ownership to your company, your business does not fully own what it has built. That gap is manageable early. By the time investors or acquirers discover it, the cost of fixing it grows significantly.
Hansen Tong at TOSLawyer.com works with startups, SaaS companies, and technology businesses on IP assignment agreements, contractor agreements, and the full range of technology contracts. If your company’s IP ownership needs a review — or if you are preparing for a fundraising round and want to audit your documentation — contact TOSLawyer.com to schedule a consultation.