IP Assignment Agreements Every Tech Startup Must Have (Before Your First Hire or Investor Meeting)

Of all the legal issues that surface during venture due diligence, missing IP assignment agreements are the most common, the most preventable, and — when discovered late — the most expensive to fix.

Not "expensive" as in legal fees, though those add up too. Expensive as in: a signed term sheet going into extended limbo while founders track down a contractor who's now unreachable, a deal repriced because a co-founder won't sign a cleanup assignment without negotiation, a round that closes six weeks late because a prior employer's shadow looms over the codebase.

This post is about preventing all of that. What you need to have in place, when you need it, the open-source and AI training data landmines that weren't issues in 2023 but are now, and a founder/contributor assignment template you can use or adapt.

For a deeper treatment of what investors are actually checking in diligence, see How Startup IP Due Diligence Works Before a Fundraise. For the clause-by-clause anatomy of a CIIA, see What Is a CIIA?. For why the words "hereby assigns" are the most important two words in any IP document, see Hereby Assigns: The Two Words That Make IP Assignments Actually Work.

This post focuses on timing, the new 2026 gotchas, and giving you something you can actually use.

---

The Timeline Problem

Most founders know they need IP assignment agreements. The mistake isn't ignorance — it's timing. The typical pattern:

1. Founders start building, often before the company is even incorporated
2. A contractor builds a key feature under a casual agreement or no agreement at all
3. The company incorporates, raises a small friends-and-family round, gets traction
4. A serious investor starts diligence
5. The investor's counsel asks for the IP assignment chain
6. Founder realizes the codebase has three contributors with no signed agreements

At step 6, you are now negotiating cleanup assignments with people who have leverage. The contractor who built your authentication module in exchange for equity knows you need their signature. The co-founder who left amicably eighteen months ago has moved on and doesn't want to deal with paperwork. The freelancer you paid through Venmo has a new phone number.

The right timeline:

Milestone	What must be signed
At incorporation	Founder IP assignment agreements for all pre-incorporation work
Before any contractor starts work	Contractor agreement with present-tense IP assignment
Before any employee's first day	CIIA signed, dated on or before start date
Before any advisor accesses your codebase or roadmap	Advisor agreement with IP and confidentiality provisions
Before first investor conversation	All of the above in place; gaps identified and being closed

The window that matters most: the period between "building something" and "having anyone besides the founders touch it." Once a second person creates IP for the company without a signed agreement, you have a problem that only gets harder to solve.

---

Founder IP Assignment: The One Nobody Does at Incorporation

The most consistently missed assignment is the simplest one. When a company incorporates, founders sign stock purchase agreements and bylaws — but frequently don't execute a proper IP assignment covering the work they did before the company existed.

That pre-incorporation work — the prototype, the initial architecture, the brand, the domain, the customer research — was created by the individual founders, not the company. The company didn't exist yet. Unless it's formally assigned, it belongs to whoever built it.

Most formation packages address this with a paragraph in the stock purchase agreement or CIIA that assigns "all IP related to the company's business, including any IP created prior to the date of this agreement." That's functional if it's there. If your formation documents don't include this language, or if you incorporated with a bare-bones filing service that didn't generate a CIIA, this is worth verifying now.

What a founder IP assignment at incorporation should cover:

• All inventions, code, designs, and works created before incorporation that relate to the company's business
• Assignment of any domain names, social media handles, or other assets held personally
• A Schedule A / prior inventions carve-out for anything the founder is not assigning (personal side projects, pre-existing open source work, etc.)
• A present-tense assignment: "Founder hereby assigns" — not "agrees to assign"

The Schedule A carve-out matters. Without it, a founder signing a broad assignment may inadvertently transfer rights to personal projects created before the company. Courts have found this ambiguity against founders. List what you're keeping.

---

Contractors: The Highest-Risk Category

Employees get automatic work-for-hire protection in most cases. Contractors don't. Under copyright law, work made for hire in the independent contractor context only applies to nine specific categories of works — and standalone software doesn't make the list. A contractor agreement that says "all work product is work for hire" alone is legally insufficient for software.

You need both: a work-for-hire designation and a present-tense assignment as a backup. The assignment does the work the work-for-hire clause can't. For more on why the present tense matters specifically, see our piece on the "hereby assigns" language.

Signs your existing contractor agreements may be deficient:

• Downloaded from a generic template site with no startup-specific IP provisions
• Say "agrees to assign" rather than "hereby assigns"
• Link IP ownership to payment (the company owns it once the invoice is paid)
• Were signed after the contractor started work
• Were never signed at all

The last one is more common than it sounds. Plenty of early-stage contractors start with a Slack DM and a Venmo payment, no agreement in sight.

---

2026 Gotchas: AI Training Data and Open Source

AI Training Data Is Now an IP Assignment Issue

This is new ground that most startup legal guides haven't caught up to yet. If your company is:

• Building a model trained on proprietary data
• Using contractors or employees to label, curate, or generate training data
• Using human feedback (RLHF or similar) from contractors to shape model behavior

...then the training data itself is a form of IP, and the people who created it need to have assigned their rights.

Here's the specific risk: a data labeler or contractor who curated your fine-tuning dataset made creative selections and judgments. Under copyright law, original creative selection and arrangement is copyrightable. If there's no IP assignment in their contract, your training data has a clouded chain of title — and so does any model trained on it.

This is not theoretical. Investor diligence on AI companies in 2025–2026 is increasingly asking not just "who wrote your code" but "who created your training data and what did they sign." The assignment chain for training data is becoming as scrutinized as the assignment chain for the codebase.

What to do:

• All data labelers, annotators, and RLHF contractors need a present-tense IP assignment covering their contributions
• Your training data pipeline documentation should identify the source and license status of every data source
• Any proprietary dataset assembled from third-party sources needs a clear record of what was licensed and how

Open Source AI Libraries: The AGPL Trap

The open source risk that most startup founders are familiar with — don't include GPL code in your proprietary codebase — has a new wrinkle in the AI stack. Several widely-used AI libraries and model weights are released under the AGPL (GNU Affero General Public License), which extends copyleft obligations to network use. Running AGPL-licensed code as a service, even without distributing it, can trigger the obligation to open-source your modifications.

Examples that have tripped up founders:

• Certain versions of libraries in the Hugging Face ecosystem ship under AGPL. Developers pulling from Hugging Face without reading license files have incorporated AGPL code into proprietary inference infrastructure.
• Some database adapters and vector store integrations used in AI applications are AGPL-licensed, not MIT.
• Model weights themselves sometimes carry restrictive commercial licenses (Meta's Llama models, for example, have their own commercial use restrictions that prohibit certain high-volume applications)

An AI application that appears to be built on permissive libraries may have AGPL components buried several dependency levels deep. Investors ask for a software bill of materials (SBOM) specifically to find these. Running an automated scan (tools like FOSSA or Snyk) before your first investor meeting is cheap. Discovering a GPL-contaminated codebase in diligence is not.

---

Automatic Assignment Clauses That Actually Hold Up

The gold standard is a present-tense, present-assignment clause that doesn't depend on any future action or condition:

"Employee/Contractor hereby irrevocably assigns to the Company, its successors and assigns, all right, title, and interest in and to any and all Inventions (as defined herein), including all patent rights, copyrights, trade secret rights, mask work rights, and all other intellectual property rights therein."

Four elements that make this hold up:

1. Present tense. "Hereby assigns" — not "agrees to assign," "shall assign," or "will assign." The Stanford v. Roche case established that a present-tense assignment conveys legal title the moment IP is created; a promise to assign conveys only an equitable interest that loses to a later present assignment. See our full breakdown.

2. No payment contingency. The assignment is effective upon creation of the IP, not upon payment of the invoice. Payment is a separate contractual obligation. Linking the two makes the IP a hostage in any billing dispute.

3. Explicit catch-all scope. Cover patents, copyrights, trade secrets, mask works, and "any other intellectual property rights." IP law creates new categories; don't list only the ones you thought of today.

4. Cooperation and power of attorney. The assignor agrees to execute whatever further documents are needed to perfect the assignment, and grants an irrevocable power of attorney to sign those documents on their behalf if unavailable. This is the safety net — it means a contributor who becomes unreachable doesn't block you from filing a patent or closing a round.

---

Before Your First Investor Conversation: A Quick Checklist

• Every founder has signed an IP assignment agreement at or near incorporation, covering pre-incorporation work
• Schedule A / prior inventions carve-outs completed and signed by each founder
• Every contractor engagement — no matter how small — has a written agreement with a present-tense IP assignment
• Every employee has a signed CIIA from their start date (no gaps, including early hires who joined informally)
• Open source usage has been audited — no copyleft licenses in proprietary code, no AGPL AI libraries in production infrastructure
• AI training data contributors have signed IP assignments covering their labeling/curation work
• No contractor agreements condition IP ownership on payment
• Gaps identified and remediation underway (cleanup assignments, confirmatory assignments from departed contributors)

Getting this right before you raise is straightforward. Getting it right after a diligence finding is expensive, slow, and occasionally deal-killing.

---

Flux Law works with early-stage founders on IP assignment, formation documents, and fundraising preparation. Learn more →