Founder IP Assignment: Why You Can't Raise Without It and How to Get It Done

The IP Assignment Gap That Kills Series A Deals

When a VC's counsel opens a diligence request list, one of the first things they look for is signed IP assignment agreements from every founder and early contributor. Missing contractor IP assignments kill more deals than any other issue — not because investors are looking for a reason to walk, but because unassigned IP creates a genuine ownership problem that no amount of goodwill can paper over. Founders routinely assume that code they wrote for their own company belongs to the company. It doesn't — not without a written assignment.

The problem surfaces in a predictable place: the IP representations in your Series A Stock Purchase Agreement. Under the NVCA model SPA, the company makes extensive representations and warranties about intellectual property ownership — covering chain of title, absence of infringement claims, and the completeness of all required assignments. Gaps don't disappear — they get disclosed on the Disclosure Schedules, which investors review line by line. Once something appears on Schedule C as an IP exception, you've converted a private problem into a documented deal risk. Every investor at the table sees it.

The downstream consequences compound quickly. 409A valuations for pre-revenue startups typically rely on an asset-based approach, which requires the company to document clean ownership of its intangible assets — primarily the core technology. If the IP chain of title is broken, the 409A provider cannot properly value what the company claims to own. That's a problem for option pricing, and it's a problem for any investor trying to model the company's asset base. Separately, representations and warranties insurance — which buyers and investors increasingly use to backstop SPA reps — explicitly excludes matters disclosed during diligence. Once the IP gap surfaces on a disclosure schedule, it becomes a known issue, outside RWI coverage entirely.

The instinct to fix it retroactively under deal pressure is understandable but costly. Emergency IP cleanup during a live fundraise means negotiating assignment agreements with founders who now have leverage — especially any co-founder who has since departed. Retroactive cleanup requires significant emergency legal fees, and a co-founder who left with no formal IP assignment and no alignment with the company's success is a litigation risk that doesn't disappear even after a belated signature. The assignment transfers ownership going forward; it does not cure claims or standing issues arising from the pre-assignment period. Investors know this. The ones who don't walk away will price the risk into your valuation.

What Needs to Be Assigned

The starting point is a legal fact that surprises most founders: copyright in anything you write — code, a whitepaper, a pitch deck — vests automatically in the human author under 17 U.S.C. § 201(a). Not in the company. Not even if you built it entirely to launch the company. The entity didn't exist when you wrote it, so there was no employer, no employment relationship, and no work-made-for-hire. The same logic applies to inventions, trade secrets, and brand assets. If you created it before incorporation, the company needs a written assignment — full stop.

The work-made-for-hire doctrine doesn't rescue you here either. That doctrine transfers IP to an employer only when an employment relationship exists at the time of creation. Pre-incorporation, no such relationship exists. And even post-incorporation, the doctrine explicitly excludes software created by independent contractors — meaning a co-founder who was never formally employed by the entity holds their code personally, regardless of intent.

Six IP Categories to Assign

Pre-incorporation code. Every line of the MVP, every prototype, every deployment script written before the entity was formed belongs to the individual who wrote it. "I built this for the company" is not a legal transfer. IP assignment agreements need to define IP broadly to capture everything from source code to compiled object code — and they need to reach back to the date the first line was written, not the date the company was formed.

Patent-eligible inventions. If you conceived of a novel process, method, or system before incorporation — even informally, even in a notebook — that invention vests in you personally. A broad assignment captures inventions conceived before the company existed and any improvements made afterward. Investors acquiring a software company with a patentable core method need that chain of title clean from day one.

Trade secrets and know-how. The formula, the algorithm, the proprietary training dataset, the production process living in a founder's head — these are assignable property. A well-drafted CIIAA covers trade secrets, formulas, know-how, processes, and techniques, not just registered IP. If the assignment agreement only captures patents and copyrights, it leaves the most defensible competitive moat unaddressed.

Domain names. A domain registered in a founder's personal account before the LLC was formed is personal property. It does not transfer automatically when the company is incorporated. Registrar records matter — if the underlying registrar account shows an individual as registrant, that individual owns the domain. The fix is a written assignment plus a registrar transfer executed before any investor looks at the cap table.

Brand assets. Logos designed by a freelancer hired personally by the founder, product names brainstormed and documented in a Notion before the entity existed, UI mockups created in Figma under a personal account — none of these belong to the company without an assignment. Copyright in the logo vests in the designer (or the founder who commissioned it, depending on whether a written work-for-hire agreement existed with the designer). The company needs an unbroken chain to each of these assets.

Written materials. Whitepapers, technical documentation, pitch decks with original prose or diagrams, blog posts that establish the company's methodological claims — these are copyrighted works that vest in the human author at the moment of creation. If a founder wrote the company's core technical whitepaper before incorporation, the company does not hold that copyright unless a written assignment transfers it.

The Founder PIIA: What the Standard Agreement Covers

Every founder signs a PIIA — a Proprietary Information and Inventions Assignment agreement — with the company at formation. The name is a mouthful, but the document does four things: it assigns all work-product IP to the company in the present tense, obligates each founder to disclose any prior inventions they want excluded, imposes a confidentiality obligation over the company's trade secrets and proprietary information, and adds a non-solicitation covenant. Get any one of those four wrong and you have a document investors' counsel will flag on first read.

The Two-Word Drafting Distinction That Controls Everything

The single highest-stakes drafting question in a PIIA is whether the assignment clause says "I hereby assign" or "I agree to assign." Those two phrases differ in meaning, but they are miles apart in legal effect. The present-tense form — "hereby assign" — is an immediate transfer of title. Under Stanford University v. Roche Molecular Systems, 131 S. Ct. 2188 (2011), the Supreme Court confirmed that a researcher's prior "agree to assign" language lost to a third party's later "hereby assign" contract — the university held no rights because its agreement was only a promise to assign, not an executed transfer. The Federal Circuit reinforced the mechanics in Speedplay, Inc. v. Bebop, Inc., 211 F.3d 1245 (Fed. Cir. 2000): where an agreement provides that the worker "hereby conveys, transfers and assigns" inventions, no further act is required once an invention comes into existence — title transfers by operation of law the moment the invention is created. That automatic transfer is exactly what a PIIA is designed to produce. If your agreement uses future-tense language, you do not own the IP your founders built — you own a contract right to ask for it.

Three Non-Negotiables in Any Market-Standard Form

YC, Orrick, NVCA, and every comparable institutional template converge on three provisions that are not optional. First, the assignment clause must use present-tense language — "I hereby assign," full stop. Second, the agreement must include a prior inventions schedule where founders list anything they owned before the company was formed that they are not assigning. Third, the agreement must include state-law carve-outs: California Labor Code § 2870 and analogous statutes in Washington, Minnesota, Utah, and Illinois limit an employer's ability to claim inventions developed entirely on the employee's own time with no company resources — the PIIA must acknowledge those limits or it may be unenforceable on its face in those states. A PIIA that skips any of these three provisions is a PIIA that sophisticated investors will require you to renegotiate before close.

The Prior Inventions Schedule: List It or Lose It

The prior inventions schedule is the part of the PIIA that founders most often leave blank — which is sometimes the right answer, but never a safe default. Investors' counsel specifically scrutinize this schedule during diligence: one of the representations a startup makes in a priced round is that no current or former founder has excluded any inventions from the assignment. A blank schedule is clean. A populated schedule requires an explanation, and a populated schedule with items that appear central to the product is a deal problem. The rule is straightforward: list anything you genuinely owned before formation that you are not conveying to the company. Do not list things you already built for the company. Do not leave the schedule blank if you should have listed something.

Late-Signed PIIAs and the Consideration Problem

A PIIA signed at formation is clean. A PIIA signed six months later — after a founder has already been contributing work to the company — is a different contract with different leverage dynamics. When a founder signs after already working, courts may question whether there is sufficient consideration to support the assignment, and the founder now has practical bargaining power: they can ask for something in return. Investors who catch late signatures during diligence will typically require the company to collect executed PIIAs from all founders before closing — which means going back to a founder who may now be disgruntled, departed, or simply difficult. Equity vesting schedules, when signed alongside the PIIA at formation, provide independent consideration and eliminate this problem. The fix is a formation-date PIIA, not a retroactive one.

When Your Prior Employer Complicates the Assignment

Many founders are still on payroll somewhere when they write their first line of code. That overlap creates a claim the company itself cannot waive — only the prior employer can release it. The question is whether the employer's proprietary information and inventions agreement (PIIA) actually reaches the startup's technology, and the answer turns on three triggers.

The Three Triggers

A prior employer's PIIA can reach a founder's work if any of the following are true: the work was performed on employer equipment or systems, it was done during business hours, or it relates to the employer's business. These factors are not equally weighted — the third one is the most dangerous. Broad assignment clauses routinely claim IP that merely relates to the employer's field, even if the founder used personal hardware on a Saturday night.

The closer the startup's technology is to what the prior employer does, the stronger the potential claim. A backend engineer at a payments company who starts a fintech startup is in a materially different position than the same engineer who starts a healthcare scheduling tool. When meaningful overlap exists, diligence counsel will flag it, and the cap table cannot be cleaned up retroactively once you're in the middle of a term sheet.

Statutory Carve-Outs and Their Limits

California Labor Code § 2870 gives founders a partial escape: any PIIA provision that purports to assign an invention the employee developed entirely on their own time, without employer equipment, supplies, facilities, or trade secret information, and that does not relate to the employer's business or anticipated research, is void as to that invention. A significant number of states track the same structure, including Illinois, Minnesota, North Carolina, Washington, Kansas, New Jersey, and Utah.

Texas has no equivalent statute. A Texas-based founder with a prior-employer PIIA gets no statutory floor — the agreement's language controls, and courts will enforce it. Founders headquartered in Austin or elsewhere in Texas need to evaluate their prior agreements directly, not assume the California framework protects them.

What to Do About It

When there is a plausible overlap between the startup's technology and the prior employer's field, the right move is to create a contemporaneous written record documenting how the two are distinct — what the startup does that falls outside the employer's business, what work was done on personal time with personal resources, and what confidential information was not used. This is the kind of analysis your attorney will build into a representation before any raise; it is far better to construct it while the facts are fresh than to reconstruct it under a due diligence deadline.

Where the overlap is substantial, a formal written release from the prior employer may be necessary. That conversation is easier to have before the employer learns about the fundraise from someone else. Discovering the exposure mid-diligence sharply limits your options, and a sophisticated investor's counsel will not simply take your word that the issue has been resolved.

If you're a hardware founder or your product involves embedded systems where the employer-overlap question gets technically complex, the analysis in our deep dive on prior employer IP claims covers that terrain in detail — including the case law on what courts have treated as sufficiently distinct. The framework here applies regardless of stack, but the hardware context adds layers worth reading separately before you assign.

If It Wasn't Done at Formation: Retroactive Assignment and Its Real Limits

Founders occasionally reach the seed round and discover the PIIA was never executed, or was signed only by some co-founders, or omitted entire categories of IP. The instinct is to fix it immediately with a backdated or retroactive assignment — and that instinct is mostly right, but the legal effect has a hard ceiling.

A retroactive (nunc pro tunc) assignment does transfer chain of title between the parties going forward. Investors will see a clean chain from founder to company at closing. What it cannot do is manufacture standing that did not exist before the assignment was executed. Courts determine standing based on the effective date of the assignment, not any earlier date the document lists — meaning that for litigation purposes, the assignment is only as old as the day it was actually signed.

The Federal Circuit made this concrete in a case where a parent corporation executed a retroactive assignment to cure a broken chain of title it had never properly obtained from its own subsidiary. The court dismissed for lack of standing. The holding: a party must hold legal title on the day the complaint is filed, and that requirement cannot be satisfied retroactively. A retroactive assignment by a parent corporation that never obtained a valid written assignment of patents actually held by its subsidiary failed to cure a break in the chain of title. If your company ever needs to assert a patent — against a competitor, in a licensing dispute, during M&A — an unassigned period in the chain of title is a structural liability that a late signature cannot fully erase.

What Investors Read Into a Late Assignment

When a retroactive IP assignment surfaces in diligence, sophisticated investors do not simply accept it as resolved. The assignment signals that the company's early legal housekeeping was incomplete, which prompts the natural follow-on question: what else was missed? Investors may condition the investment on IP cleanup completion with escrow mechanisms for resolvable issues, or decline entirely for unresolvable problems. The cure document closes one gap; it opens a wider conversation about the company's legal infrastructure.

When a retroactive assignment is executed close to closing, investors or their counsel may require a legal opinion letter from company counsel as an additional closing condition. A legal opinion is a formal letter from company's counsel containing various conclusions regarding the company's legal matters — it gives investors an additional layer of comfort, but it is not a substitute for diligence, and whether one is required is determined case by case. Requiring an opinion letter adds time and cost to closing; it is not a routine ask, and its presence signals that the investor's counsel has assessed residual risk as material enough to warrant the extra step.

The Practical Playbook

If a gap surfaces before or during diligence, the sequence matters. Execute the assignment immediately — do not wait for the investor to raise it. Disclose it on the representations schedule with a plain-language description of the gap period and the cure. Investors and their counsel typically require, as a closing condition, that the chain of title is clean as of the assignment date, that the assignment does not conflict with any prior employment or consulting agreement, and that the company will cooperate in any post-closing chain-of-title recordation. If any third-party dealings — licenses granted, work shared with contractors, collaborations with former employers — occurred during the period when IP was not formally assigned to the company, those must be disclosed separately. A retroactive assignment cannot unwind a license already granted or a disclosure already made; each such event needs its own analysis and potentially its own cure.

The window to fix this cleanly is before you send the first data room link. After that, every document you add is part of the diligence record, and the story of a late assignment is a harder one to tell than the story of one done correctly at formation.