Startup acquisitions are a distinct category of M&A diligence, and the IP chain-of-title review is where their peculiarities are most likely to create post-close problems. The acquirer is buying technology — often the product is the entire reason for the deal — and the question of who actually owns that technology turns out to be more complicated than a clean data room suggests.
The pattern is consistent enough that we've started calling it the day-two problem: a reviewing associate works through the obvious first-tier IP documents on day one, sees Invention Assignment and Confidentiality Agreements (IACAs) for the founding team and finds formal patent filings, and marks the IP review as substantially complete. Day two — or week three, or six months post-close — the gap surfaces. Someone contributed code or a key algorithm who didn't sign an IACA. A contractor worked on the core module under an agreement that didn't include an IP assignment clause. A co-founder left the company before the assignment documentation was executed. The acquirer now owns a company whose product depends on IP that it doesn't clearly own.
Why the Gap Exists: The Startup IP Formation Pattern
Understanding why IP chain-of-title gaps are so common in startup acquisitions requires understanding how startups actually form and how IP ownership gets established (or doesn't) during that formation period.
In the first six to eighteen months of a startup's existence, the founding team is focused on building the product, acquiring customers, and surviving. Legal structure is handled by an attorney who sets up the corporate entity and issues equity. If the founding team uses a standard incorporation service or an attorney who isn't deeply experienced in IP formation, the documentation package may be technically complete in its employment agreement and equity documentation but missing the specific clause language that creates a valid present assignment of IP developed during the pre-formation period.
This is the most common gap: the founding team incorporated in month three, signed IACAs as part of incorporation, but had been writing code for four months before that. The IACA says "I hereby assign all IP developed during my employment." It doesn't say "I hereby assign all IP developed in connection with the Company's business, including IP developed before employment commenced." That gap — pre-incorporation work product — is a meaningful title cloud on a core technology asset.
The contractor problem
Outside the founding team, the contractor IP problem is at least as common. Early-stage companies routinely engage developers, designers, data scientists, and other technical contributors as contractors — for legitimate cost, flexibility, and efficiency reasons. Under U.S. copyright law, work-for-hire doctrine applies to employees' work created within the scope of employment, but not automatically to contractor work. For contractor work to be work-for-hire, it must meet specific statutory requirements: it must fall within one of the enumerated categories of works, and there must be a written agreement expressly designating it as work made for hire.
Startup contractor agreements from the 2018–2022 formation period are highly variable in quality. Some are well-drafted with explicit IP assignment and work-for-hire language. Others are project-scoped statements of work that are silent on IP ownership or that contain language that raises rather than resolves ownership questions. When the startup's core platform includes modules written by contractors under agreements that lack IP assignment language, the acquirer has a potential ownership gap in the product's most important code.
The departed co-founder gap
Startups with multiple founders frequently experience founder departures. A co-founder who leaves before Series A takes their equity position down in a negotiated buyout and departs. The question for IP diligence is whether that departure documentation addressed IP ownership — specifically, whether the departed co-founder executed a separate IP assignment agreement as part of the departure, or whether the departure was handled through equity mechanics only.
In a surprising number of cases, the departure agreement is silent on IP. The co-founder signed an IACA at formation that should cover the work they did while employed. But there's often ambiguity about work they did before signing the IACA, work they did on their personal equipment after hours, and improvements they contributed informally after their official departure date. When that co-founder's contributions touched the product's core, the ambiguity creates a title issue that an acquiring company's diligence counsel needs to address.
What Thorough IP Diligence Actually Reviews
Standard IP diligence checklists ask for: patent filings, trademark registrations, IACA copies for current employees, and employment agreements for technical staff. That list is necessary but not sufficient for startup acquisitions where the technology is the deal asset.
A thorough IP chain-of-title review in a startup acquisition should cover:
- Pre-incorporation work product. Interview the founders (or review available records) to understand when meaningful development work began relative to the incorporation date. If pre-formation development occurred, verify that IACA language covers it or obtain a confirmatory assignment from the founders.
- Contractor agreement inventory and IP clause audit. Obtain all significant contractor agreements for contributors to core technology. For each agreement, specifically examine whether it contains (a) a present assignment of IP developed under the engagement, or (b) valid work-for-hire language. Agreements that are silent on IP ownership or that contain ambiguous language should be flagged for remediation before close — confirmatory assignments from the contractor, where obtainable, are the standard fix.
- Departed founder and employee departure documentation. Review departure agreements for any departed technical co-founders or engineers who contributed to core technology. Where departure agreements are silent on IP, assess whether the original IACA covers the relevant work and whether any gap requires a confirmatory assignment.
- Open source license review in the code base. Copyleft licenses (GPL, LGPL, AGPL) in the target's code base create IP distribution obligations that can affect the acquirer's ability to commercialize the technology. The question isn't just what open source libraries were used; it's whether those libraries are integrated in ways that trigger license obligations, and whether the target has complied with those obligations.
- Third-party development agreements and joint development arrangements. If the startup engaged in any joint development with a customer, university, or industry partner, those agreements should be examined for IP ownership allocation clauses. Joint development arrangements frequently split ownership of resulting IP in ways that limit the acquirer's freedom to operate.
The Remediation Options and Their Limits
When IP ownership gaps are identified during diligence, the question becomes whether they can be remediated before close and at what cost. The options depend on who holds the potentially conflicting rights and whether they're reachable.
For current employees and contractors who are still engaged with the company, obtaining confirmatory assignments is usually feasible — the company has an ongoing relationship and can request that the individual execute a confirmatory IP assignment agreement. The timing and compensation implications vary; some individuals will sign without consideration, others will see it as an opportunity to negotiate.
For departed co-founders and former contractors, the picture is more complicated. A departed founder who left on bad terms may be difficult to reach or may see the acquisition as an occasion to assert leverage. A contractor who did work three years ago may be unreachable. When the gap involves a material portion of core IP and remediation isn't achievable before close, the standard approach is to adjust deal terms — price reduction, escrow, rep and warranty coverage, or a combination — to account for the title risk.
What's not an acceptable answer is to note the gap in the diligence memo and proceed to close without either remediation or deal-term adjustment. The acquirer's business team may accept that approach; the acquirer's counsel should not recommend it without clear client acknowledgment of the risk and explicit instruction to proceed.
Why This Is Hard to Catch Without Systematic Review
The IP chain-of-title gaps described here are not buried in obscure contract language. They're gaps — absences of language that should be there. That's harder to catch in a manual review process than a non-standard clause, because reviewers are trained to flag what's present, not to flag the absence of required provisions. An IACA that simply doesn't address pre-formation work product looks complete on its face. Only comparison against a checklist of what the document should contain reveals the gap.
When we built Undwrlyft's approach to IP assignment review in startup acquisitions, the absences problem was central to how we defined the extraction targets. The relevant question isn't just "what does this IACA say about IP assignment?" It's "does this IACA contain the specific coverage elements that a defensible chain-of-title requires?" Flagging the gap is at least as important as flagging the non-standard clause.
Day two of startup diligence is when the IP chain-of-title questions surface — if the review process is designed to surface them. When it isn't, they show up at closing, or post-close, or when the acquirer tries to enforce the technology in a context where a third party has standing to contest ownership. That's a materially worse time to find a gap.