What Cross-Border M&A Teaches About the Limits of Legal AI
Legal AI can read a contract. That much is settled. In due diligence, where hundreds or thousands of agreements once required two weeks of associate time, a well-built model now finishes the work in an afternoon.
The temptation is to treat that as victory. It is not. Compressing the middle of a process does not eliminate the work at either end. It moves that work forward and backward, and those are precisely where AI for Legal is least useful.
The Three Phases of Diligence
Due diligence moves through three phases: scoping, issue identification, and remediation. Historically, issue identification consumed the calendar and the associates who read every contract.
Legal AI has compressed that middle phase. The consequence mirrors what happened when coding assistants sped up software engineering. When the middle is no longer the bottleneck, judgment shifts to the front and back.
Engineers now spend their judgment on architecture and deployment. Diligence lawyers should spend theirs on scoping-deciding what to examine-and on remediation, deciding what findings mean. Both turn on judgment rather than volume. A model does not provide judgment.
The Sorting Problem
A fast engine executes a poor instruction faithfully. Point legal AI at a loosely scoped review and it returns 500 findings. Perhaps 50 bear on the transaction. The fee a team thought it saved comes back as the labor of sorting the pile.
A deal-defining issue can sit in that pile receiving the same brief attention as boilerplate. This is the part of the story that tends to go unmentioned.
The model surfaces everything. A person still has to decide what everything means. A tool that makes identification cheap raises the value of the scoping before it and the remediation after. It does not lower either.
Where Judgment Matters in Practice
The point is clearest in the diligence of a modern software company. Code is written wherever engineers live. Intellectual property is created across jurisdictions. A target with modest revenue can carry employees, data, and tax exposure in a dozen countries without a single foreign office.
The central scoping question becomes geographic. Which jurisdictions deserve real scrutiny, and which do not.
That question rests on a distinction a model will not draw reliably on its own: the difference between a few foreign employees and a genuine foreign operating footprint. A handful of remote engineers in three countries presents real but bounded risk, usually handled with focused local employment advice. Running a full review in each country spends money to disprove a risk that was never material.
A company that genuinely operates abroad is different. Two questions reward careful attention. The first is whether the company owns its intellectual property at all. Many jurisdictions, unlike the United States, do not vest an employee's work product in the employer by default. If the chain of title fails under local law, the buyer may not own the asset it is paying for.
The second is tax. The assumption that a structuring review has answered the tax question can obscure whether a dispersed workforce has created a taxable presence in a country where nothing was ever filed.
A model can flag an assignment clause. It will not tell you that the clause is unenforceable under Portuguese law, or that the missing clause for a contractor in Bangalore is the one that matters. Recognizing that is scoping and remediation. It remains human work.
Discipline at the Ends
An accelerated middle pays off only when the ends are handled with discipline. In diligence that means scoping tightly enough that the machine looks in the right places, and remediating carefully enough to separate exposures that threaten a deal from the ones that only look alarming on a printout.
It also means scoping for the parties who rely on the work after signing. The representations and warranties insurer decides what it needs to see before it will cover a risk. It penalizes too little diligence and too much in equal measure. Lenders have their own requirements for guarantees, share pledges, and audited financial statements. Those requirements surface at financing rather than at signing unless counsel has anticipated them.
Legal AI can read every document in a data room faster than any team a firm could assemble. It cannot tell a buyer which jurisdiction holds a real operation and which holds a single laptop. It cannot tell the buyer what the deal's eventual insurers and lenders will require.
That judgment is the work the technology has made more valuable rather than less.
The firms that see this will use AI to clear the middle and put the time it frees back into judgment at the ends. The firms that treat a faster review as a finished one will reach the wrong answer sooner than before.
For those working in due diligence, understanding this distinction is critical. AI Learning Path for Paralegals offers practical grounding in how these tools fit into actual workflows.
Your membership also unlocks:
