Assignment of Invention Agreements: What Startups Must Know

Assignment of Invention Agreements: What Startups Must Know

Assignment of invention agreements transfer ownership of employee-created intellectual property to the employer, a foundational requirement for venture-backed startups. Without properly executed assignment agreements, companies cannot secure funding, complete acquisitions, or defend their patent portfolios—making this the single most critical legal document most founders overlook until it kills their deal.

Angel Investors Network provides marketing and education services, not investment advice. Consult qualified legal, tax, and financial advisors before making investment decisions.

Why Assignment of Invention Agreements Matter for Fundraising

When a venture capital firm conducts legal diligence, the first document they request is a complete set of executed assignment agreements from every person who touched the codebase, prototype, or algorithm. Missing even one signature creates a cloud on title that can delay a round for months or collapse it entirely.

In acqui-hire situations, acquiring companies demand proof that the startup actually owns the work product those engineers created. If a former contractor built the core technology but never signed an assignment agreement, the startup owns nothing. According to research published by the Stanford Technology Law Review, IP ownership disputes rank among the top three reasons early-stage M&A transactions fail during diligence.

What Is an Assignment of Invention Agreement?

An assignment of invention agreement is a contract where an individual transfers all ownership rights in their inventions, discoveries, and works of authorship to an employer or company. The agreement typically covers:

• Scope of covered work: Inventions created using company resources, on company time, or related to the company's business
• Timing: Usually covers all work created during employment, not just specific projects
• Future cooperation: Employee agrees to assist with patent prosecution and litigation after employment ends
• Prior inventions disclosure: Employee lists any IP they created before joining to exclude it from the assignment
• State law compliance: Carve-outs for non-work-related inventions created entirely on personal time (required in California, Delaware, and other states)

The agreement must be signed before the work begins. A retroactive assignment executed months after code was written raises questions about consideration and can be challenged in court.

How Do Assignment Agreements Differ From Work-for-Hire?

Work-for-hire doctrine automatically assigns copyright ownership to employers for certain categories of work created by employees. But work-for-hire doesn't cover patents, trade secrets, or works created by contractors.

Assignment agreements eliminate ambiguity. They create a paper trail proving the company owns the IP regardless of employment classification or work-for-hire applicability. For hardware startups raising capital through equity crowdfunding platforms, patent ownership becomes even more critical.

What Happens When Founders Skip Assignment Agreements?

Here's a typical scenario: Two technical co-founders start building a SaaS platform, incorporate in Delaware, split equity 50/50, and start coding. No assignment agreements signed—they figured they'd handle it "when we raise money."

Fast forward 18 months. Product has traction. They raise a $2M seed round led by a regional VC fund. Diligence reveals one co-founder built the core recommendation algorithm while still employed full-time at Amazon. No assignment agreement exists transferring that co-founder's rights to the startup.

Amazon's employment agreement—standard across FAANG companies—claims ownership of all inventions "related to the company's business or anticipated research and development." The VC kills the deal. The startup spends six months negotiating a settlement with Amazon, ultimately surrendering 15% equity in exchange for a clear title opinion. The seed round finally closes at half the original valuation.

All preventable with a $500 legal document signed on day one.

Which Employees and Contractors Need to Sign?

Everyone who creates anything. No exceptions.

Technical co-founders: Even if they founded the company, execute assignment agreements transferring their individual IP rights to the corporation.

Early employees: Engineers, designers, product managers—anyone who contributes to the product, codebase, or trade secrets.

Contractors and consultants: Every freelancer, offshore dev shop, and part-time designer must sign before starting work. Contractor assignments require explicit language stating the work is "made for hire" AND assigning all rights to the company.

Advisors, interns, and temporary workers: Any contribution to the product requires an assignment.

For companies raising through Regulation Crowdfunding—like mission-critical AI startups targeting institutional capital—incomplete assignment records create regulatory risk beyond just investor concerns.

How Should Startups Handle Prior Employer IP Conflicts?

Every technical founder or early engineer should complete a Prior Inventions disclosure listing any IP created before joining the startup. This forces the question: Did the founder bring code, algorithms, datasets, or trade secrets from a previous employer?

Most corporate employment agreements assign all work-related inventions to the employer, even if created outside normal working hours. Safe harbors exist—California Labor Code Section 2870 limits employer IP claims to inventions developed using employer equipment, on employer time, or relating to employer's business. Similar statutes exist in Delaware, Illinois, Kansas, Minnesota, Nevada, North Carolina, Utah, and Washington.

But relying on statutory protection requires proof: GitHub commits timestamped outside work hours, cloud server bills in the founder's name, development notebooks with dates. Without documentation, investors assume the worst. Smart diligence counsel will request: (1) the founder's employment agreement from the prior job, (2) the Prior Inventions disclosure, and (3) an opinion letter from the startup's attorney.

What Terms Should Assignment Agreements Include?

Effective assignment agreements balance maximum protection for the company, enforceability under state law, and fairness to employees.

Broad definition of "Inventions": Cover discoveries, improvements, designs, processes, software, algorithms, trade secrets, and works of authorship.

Temporal scope: Cover all work created during employment, from first day through termination.

Geographic scope: Worldwide assignment for international investors and acquirers.

Cooperation obligation: Employee agrees to sign patent applications, testify in litigation, and assist with prosecution—even after leaving the company.

Disclosure requirement: Employee must promptly disclose all potentially covered inventions to the company.

State law carve-outs: In California and other employee-protective states, explicitly exclude inventions that qualify for statutory protection.

Prior inventions attachment: Provide a schedule where employee lists excluded IP created before joining.

Compensation acknowledgment: State that employee's salary/equity compensation includes consideration for the assignment.

How Do Courts Enforce Assignment Agreements?

California courts apply strict scrutiny to employer IP claims, establishing a three-part test: Was the employee hired to invent? Did the employee use company resources? Does the invention relate to the company's actual business? Employers lose when they claim ownership of side projects unrelated to the employee's job function.

Delaware courts enforce broad assignment language more liberally. The practical impact for startups: Incorporate in Delaware, hire employees in California or other employee-friendly states, draft assignment agreements that comply with the most restrictive jurisdiction where employees work.

Litigation risk compounds with retroactive assignments. If a startup asks an employee to sign an assignment agreement years after they started, the employee can demand additional compensation. Courts have held that continued employment alone doesn't constitute sufficient consideration for a retroactive IP assignment in most states.

What Role Do Assignment Agreements Play in M&A Transactions?

In asset acquisitions, buyers purchase specific IP assets, not the company itself. The seller must prove it has clear title through assignment agreements. Corporate acquirers employ specialized diligence teams that review every line of code, every patent application, and every employment record, building matrices tracking which employees contributed to which features.

Gaps create indemnity exposure. Strategic acquirers handle this risk by holding back 10-30% of purchase price in escrow for 12-24 months. Every missing assignment agreement increases the escrow percentage or extends the escrow period. For companies pursuing middle-market private equity acquisitions, assignment documentation quality directly affects transaction multiples.

How Should Startups Remediate Missing Assignments?

Start with a comprehensive audit, then negotiate from transparency.

Step 1: Build a contributor matrix. List every person who touched the product. Cross-reference against executed assignment agreements.

Step 2: Categorize gaps by risk level. High risk: current employees or contractors who own mission-critical IP. Medium risk: former employees who contributed to features still in production. Low risk: early contractors who built prototypes later replaced.

Step 3: Execute assignments for current team members. Provide equity refreshes or cash bonuses as consideration.

Step 4: Negotiate with former contributors. Locate them, explain the gap, and request executed assignments. Offer modest compensation.

Step 5: Document inability to locate contributors. Create a paper trail: LinkedIn searches, email attempts, certified mail to last known address.

Step 6: Obtain legal opinions for material gaps. If high-risk contributors refuse to sign, engage IP counsel to provide an opinion letter evaluating ownership risks.

Startups that proactively fix assignment gaps before fundraising negotiate from strength. Those forced to remediate during diligence negotiate from weakness.

What Mistakes Do Startups Make With Assignment Agreements?

Using generic templates without state-specific modifications. Work with counsel admitted in each state where employees work.

Treating contractors like employees. Contractor assignments require "work made for hire" language plus explicit assignment of all rights.

Failing to collect signatures before work begins. Retroactive assignments create consideration problems.

Omitting cooperation obligations. If a former employee refuses to sign patent declarations after leaving, the patent may be unenforceable.

Ignoring founder IP conflicts. Technical founders who worked at Google, Amazon, or similar employers within 12 months of starting their company create presumptive IP conflicts.

Assuming equity grants substitute for assignments. Stock option grants don't transfer IP ownership.

For startups raising capital through Regulation Crowdfunding platforms, these mistakes multiply disclosure obligations.

When Should Startups Execute Assignment Agreements?

Before the first line of code. The optimal sequence for new company formation:

Day 1: Incorporate the entity (Delaware C-corp for VC-backed startups).

Day 2: Execute founder assignment agreements transferring all pre-incorporation IP to the company. Include comprehensive Prior Inventions disclosures.

Day 3: Begin building the product.

For companies adding team members post-formation, execute assignments on the hire date. This timing creates a clean timeline for investors—every invention created after the assignment date belongs to the company.

How Do Assignment Agreements Interact With Open Source Licensing?

If an employee incorporates GPL-licensed code into a company product, the company may be required to open-source the entire codebase under GPL's viral licensing terms. The assignment agreement doesn't override the GPL—it just means the company owns code that it can't control.

Smart assignment agreements include a representation that the employee has not incorporated third-party IP (including open source) without proper licensing. But representations don't fix the underlying problem. The solution: Implement automated code scanning tools that detect open source components and flag licensing issues before they reach production.

What Should Investors Look for When Reviewing Assignments?

Completeness: Every contributor listed in the code repository, patent applications, or product documentation should have a signed assignment.

Timing: Assignments executed before work began are clean. Retroactive assignments executed years later are red flags.

Consideration: For retroactive or post-employment assignments, verify the employee received valuable consideration.

Scope: The assignment should cover all forms of IP and all geographies.

Cooperation: The agreement should compel post-employment cooperation for patent prosecution and litigation.

State law compliance: Verify the agreement includes required statutory carve-out language.

Related Reading

• Mid-Market Fund Capital Commitments Surge in 2026 — institutional LP diligence
• AvaWatz RegCF: $80.8M Target for Mission-Critical AI — IP disclosure requirements
• Court Square's CallTower Buy: Why Middle-Market PE Wins — M&A diligence standards

Frequently Asked Questions

What is the difference between an assignment of invention agreement and a non-compete?

An assignment of invention agreement transfers IP ownership from employee to employer and survives indefinitely—the company owns the IP forever. A non-compete restricts the employee's ability to work for competitors or start competing businesses, typically for 6-24 months after employment ends. Courts enforce assignments more readily than non-competes because assignments involve property transfer (IP ownership) rather than restraint of trade. California prohibits most non-competes but allows broad invention assignments with statutory carve-outs.

Can an employer claim ownership of inventions created before employment?

No, unless the employee explicitly assigns pre-existing IP to the employer. This is why Prior Inventions disclosures are critical—they document what IP the employee created before joining and exclude it from the assignment. If an employee fails to disclose pre-existing IP, the assignment agreement creates a presumption that all inventions during employment belong to the employer, potentially capturing IP that predates the employment relationship. Employees should always complete Prior Inventions schedules, even if they believe they have no relevant IP to disclose.

Do assignment of invention agreements apply to remote workers in different states?

Yes, but enforceability depends on which state's law governs. Most assignment agreements include a choice-of-law provision specifying that Delaware law or the company's home state law applies. However, some states—particularly California—apply their protective employment statutes to their residents regardless of choice-of-law provisions. Companies hiring remote workers should execute state-specific assignment agreements or include carve-outs complying with the most protective state where any employee works. Otherwise, courts may void overly broad assignments under employee-protective state laws.

What happens if a startup discovers a missing assignment during due diligence?

The round typically pauses while the company remediates the gap. If the missing assignment involves a current employee, the company can execute a new agreement with additional equity or cash as consideration. If it involves a former employee, the company must locate them and negotiate an assignment, often for cash consideration. If the former employee refuses or can't be located, legal counsel provides an opinion letter evaluating the ownership risk. Material gaps involving core technology can kill the round entirely—investors won't close without clear IP ownership.

Are verbal agreements or email acknowledgments sufficient for IP assignment?

No. Patent law and most state statutes require written, signed assignment agreements. Verbal agreements and email exchanges may create evidence of intent but don't satisfy formal assignment requirements. Courts have repeatedly held that informal communications don't constitute effective IP transfers. Investors will not accept verbal agreements or email threads as proof of ownership during diligence. The assignment must be a standalone written document signed by both parties, ideally notarized for added enforceability, particularly for patent assignments filed with the USPTO.

How long should companies retain executed assignment agreements?

Permanently. Assignment agreements are foundational corporate documents that prove IP ownership indefinitely. Companies should maintain both physical and digital copies in secure storage. During M&A transactions, acquirers request complete assignment records going back to company formation. Some acquirers require copies signed in wet ink, not just digital signatures, particularly for patent assignments. Best practice: Store originals in a bank safe deposit box or legal vault, maintain scanned copies in cloud storage with access controls, and keep a summary spreadsheet tracking who signed what and when.

Can assignment agreements be modified or terminated after signing?

Assignment agreements can be modified through written amendments signed by both parties, but terminating an assignment is nearly impossible once IP has been transferred. The company would need to re-assign the IP back to the employee, which no sophisticated company would do after closing a funding round or acquisition. Courts occasionally void assignments for fraud, duress, or lack of consideration, but these situations are rare and require clear evidence of misconduct. Once IP transfers to the company, employees should assume the transfer is permanent and irreversible.

Do founders need assignment agreements if they own 100% of the company?

Yes. Corporate law distinguishes between individual ownership and corporate ownership. Even if a founder owns 100% of the company stock, IP created by the founder individually belongs to the founder personally unless explicitly assigned to the corporation. This matters when the founder later brings on co-founders, employees, or investors—the company must be able to prove it owns its IP independently of founder personal ownership. Additionally, if the founder later sells their stock or the company is acquired, the acquirer needs proof that IP belongs to the company, not the founder's personal estate.

Ready to raise capital with ironclad IP documentation that institutional investors trust? Apply to join Angel Investors Network and connect with accredited investors who understand what proper diligence requires.