AI-Specific Legal Due Diligence: What Standard Tech DD Misses
AI-Specific Legal Due Diligence: What Standard Tech DD Misses
The standard tech DD checklist was built for SaaS companies. AI companies have a different IP structure, a different regulatory exposure, and contract risks that simply do not appear in software DD. Here is what experienced AI investors and M&A counsel add to the standard list.
Why Standard Tech DD Falls Short for AI Companies
Standard tech DD was designed to surface the risks that matter for software businesses: code ownership, customer contracts, regulatory exposure, employment terms. For AI companies, those categories still apply — but they require a fundamentally different interrogation. Our AI Due Diligence practice covers the full range. Start with the overview at AI Due Diligence.
The reason standard checklists fail is structural. Traditional SaaS companies own their IP clearly: the code was written by employees under work-for-hire agreements, customer data is held under a well-understood licence, and the product is not legally a “model.” AI companies are different in at least three ways.
First, the core IP asset — a trained model — is a composite work that inherits properties from its training data, its base model, its fine-tuning process, and its inference configuration. Each of those layers may have a different owner, licensor, or restriction. Standard IP reviews look for ownership; AI DD must additionally trace the full provenance chain.
Second, AI companies are dependent on third-party providers in a way that creates contractual risk at exit. API agreements with major model providers typically contain change-of-control provisions that have never been tested at acquisition. An acquisition may trigger automatic termination of agreements that underpin the entire product. Standard contract review does not surface this risk.
Third, the EU AI Act creates a new category of pre-close regulatory exposure. If an AI company operates a system that will be classified as high-risk under the Act, the acquirer inherits that compliance obligation at closing. Standard regulatory reviews check for GDPR and sector licences. They do not check for AI Act classification, conformity assessment requirements, or Article 4 literacy obligations.
Five Things Standard Tech DD Misses
These are the categories where standard DD provides inadequate coverage for AI targets. Each one has produced deal-level consequences in AI M&A transactions.
Standard DD vs AI DD: Category-by-Category Mapping
Select a DD category to see what standard tech DD covers — and what AI-specific items it misses. Use this as a gap analysis starting point for your next AI transaction.
AI Legal Due Diligence: 8-Point Checklist
Use this checklist to track completion of AI-specific DD items. These are items that sit on top of — not instead of — a standard tech DD review.
AI-specific legal DD should begin as early as the initial data room review — ideally at the same time as standard IP and contract review, not as a separate phase after it. The reason is sequencing: the most consequential AI DD findings — training data provenance gaps, change-of-control triggers in API agreements — affect deal structure, escrow requirements and representations and warranties. These need to be identified before deal terms are finalised, not after signing.
In practice, commissioning AI DD as a standalone workstream after standard DD is complete means re-reviewing documents already reviewed, which wastes time and budget. Build AI-specific questions into the standard DD questionnaire from the outset.
A provenance gap — where there is insufficient evidence that training data was lawfully obtained and the company has commercial rights to use it — is typically addressed in one of three ways. First, representations and warranties from the seller about data ownership and licence chain, backed by W&I insurance if available. Second, an escrow arrangement sized to the estimated cost of re-training or re-curating the affected data. Third, a price reduction reflecting the contingent liability.
The worst outcome is discovering the gap post-close, when the acquirer bears the full cost of third-party copyright claims with no recourse. For detailed analysis of training data provenance requirements see our article on Training Data Provenance in M&A.
This depends on the specific clause wording. Some change-of-control provisions give the provider a right to terminate on notice — typically 30 to 90 days. Others require the acquirer to re-apply for access or re-negotiate pricing. In the most restrictive cases, the agreement terminates automatically on close, with no continued access to the API.
The practical risk for acquirers is that if the acquired company’s product runs on a single provider’s API and that agreement terminates, the product may be non-functional within days of close. Mitigation strategies include: pre-close consent from the provider, parallel deployment on an alternative provider before close, or contractual conditions that make closing contingent on provider consent. All of this requires identifying the clause before signing, not after. See our analysis of Change-of-Control Clauses in AI Contracts.
Yes. When you acquire a company that operates an AI system, you acquire its regulatory status — including any existing non-compliance with the EU AI Act. If the target operates a system that will be classified as high-risk under Annex III but has not completed the required conformity assessment, that obligation transfers to the acquirer at close.
Acquirers should obtain a legal opinion on EU AI Act classification as part of DD for any AI company with EU market exposure. If non-compliance is identified, the risk should be priced in, or the acquisition should be structured to give the acquirer time post-close to complete the conformity assessment before commercial deployment. For classification analysis, see our article on EU AI Act High-Risk SaaS Classification.
The scope of AI DD varies depending on the transaction type, but the core categories remain the same. For a majority acquisition or merger, the acquirer becomes the legal successor to all IP, contracts and regulatory obligations — making full AI DD essential. For a Series A or B minority investment, the investor’s primary concern is protecting the value of the investment, which means verifying that the IP chain is clean, key agreements are not terminable at exit, and the regulatory picture will not prevent a future acquisition or IPO.
In practice, the training data provenance, model weights assignment and EU AI Act classification questions apply with equal force at both stages. What changes is the remediation leverage: a pre-investment investor can make clean IP a condition of funding; a post-acquisition acquirer has fewer options if gaps are discovered late. Early-stage founders should treat these questions as a pre-emptive structuring exercise before their first institutional round.
AI DD That Covers What Standard Lists Miss
WCR Legal provides specialist AI legal due diligence for investors, M&A counsel and corporate acquirers. We cover training data provenance, upstream model licences, API change-of-control risk, EU AI Act classification and founder IP chain — on deal timelines.



Post Comment