IP Assignment Clauses: The Clause That Destroys Startups (and How to Fix It)

A Series A round dies in due diligence because the lead developer — a contractor who built the MVP — never assigned the IP to the company. The investor’s counsel finds no CIIA, no IP assignment clause, and no work-for-hire agreement. The contractor left eight months ago. Now the company’s entire codebase belongs, legally, to someone who isn’t answering emails.

This isn’t a hypothetical. According to Jones Day’s analysis of IP due diligence in venture capital, IP chain-of-title failures are among the most common diligence killers in early-stage financings and acquisitions. With 85% of VC-backed exits occurring through acquisitions — where the buyer is literally paying for the company’s IP — a missing assignment clause doesn’t just create legal risk. It destroys the entire value proposition.

If you advise startups, review contractor agreements, or handle employment contracts, this article covers the five IP assignment mistakes that cause the most damage and how to prevent each one. Upload any contractor or employment agreement to Clause Labs to check whether the IP provisions actually protect the company — the free analyzer flags missing assignments, overly broad language, and absent prior inventions carve-outs in under 60 seconds.

What Is an IP Assignment Clause?

An IP assignment clause is a contractual provision that transfers ownership of intellectual property from the creator (employee, contractor, co-founder) to the company. Without one, the default rules of copyright, patent, and trade secret law determine ownership — and those defaults rarely favor the company.

The key concepts:

Assignment vs. license. An assignment permanently transfers ownership. A license grants permission to use. If your client needs to own the IP outright — and in most startup contexts, they do — a license isn’t sufficient. Investors and acquirers want clean title, not a license that could be revoked.

Types of IP covered. A comprehensive assignment covers patents, copyrights, trade secrets, trademarks, and moral rights (relevant in Canada and the EU). Narrow assignments that cover only “inventions” may miss copyrightable code, designs, or written content.

Work-for-hire vs. assignment. Under 17 U.S.C. § 101, a “work made for hire” is automatically owned by the employer. But the work-for-hire doctrine only applies to employees creating within the scope of employment, or to independent contractors creating works in nine specific statutory categories (and only with a written agreement). For most contractor-created work, work-for-hire doesn’t apply — explicit assignment is required.

The 5 IP Assignment Mistakes That Destroy Startups

Mistake 1: No IP Assignment from Founders

The problem. Two founders build a product for six months before incorporating. They form the company, issue stock, hire employees, and raise a seed round. But neither founder ever assigned the IP they created — the code, the algorithms, the designs, the brand — to the company.

The legal reality. Each founder personally owns their contributions. The company has, at best, an implied license to use the IP. If one founder leaves, they can argue they own “their” portion of the codebase. If the company is acquired, the buyer’s counsel will find the gap in due diligence.

The fix. Every founder should sign a Confidential Information and Inventions Assignment Agreement (CIIA) at incorporation — or ideally, before. According to Cooley GO’s guidance on CIIAs, the CIIA should assign all IP created for the company, include a prior inventions schedule, and cover confidentiality obligations. This is standard Silicon Valley practice, and investors expect it.

What the CIIA should include:
– Assignment of all IP created for or related to the company’s business
– Prior inventions schedule (Exhibit A) listing excluded pre-existing IP
– Confidentiality obligations
– Cooperation clause (founder will sign additional documents to perfect assignment)
– Representations that the founder has the right to assign

Mistake 2: Contractor Work Without IP Assignment

The problem. A startup hires a freelance developer to build the MVP. The contractor agreement covers scope, timeline, and payment — but says nothing about who owns the resulting code. Six months later, the contractor is building a competing product using “their” code.

The legal reality. Unlike employees, contractors own what they create by default. As California’s IP assignment framework makes clear, the statutory protections for employee inventions (Labor Code § 2870) don’t extend to independent contractors. There’s no statutory scheme governing contractor IP assignment — the parties must contractually address it. If the contract doesn’t include an explicit IP assignment, the contractor retains all rights.

Work-for-hire won’t save you in most cases. The work-for-hire doctrine under copyright law only applies to independent contractors in nine specific categories — including contributions to collective works, parts of a motion picture, and compilations — and requires a written agreement. Custom software development generally doesn’t qualify.

The fix. Every contractor agreement must include:
– Explicit IP assignment (not just work-for-hire language)
– Scope definition covering all deliverables and work product
– Representations that the contractor has the right to assign and hasn’t used third-party IP without authorization
– A cooperation clause for perfecting the assignment

Mistake 3: Overly Broad IP Assignment in Employment Agreements

The problem. An employment agreement states: “Employee assigns to Company all inventions, works of authorship, and intellectual property created during the term of employment.” The employee’s weekend side project — an app completely unrelated to the employer’s business, built on the employee’s personal laptop, on personal time — is now arguably company property.

The legal reality. Overbroad assignment clauses create three risks. First, they may be unenforceable in states with employee invention protection statutes. California Labor Code § 2870 explicitly protects inventions developed entirely on personal time without employer resources, provided they don’t relate to the employer’s business. Similar statutes exist in Delaware, Illinois, Minnesota, North Carolina, Washington, and several other states. Second, overbroad clauses generate employee resentment and departures. Third, if the employee’s personal invention has third-party encumbrances (like an open-source license), those encumbrances now affect the company.

The fix. Narrow the assignment to IP that is:
– Created within the scope of employment, OR
– Created using company resources, equipment, or information, OR
– Related to the company’s current or reasonably anticipated business

And explicitly exclude inventions covered by California Labor Code § 2870 or equivalent state protections. The agreement should include a written notice that the assignment doesn’t cover protected personal inventions.

Mistake 4: No Prior Inventions Carve-Out

The problem. A senior engineer joins a startup and signs a standard IP assignment. The engineer previously developed a machine learning framework on their own time — a framework they now use (with modifications) in their work for the startup. Without a prior inventions carve-out, that framework is now arguably assigned to the company.

The legal reality. If the prior invention has encumbrances — an existing license to another company, open-source obligations, or a co-ownership arrangement — those encumbrances now affect the startup’s IP portfolio. During due diligence, an acquirer or investor will discover the clouded title and demand indemnification, escrow, or a price reduction.

The fix. Every CIIA and employment agreement should include a prior inventions schedule — typically Exhibit A — where the employee or contractor lists all pre-existing IP that is excluded from the assignment. The schedule should include:
– Description of the prior invention
– Date of creation
– Any existing licenses or encumbrances
– Whether the employee intends to use it in company work (and if so, a separate license grant)

If the employee states “none” on the prior inventions schedule, that’s a representation the company can rely on.

Mistake 5: Missing License-Back After Assignment

The problem. A contractor builds a web application using their proprietary framework — a toolkit they’ve developed over years and use across multiple client projects. The contractor agreement assigns “all IP created in connection with the Services” to the client. Technically, the contractor can no longer use their own general-purpose framework for other clients.

The legal reality. This creates an unenforceable or unworkable provision. No contractor will actually stop using their own development tools. But if the assignment is drafted broadly enough, the client could theoretically enforce it — or at minimum, it creates a dispute.

The fix. Include a license-back clause:

Contractor assigns to Company all right, title, and interest in Deliverable IP
(defined as intellectual property created specifically for Company under this
Agreement). Company grants Contractor a non-exclusive, perpetual, royalty-free
license to use, modify, and distribute Background IP (defined as pre-existing
tools, frameworks, and methodologies owned by Contractor prior to or independent
of this engagement) for any purpose, including for other clients.

This structure gives the company clean ownership of the custom work while letting the contractor continue using their general-purpose tools.

If you’re reviewing a contractor agreement right now, Clause Labs’s Solo tier ($49/month for 25 reviews) catches all five of these IP assignment mistakes — including missing prior inventions carve-outs and work-for-hire misapplication — across every contract type.

IP Assignment Clause Elements: The Complete Checklist

A well-drafted IP assignment clause should address each of these elements:

Scope of assignment. What specific IP is being assigned? “All intellectual property” is common but can be overbroad. Better: “All Deliverable IP, including inventions, works of authorship, designs, and trade secrets created in the performance of Services under this Agreement.”

Timing of assignment. When does the assignment occur? Options include upon creation (strongest for the company), upon delivery, or upon final payment. Assignment upon creation is the standard approach in CIIAs and employment agreements.

Territory. Worldwide assignment is standard and necessary for companies operating across jurisdictions.

Consideration. What does the assignor receive in exchange? For employees, it’s bundled into compensation. For contractors, it’s typically bundled into the service fees. Make sure the consideration is clearly stated — assignment without consideration can be challenged.

Moral rights waiver. Required in jurisdictions that recognize moral rights (Canada, EU member states, Australia). In the US, moral rights are limited to visual art under VARA (17 U.S.C. § 106A), but international assignments should include a waiver.

Cooperation clause. The assignor agrees to execute additional documents (patent applications, copyright registrations) necessary to perfect the assignment. Include a power of attorney as a backstop.

Representations. The assignor represents they have the right to assign, haven’t previously assigned the IP to anyone else, and haven’t incorporated third-party IP without authorization.

Work-for-hire declaration. For copyrightable works that fall within the nine statutory categories, include a work-for-hire declaration as a belt-and-suspenders approach alongside the assignment.

IP Assignment by Agreement Type

Founder and Co-Founder Agreements

All IP created for the company is assigned to the company at incorporation via CIIA. Prior inventions are excluded. The critical question: what happens to assigned IP if a founder is terminated or leaves? Standard approach: the IP stays with the company (it was assigned, not licensed), but unvested stock is forfeited under the vesting schedule.

Employment Agreements

The assignment covers inventions and works created during employment, using company resources, or related to the company’s business. State-specific notice requirements apply — California, Delaware (19 Del. C. § 805), Illinois (765 ILCS 1060/2), Minnesota (Minn. Stat. § 181.78), and Washington (RCW 49.44.140) all have statutes protecting employee personal inventions. Failure to include the required statutory notice can render the assignment provision unenforceable. For guidance on related employment agreement issues, see our article on how to review contracts for red flags.

Independent Contractor Agreements

No automatic assignment exists. The contract must explicitly assign IP, and the work-for-hire doctrine has narrow applicability for contractors. Every contractor agreement should include: explicit IP assignment, background IP definition and license, prior inventions schedule, cooperation clause, and representations about third-party IP. For a more comprehensive review framework, see our guide on reviewing contractor agreements for misclassification risk.

Development and Software Contracts

The standard structure separates deliverable IP (assigned to the client) from background IP (retained by the developer with a license to the client to use it within the deliverables). Open-source components require special attention — if the developer incorporates GPL-licensed code, the copyleft obligations may affect the client’s proprietary code. The contract should require disclosure of all open-source components and compliance with their respective licenses. For SaaS-specific IP considerations, see our analysis of SaaS agreement review issues.

IP Assignment Red Flags

When reviewing any contract, flag these immediately:

No IP assignment clause in a development contract. The contractor owns everything by default. This is the single most common and most expensive IP mistake in startup law.

“All IP ever created” scope. Assignments covering all intellectual property created by the assignor, regardless of context, are overbroad and potentially unenforceable under state invention protection statutes.

No prior inventions schedule. Without a carve-out, pre-existing IP with encumbrances gets swept into the assignment, creating title problems.

Assignment conditioned on payment. If IP assignment only occurs upon full payment, a payment dispute means the company doesn’t own its own product. Standard practice: assignment upon creation, with a security interest or license-back if payment protection is needed.

No cooperation clause. Without one, perfecting the assignment (filing patent applications, registering copyrights) requires the assignor’s voluntary cooperation — which may not be forthcoming after the relationship ends.

Work-for-hire misapplication. Using work-for-hire language for contractor work that doesn’t fall within the nine statutory categories creates a false sense of security. The company thinks it owns the IP. It doesn’t. According to Farella Braun + Martel’s analysis, misapplying work-for-hire in contractor agreements can also create employment classification risk — if the IRS or a court determines that calling the relationship “work-for-hire” implies an employment relationship rather than an independent contractor arrangement.

No representations about right to assign. The assignor may not own what they’re assigning — they may have used code from a previous employer, incorporated open-source components with restrictive licenses, or already assigned rights to someone else. IP assignment issues often interact with limitation of liability provisions — if the assignor breaches a representation about IP ownership, the damages may exceed the contract’s liability cap.

How Clause Labs Handles IP Provisions

Clause Labs’s AI identifies IP assignment, license, and work-for-hire clauses in any contract and flags:

• Missing IP assignment in contractor and development agreements
• Overly broad assignment language that may conflict with state employee invention protections
• Absent prior inventions carve-outs
• Missing cooperation clauses
• Interactions between IP provisions and termination clauses (does IP assignment survive termination?)
• Work-for-hire declarations used outside their statutory scope

The analysis takes under 60 seconds and provides a clause-by-clause breakdown with risk ratings and suggested edits.

Frequently Asked Questions

Who owns IP by default without a contract?

It depends on the relationship. For employees creating within the scope of employment, the employer generally owns copyrightable works under the work-for-hire doctrine, and many states have “hired to invent” doctrines for patentable inventions. For independent contractors, the contractor owns everything they create unless a written agreement says otherwise. For co-founders without a CIIA, each founder personally owns their individual contributions. These defaults are why written IP assignment agreements are essential.

Can I assign IP verbally?

Patent rights can potentially be assigned verbally, but copyright assignments require a written instrument signed by the owner under 17 U.S.C. § 204. In practice, verbal IP assignments are virtually impossible to enforce because they’re impossible to prove. Always get IP assignments in writing.

What’s the difference between IP assignment and work-for-hire?

Work-for-hire means the hiring party is considered the author and original owner — the creator never owned the IP at all. Assignment means the creator owned the IP and then transferred it to the company. The practical difference: assignment can theoretically be terminated by the author after 35 years under 17 U.S.C. § 203, while work-for-hire cannot. For most startup purposes, both achieve the same practical result — company ownership — but using both approaches (work-for-hire declaration plus assignment as backup) provides the strongest protection.

Do I need IP assignment for every contractor?

Yes, if the contractor is creating anything that could constitute intellectual property — code, designs, written content, inventions, processes. The only exception is contractors performing purely mechanical tasks with no creative component (e.g., data entry using your templates). When in doubt, include the clause. The cost of including an unnecessary IP assignment clause is zero. The cost of omitting a necessary one can be the entire company.

What happens if an IP assignment is invalid?

The company doesn’t own the IP it thought it owned. In an acquisition, this can reduce the purchase price, require escrow holdbacks, or kill the deal entirely. In a financing, investors may demand that IP issues be resolved before closing. In operations, the actual IP owner could demand license fees, seek an injunction, or start competing using “your” technology. The fix is to obtain a valid assignment as soon as possible — but if the assignor is uncooperative, it may require litigation.

---

This article is for informational purposes only and does not constitute legal advice. Consult a qualified attorney for advice specific to your situation.

---

IP assignment issues are among the most expensive mistakes in startup law. If you’re reviewing a contractor agreement, employment contract, or founder CIIA, upload it to Clause Labs to check whether the IP provisions actually protect the company. The free tier includes 3 reviews per month — no credit card required.