Diligence copilot
The diligence copilot answering a question about large open losses with numbered sources
The diligence copilot on an illustrative target, answering “What are the large open losses?” with each figure cited to the claims history or the data room, and saying what the record does not hold.

Halfway through a review, a deal broker has a question the screen does not answer in one look: which open losses are large, what the buyer has to do at closing, what to ask the seller for. The diligence copilot is the side panel on every engagement that answers those questions from the engagement itself, with numbered sources, and never takes an action.

How an answer is made

sequenceDiagram participant U as Deal broker participant C as Copilot participant T as Read-only tools participant M as Claude U->>C: "What are the large open losses?" C->>C: Is this engagement in the asker's scope? C->>M: Plan: which tools? M-->>C: claims, findings C->>T: claims(engagement), findings(engagement) T-->>C: Rows, each with its source C->>M: Answer from these, cite [S1], [S2] M-->>C: Draft answer C->>C: Every figure supported? If not: "not in the record" C-->>U: Answer, sources, suggested questions

The eight tools

The copilot can only see what its tools return, and the tools only return the engagement in front of the asker, inside their scope: overview, program, claims, findings, gaps, Target 360, search over the data room, and the cost after closing.

Ask the copilotLookups it callsWhat the answer covers
“What are the large open losses?”claims, findingsClaims over the large-loss threshold, paid and reserved, what happened, and what the record does not say
“What does the buyer need at closing?”gaps, programTails and run-off, change-of-control clauses, subsidiaries to add, collateral to settle
“Which lines are on the seller's program?”programEach line's structure, carrier and premium, with the schedule page
“What will the program cost after closing?”costToday against the standalone estimate and the one-time tails, with the assumptions
“What should we ask the seller for?”gaps, findings, searchMissing documents and the open questions the agents raised
“Who leads the target?”targetLeadership from InsightPulse, cited with its as-of date

What it will not do

  • Act. It suggests questions and links into the workspace; approving a finding, delivering a report or sharing with the deal stay buttons a person presses.
  • Invent a figure. Answers are read to the precision each figure is written in, and a figure no tool returned is replaced with “not in the record”.
  • Reach outside scope. A deal broker sees their own engagements; a practice leader or compliance sees the practice.
  • Pretend. With no model configured it answers in facts-only mode from the same tools, and says so.

Saying what is missing is part of the answer

In the screen above, on an illustrative industrial target, the copilot reports one large open general liability loss and then says what the record does not hold: whether the reserve is adequate, whether the claim is in suit, and which program responds. Those are the questions to take to the seller, and the copilot offers them as follow-ups.

Questions we get asked

Which model does it use?

Claude on Bedrock in the practice’s own AWS account. Prompts are versioned and every answer is traced, like the agents.

Is the conversation kept?

Each answer is traced for audit with its tools and sources. The copilot keeps no memory beyond the conversation on screen.

Keep reading