Acquisition diligence is one of those workflows where the data room is the product. You sign the LOI, the seller drops 600 PDFs into a virtual room — financials, contracts, employment agreements, IP assignments, customer lists, board minutes, an HR audit nobody read at the time — and the meter starts running. Four weeks. You and a small diligence team need to read all of it, find the issues, run the management calls, write the synthesis, and decide whether to close.
The expensive part isn't the reading. It's keeping a coherent picture across hundreds of documents while the seller's counsel is texting you about the next set of redlines. A working notes setup doesn't change the deal's clock; it changes how much of the clock you spend re-reading versus thinking. Adjacent multi-document workflows — contract negotiation with AI notes and AI notes for angel investors: deal screening and portfolio tracking — share the same vault shape with a different audience.
A vault that mirrors the diligence streams
The shape that holds up is one top-level page per acquisition — Acme Corp acquisition — with sub-pages for each diligence stream: financial, legal, commercial, technical, HR, IP, customer concentration, and the open-issues list. Capy supports unlimited page nesting, so a deal that grows a separate page per material contract or per key customer fans out without forcing you to flatten anything.
Plain markdown matters here because the agent can read across every stream in a single query. When the financial reviewer surfaces something that touches a customer contract, you ask Capy to find the relevant clause across the legal pages and tell you whether the financial picture and the contractual picture are consistent. The answer takes the time it takes to read it — not the time it takes to rummage through a data room.
Data-room intake without the spreadsheet of file links
The default workflow is a spreadsheet listing every file in the data room with a column for "reviewer assigned" and another for "comments." It's better than nothing and considerably worse than what's possible.
Drop the data-room PDFs onto the right diligence-stream page. Capy auto-converts each PDF to markdown via docstrange, which means every contract, every financial statement, every audit report becomes searchable text the agent can quote. You can ask "which contracts include change-of-control provisions" and get a list grounded in the actual documents — not a guess that you then go verify by opening sixteen PDFs. The agent acting on the converted text in place is the Cursor-for-documents pattern at deal-room scale.
The intake stops being clerical. The reviewer's time goes into reading the material that matters, not into hunting for which file the material is in.
Management calls with speaker labels you can quote
The management calls during diligence are where the deal actually gets read. The seller's CFO answers a question about a customer concentration issue, the seller's CEO walks back a forward-looking claim from the LOI, somebody on the seller's side mentions a regulatory matter that wasn't in the disclosures. These calls are the highest-information surface in the deal and routinely the worst-recorded.
Record each call in Capy. The transcript comes back with speaker diarization — labels like Speaker 1: … and Speaker 2: … so you can tell who from their side answered the question and who from yours asked it. Park the recording on the relevant diligence-stream page. Then ask Capy to pull out:
- Specific numbers cited (with the speaker who cited them)
- Forward-looking claims (and any softening qualifiers)
- New information disclosed verbally that wasn't in the data room
- Open questions the seller's team committed to follow up on
When the seller later claims they "addressed customer concentration on the call," you can search the transcript and find the exact passage. The shape of the answer changes from "I think they said…" to "here's the line."
A red-flags log the agent helps you keep current
Diligence findings come in fast, get triaged in working sessions, and decay into a five-page synthesis memo at the end. The intermediate state — every flagged issue across every stream, with status — is usually a Google Doc nobody likes editing.
A working setup is a red flags inline database on the deal page, with rows for date, stream, finding, severity, status, and the source document or call. The database lives directly inside the markdown page via the :::database::: directive, so it sits next to the prose context — the deal narrative, the open questions, the timeline. After each new finding, ask Capy to read the source and propose an entry; you confirm and edit.
When a partner asks "what's our current red-flag count and how have they moved this week," the answer is two clicks, not a Saturday of synthesis.
Cross-stream synthesis the room can't do alone
The hardest synthesis question in diligence is the one that crosses streams: "does the customer concentration risk that the financial reviewer flagged actually map onto the change-of-control provisions in the legal review, and what does that mean for our hold period?" That question requires somebody to hold three different streams in their head at the same time.
Ask Capy to read across the relevant pages and produce a one-page cross-stream brief: financial picture for the top five customers, contractual picture for those same customers (assignment rights, change-of-control, exclusivity, term), and the implications for post-close risk. The agent's not making the call; it's assembling the material so the partner who's making the call doesn't have to be the synthesis engine themselves.
This is the kind of work that historically swallows a Saturday at the end of week three of diligence. The vault makes it a Tuesday afternoon.
A live synthesis memo that updates with the deal
The deal memo at the end of diligence is the artifact the IC reads. The honest version of how it gets written is: a partner pulls an all-nighter the day before IC because the memo only existed as a Word doc that hadn't been touched in two weeks.
Inverting this: keep a live synthesis memo page in the vault from day one. Each section maps to a diligence stream. As findings come in, the memo updates. Ask Capy to read across the diligence pages and refresh the memo weekly — what's new, what's resolved, what's still open. By the time IC arrives, the memo isn't a sprint; it's been current for two weeks. You spend the night before IC sharpening the thesis, not assembling the material. (The same live-memo discipline shows up in our writeup of board-of-directors meeting notes.)
The memo cites the source pages in the vault. Any IC reviewer who wants to drill in can follow a link to the underlying contract, call transcript, or financial statement.
Customer reference calls with structured capture
A diligence cycle usually includes 5–15 customer reference calls. Each one is 30–45 minutes of qualitative material that's enormously valuable in aggregate and individually hard to use.
Record each call in Capy. The transcript with speaker labels gets parked on a customer references sub-page. Ask Capy to read across all the call transcripts and produce: the three most-recurring praise points, the three most-recurring complaints, anything that contradicts the seller's stated narrative, and the named customers whose use case looks fragile post-close.
The aggregate picture is grounded in customers' actual sentences, not in the seller's curated reference list narrative. The contrast between what customers said and what the seller's deck claimed is often the most useful single output of diligence.
What this isn't
Capy isn't a virtual data room and isn't legal counsel. The data room still lives where it lives; the contracts still get reviewed by lawyers; the financials still get audited by accountants. The vault holds the thinking part of diligence — the synthesis, the cross-stream connections, the call transcripts, the red-flag log, the live memo — which is the part that's currently spread across emails, working sessions, and four different reviewers' inboxes.
It's also single-user by design. The deal lead owns the vault. Stream reviewers send their findings as documents the lead drops onto the relevant pages; the synthesis lives in one person's hands. That's the right shape for the deal lead who's accountable to IC for the picture.
A small first test
The cheapest way to see whether this fits a real deal is to take one diligence stream — say, the legal contracts review — and rebuild it in a Capy page. Drop the contracts as PDFs, let docstrange convert them, and ask Capy to summarize the change-of-control provisions across the portfolio. If the synthesis surfaces something the original review missed — or surfaces it faster — you've got a sense of what running the next deal in this shape would feel like.
Try Docapybara free. Load one diligence stream's documents and see what the agent does with the data room.