Due diligence assesses
what the target is worth.
It doesn't assess what you will inherit.
tointelligence · omer taki

What the data room doesn't show.

A well-conducted AI due diligence maps the target's AI assets, evaluates known dependencies, identifies EU AI Act obligations and estimates real model value. Necessary, but not sufficient.

What it doesn't see: dependencies that reveal themselves through real usage, not inventory. Conflicts between the acquirer's and target's AI architectures : which don't exist before integration. The regulatory implications of combining both AI portfolios. And the real AI tool behaviours of the target's teams, which often differ substantially from official inventories.

The most costly AI dependencies are not in data rooms. They are in undocumented real usage patterns.

What our observations consistently reveal.

· surprise 1 · inherited vendor dependencies

The target uses proprietary AI models with specific usage terms. Some contracts include pricing or condition changes upon change of control. What you evaluated before closing is no longer what you have after.

· surprise 2 · unanticipated EU AI Act obligations

The target uses AI systems you don't use. Some may be classified as high-risk under the EU AI Act in domains where you have no compliance processes. By inheriting these systems, you inherit their obligations on timelines not aligned with your own compliance calendar.

· surprise 3 · non-reversible exposed data

The target's data fed third-party AI models. That data is not recoverable in its processed form. You inherit the terms of an agreement you didn't negotiate.

· surprise 4 · the target's shadow AI

The target's teams use AI tools no one inventoried. These usages create operational dependencies that surface during integration. Removing these tools creates operational disruption. Leaving them extends your exposure surface without explicit decision.

The first 90 days structure the next 5 years.

AI integration decisions made in the first 90 days post-closing have a structuring effect over 5 to 10 years. Systems deeply integrated in this period create dependencies that become progressively irreversible.

Post-acquisition AI governance is not a phase 3 activity. It is a first-90-day priority, at the same level as financial synergies and HR decisions.

day 1-30
Real mapping
Inventory of the target's actual AI systems, field usages, vendor dependencies, externalised data. Not the official inventory: operational reality.
day 30-90
Architecture decision
Which target AI systems are kept, migrated or abandoned. Which dependencies are accepted or renegotiated. This decision belongs to the board, not IT teams.
day 90-180
Unified governance
Single AI governance framework for the combined entity. Common usage policy. Consolidated EU AI Act obligations. Unified board-level reporting.