The 'Handshake Discount': Why Chain of Title Failures Cost Millions
In the high-velocity world of early-stage growth, intellectual property (IP) documentation often falls victim to the "move fast and break things" ethos. Founders assume that because they paid for the code, they own the code. In the context of a Private Equity exit or strategic acquisition, this assumption is a multi-million dollar liability.
The most common, yet most expensive, failure point in technology due diligence is the Chain of Title. Acquirers are not just buying your revenue stream; they are buying the exclusive right to exploit your underlying assets. If you cannot prove—with an unbroken paper trail—that every line of code, every algorithm, and every design element was legally assigned to the company, you are handing the buyer a loaded gun to renegotiate the purchase price.
The 100% Assignment Rule
We routinely see Series B and C companies arrive at the data room stage with "handshake" agreements with early contractors or co-founders who left three years ago. This is the "Handshake Discount." If a key contributor did not sign a Proprietary Information and Inventions Assignment Agreement (PIIAA) at the time of creation, they technically retain rights to that IP. In 2025, PE firms are weaponizing these gaps to demand 20-30% holdbacks or valuation reductions until Confirmatory Assignments are secured—a process that gives disgruntled former employees immense leverage.
The Fix: Conduct a comprehensive employee agreement audit 12 months before you intend to exit. Every employee, contractor, and intern must have a signed PIIAA on file. For historical gaps, secure Confirmatory Assignments immediately, well before an LOI is signed.
The 'Viral License' Trap: Open Source Compliance in 2026
The era of "don't ask, don't tell" regarding Open Source Software (OSS) is over. With the rise of automated code scanning tools like Black Duck and Synopsys, acquirers can now map your entire codebase in 48 hours. The results are often devastating for unprepared sellers.
The Black Duck Reality Check
Recent data indicates that 100% of audited codebases contain open source components, and alarming 85% contain license conflicts. The primary valuation killer is the "Copyleft" or viral license (e.g., GPL v2/v3). If your proprietary software statically links to a GPL library, legally, your entire codebase may be subject to the GPL's requirement to be open-sourced. This effectively renders your proprietary IP worthless in the eyes of an acquirer looking to maintain a closed-source commercial model.
We recently observed a deal where a target company's core AI engine was built upon a GPL-licensed library. The remediation required a complete re-architecture of the product, delaying the close by four months and resulting in a $4M reduction in the final purchase price to cover the "technical debt" of the rewrite.
Mandatory Documentation: The SBOM
To survive this scrutiny, you must generate a Software Bill of Materials (SBOM) proactively. This is no longer optional; it is a standard deliverable in the technical data room. Your SBOM must list every third-party component, its version, and its specific license. Do not wait for the buyer's audit to find violations; find them yourself and remediate them (replace the library or purchase a commercial license) before you go to market.
Trade Secrets vs. 'Tribal Knowledge': Documenting the 'How'
Patents protect the "what," but trade secrets protect the "how." However, for a trade secret to be an asset that a PE firm can value, it must be documented. If your "secret sauce" exists only in the head of your CTO, it is not an asset—it is a Key Person Risk.
Buyers are increasingly distinguishing between "documented IP" and "tribal knowledge." High-performing engineering organizations document their architecture, API schemas, and data flows. This documentation serves as proof that the IP is transferable and scalable without the founder's direct involvement.
The Documentation Gap Valuation
When we assess companies for exit readiness, we look for the "Diagram Gap." If a buyer asks how your data ingestion engine works, and you have to draw it on a whiteboard because no documentation exists, you have just signaled that your technology is fragile. Acquirers pay a premium for Transferability. Thorough technical documentation proves that the asset can survive the departure of its creators.
Actionable Benchmark: Your data room should contain a "Technical IP" folder including:
- Current System Architecture Diagrams (C4 model preferred).
- API Documentation (Swagger/OpenAPI specs).
- List of all Trade Secrets (algorithms, customer lists, pricing models) and the security measures taken to protect them.
- Third-party dependency map (the SBOM).
By transforming "tribal knowledge" into structured assets, you move the negotiation from "earnout based on retention" to "cash at close."
