Home
Back to Blog
GUIDEIntermediate

Private Equity Due Diligence with AI: What to Automate and What to Leave Alone

Where AI earns its place in PE due diligence (extraction, tracking, benchmarking, meeting prep) and where it doesn't (judging management, legal conclusions, QoE sign-off, anything it hasn't seen), with a findings format that makes every claim checkable.

October 27, 202613 min readClaude Code Playbooks
ai due diligencepe due diligence automationai deal diligence checklistdata room ai reviewprivate equity aidue diligence claudepe diligence workflow

This post contains affiliate links. If you sign up through one, we may earn a commission at no extra cost to you. How we handle this.

Due diligence is where AI looks most useful and where its failure costs the most. A data room has thousands of pages, a tight clock and a team that is tired by the third week, which is a very good description of the work an AI model is fast at. It is also the one stage of a deal where a missed clause or a wrong number is not caught by anything downstream. The closing documents are signed, and the money has moved.

So the useful question isn't whether to use AI in diligence. It is where it shortens the work without adding risk, and where the answer is to leave it alone. This guide draws that line, and then shows the setup that makes the automated half checkable.

The Line

AutomateLeave alone
Extracting terms, dates and figures from documentsConcluding what a clause legally means
Tracking requests, responses and open itemsJudging the management team
Building the first draft of the QoE bridgeSigning off adjustments
Benchmarking against public peersSetting the price or the recommendation
Preparing question lists and meeting briefsRunning the meeting or the reference calls
Cross-checking documents against each otherDeciding something is fine because nothing was found

The pattern: automate work where output can be checked against a source in seconds, and leave alone work where being wrong is both costly and hard to detect. The rest of the guide gives the reason for each item on the right.

New Claude workflows for finance professionals, every week

One email a week with the newest playbooks. Free, like everything here.

No spam. Unsubscribe anytime.

What to Leave Alone, and Why

1. Legal conclusions

Claude is good at finding the change-of-control provision on page 40 of a customer contract and quoting it. It shouldn't be the one saying whether that provision is enforceable, whether a waiver is needed, or how it interacts with governing law. Use it to surface and rank clauses for counsel, who decide what they mean. Every legal finding should end with a name, not a model.

2. Judging people

A good deal team forms its view of management from how they answer, what they volunteer, who defers to whom and what they do when pushed. A model can prepare sharper questions. It can't sit in the room. Reference calls are the same: the value is the tone and the hesitation, which don't survive a transcript.

3. QoE sign-off

A draft bridge from reported to adjusted EBITDA is excellent AI work: pull each proposed addback, link it to the supporting document, and flag the ones without support. Deciding that an addback is truly non-recurring is a judgment the accounting advisers own, and it often decides the price. Draft with AI, sign with people.

4. Conclusions from absence

This one is the most dangerous. If Claude reviews 400 documents and reports no issues, that means it found no issues in the documents it read, in the form it could read them. A scanned PDF with bad OCR, a file that was truncated, an attachment that never made it into the data room: each is a silent gap. "No findings" must always come with a coverage statement, as described below.

5. Price and recommendation

The IC recommendation and the bid are the deal team's to own. AI can assemble the memo, run the sensitivities and argue the bear case. The call is not delegable, and the people who sign it need to understand every number in it.

6. Where the data goes

Data room contents are covered by NDAs and the seller's rules. Many processes restrict which tools may touch the material, and some prohibit external AI services altogether. Check the data room terms, the NDA and your own firm's policy before any document reaches a model. If the answer is no, the playbooks below still help with structure and preparation using non-confidential inputs.

What to Automate

The checklist and request tracker

Start with the Due Diligence Checklist Generator, which produces workstream checklists tailored to the sector, with priorities, status tracking and a red-flag escalation framework. Keep it as a living file that Claude updates as documents arrive and requests are answered, so the open-items list is always current.

Document extraction, with a findings format

The Due Diligence Automator processes data room documents and produces structured findings. Whatever tool you use, require every finding to have the same shape, so it can be checked:

{
  "finding": "Customer may terminate on change of control",
  "document": "MSA-Acme-2023.pdf",
  "location": "Section 14.2, p. 31",
  "quote": "exact text copied from the document",
  "severity": "high | medium | low",
  "confidence": "extracted | inferred",
  "needs": "counsel review"
}

The quote and location fields turn each finding into something a reviewer can verify in a few seconds. You can also check the quotes with code, since a quote that doesn't appear in the extracted text of its document is an invention. We show the exact-match check in the earnings season guide; the same idea applies here. The confidence field separates what the document says from what Claude infers, and the needs field routes legal and accounting questions to the right adviser.

A coverage log, so silence means something

After processing the data room, write coverage.md. List every file with its page count, the number of pages you extracted text from, and any file that is scanned, password-protected, truncated or failed to parse. List the checklist items for which no document was found. Don't say a workstream is clean; say what was reviewed and what was not.

This is the control that makes "no findings" mean something. A reviewer who sees that 38 of 400 files could not be read knows exactly where a person has to look.

Meeting prep

The Diligence Meeting Prep playbook turns the findings and the checklist into a prioritized question list organized by topic, relevant benchmarks, red flags to probe and a one-page brief. This is AI at its best in diligence: the preparation is thorough, and the conversation stays human.

Benchmarking Against the Public Market

A private target's data room tells you about the target. It doesn't tell you whether management's claims fit the market, and that is where public data helps. If the CIM says the market grows 15% a year and the company will take share, public peers have said something about their own growth, margins and demand on their earnings calls.

  • Fiscal.ai gives Claude standardized peer financials and earnings call transcripts over MCP. Ask for what each public peer said about demand, pricing and competition in the last two calls, with verbatim quotes. See the MCP setup.
  • Koyfin is useful for screening the peer set and checking where they trade. Its fundamentals can't be exported, so use it to choose peers and look at charts, and take the numbers from a source Claude can read. Our comps guide covers the split.

To be clear about scope: neither tool helps with the target's own documents. They help you test the story around the target. For take-privates, where the target itself is public, the same tools cover much more of the work.

After Diligence: The Handoff

Clean diligence output carries straight into the next stages. The IC Memo takes the findings and risks, the Returns Analysis turns the diligence-adjusted numbers into IRR and MOIC sensitivities, and after close the Value Creation Plan builds the EBITDA bridge and the 100-day plan from the same findings. The Portfolio AI Readiness Assessment then scans the holdings for where automation could move EBITDA, which is the same kind of question diligence should have started asking. For the wider toolkit, see AI for private equity and investment banking.

A Working Rule

Before you give AI a diligence task, ask two questions. Can I check the output against a source in under a minute? If I'm wrong, will I find out before the money moves? If both answers are yes, automate it. If either is no, keep a person on it, and use AI only to prepare.

This article is for education and isn't legal, accounting or investment advice. Data room terms, NDAs and your firm's policies govern what material may be used with any AI service. Confirm them before you upload anything. Vendor features are as of October 2026.