IP Diligence for Fundraising & M&A

Term sheets are exciting; diligence is where deals actually live or die. And in a technology company, the single most common reason a promising round or acquisition stalls is intellectual property — not the tech itself, but the paperwork proving who owns it. This is the pillar guide to IP diligence for fundraising and M&A: what investors and buyers actually look for, the gaps that scare them, and how to walk into a deal with an IP file that speeds the wire instead of stopping it.

Why does IP diligence decide valuations and kill deals?

For most startups, the company is its intellectual property. There are rarely factories or hard assets — the value is the code, the algorithms, the brand, the data, and the trade secrets. So when a sophisticated investor or acquirer evaluates you, a huge share of their diligence is aimed at one question: does this company clearly and exclusively own the assets it’s charging us for?

If the answer is a confident yes, IP becomes a value driver — registered patents and trademarks, a clean codebase, and airtight assignment agreements all support a higher valuation. If the answer is murky, IP becomes a deal risk, and buyers respond in predictable ways:

• Price reductions to account for the risk they’re absorbing.
• Larger escrow holdbacks or purchase-price adjustments tied to specific IP fixes.
• Special indemnities that carve IP out of the normal liability caps.
• Closing conditions requiring you to cure the defect before money moves.
• Walking away entirely when the problem is severe or the seller can’t fix it in time.

The through-line is simple: uncertainty about ownership transfers risk to the buyer, and buyers price or reject risk. Everything below is about removing that uncertainty before someone else finds it. For a founder-level overview of the process from the investor’s side, our companion guide on IP in fundraising due diligence walks through what a typical data-room request looks like.

What do investors and acquirers actually look for?

Across venture rounds and acquisitions, the IP diligence checklist rhymes. The core items are:

• Clean chain of title. Documented, unbroken assignment of every core asset from its creator (founder, employee, or contractor) to the company.
• Registered IP in good standing. Patents, trademarks, and copyright registrations that are current, correctly owned by the entity, and not lapsed for missed maintenance fees.
• No encumbrances. No liens (often from a bank loan or venture debt via a UCC-1 filing), no exclusive licenses that gave away a field of use, and no obligations that limit what a buyer can do with the IP.
• No infringement exposure. No pending or threatened litigation, cease-and-desist letters, or obvious freedom-to-operate problems.
• Controlled open source. A known inventory of open-source dependencies with license terms that don’t jeopardize your proprietary code.
• Proper confidentiality. Trade secrets protected by NDAs and reasonable measures, so they still qualify as protectable assets at closing.

Each of these gets its own sibling guide in this pillar. Start with the one that catches the most companies off guard: whether the company even owns its own product.

How do you run an IP audit before you raise?

The best time to find an IP problem is roughly 6 to 12 months before you need to close a deal — because most defects are fixable, but only if you have time to chase down signatures from people who have since left the company. A pre-raise audit inventories what you have and stress-tests whether you truly own it.

At a minimum, the audit should:

1. Build an IP inventory — every patent, trademark, copyright, domain, key trade secret, and material piece of software, mapped to who created it and when.
2. Trace each asset’s chain of title back to a signed assignment.
3. Collect the agreements — founder IP-assignment agreements, employee PIIAs (proprietary information and invention-assignment agreements), and contractor contracts.
4. Scan the codebase for open-source components and their licenses.
5. Confirm registrations are current and recorded to the correct legal entity at the USPTO and Copyright Office.
6. Flag any encumbrances or disputes — liens, licenses, demand letters, or prior employer claims.

This is not busywork; it’s the difference between handing a buyer a tidy data room and scrambling during an exclusivity period. Our detailed walkthrough lives in the IP audit before you raise, and the foundational question of entity ownership is covered in who owns your startup’s IP.

Who owns the code — and where do assignment gaps come from?

This is the number-one killer in tech diligence. Founders assume the company owns everything built for it. The law often disagrees.

Two default rules create the trap:

• Copyright: Under the Copyright Act, work created by an employee within the scope of employment is generally a “work made for hire” owned by the employer. But an independent contractor’s work is not automatically the company’s — it’s a work made for hire only if it falls into one of nine narrow statutory categories and there’s a signed agreement. Software usually doesn’t fit those categories, so absent a written assignment, the contractor keeps the copyright.
• Patents: Under the Supreme Court’s decision in Board of Trustees of Stanford University v. Roche (2011), an invention is initially owned by the individual inventor, not their employer, unless they’ve signed a present assignment.

That case also underscored a drafting subtlety courts still enforce: an agreement saying an employee “agrees to assign” future inventions may only create a promise, while “hereby assigns” operates as a present transfer. The wrong verb can leave a gap even when everyone signed something.

Classic assignment gaps include:

• A co-founder who left early and never signed an IP assignment.
• Contractors or offshore developers who wrote core code with no assignment clause.
• Work done before the company was incorporated, never contributed to the new entity.
• Inventions an engineer created at a prior employer whose agreement may capture them.

The fix is usually a confirmatory assignment signed before closing — cheap and easy if the person is cooperative, expensive or impossible if they’ve become a competitor or a holdout. That’s exactly why you hunt for these early. We go deep on identifying and curing them in IP assignment gaps.

Why is open-source software a diligence red flag?

Nearly every modern product is built on open source, and open source is not inherently a problem — the problem is not knowing what you’re using and under what terms. Licenses fall into two broad camps:

• Permissive licenses — MIT, BSD, Apache 2.0 — let you use the code in proprietary products with light obligations, mostly attribution and (for Apache) a patent grant. These are generally acceptable to acquirers.
• Copyleft licenses — GPL and especially AGPL — can require that if you distribute (or, for AGPL, even network-serve) software that incorporates the component, you make your combined source code available under the same terms. LGPL is weaker: it generally lets you link to a library (especially dynamically) and keep your own code proprietary, so long as users can relink. For a company whose value is its proprietary code, an unnoticed strong-copyleft dependency is a potential catastrophe.

During diligence, acquirers run software composition analysis (SCA) tools to inventory every dependency and its license — they will find what you don’t disclose. A single strong-copyleft library linked into your core product can force a costly rewrite, a special indemnity, or a price cut. The defense is an ongoing open-source policy and a maintained bill of materials (SBOM) so you can answer license questions instantly. We cover detection and remediation in open-source risk in due diligence, and license selection strategy in open-source licensing for startups.

What IP reps and warranties will founders have to sign?

In an acquisition — and in the representations section of many financing documents — the company and often the founders personally make a set of IP representations and warranties: contractual promises that, if false, shift money or liability. Typical IP reps state that:

• The company owns or has valid licenses to all IP used in the business.
• The IP does not infringe any third party’s rights, and no one has claimed it does.
• There are no liens, encumbrances, or exclusive licenses except those disclosed.
• All employees and contractors have assigned their work to the company.
• Open-source use complies with applicable licenses.

These reps are enforced through several mechanisms buyers negotiate hard: indemnification (you cover the buyer’s losses), an escrow holdback (often 10–15% of the price parked for 12–24 months), a survival period defining how long claims can be brought, and sometimes a special or fundamental indemnity for IP that sits outside the normal liability cap. Increasingly, deals use representations and warranties insurance (RWI) to backstop these promises — but insurers do their own diligence and won’t cover known problems.

Two terms worth knowing: a “knowledge qualifier” (“to the company’s knowledge…”) limits a rep to what you actually know, and an anti-sandbagging clause can bar the buyer from recovering for problems they already knew about. What you can honestly represent depends entirely on the audit you did beforehand. See IP reps and warranties for how to negotiate and survive them.

How does IP diligence work in an acquihire?

An acquihire — buying a company mainly for its team rather than its product — flips the usual emphasis, but IP diligence still matters intensely. Even if the acquirer plans to shelve the product, they need clean rights to whatever they’re absorbing and, critically, to the people.

The key issues:

• Employee assignment and retention. The acquirer wants every engineer’s inventions clearly assigned and those engineers on board post-close, usually via new offer letters, retention bonuses, or golden handcuffs.
• Wind-down of the old entity. If the acquirer buys assets and lets the shell dissolve, they need the target’s IP assigned out cleanly first, with investor and board consents.
• Trailing IP claims. Any code or invention the team built at the target must not be encumbered by its prior obligations or open-source entanglements.
• Prior-employer conflicts. The acquihired engineers must not be dragging in IP or trade secrets from where they worked before.

Even a modest acquihire priced mostly as compensation still requires the buyer to confirm it isn’t inheriting an ownership dispute. Our guide on IP in acquihires breaks down the structure and the traps.

The bottom line

IP diligence rewards preparation and punishes surprises. Investors and acquirers are asking one thing in a dozen ways: does this company cleanly own what it’s selling, free of infringement, liens, and license landmines? The founders who breeze through diligence are the ones who audited themselves first — inventoried every asset, traced each to a signed present assignment, scanned their code for copyleft, kept registrations current, and could stand behind their reps and warranties without crossing their fingers. Do that work before you circulate a deck, and IP becomes the reason your valuation holds. Skip it, and you’ll be chasing a former contractor’s signature during the one week you can least afford to. To see how these ownership fights actually play out in litigation, browse our trade secret and IP-ownership case archive.

This guide is general education, not legal advice, and does not create an attorney-client relationship. IP diligence and deal terms turn on your specific facts, corporate structure, and the governing agreements — consult an attorney licensed in your jurisdiction before raising capital or signing a purchase agreement.