Guide to IP Diligence in Emerging VC
A framework for assessing intellectual property when evaluating deals
Intellectual property has a way of showing up in two very different flavors during a fundraise. The first is the founder who opens the pitch with "we're fully patent-protected" as though that phrase alone closes the conversation — it doesn't. The second is the fund manager who never asks about IP at all, discovers a chain-of-title problem at Series B, and watches a clean exit turn into a litigation nightmare. Both approaches are wrong, and both are more common than they should be.
The goal for fund managers is not to become an IP expert. It is to know which questions expose real risk, which answers should raise flags, and when to bring in a qualified IP expert before writing a check. IP diligence does not require a law degree. It requires a framework — and a healthy instinct for when something does not add up.
What You Are Actually Evaluating in IP Diligence
When you look at a portfolio company's IP position, you are really asking three questions: Who owns it? Is it defensible? And does it actually cover the product being sold? Founders routinely conflate these, which is why "we filed a patent" is a starting point for diligence, not an ending point.
Ownership is the question that catches people off guard most often. IP ownership disputes are among the most common — and most dangerous — issues in early-stage diligence. Common landmines include:
University spinouts: Many founders developed their core technology while affiliated with a university. Universities have IP assignment policies that may give them ownership or licensing rights over inventions created using university resources. If this has not been formally resolved with a clear license or assignment, the company may not actually own its own technology.
Prior employer claims: Founders who built prototypes or developed core concepts while employed elsewhere may face claims from former employers under invention assignment agreements. This is especially common in deep tech, biotech, and enterprise software.
Contractor assignments: Work done by contractors or freelancers does not automatically belong to the company. Without a written assignment agreement, the contractor may hold IP rights — and they may not even know it.
Departed co-founders: A co-founder who left before the company's IP was formally assigned to the entity can be sitting on rights that now belong to a person with no interest in the company's success.
Validity asks whether the IP is actually defensible — whether the patent claims are broad enough to matter and whether a challenge under inter partes review (IPR) would likely survive. A weak patent can be worse than no patent, because it creates false confidence.
Scope closes the loop: does the IP actually cover the product being commercialized, or does it protect a version of the product that no longer exists?
Green Flags in IP Diligence
Not every IP situation is a problem waiting to be discovered. Some founding teams have done the work, and it shows. The following signals indicate a team that has thought carefully about IP as a strategic asset rather than a compliance checkbox. Strong IP positions share common characteristics. When you see these, it is a meaningful positive signal — not just about the IP itself, but about the quality and sophistication of the founding team:
Clean chain of title: All IP is formally assigned to the company entity — not held personally by founders, not lingering in a university agreement, not split across multiple individuals from a previous venture.
Provisionals filed before public disclosure: The team understood first-to-file principles and secured priority dates before pitching publicly, publishing, or presenting at conferences.
Patent strategy aligned with business model: The team has filed where infringement is actually detectable and enforceable, rather than reflexively filing on everything or filing nothing at all.
Founders who can articulate the boundaries of their protection: A founder who can tell you exactly what is and is not covered by their IP — and why — is a dramatically better signal than one who says "our IP expert handles all of that."
IP expert already engaged: Having a qualified patent strategist involved early, especially one with domain expertise in the relevant technology area, signals institutional-grade thinking from a team that may still be pre-revenue.
Red Flags That Deserve a Harder Look
Red flags in IP diligence rarely announce themselves. They tend to surface as small inconsistencies, vague answers, or phrases that sound reassuring until you think about them for a moment. "Our IP expert is handling it" is not an answer — it is a deflection. Here is what to listen for:
"We disclosed at a conference before filing." The US grace period may apply, but international patent rights may already be lost. Ask specifically which jurisdictions matter to the business model. If the target market is Europe or Asia, this may be a significant problem.
"Our IP expert is handling all the IP." Founders should understand the basics of their own IP position. A team that cannot explain what is filed, what it covers, or what stage prosecution is at has outsourced their strategic thinking to a vendor.
Trade secrets with no formal protection in place. Claiming trade secret protection while having no NDAs with employees, no access controls on sensitive systems, and no written policies around confidential information is not trade secret protection — it is wishful thinking.
Software or algorithm IP filed in unfavorable jurisdictions. Software patent enforceability varies significantly by jurisdiction. A US software patent may have limited value in markets where the company plans to operate.
Infringement that cannot be detected. If the core IP protects a method that runs inside a competitor's closed system — an algorithm, a data processing approach, a model architecture — there may be no practical way to identify infringement.
Deal-Breakers That Can Kill a Transaction
Some IP issues are fixable with time and money. Others are not — or at least, not without conditions that change the nature of the deal. The following scenarios warrant serious consideration about whether to proceed at all, and under what terms:
IP owned by a university or prior employer with unresolved claims. If the core technology was developed at MIT, Stanford, or a major tech employer and the ownership question has not been formally resolved, the company may be operating on borrowed time. This is not a disclosure footnote — it is a foundational question about whether the company owns its own product.
Core product relying on IP held by a departed co-founder. A co-founder who left with no formal IP assignment and now has no alignment with the company's success is a litigation risk that will surface at the worst possible time.
Public disclosure before filing in a non-grace-period jurisdiction. If the company's target markets include the EU, Japan, or China — and the technology was publicly disclosed before any filing — those international patent rights may be permanently lost.
Pending litigation or known third-party IP conflicts. Active disputes, cease-and-desist letters, or awareness of potentially infringing patents that have not been addressed are not background noise — they are existential risks.
When these issues surface, the appropriate response depends on severity. For resolvable problems, consider conditioning the investment on completion of IP cleanup — formal assignments obtained, university licenses secured, FTO analysis completed — with clear milestones and escrow mechanisms if necessary. For unresolvable problems, walk.
Diligence Questions to Ask in Early Conversations
You do not need to wait for formal diligence to start building an IP picture. These questions belong in early founder conversations — they take five minutes and reveal an enormous amount about the sophistication of the team:
What IP have you filed, and who legally owns it?
Has any technical disclosure happened before any filing was made?
Is there anything you are protecting as a trade secret, and what specific steps are you taking to maintain that secrecy?
Has an IP expert reviewed all IP assignment agreements — including with co-founders, employees, and contractors?
Have you done any freedom-to-operate analysis? (See Article 3 in this series.)
Were any elements of the core technology developed while founders were affiliated with a university or prior employer?
Do you have NDAs in place with all parties who have had access to technical details?
Founders who answer these questions fluently and specifically — without needing to check with anyone else first — are telling you something important about how they run their company. Founders who cannot answer them are telling you something important too.
When to Bring in an IP Expert for Diligence
The instinct to bring in an IP expert late in the process is one of the most common — and costly — mistakes in diligence.
By the time a deal reaches formal review, timelines are compressed, positions are entrenched, and leverage is limited. At that stage, IP diligence often becomes a confirmation exercise rather than a true risk assessment. If a material issue surfaces late — unclear ownership, problematic prior art, or overlooked third party rights — the options are no longer strategic. They are reactive.
An IP expert is most valuable before the deal feels real.
Early engagement allows for something far more important than issue-spotting. It creates space for interpretation, context, and judgment. It allows risk to be understood in degrees, not discovered as a surprise. It allows investment decisions to be made with clarity rather than urgency.
In practical terms, this means bringing in an IP expert as early as:
Initial screening conversations, when a company’s core technology is first being evaluated
Pre-term sheet discussions, when conviction is forming but before positions harden
Any point at which the deal thesis relies meaningfully on proprietary technology
Waiting until formal diligence assumes the IP will hold up. Bringing in an expert early tests whether that assumption is warranted.
There are also specific signals that should trigger immediate involvement:
Inconsistent or vague answers around ownership or inventorship
Prior affiliations with universities or employers tied to the core technology
Claims of broad protection without the ability to articulate what is actually covered
Any indication that the product may operate in a crowded or highly patented space
Known competitors with active patent portfolios in the same area
In these moments, speed matters — but not in the way most teams think. The goal is not to move faster to close. The goal is to move earlier to understand.
IP diligence is not a box to check at the end of a process. It is a lens that should be applied from the beginning.
Because the real cost of IP risk is not what you discover.
It is what you discover too late.
Know what you need to know: have an IP diligence plan.
IP diligence is not about becoming a patent expert. It is about asking the right questions early, recognizing the signals that separate well-prepared founding teams from those sitting on landmines, and knowing when the stakes are high enough to bring in a specialized expert. The founders who have done the work — clean assignments, comprehensive provisionals, deliberate trade secret policies — will tell you clearly and confidently. The ones who have not will give you vague answers and redirect to someone else. Both responses are data. Use them.