How Startup IP Due Diligence Works Before a Fundraise

IP due diligence before a fundraise requires proving that your company cleanly owns every piece of intellectual property it relies on. Investors verify assignment chains from founders and contractors, audit open source license exposure, check for prior employer contamination, and confirm trademark clearance. Gaps in any of these areas routinely delay closings by weeks or kill deals entirely.

---

What Investors Actually Look for in IP Diligence

Venture investors aren't conducting IP diligence because they enjoy paperwork. They're protecting against the existential risk that the company doesn't actually own its core technology. If a former employer, contractor, or co-founder can credibly claim ownership of the codebase, the entire investment thesis collapses.

Here's what a thorough investor-side IP review covers, roughly in order of importance:

The Assignment Chain

The single most scrutinized element is whether every person who contributed to the company's intellectual property has signed a valid assignment agreement transferring their rights to the company. This includes:

• Founders: Did each founder execute an IP assignment agreement at or before incorporation? Was the assignment of pre-incorporation work (the "background IP") explicitly covered?
• Employees: Does every employee have a signed CIIA (Confidential Information and Inventions Assignment agreement) with a present-tense assignment of work product?
• Contractors: Were independent contractors engaged under agreements with explicit work-for-hire language and a backup assignment clause? (Work-for-hire alone is insufficient for many IP types under copyright law.)
• Advisors: Did advisors who contributed to product development sign IP assignment provisions?

A single missing signature in this chain — especially a departed co-founder — can create a cloud on title that sophisticated investors won't ignore.

Prior Employer Contamination

This is the risk that a founder or early employee developed key technology while employed elsewhere, meaning the former employer may have a claim. Investors look for:

• Employment agreement review: What did the founder's prior employment agreement say about inventions? Many tech company employment agreements include broad invention assignment clauses covering anything "related to" the employer's business.
• Temporal overlap: Was there any period where the founder was simultaneously employed elsewhere and building the startup's technology?
• Equipment and resources: Was any former employer's equipment, code, data, or proprietary information used in developing the startup's IP?
• Non-compete/non-solicit provisions: Are there restrictive covenants that could give a former employer leverage?

Investors may require founder representations and warranties specifically addressing prior employer IP issues. In high-risk cases (founder left Google to build a competing product), expect deeper scrutiny and possibly an opinion letter.

Open Source Exposure

Nearly every modern software company uses open source components. Investors don't object to open source usage — they object to unmanaged open source usage that creates legal exposure. The key concerns:

Copyleft licenses (GPL, AGPL, LGPL): These "viral" licenses require that derivative works be distributed under the same license terms. If GPL-licensed code is integrated into your proprietary codebase in certain ways, the entire codebase may need to be open-sourced. The AGPL extends this to network use (SaaS), making it particularly dangerous for cloud companies.

Permissive licenses (MIT, BSD, Apache 2.0): These are generally investor-friendly. They require attribution and license notice inclusion but don't impose copyleft obligations. Most investors are comfortable with permissive license usage as long as compliance (attribution) is maintained.

What investors want to see:

• A software bill of materials (SBOM) or open source audit showing all third-party components
• Confirmation that no copyleft-licensed code is integrated in a way that triggers copyleft obligations on proprietary code
• Evidence of a process for reviewing open source before inclusion (even an informal one)
• Compliance with attribution requirements

What kills deals: Discovering that the core product is built on top of AGPL-licensed components with no isolation layer, or that nobody tracked open source usage and a full audit would take months.

Trademark Clearance

Investors want to know that the company's name, product names, and key branding don't infringe existing trademarks. This is less about conducting a full trademark search (though that's ideal) and more about confirming:

• No cease-and-desist letters have been received
• A basic knockout search hasn't revealed obviously conflicting marks
• The company has filed (or plans to file) trademark applications for core marks
• Domain names are secured

Trademark issues rarely kill deals, but they can result in expensive rebranding requirements that investors factor into their risk assessment.

The CIIA Audit: Your First Line of Defense

The CIIA audit is the starting point for any IP diligence cleanup. Here's what a proper audit looks like:

Step 1: Build the Personnel Roster

List every person who has ever contributed to the company's intellectual property. This includes:

• All current and former founders
• All current and former employees
• All current and former contractors (including offshore developers, design agencies, freelancers)
• Advisors who contributed to product or technology

Step 2: Match Agreements to People

For each person on the roster, confirm:

• A signed CIIA or IP assignment agreement exists
• The agreement was signed before or on the date they began contributing work
• The assignment language covers the specific type of IP they contributed (code, designs, inventions, trade secrets)
• For contractors: the agreement includes both work-for-hire and backup assignment language

Step 3: Identify Gaps

Common gaps include:

• The "handshake" co-founder: An early contributor who helped build the MVP but never signed anything and has since left. This is the most dangerous gap.
• The overseas contractor: A development shop engaged over email without a formal agreement, or with an agreement governed by foreign law without clear assignment provisions.
• The intern: A summer intern who wrote a meaningful code module. Nobody thought to get a CIIA signed.
• Pre-incorporation work: Technology developed before the company existed, never formally assigned to the entity.

Step 4: Remediate

For current personnel, getting signatures is usually straightforward (though you may need consideration — a small equity grant or bonus — to make a retroactive assignment enforceable in some jurisdictions).

For departed personnel, remediation is harder and more expensive. You may need to:

• Track them down and negotiate a retroactive assignment (often requiring payment)
• Obtain a legal opinion that their contributions were minimal or non-copyrightable
• In worst cases, rewrite or replace the contributed code

This is why getting CIIAs signed on day one is so critical. Fixing the gap later is always more expensive.

Pre-Round IP Cleanup Checklist

Start this process at least 60–90 days before you plan to begin fundraising. IP cleanup takes longer than founders expect.

Weeks 1–2: Assessment

• Complete the CIIA audit (above)
• Run an open source scan (tools like FOSSA, Snyk, or Black Duck can automate this)
• Review all founder and key employee prior employment agreements for invention assignment and non-compete clauses
• Conduct a basic trademark knockout search for the company name and key product names
• Inventory all patents, patent applications, and trade secrets
• Identify any third-party IP licenses the company depends on

Weeks 3–6: Remediation

• Obtain missing CIIA/assignment signatures (current personnel)
• Begin outreach to former contributors for retroactive assignments
• Remove or isolate problematic open source components (replace AGPL with permissive alternatives where possible)
• File trademark applications for core marks if not already done
• Document the open source policy going forward
• Ensure all contractor agreements have proper IP provisions

Weeks 7–9: Documentation

• Prepare an IP summary memorandum for the data room
• Organize all signed IP agreements in a single, indexed folder
• Create the open source component inventory / SBOM
• Draft founder IP representations for the financing documents
• Prepare responses to standard due diligence checklist IP questions

Weeks 10+: Ready for Diligence

By this point, your IP house should be in order. When investors send their diligence request list, you can respond promptly and completely — which signals operational maturity and reduces friction in the closing process.

Open Source License Risks: A Deeper Dive

Because open source issues are increasingly central to IP diligence, it's worth understanding the risk spectrum in more detail.

The License Spectrum

From most to least restrictive:

1. AGPL-3.0: Copyleft triggered by network interaction (SaaS). Most dangerous for cloud companies.
2. GPL-3.0 / GPL-2.0: Copyleft triggered by distribution of derivative works. Dangerous for on-premise/distributed software.
3. LGPL: Copyleft applies to modifications of the library itself, but not to code that merely links to it. Manageable with proper architecture.
4. MPL-2.0: File-level copyleft. Modifications to MPL files must be open-sourced, but other files in the project are unaffected.
5. Apache-2.0: Permissive. Includes a patent grant. Generally safe.
6. MIT / BSD: Permissive. Minimal restrictions (attribution only). Generally safe.

Practical Guidance

• SaaS companies: AGPL is the main risk. GPL is less concerning because SaaS typically doesn't "distribute" software (it runs on servers), but the legal analysis isn't entirely settled.
• On-premise/SDK companies: Both GPL and AGPL are high risk. Even LGPL requires careful attention to linking architecture.
• All companies: Regardless of license type, maintain an SBOM and review new dependencies before adding them. An informal "someone checks the license" process is better than nothing.

What "Derivative Work" Means (and Why It's Ambiguous)

The core question with copyleft licenses is whether your code constitutes a "derivative work" of the copyleft-licensed component. Copyright law's derivative work definition is notoriously vague in the software context. Static linking vs. dynamic linking, API boundaries, and process separation all factor into the analysis. This ambiguity is itself a risk — investors don't like legal uncertainty around core IP.

Common Gaps That Kill or Delay Deals

Having advised on numerous venture financings, certain IP issues recur with painful regularity:

The Departed Co-Founder Problem

A co-founder who left acrimoniously and never signed an IP assignment agreement. They contributed to the core codebase. Now they're unresponsive, or they want money/equity to sign a retroactive assignment. This scenario can delay a financing by months and sometimes requires rewriting significant portions of the codebase. Preventing this requires proper founder agreements from day one.

The Consulting Company Origin Story

The company's technology was originally developed as a consulting project for a client, and the founders "spun it out." But the consulting agreement assigned all work product to the client. The founders need a license-back or assignment from the original client — who may not be inclined to cooperate, especially if the startup is now a competitor.

The University Research Connection

A founder developed core technology during a PhD program or research appointment. University IP policies typically give the university ownership of inventions created using university resources. A technology license from the university may be required, and the terms can be onerous (equity stakes, royalties, milestone payments).

The Unaudited Contractor Codebase

An offshore development team built significant portions of the product under vague contractual terms. The contracts may be governed by foreign law, making enforceability uncertain. The developers may have reused code from other client projects, introducing third-party IP contamination that's nearly impossible to detect without a code audit.

Building a Long-Term IP Hygiene Practice

IP diligence shouldn't be a fire drill before each fundraise. Companies that maintain clean IP practices continuously have faster, smoother closings. This means:

• CIIA on day one: Every employee and contractor signs before accessing any company IP
• Open source policy: Document which licenses are approved, which require review, and which are prohibited
• Quarterly IP reviews: Brief check-ins to confirm new hires have signed CIIAs, new open source dependencies are tracked, and no new third-party IP issues have emerged
• Invention disclosure process: For patent-eligible inventions, establish a lightweight process for engineers to flag potentially patentable innovations

These practices are part of scaling your legal operations as the company grows, and they pay dividends far beyond fundraising — they protect the company's most valuable asset on an ongoing basis.

Conclusion

IP due diligence is where many seed and Series A deals hit unexpected friction. The founders who close quickly are the ones who treat IP hygiene as an ongoing discipline rather than a pre-fundraise scramble. Start the cleanup early, get your assignment chain bulletproof, know your open source exposure, and have a clear story for any prior employer overlap. Investors will notice — and the deal will move faster because of it.