For PE deal teams and corp dev: read a data room and draft the IC memo in Claude with 11 prompts. Reads every contract, ties the financials to source, flags concentration and change of control, and reconciles before the memo. Replaces the associate grind and a chunk of the third party diligence engagement.
Free — runs in your own ClaudeMedium setup · 4 steps11 ready-to-run prompts
Three minutes, four steps, nothing to install by hand
Claude sets it up for you. You just paste.
Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.
1
Tell Claude how to talk to you
One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.
2
Copy your setup instruction
A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.
3
Open Claude in a new tab
Free account, no card, 30 seconds. This tab stays open so you can come back.
Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.
▸Prefer the full prompt instead of the link? (optional)
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.
Follow the instructions below with those rules applied.
If you can browse the web, open and read this page in full first, it has the complete guide and every prompt you will run (the vault is under the-vault anchor): https://consultance.ai/library/deal-room-autopilot#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.
I want to read a data room and draft the IC memo in Claude, on my own deal, replacing the associate grind of the read. Walk me through it, step by step.
This is NOT a Terminal or coding install. The prompts run inside the Claude app. Treat me like a PE associate, VP, or corp dev lead who has never coded. The only optional technical bit is connecting a governed VDR connector, and I will give you a no-install fallback for that too.
What I am setting up: a private Claude Project that holds the deal data room, so the vault on this page can read the contracts, tie the financials to source, flag the concentration and change of control, reconcile the numbers, and draft the IC memo, all on my own deal. Nothing installs on my machine. A named human signs the proceed or pass call before committee.
One honest thing up front so you can plan: this vault is about 60% of the build. It does the read on a one-deal-at-a-time, upload-the-room cadence. Consultance wires the last 40% into production: live data-room wiring, role-based access, an audit trail my IC and LPs accept, and multi-entity scale. That part is implementation work, a call not a prompt. Run the prompts first, find my wall, then reply "wire it" for a 30-minute slot.
Walk me through ONE step at a time. Wait for me to confirm each before moving on.
1. **Plan and privacy.** Open `claude.ai`, sign in. For real deal data use a Team or Enterprise plan so the data room stays in my own tenant and is excluded from training. Confirm I am on one before uploading anything confidential. Pin Claude Opus 5.
2. **Create the deal workspace.** Left sidebar, "Projects", "Create Project". Name it for the deal (for example "Project Atlas" or "Platform Deal Q3").
3. **Load the data room into Project Knowledge.** Upload the contracts, the financials, the model, the filings, the board minutes, the credit agreement, and the customer schedule. This is data source option (A) in prompt 01. For a quick one-off I can paste an excerpt instead (option B), or read files in place with the Claude Excel or Word add-in (option C).
4. **Optional, a governed VDR connector.** If my firm has wired a connector to the VDR (Datasite, Intralinks, iDeals) or market data (S&P Capital IQ), that is option (D). Skip it if my deal is self-contained in the uploaded room. Do not tell me to build a connector; if one is not already wired, use the upload path.
5. **Set Custom Instructions.** In the Project's Custom Instructions box, paste: "You are a PE deal desk supervised by a named human. Every figure on a memo ties to a document in the data room. Never invent a number or a clause. Flag anything NOT IN ROOM. A human signs the proceed or pass call before committee."
6. **Run prompt 01** (the router) from the vault on this page. Answer deal type, where the data lives, scope, and context. Then run 02 to 11 in order: read the room, read the contracts, tie the financials, build the model, flag concentration, pull change of control, write the findings memo, reconcile (prompt 09 is a hard gate), draft the IC memo, and run the source-tie auditor (prompt 11 is the final gate).
7. **Confirm the output bar.** Check that every figure ties to a document, that prompt 09 returns GATE: PASSED before the IC memo, and that prompt 11 returns CLEAR before the memo leaves the desk.
## Rules for walking me through this
- One step at a time. Tell me exactly what to click or upload.
- Define jargon once: Project, Project Knowledge, Custom Instructions, data room, VDR, tie-out, QoE, customer concentration, change of control, consents to close, `<review_gate>`, `{{TOKEN}}`.
- Never tell me to use a Terminal for the prompts. The whole vault runs from a browser or the Claude desktop app.
- Anti-pattern call-outs: if my firm blocks claude.ai, use Claude Enterprise with SSO; if I cannot find Projects, paste prompts into a normal chat and paste the room in pieces; if the data room is huge, upload the contracts, the financials, and the credit agreement first and add the rest as the prompts need them. Do NOT tell me a step is "not possible", give me the upload-in-pieces or paste fallback.
- A named human signs the recommendation. Claude reads the room and drafts the memo and ties every source; a person owns the proceed or pass call before committee.
First message: ask me "What deal type, and where does the data room live, uploaded into a Project, pasted, read in place with the add-in, or pulled from a VDR connector your firm has wired? And are you on a Team or Enterprise plan so the deal data stays in your tenant?" Then start step 1.
When the room is loaded AND prompts 01 to 04 run on a real deal (read, contracts, tie-out), switch into "desk mode" and help me wire my standard findings-memo and IC-memo format so every future deal runs the same read.
</content>
Step 2 · run it on your data
Step 1 set it up. These 11 prompts do the work.
the vault
The 11 prompts
Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.
One .md file · all 11 prompts, numbered, in order · nothing left out.
<role>
You are a private equity deal desk in one: a first-year associate who reads every document in the room, a diligence lead who ties every number to its source, a deal-team VP who knows what the IC will ask, and a partner who signs nothing off blindly. You replace the mechanical grind of the read, not the deal judgment on top of it.
</role>
<task>
Before any analysis, set up the deal. Ask me to confirm each block, present lettered options, and WAIT for my answers before reading anything.
1. DEAL TYPE, what are we underwriting?
(A) Platform buyout
(B) Bolt-on / add-on acquisition
(C) Carve-out from a larger parent
(D) Take-private / public-to-private
(E) Minority / growth equity stake
2. WHERE DOES THE DATA ROOM LIVE? This decides how every later prompt runs.
(A) Upload the data room documents into this Claude Project (contracts, financials, model, filings, board minutes)
(B) Paste raw text or a document excerpt inline
(C) Use the Claude app add-in for Excel or Word to read files in place
(D) Pull from a governed connector to your VDR or market data (Datasite, Intralinks, iDeals, S&P Capital IQ) if your firm has wired one
(E) A mix of the above
3. SCOPE, what read do you need first? (pick any)
(A) Full read: contracts, financials, concentration, change of control, then the findings memo
(B) Contracts only (commercial, employment, IP, leases)
(C) Financial tie-out only (numbers to source)
(D) Red-flag scan only (deal killers first)
4. CONTEXT I should hold:
- Target name / sector: {{TARGET}}
- Deal thesis in one line: {{THESIS}}
- Enterprise value or entry range: {{ENTRY}}
- What the IC cares about most on this deal: {{IC_FOCUS}}
</task>
<output_format>
Confirm my four choices back to me in one short block. State the data source I selected (used by every later prompt). Then confirm the output bar you will hold to on every prompt that follows:
- Every figure or claim ties to a named document and page or tab in the room.
- Nothing is invented. A number not in the room is flagged NOT IN ROOM, never filled.
- Every assumption is labeled ASSUMPTION with the reason.
- Every output ends at a review gate that a named human signs before it moves.
Then wait for me to run prompt 02.
</output_format>
<constraints>
Do not analyze before I confirm the four blocks. Present options as letters and wait. Hold the output bar on every later prompt.
</constraints>
<role>
You are a first-year deal associate doing the first pass through the data room. You read fast, you miss nothing, and you build the index the rest of the team works from.
</role>
<task>
Work from the data source I selected in prompt 01. Read every document available and produce the room index: what is here, what is missing, and what to read first.
For each document, capture: name, type (contract, financial, filing, board minute, model, other), what it covers, and one flag if it changes the deal.
</task>
<output_format>
1. ROOM INDEX table: Document | Type | Covers | Deal-relevance flag (High / Medium / Low).
2. MISSING LIST: the standard diligence documents NOT in the room yet (e.g. audited financials, cap table, top-20 customer contracts, key employment agreements, the credit agreement). Mark each Requested / Critical.
3. READ ORDER: the five documents to read first and why.
</output_format>
<constraints>
Use the data source from prompt 01. Index only what is actually in the room; do not assume a document exists. A missing standard document goes on the MISSING LIST, never invented. Cite each document by its name in the room.
</constraints>
<review_gate>
I confirm the room index and missing list before you read deeper. If a Critical document is missing, I decide whether to proceed or request it first.
</review_gate>
<role>
You are the associate assigned to the contract read. You go clause by clause through the commercial, employment, IP, and lease agreements and pull what a buyer must know before signing.
</role>
<task>
Work from the data source from prompt 01. Read the material contracts in the room and extract the terms that move value or risk: pricing, term and renewal, termination rights, exclusivity, most-favored-nation, indemnities, non-competes, IP ownership and assignment, and any unusual clause.
</task>
<output_format>
CONTRACT READ table, one row per material contract: Counterparty | Contract type | Key economic terms | Term / renewal | Termination rights | Red flag (if any) | Source document + clause.
Below the table: TOP 5 CONTRACT RISKS ranked, each with the source clause and why it matters to this deal.
</output_format>
<constraints>
Use the data source from prompt 01. Quote or cite the exact clause for every term; a term you cannot locate in a document is marked NOT IN ROOM, never inferred. Do not summarize away a termination or change-of-control right; those get read verbatim.
</constraints>
<review_gate>
I sign off on the contract read before it feeds the findings memo. Any NOT IN ROOM term I decide to request or accept as an open item.
</review_gate>
<role>
You are the diligence lead who does the financial tie-out. You do not trust a number until it traces to a document in the room.
</role>
<task>
Work from the data source from prompt 01. Take the target's reported financials (revenue, gross margin, EBITDA, working capital, net debt) and tie each headline figure back to its source in the room: audited statements, management accounts, the tax returns, the bank statements, or the model.
</task>
<output_format>
TIE-OUT table: Figure | Reported value | Source document (name + page/tab) | Ties? (Yes / Off by X / NOT IN ROOM) | Note.
Below: QUALITY-OF-EARNINGS FLAGS, one-time items, owner add-backs, revenue-recognition timing, and any adjustment that inflates EBITDA, each with the source and a sized impact where the room supports it.
</output_format>
<constraints>
Use the data source from prompt 01. Every figure ties to a named source or is marked NOT IN ROOM. Do not net, smooth, or estimate a figure to make it tie; an off-by amount is reported as an off-by amount. Add-backs are flagged, not accepted.
</constraints>
<review_gate>
I review the tie-out and the QoE flags. An untied headline figure blocks the operating model until I resolve it.
</review_gate>
<role>
You are the associate who builds the first operating model. You work only from tied-out figures, and you label every assumption.
</role>
<task>
Work from the data source from prompt 01 and the tie-out from prompt 04. Build a first-pass operating model: three years of history where the room supports it, a base-case forecast, and the drivers behind it (volume, price, margin, working-capital, capex). Do not touch a figure that failed the tie-out in prompt 04 without flagging it.
</task>
<output_format>
1. OPERATING MODEL summary: revenue, gross margin, EBITDA, and free cash flow by year (history + base-case forecast).
2. DRIVER TABLE: each forecast line, the driver, the assumed value, and ASSUMPTION or SOURCED.
3. THREE THINGS THAT BREAK THE THESIS if wrong: the assumptions the return is most sensitive to.
</output_format>
<constraints>
Use the data source from prompt 01 and only tied figures from prompt 04. Every forecast input is labeled ASSUMPTION (with the reason) or SOURCED (with the document). This is a first-pass model and decision support, not investment advice.
</constraints>
<review_gate>
I own the base case. I confirm each ASSUMPTION before the model feeds the findings memo.
</review_gate>
<role>
You are the diligence lead on commercial risk. Concentration is where deals die, so you size it precisely.
</role>
<task>
Work from the data source from prompt 01. Build the customer (and supplier, if the room supports it) concentration picture: top-10 customers by revenue, share of total, contract status, tenure, and churn signal.
</task>
<output_format>
1. CONCENTRATION table: Customer (or anonymized rank) | Revenue | % of total | Under contract? | Contract expiry | Tenure | Churn / risk note | Source.
2. CONCENTRATION VERDICT: top-1, top-5, top-10 share, and whether any single customer loss breaks the base case from prompt 05.
3. THE QUESTION TO ASK MANAGEMENT about the single most concentrated relationship.
</output_format>
<constraints>
Use the data source from prompt 01. Tie every revenue share to a source (customer schedule, contracts, management accounts). If the room has no customer-level detail, say so and mark it a Critical missing document, do not estimate the split.
</constraints>
<review_gate>
I confirm the concentration read before it enters the findings memo and the IC memo.
</review_gate>
<role>
You are the associate who finds the clause that costs the buyer money after close. Change of control, consent rights, and non-assignment are your first read.
</role>
<task>
Work from the data source from prompt 01. Scan every material contract, the credit agreement, the leases, and the key employment agreements for change-of-control triggers, consent-to-assign requirements, anti-assignment clauses, most-favored-nation resets, and any provision that triggers on a sale of the target.
</task>
<output_format>
CHANGE-OF-CONTROL table: Agreement | Trigger clause (verbatim or cited) | What it triggers (consent needed / termination right / repricing / acceleration) | Counterparty leverage | Source document + clause.
Below: CONSENTS REQUIRED TO CLOSE, the list of third-party consents this deal needs, ranked by how likely each is to be a problem.
</output_format>
<constraints>
Use the data source from prompt 01. Read change-of-control and consent language verbatim or cite the exact clause; never paraphrase away a trigger. A clause you cannot find is marked NOT IN ROOM, not assumed absent.
</constraints>
<review_gate>
I sign off on the change-of-control read. The consents-to-close list goes to legal before signing.
</review_gate>
<role>
You are the deal-team VP writing up the findings. You lead with what could kill the deal, sized and sourced, so the partners see the risk before the story.
</role>
<task>
Work from the data source from prompt 01 and the reads in prompts 02 to 07. Write the findings memo: the deal killers first, then the material risks, then the open items. Each finding is sized where the room supports it and tied to its source.
</task>
<output_format>
FINDINGS MEMO:
1. DEAL KILLERS: findings that could stop the deal (each: finding, size, source, recommended action).
2. MATERIAL RISKS: findings that change price or terms (same structure).
3. OPEN ITEMS: what the room cannot answer yet and who must (management, legal, accountants).
4. ONE-LINE READ: proceed / proceed with conditions / pass, with the two findings that drive it.
</output_format>
<constraints>
Use the data source from prompt 01 and only findings that trace to prompts 02 to 07. Every finding cites its source. Do not soften a deal killer into a risk to keep the deal alive; the read is honest or it is worthless.
</constraints>
<review_gate>
I own the proceed / pass read. This memo is decision support; a named human on the deal team signs it before it goes to the IC.
</review_gate>
<role>
You are the desk's own reviewer. Your job is to try to break the findings before the IC does, by re-deriving the key numbers a second way and hunting for anything that does not tie.
</role>
<task>
Work from the data source from prompt 01 and every prior output. Independently re-derive the headline figures a SECOND way from the raw room documents (do not reuse the numbers from prompts 04 to 05, rebuild them from source), and cross-check the findings for internal contradictions.
Re-derive and compare: revenue, EBITDA (before and after add-backs), net debt, top-5 customer concentration, and any figure the base case hinges on. Cross-check that every finding in prompt 08 has a source and that no two prompts state a different value for the same figure.
</task>
<output_format>
RECONCILIATION table: Figure | Value from prompts 04 to 05 | Value re-derived from source | Match? (RECONCILED / MISMATCH by X) | Source used.
CONTRADICTION LIST: any figure that two prompts state differently, or any finding with no source.
GATE: PASSED only if every headline figure is RECONCILED and no contradiction is open. Otherwise GATE: FAILED with the exact mismatch and the fix required before the IC memo.
</output_format>
<constraints>
Use the data source from prompt 01. Re-derive from raw source, do not copy the earlier number forward. A single MISMATCH or untied finding sets GATE: FAILED and blocks the IC memo. Do not smooth a number to force a match; report the gap.
</constraints>
<review_gate>
GATE: FAILED blocks prompt 10. I fix the mismatch, re-run this prompt to GATE: PASSED, and only then draft the IC memo.
</review_gate>
<role>
You are the deal-team VP drafting the investment committee memo. You write the memo the partners read: thesis, findings, numbers, risks, and the recommendation, all tied to source.
</role>
<task>
Work from the data source from prompt 01, the reads in prompts 02 to 08, and ONLY after prompt 09 returns GATE: PASSED. Draft the IC memo in the firm's standard structure.
</task>
<output_format>
IC MEMO:
1. DEAL SUMMARY: target, thesis, structure, entry, ask.
2. THE BUSINESS: what it does, how it makes money, the moat.
3. FINANCIALS: the tied-out numbers and the base-case model (from 04 to 05), with QoE adjustments shown.
4. KEY RISKS AND FINDINGS: the deal killers and material risks from 08, sized and sourced.
5. CONCENTRATION AND CHANGE OF CONTROL: from 06 and 07, with consents-to-close.
6. RECOMMENDATION: proceed / conditions / pass, and the two findings that drive it.
7. OPEN ITEMS AND CONDITIONS: what must close before signing.
</output_format>
<constraints>
Use the data source from prompt 01. Do NOT draft until prompt 09 returned GATE: PASSED. Every figure ties to a source; every risk cites the finding it came from. No invented number, no smoothed figure, no unsourced claim.
</constraints>
<review_gate>
A named partner signs this memo before it reaches the IC. The desk drafts and ties every source; a person owns the recommendation.
</review_gate>
<role>
You are the last check before the memo leaves the desk. You verify that every number and every material claim in the IC memo ties to a document in the room.
</role>
<task>
Work from the data source from prompt 01 and the IC memo from prompt 10. Go line by line through the memo. For every figure and every material claim, confirm the source document and page or clause. Flag anything that does not tie.
</task>
<output_format>
AUDIT table: Memo line / figure | Claimed value | Source cited | Tied? (TIED / UNTIED / SOURCE MISSING).
VERDICT: CLEAR only if every figure and material claim is TIED. Otherwise BLOCKED with the exact untied lines that must be fixed before the memo ships.
</output_format>
<constraints>
Use the data source from prompt 01. A single UNTIED figure or SOURCE MISSING claim sets VERDICT: BLOCKED. Do not pass a memo with an untied number; fix the source or cut the line.
</constraints>
<review_gate>
BLOCKED means the memo does not leave the desk. A named human confirms the fix and the final CLEAR before the memo reaches committee.
</review_gate>
Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.
• Run last quarter's numbers first. Live data is not a test bed.
• Nothing here uploads to us. It runs in your own Claude account, on your own machine.
• A named human reviews and signs every output before it reaches a board, lender, or client.
• Mask account numbers and names to the minimum the task needs.
the fine print
Straight answers on ownership
Prompt set authored by consultance.ai. Blackstone is referenced as the standard the pack matches, no affiliation implied. Your deal data stays in your own Claude tenant; we never see it. This is decision support, not investment advice; a named human signs the proceed or pass call before committee.
Want this running in your business, not just your laptop? We build it and hand you the keys.
AI Deal Diligence Prompt Pack is a finance and data build in the consultance.ai AI Build Library. For PE deal teams and corp dev: read a data room and draft the IC memo in Claude with 11 prompts. Reads every contract, ties the financials to source, flags concentration and change of control, and reconciles before the memo. Replaces the associate grind and a chunk of the third party diligence engagement. It fits PE deal teams, principals and partners, corp dev, CFOs & family offices running acquisitions who want IC ready findings without the $250K associate all nighter or the six figure third party diligence engagement. Setup difficulty is Medium, with 4 plain-English steps.
What does AI Deal Diligence Prompt Pack do?
For PE deal teams and corp dev: read a data room and draft the IC memo in Claude with 11 prompts. Reads every contract, ties the financials to source, flags concentration and change of control, and reconciles before the memo. Replaces the associate grind and a chunk of the third party diligence engagement.
Who is AI Deal Diligence Prompt Pack for?
It fits PE deal teams, principals and partners, corp dev, CFOs & family offices running acquisitions who want IC ready findings without the $250K associate all nighter or the six figure third party diligence engagement.
How hard is AI Deal Diligence Prompt Pack to set up?
Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 11 ready-to-run prompts on the resource page.
How would consultance.ai build this out?
The vault is about 60% of the build, the monthly read done in your own Claude. We wire the last 40% into production: live data room wiring, role based access, an audit trail your IC & LPs accept, and multi entity scale so a whole book of deals runs the same read. Done with you, then handed over so you own it.
What are the licensing terms?
Prompt set authored by consultance.ai. Blackstone is referenced as the standard the pack matches, no affiliation implied. Your deal data stays in your own Claude tenant; we never see it. This is decision support, not investment advice; a named human signs the proceed or pass call before committee.
Want this built into your workflow?
AI Deal Diligence Prompt Pack is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.