IP Due Diligence in Startup Funding Rounds: Navigating Ownership, Licensing, Open-Source Risks, and Warranties

Introduction : Facebook’s 2014 purchase of Oculus VR for $2 billion was a triumph for the startup world, but a legal reckoning was brewing in the background. Before acquisition, ZeniMax Media alleged Oculus Co-founder Palmer Luckey, and former ZeniMax employee John Carmack had used ZeniMax’s proprietary code and trade secrets to build the Oculus Rift. The jury ultimately found Oculus liable not for trade secret misappropriation, but for breach of a non-disclosure agreement, copyright infringement, and trademark violation, and awarded ZeniMax $500 million. The case remains a cautionary tale: investors don’t just finance projections of future returns – they invest in intellectual property IP. If that IP is defective, or carries infringement liabilities, the whole deal can fall apart.

For early-stage startups, value rarely sits in a server rack or office lease, it sits in intangible assets: source code, trade secret algorithms, patentable designs, data pipelines, and brand trademarks. IP due diligence is therefore central to the legal and commercial audit that venture capital firms run before committing to Seed and Series A rounds.

The investor counsel conducts this inquiry to confirm the target firm actually owns, or holds the right to exploit the technology behind its product. Gaps in this chain can depress valuation, derail funding altogether, or expose founders to personal liability, and costly pre-closing restructuring.

This article examines how VC firms conduct IP audits at the early stage of common ownership issues, open-source software risks, trade secret contamination and the negotiation of IP representations and warranties – drawing on real disputes, statutes and case law. It closes with a practical pre-diligence checklist founders can use before approaching institutional investors.

Legal Provisions

Auditing a startup’s IP portfolio draws on statutory intellectual property regimes, employment law, contract law and commercial licensing standards. Four legal areas matter most when reviewing a startup’s IP assets.

Statutory Ownership Principles vs. Work-Made-for-Hire : Under statutory copyright regimes – the US Copyright Act 1976, s. 201 and the Indian Copyright Act 1957, s. 17: the individual who creates an original work is its first owner. The ‘work-made-for-hire’ doctrine is a statutory exception: copyright in work created by an employee within the scope of employment vests automatically in the employer.

VC auditors take an in-depth look at the width of this exception. Owners of a company are not automatically covered, neither are independent contractors, offshore developers, advisors or pre-incorporation founders. The startup has an implied, non-exclusive license, and not an ownership right over their contributions, if there is no written assignment agreement. Patents work differently. US law (35 U.S.C. § 111) and Indian law (Patents Act 1970) grant rights as first to the individual inventor with no work-made-for-hire equivalent. A mere act of hiring does not give the employer the right to an employee’s invention without an express written assignment.

Assignment Language – Present vs. Future Assignments : A common issue cropped up during the IP audits was the use of standard employment and contract agreements. The difference under contract law is extreme: If they have to be assigned in the future, then nothing is assigned now; there is only a contractual promise to assign them at a later time. Present-tense language: an individual “assigns” or “hereby assigns” all right, title, and interest in “future inventions”, is deemed a self-executing assignment. When the invention or the source code is developed the legal title to the source code or invention becomes vested in the company automatically at that time.

In contrast, language like “agrees to assign” or “shall assign future inventions” does not constitute an actual promise to assign the asset but rather an equitable promise which requires a second and affirmative assignment document when the asset is actually created. If the engineer or founder leaves the company before signing the second document, then the legal title to the work is still in the hands of the engineer, not the company, and that’s something that can be problematic in diligence, or only come up when someone looks for it.

Open Source Software (OSS) Licensing Governance : A typical software stack can be composed of open-source libraries, up to 80% of it. Open source accelerates development but carries with it the risk of copyright law. There are two types of licenses that are the most important:

• Library licenses that are permissive (MIT, Apache 2.0, BSD): these licenses permit commercial use, modification and redistribution with minimal obligations, usually a copyright notice.
• Copyleft/reciprocal licenses (GPL v2/v3, AGPL): impose requirements that proprietary code used in conjunction with the open source code be made available under the same conditions; “copyleft contamination” risk that can compel disclosure of code that rests in a startup’s trade secret.

Key Arguments and Legal Analysis

An Investor Evaluation: Seed vs. Series A : Seed : Chain of title. Investor counsel’s main question at Seed stage is very simple: Does the company own what it claims to have built? In the early days of a startup, when it is being developed by its co-founders either while they are still students or working elsewhere, diligence is directed at the absence of an unbroken chain of title; that is, that each and every contributor has signed a Proprietary Information and Inventions Agreement (PIIA) and that no third party, whether a university tech-transfer group or a previous employer, has a competing claim. The series A is entitled Freedom to Operate and Portfolio Defensibility. At Series A when product-market fit and scaling the business, diligence expands to three areas:

• Freedom-to-Operate (FTO): counsel reviews patent, copyright and trademark databases to identify infringement risks, including those posed by Patent Assertion entities.
• Portfolio strength: investors check for the presence of patents (especially hardware, biotech, deep-tech software). Investigate filing strategy; domestic, PCT and prosecution history for vulnerability to invalidation.
• Contractual leakage: Auditors check enterprise client contracts and vendors’ contracts to identify any enterprise clients that may have unintentionally acquired customizations or source code during a rushed pilot.

Common Red Flags

Red Flag 1: Defective founder assignments. The most common problem uncovered in early-stage IP audits is a broken ownership chain. Consider three co-founders who build a fintech prototype at a hackathon over a weekend. Six months later they incorporate, but one co-founder resigns over a strategy dispute. The remaining two then receive a $2 million Seed term sheet. In the course of diligence, investor counsel learns that the departed co-founder wrote 30% of the core repository before incorporation and never signed a PIIA or a formal IP assignment agreement. Under the law, that founder is a co-legal owner of the original codebase, and can either demand an equity buyout or seek an injunction to stop the round entirely. To manage this risk, VC counsel routinely requires signed assignment agreements and quitclaim releases from every founder and early contributor before an investment closes.

Red Flag 2: Moonlighting and prior-employer contamination. If a founder or lead engineer develops the core ideas behind a startup while employed at a third-party tech firm, that employer can assert a claim to the resulting IP. The highest-profile example remains the dispute between Waymo Alphabet’s autonomous vehicle division and Uber. Waymo alleged that its star engineer, Anthony Levandowski, accessed more than 14,000 confidential documents, including lidar trade secrets, in the months before he left to start a self-driving truck company called Otto, which Uber then acquired for $680 million. The litigation led to Levandowski’s criminal indictment and a settlement in which Uber gave Waymo equity valued at roughly $245 million. During diligence, investors check whether technical founders built key software on personal equipment and personal time. Statutes such as California Labor Code § 2870 do offer some protection for inventions developed on an employee’s own time without employer equipment or trade secrets but that protection weakens sharply once the startup’s product overlaps with the former employer’s actual or reasonably anticipated business.

Red Flag 3: AGPL/copyleft contamination in SaaS architectures. Modern software audits increasingly run static code scanners, tools like Black Duck or FOSSA across the target startup’s repositories to flag open-source license violations. The most troublesome red flag in today’s SaaS architecture is the GNU Affero General Public License (AGPL). Ordinary GPL v2/v3 licenses trigger a disclosure obligation only on physical distribution to end users; the AGPL adds a network-use trigger. If an AGPL-licensed library is deployed on a server and communicates with users over a network, the business can be required to publish the entire communicating proprietary codebase under the AGPL. Where such a library isn’t cleanly isolated from the rest of the SaaS backend, the startup may need to rewrite core parts of its infrastructure before an investor will release funds.

IP Representations, Warranties and Indemnities : IP reps and warranties (R&Ws) are core provisions in Series A Stock Purchase Agreements and Share Subscription Agreements, allocating risk between founders and investors.

Core representations investor counsel typically requires

• Clear title: the company owns its IP free of third-party liens, royalties, or claims.
• Non-infringement: company operations don’t infringe or misappropriate any third party’s patent, copyright, trademark, or trade secret.
• Open source compliance: no OSS use that would compel disclosure of proprietary code.
• Valid assignments: every employee and contractor who contributed to the IP has signed a PIIA with present-tense assignment language.

Negotiating modifiers

• Knowledge qualifiers: While “founder’s knowledge after reasonable inquiry” absolute global non-infringement is not possible at the early stage of a company due to the number of existing patents.
• Disclosure schedules: If there are known exceptions, such as an open-source dependency, a pending trademark dispute or an unrecorded contractor assignment, that is a risk that is assumed by the investor once the contract is signed.
• Unresolved issues that arise during diligence can be addressed through a targeted indemnity with an escrow that will cover a portion of the investment for a certain period of time.

Founder Pre-Diligence Checklist

Phase 1: Chain of Title and Assignment

• Ensure that each co-founder signed a PIIA in the present tense (“does hereby assign”) prior to any coding.
• Vouch for freelancers, offshore agencies, and designers to be paid for work and have signed written contracts.
• Secure releases from the university or employer for any founder who created core assets during his or her university or employer affiliation.

Phase 2: Codebase and Open-Source Governance

• Run automated OSS compliance scans (FOSSA, Black Duck, Snyk) across all repositories.
• Find and remove copyleft parts or substitute AGPL/GPL libs with permissive parts (MIT, Apache 2.0) before the data room opens.
• Have an up-to-date list of commercial APIs and licensed components, and ensure subscribed and renewed.

Phase 3: Trade Secret and Brand Protection

• Establish formal trade secret controls: role-based access, encrypted repositories, two factor authentication for source code, model weights.
• Register core trademarks: company name, logo, product lines in major jurisdictions of operation prior to announcing a large round.
• Create a consistent approach to NDAs with commercial partners, advisors and pilot customers before technical disclosure.

Relevant Case Law

Board of Trustees of the Leland Stanford Junior University v. Roche Molecular Systems, Inc. (2011)

A Stanford research fellow, Dr. Holodniy had signed an agreement in which he “agreed to assign” future inventions to the university. Subsequently, he worked for Cetus (now acquired by Roche), and signed a separate agreement which assigned “does hereby assign” to Cetus on his own inventions made at Cetus. When Roche was later sued by Stanford for patent infringement for the HIV assay technology, the Supreme Court ruled that the contract did not constitute an executory promise to assign, but rather Cetus’s language was an immediate transfer of legal title, and Roche was therefore not liable to Stanford. 

Significance: This is the standard case when writing assignments. VC counsel looks carefully at both employment and contractor agreements for assignment language in the present tense, and well-intentioned “agrees to assign” can vest title in the inventor.

Jacobsen v. Katzer (2008)

Robert Jacobsen published model train automation software that had been written under the Artistic License, an open source license. Matthew Katzer downloaded, modified and integrated it into a commercial product and did not meet the attribution requirements of the license. Katzer said this was a breach of contract rather than copyright infringement at best. The Federal Circuit disagreed, finding that the conditions in the open-source licenses can be considered copyright conditions and thus can be enforced in the context of copyright law (in that case, statutory damages and injunctive relief).

The significance: In the eyes of VC-backed startups, it means that using an open-sourced component without its license agreement is a copyright exposure, not a contractual one which would increase the risk of unmanaged OSS use.

Darius Rutton Kavasmaneck v Gharda Chemicals Ltd, (2014) 4 Bom CR 141.

The minority shareholder Darius Rutton Kavasmaneck brought a derivative action against Dr Keki Hormusji Gharda, the Managing Director of the company, to enjoin him from dealing with chemical process patents acquired by him in his own name. The Bombay High Court ruled that automatic transfer of patent rights to the company simply by virtue of the fact that the inventor is a director or utilized the company’s resources is not possible; a written assignment is necessary for the transfer of patent rights.

Significance: It highlights that a company is a legal entity distinct from its founders/directors; that equity shareholding or holding a position of responsibility within the company is not, in and of itself, sufficient to make the company the owner of the IP created by the individual. Only a formal written assignment does.

Practical Application & Industry Relevance

AI training- data diligence : AI startups have an additional two layers of responsibility. One, training data audits: investors’ legal counsel is looking into the model’s code and data flow for copyrighted information or material that was scraped from online sources that could be embroiled in pending litigation, like The New York Times Co. v. OpenAI or Getty Images v. Stability AI.

Second, open-weight model licenses, where many AI startups are founded on open-weight models like Meta’s Llama and Mistral, come with specific restrictions on commercial usage that can kick in once a certain usage threshold is reached, and require auditors to validate the startups’ scaling plans.

Valuation and Deal Mechanics

Legal risk rarely kills a deal outright once an investor is committed, it gets priced in instead, through

• Pre-money valuation adjustments for anticipated legal remediation costs.
• Holdbacks and indemnity escrows reserving part of the investment against specific known issues.
• Pre-closing conditions precedent requiring replacement of copyleft-encumbered libraries, formal university releases, or missing contractor assignments before funds release.

Conclusion

The reality of conducting due diligence on IP in an early-stage round isn’t a formality, it’s a way for investors to ensure that a startup has the legal rights to its core technology, and its quality of IP assets will directly influence, at least in part, the value of the business and how neatly a round goes. When founders skip IP documentation, they open themselves up to potential litigation in the future, lower valuation or possibly delayed deals.

It’s best to think about IP governance in the startup stage as something to establish from the beginning, rather than something to fit into under the gun pressure. Clean, present-tense assignment language from the get-go, disciplined open-source practices, documented controls over trade secrets, and periodic in-house legal review. But by taking an active approach to IP, startups can successfully complete institutional due diligence, secure growth capital and create actual enterprise value that can be protected from IP infringement claims.

Author:- Tanishka Gora, in case of any queries please contact/write back to us at support@ipandlegalfilings.com or   IP & Legal Filing.

References / Endnotes

Primary Sources: Legislation and Statutes

1. Copyright Act 1976, 17 USC § 201(b) (United States).
2. Patent Act, 35 USC § 111 (United States).
3. California Labor Code, § 2870 (United States).
4. Indian Copyright Act 1957, s 17 (India).
5. Patents Act 1970, s 6 (India).

Primary Sources: Case Law

1. Board of Trustees of the Leland Stanford Junior University v Roche Molecular Systems, Inc 563 US 776 (2011).
2. Jacobsen v Katzer 535 F 3d 1373 (Fed Cir 2008).
3. Darius Rutton Kavasmaneck v Gharda Chemicals Ltd (2014) 4 Bom CR 141 (India).
4. Waymo LLC v Uber Technologies, Inc 2017 WL 2120060 (ND Cal 2017).
5. ZeniMax Media, Inc v Oculus VR, LLC 166 F Supp 3d 697 (ND Tex 2015).

Secondary Sources: Books, Journal Articles & Legal Reports

1. Robert W Gomulkiewicz, ‘Conditions and Covenants in License Contracts: Tales from a Test of the Artistic License’ (2009) 17 Texas Intellectual Property Law Journal 335.
2. Ted Hagelin, ‘The Unintended Consequences of Stanford v. Roche’ (2012) 52 Santa Clara Law Review 835.
3. Sean M O’Connor, ‘The Real Issue Behind Stanford v. Roche: Faulty Conceptions of University Assignment Policies’ (2013) 19 Michigan Telecommunications and Technology Law Review 379.
4. Bryan M Carson, ‘Legally Speaking — The Legality of Open Source Part II: Jacobsen v. Katzer’ (2009) 21(1) Against the Grain 60.
5. R Michael Azzi, ‘Resuscitation of the Open Source Movement: Jacobsen v. Katzer’ (2010) 2010 University of Illinois Law Review 1271.
6. Mark A Lemley, ‘Intellectual Property and Shrinkwrap Licenses’ (1995) 68 Southern California Law Review 1239.