IP assignment agreement for startups: what to sign before hire one

An IP assignment agreement startup founders sign before hire one is a three-document kit: a founder assignment transferring pre-incorporation code to the company, a PIIA for every employee, and a stronger contractor variant with explicit present-tense assignment. Miss any of the three and a Series A diligence team will find it, freeze the round, and hand leverage to whoever did not sign.

Most founders treat IP paperwork as something to clean up before a priced round. That is how deals die. The three documents below get signed on day one, before anyone who is not a founder writes a line of code, because every day you delay is a day someone with unclear ownership is producing the asset you are trying to sell.

This is the tactical version: what each document does, when to sign it, and the specific clauses investor counsel checks during diligence.

The three documents every pre-seed startup signs before hire one

Here is the order, and the reason each exists.

1. Founder IP assignment to the corp. Signed the day the C-corp is formed. Transfers every line of code, design, and invention the founders built pre-incorporation into the company. Without it, the company does not own its own product.
2. Employee PIIA (Proprietary Information and Invention Assignment). Signed on or before an employee's first day, never after. Combines confidentiality, present assignment of existing inventions, and agreement to assign future ones. Cooley flags both pieces as required because a future-only promise does not transfer anything that already exists.
3. Contractor PIIA variant. Signed before any contractor opens a repo. US copyright law does not automatically hand contractor work to the company, so the assignment language has to be explicit and present-tense. Orrick lists the PIIA as the standard vehicle for both employees and service providers for exactly this reason.

If any of those three is missing when a Series A term sheet lands, you are starting a legal remediation project during the most time-sensitive two weeks of your year.

What a PIIA agreement actually does

A PIIA agreement (sometimes called a confidentiality and invention assignment agreement, or CIIAA) bundles four things into one signature: confidentiality, present assignment, future assignment, and a carve-out for prior inventions. The four-way bundle is the whole point. Drop any one and the chain of title has a gap.

The specific magic, per Cooley's guidance on protecting employee-generated IP, is the combined present-and-future assignment language. Present assignment ("I hereby assign") transfers what already exists. A promise to assign in the future ("I agree to assign") is not self-executing and requires a second signature later, which is exactly the signature you will not be able to get from an angry ex-employee.

What investors' counsel actually checks:

• Signed before employment start date. A PIIA signed two weeks in is presumed to not cover the first two weeks of work.
• Present-tense assignment language. "I hereby assign" beats "I will assign." The second form is a promise, not a transfer.
• Prior-invention schedule attached. A blank Schedule A means the employee is asserting they had no prior inventions. An unfilled schedule left ambiguous is a red flag.
• Spousal acknowledgement in community-property states (California, Texas, and seven others). Missing sign-off from a spouse in California can cloud title on inventions made during the marriage.

Contractors are the IP risk, not employees

The contractor gap is where most early-stage IP ownership goes wrong. US copyright law's work-for-hire doctrine automatically vests ownership in the employer for employees, but not for independent contractors outside nine narrow categories (software development is not one of them). So calling a freelance dev's output "work for hire" in the contract does not by itself make it yours.

The fix is a contractor PIIA with explicit present assignment. The clause should read something like: "Contractor hereby irrevocably assigns to the Company all right, title, and interest in and to all Work Product." Any softer framing, "the parties agree the Work Product shall be the property of the Company," "Company shall own," is interpretable as a promise rather than a transfer, and Fenwick's due-diligence practice treats it that way during IP audits.

The other three contractor gotchas investor counsel looks for:

• Open-source contributions. If a contractor pushed code under a copyleft license (GPL, AGPL), your proprietary product may have just become subject to the copyleft terms. The contract should require disclosure and approval of any OSS inclusion.
• Moonlighting employer conflicts. A contractor with a full-time day job at BigCo may have signed a PIIA there that claims their off-hours inventions. Your contract needs a rep that they have no conflicting obligations.
• Foreign contractors. Assignment enforceability varies by jurisdiction. For developers in Germany, France, or Brazil, local moral-rights or inventor-compensation regimes can survive an assignment. Get counsel on the specific country before the first commit.

The Series A horror story that should scare you

Here is the scenario every Series A lawyer has lived through at least once.

A seed-stage startup hires a freelance ML engineer for three months to build the recommendation model. The founder sends a Notion page called "Contractor Terms" and the engineer replies "sounds good," no signed agreement. The engineer ships, gets paid, moves on. Eighteen months later, the startup is in final diligence on a $15M Series A. The investor's counsel runs a chain-of-title check, pulls the GitHub commit history, and finds the ex-contractor's email address on 40% of the production model's commits. No PIIA, no assignment, no signed NDA.

The deal does not die, but it pauses for six weeks while the founder negotiates a retroactive assignment with a contractor who now knows he has leverage. Final cost: a five-figure settlement and a materially worse Series A timeline. Fenwick's IP audit practice exists specifically because this pattern is the single most common clean-up problem at Series A.

The context that makes this worse in 2026: Carta data shows about 40% of seed and Series A rounds in Q3 2024 were bridge rounds, which means more financings that include IP clean-up as a closing condition, and more leverage for investors to insist on perfect documentation. Carta counted 1,287 new rounds in Q2 2024 alone, every one of them running a diligence gauntlet that includes chain-of-title proof for every line of production code.

Founder assignment: the document founders skip

The founder assignment is the document founders forget, because it does not feel like "hiring." It is the most important one.

Before the company existed, the founders were individuals writing code on personal laptops. That code was owned by them personally, not by a company that did not exist yet. The founder assignment, signed at incorporation, transfers every pre-formation contribution into the corp. Without it, the company is building on an asset it does not own, and a co-founder who later departs on bad terms can assert personal ownership of the pre-formation codebase.

Cooley's template kit, Orrick's Tech Studio forms, and Fenwick's startup package all include a founder assignment as day-one paperwork. Use one of them. Do not draft your own.

FAQ

What is a PIIA agreement? A PIIA (Proprietary Information and Inventions Assignment Agreement) is the standard contract that assigns to the company any confidential information, inventions, and work product created by an employee or service provider. It combines a confidentiality obligation with both a present assignment of existing inventions and an agreement to assign future ones, which is how the company gets clean title to the code and IP its team produces.

Do contractors need IP assignment agreements? Yes, and a stronger one than employees. Under US copyright law, work by independent contractors does not automatically belong to the company even if you call it work-for-hire, so without a signed assignment the contractor owns what they built. A contractor PIIA with explicit present assignment language is the only reliable fix.

What happens if an employee doesn't sign an IP agreement? The company may not own the code that employee wrote, which becomes a diligence problem the instant you raise a priced round. Investors require chain-of-title proof for every contributor. If one is missing, they pause the deal until you get a retroactive assignment signed, and the employee now has leverage they did not have before.

Can you backdate IP assignment? No. Backdating a signature is forgery. What you can do is sign a present-dated assignment that explicitly covers inventions created during a prior work period, sometimes called a confirmatory assignment. Investor counsel accepts this during clean-up if the language is clear and the signer still cooperates.