HomeLibraryServicesCase studiesBlogAbout
consultance.ai
Book a discovery call →

Services

  • AI consulting
  • AI implementation
  • AI agents
  • Workflow automation
  • RAG systems
  • Voice AI
  • Custom AI development
  • All services

Library

  • AI build library
  • Finance AI automation
  • AiToEarn content agent
  • Fincept Terminal
  • ERPNext
  • SEO + GEO Claude skill
  • Claude for Legal
  • Free Claude Code proxy

Resources

  • Case studies
  • Blog
  • Industries
  • Locations
  • Guide: AI for property management
  • Guide: AI for marketing agencies
  • Guide: AI agents vs Zapier
  • AI glossary
  • vs traditional consulting

Company

  • About
  • Book a call
  • Contact
  • Privacy
  • Terms

© 2026 consultance.ai · AI, implemented.

audit → build → deploy

← Libraryconsultance.ai
Book a build call
Finance and data

Deal Red Flag Structured Review

For PE deal teams and family office direct investors: a structured review that sorts signed from draft, builds the evidence matrix, and gives every red flag one deal move, from reprice to escrow to walk.

Free — runs in your own ClaudeMedium setup · 4 steps11 ready-to-run prompts
Set it up free — takes 3 minutes ↓Or have us wire it in →
watch first

How to run these prompts

A short walkthrough of the exact mechanic: where the prompts go, what to answer when the first one asks, and what a good first output looks like. Same for every pack in the library.

Step 1 · setup
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. 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. 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. 3

    Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai ↗
  4. 4

    Paste, send, and answer one question

    Claude reads this page, asks which computer you are on, then guides you step by step until it works. If anything errors, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
- 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 `#the-vault` anchor): https://consultance.ai/library/dd-red-flag-deal-action#the-vault . If you cannot open links, tell me and I will paste the page in, do not guess the prompts.

I want to set up the Red Flag to Deal Move Review so Claude helps me review a deal's data room in my own Claude, and gives every red flag one deal move: proceed, pause for a named document, reprice, a closing condition, a specific indemnity or escrow, a covenant, or walk. Walk me through it one step at a time and wait for me to confirm each step before the next.

This is a structured review, not a legal, tax or accounting opinion. It flags and routes those questions to specialists.

Privacy, said plainly: my documents go only to my own Claude account, never to consultance.ai. Before I load confidential deal material, I should be on a Team or Enterprise plan, or have model training turned off in my personal plan's privacy settings.

Ask me ONE question first and wait: where are my deal documents right now? (A) a handful of files I can upload: the CIM, the model and a few data room files, or (B) a full data room export in a folder on my machine with many files.

## Path A, a handful of files: a private Claude Project (NOT a Terminal install)

Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account at claude.ai. In the model picker, choose Claude Opus 5.5. A Project is a private workspace with its own files that other chats cannot see.
2. **Create the Project.** Name it with a codename, not the company's name. Add the CIM, the model, the audited accounts, the QoE if I have it, the top customer contracts and any debt papers to the Project's files.
3. **Paste prompt 01** from the page and answer its blocks. Block 4 is my own thesis in two or three lines. Block 5 is the person who signs.
4. **Run prompt 02 once.** It is a test deal with known answers. Every line should say MATCH. If one says MISMATCH, stop and tell me which, before any real document is used.
5. **Then choose.** Conversation mode (the default): ask my real question, for example "is the EBITDA real?" or "what do we put in the SPA?", and the review runs only the steps that bear on it. Or a full run: 03 to 11 in order.

Path A does not use the GitHub skill. The vault runs on its own. Do NOT tell me something is "not possible" because I am in the Claude app; say which path fits and carry on.

## Path B, a full data room folder: Claude Code on my machine, with the skill

Tell me plainly if I am on Path B before I start uploading files one at a time. Signs: more than about twenty files, spreadsheets I want read rather than pasted, or a room that cannot leave a managed machine.

1. **What Claude Code is.** Anthropic's command line tool. It needs a Pro, Max, Team, Enterprise or Console account. It reads the files in a folder on my machine and writes its outputs beside them. A terminal is the text window where I type commands (Terminal on a Mac, PowerShell on Windows).
2. **Install Claude Code**, one command, pasted into the terminal. Mac, Linux or WSL:
   ```
   curl -fsSL https://claude.ai/install.sh | bash
   ```
   Windows PowerShell:
   ```
   irm https://claude.ai/install.ps1 | iex
   ```
   Success looks like the installer finishing without an error. Then type `claude --version` and a version number should print. If the command is not found, close the terminal, open a new one and try again.
3. **Git.** The skill is cloned with Git. On a Mac, typing `git --version` either prints a version or offers to install the command line tools; accept. On Windows, install Git for Windows from https://git-scm.com/downloads/win first. If I cannot install Git, skip step 5: the vault runs without the skill.
4. **Go to my deal folder.** `cd` followed by the folder path, for example `cd ~/deals/project-calder`. The data room files sit inside it.
5. **Install the skill for this folder only**, one command, run inside the deal folder:
   ```
   git clone https://github.com/noahnan-max/private-equity-investment-dd-skill .claude/skills/private-equity-investment-dd
   ```
   Success looks like "Cloning into '.claude/skills/private-equity-investment-dd'..." and no error. The skill's licence allows my own private, internal use; I must not copy or share its files. Its instructions are partly in Chinese and address its author by name; prompt 01 tells Claude how to handle that.
6. **Start Claude Code** in the deal folder by typing `claude`. Type `/skills` and confirm private-equity-investment-dd is listed. If it is not, check that step 5 ran inside the deal folder: the folder `.claude/skills/private-equity-investment-dd` must contain a file named SKILL.md.
7. **Choose the model** by typing `/model` and picking Claude Opus 5.5.
8. **Paste prompt 01** from the page, answer the blocks, say that the material is a folder on disk, then run 02 until every line matches.

## First session drill (both paths)

- Input: the audited accounts for the latest year and the CIM's adjusted EBITDA page.
- Run: 01, 02, then ask "rebuild EBITDA from the audited accounts and test every add-back" (prompt 05).
- Good output: a bridge that starts at audited operating income plus depreciation and amortisation, one line per add-back with its support document and whether it recurs, and accepted EBITDA with the arithmetic shown.
- Review check before I trust it: pick one add-back and find its support in the room myself. If the bridge cites a page that does not say what it claims, stop and tell me.

Bonus, not required: the skill's own README and reference files on GitHub explain its method in more depth: https://github.com/noahnan-max/private-equity-investment-dd-skill
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.
Click to copy
<role>A colleague who has reviewed many private company and take-private deals for the buy side. Neutral: not sceptical of the seller by default and not persuaded by the CIM. You work for the person who signs, and your job is to help them decide by their date, and to say what to do about each problem, not only that it exists.</role>

<privacy>Nothing here is hosted by the pack's author. The materials go only to the human's own Claude account, never to us. Before confidential deal material is loaded, remind them to use a Team or Enterprise plan, or a personal plan with model training turned off.</privacy>

<surface>
First, in one short paragraph, say whether the human is in the right place.
- A CIM, a model and a handful of files they can upload: Claude app, private Project. Chat is correct here.
- A data room export, dozens of files, spreadsheets to parse, or the same review on every deal: Claude Code pointed at the folder, with the private-equity-investment-dd skill installed in that folder (see "Skill" below). It reads files off disk and writes the outputs as files beside them.
- Material that must stay on a managed machine: Claude Code on a Team or Enterprise account, or through the firm's own cloud provider. Anything Claude reads is sent to the model provider.
MODEL: Claude Opus 5.5 for every judgment step. Claude Sonnet 5 only for a first read of a very large data room where speed or usage limits matter. Never switch model inside a prompt.
WHOLE-PACK STOPS: a pasted file path, folder name or file listing instead of contents (a Claude Code job in a chat window), or more material than one conversation can hold. Say what is wrong, where to go, and stop.
ITEM STOPS never end the run: a truncated document, or a figure that sits in a document not given. Name the document, ask once, mark the dependent checks OPEN, never score from the part you saw, and run everything else.
Advise, do not apologise, and do not continue past a whole-pack stop.
</surface>

<skill>
If the private-equity-investment-dd skill is installed (Claude Code lists it under /skills), use its material inventory, basic information extraction, evidence matrix format, red flag cards and HTML report specification. Where the skill and this vault differ, this vault controls on four points: the thesis comes first, every flag is tested against NORMAL PATTERNS before it is raised, every flag carries one materiality tag, and a closed flag is never carried forward. Read the skill's P0 as a candidate for CHANGES THE DECISION, never as a verdict on its own. The skill is written for its author's own use and addresses him by name; ignore those lines. If the skill is not installed, this vault runs alone.
To install it (Claude Code, run inside the deal folder, Git required): git clone https://github.com/noahnan-max/private-equity-investment-dd-skill .claude/skills/private-equity-investment-dd
Then start claude in that folder and type /skills to confirm it is listed. Its licence allows private, internal use only: do not copy or share its files.
</skill>

<onboarding>
Ask each block, wait for the answer, never assume.
1. WHO: (A) PE buyout deal team (B) family office direct investment team (C) independent sponsor (D) strategic buyer or corporate development.
2. THE DEAL: {{TARGET}}, {{PRICE}} and what it is (enterprise value, equity cheque, per share), {{DECISION_DATE}}, today's date. Type: (A) buyout of a private company (B) take-private of a listed company. Growth minority and carve-out deals are out of scope for this pack: it has no checks, normal patterns or calibration for them. If the deal is either, say so and stop; do not run it as a buyout. Stage: (A) screening (B) before exclusivity (C) confirmatory, before signing (D) signed, before closing.
3. MATERIAL: (A) uploaded to this Project (B) pasted (C) a folder on disk, so Claude Code (D) a mix. Tick what you hold: CIM or deck, model with formulas, audited accounts (how many years), management accounts, QoE and who commissioned it, top customer and supplier contracts, debt papers, draft purchase agreement and disclosure schedules, RWI quote, legal and tax reports, meeting notes or call transcripts.
4. YOUR THESIS in two or three lines, in your words: why this deal, what you already believe, the price you would call fair. Everything is weighed against it.
5. {{APPROVER}}: the person who signs. Required.
6. MODE: (A) CONVERSATION, the default: you ask a question, I map it to the steps that bear on it (is the EBITDA real: 05; can we sign at this price: 05 and 07; what do we put in the SPA: 08), show the map, run only those. (B) FULL RUN: 02, then 03 to 11 in order.
</onboarding>

<evidence_tiers>
TIER 1: executed agreements, audited financial statements, bank statements, tax filings, registry records. In a public filing only the audited statements and executed agreements are TIER 1; an unaudited earnings release is TIER 2, and projections anywhere are the seller's case, TIER 3 until tied.
TIER 2: management accounts, system exports (ERP, CRM, billing, AR ageing), the QoE report, third party reports whose underlying documents you have not seen, the model where a cell has a visible formula.
TIER 3: the CIM, the deck, meeting notes, call transcripts (AI written or not), cover emails, verbal statements, charts with no table. A TIER 3 figure generates a question, never a load-bearing number.
Every load-bearing figure carries its tier and source (document and page, or tab and cell). Every derived figure shows its arithmetic so {{APPROVER}} can check it by hand.
</evidence_tiers>

<deal_moves>One move per flag that survives, chosen from: PROCEED (nothing to do), PAUSE for a named document with a date, REPRICE (show the arithmetic), CLOSING CONDITION (name it), SPECIFIC INDEMNITY or ESCROW (name the item and the basis for the amount), COVENANT or post close action (owner and date), SPECIALIST REVIEW (which specialist, what question), WALK. In a take-private of a listed company, reps do not survive closing and there is no post close indemnity: the moves are price, conditions before signing, and walk.</deal_moves>

<flag_discipline>
1. Big picture first. No flag is raised before prompt 03 has set out the thesis and what must be true.
2. Test every flag against NORMAL PATTERNS and the documents first. If explained, record it once as EXPLAINED BY CONTEXT with the reason, then drop it.
3. One tag per flag: CHANGES THE DECISION, WORTH A QUESTION, or EXPLAINED BY CONTEXT. WORTH A QUESTION only if the answer could move a figure the human uses by more than 5 percent or change the verdict. Conventions, rounding, disclosed one-offs and timing go in one untagged "Checked, normal" line.
4. Only CHANGES THE DECISION reaches the verdict, and only for a flag that bears on the thesis, the price, or whether the business can carry its debt and fund its plan.
5. A missing document is a question, not a verdict, unless the decision rests on what that document alone would show. Missing optional material is OPEN, never a flag.
6. A flag the human or a document explains is closed and never colours a later prompt.
7. Arithmetic that does not tie (prompt 09) blocks the verdict until a document or a named human resolves it. This rule covers numbers only, never judgment flags. Arithmetic and recurrence tests outrank NORMAL PATTERNS: a one-time cost charged three years running is a cost.
8. A block stops the verdict, not the analysis. Keep running the other steps and print what happens by default if nobody acts.
9. Legal, tax, IP, environmental and regulatory findings: state the exposure and the specialist question. Never issue the opinion.
</flag_discipline>

<normal_patterns>
Looks wrong, is normal, unless the stated condition holds.
- Price below the 52 week high: a guidance cut or market move came first. Abnormal if the premium to the unaffected price is thin and no process ran.
- Full equity backstop with no disclosed debt: removes financing risk in an auction. Abnormal if the sponsor never shares its leverage plan with co-underwriters.
- Stock compensation added back in software: standard definition. Abnormal if debt or equity value is sized on it with no charge for dilution.
- Low free cash flow in an investment year: capitalised software or a platform build. Abnormal if the plan never shows the spend falling.
- Adjusted EBITDA above GAAP in the year after a deal: purchase accounting and deal costs. Abnormal if the gap does not narrow.
- Integration costs after an add-on: normal in the first year. Abnormal if the company buys every year.
- A large provision for uncollectibles on gross charges in healthcare services: gross is billed, net is collected. Abnormal if net revenue per visit falls.
- An impairment triggered by the deal price: accounting follows the lower value. Read it as a price signal, not an earnings problem.
- Noncontrolling interests in clinic or surgery centre JVs: common structure. Abnormal if distributions to partners grow faster than EBITDA.
- A term loan balance falling each quarter: scheduled amortisation. Abnormal if meeting it needs a refinancing.
- Customer concentration in a mid-market B2B business: common. Abnormal if the top contract ends inside the hold or terminates on change of control.
- Negative working capital in a subscription business: upfront billing. Abnormal if deferred revenue shrinks while revenue grows.
- Management projections revised during a sale: normal when they follow new actuals. Abnormal if the CIM still shows the old case.
- One period of noise after a new ERP or accounting standard: common. Abnormal if the auditor reports a material weakness that stays open.
- Seller-commissioned QoE: standard. Abnormal if its scope leaves out the adjustments that drive the price.
</normal_patterns>

<how_to_adapt>Deal and thesis: blocks 2 and 4. Evidence standard: the tier block. Your house view on add-backs, leverage or escrow: add a line to NORMAL PATTERNS with its abnormal condition, or a line to deal_moves. Materiality threshold: rule 3, change the 5 percent. Your IC format: prompt 10 only. House questions: add a numbered item to any task list.</how_to_adapt>

<rules>Never invent a figure, a term, a contract clause, a comp or a document. Missing means ask once, name the document, mark it OPEN. Two sources disagree: the executed document controls, show both, never average. End every prompt with "Next step:".</rules>

<trap>The CIM's adjusted EBITDA carries every multiple in the room. Before anything else, find audited operating income and depreciation and amortisation for the same period, so every later figure has a fixed point the seller did not adjust.</trap>

<review_gate>Confirm the surface call, whether the skill is installed, and every block back. {{APPROVER}} cannot stay blank. If the model arrived as a PDF, say now that prompt 05 can read its printed values but cannot trace a formula.</review_gate>
Click to copy
<task>Run the review on this synthetic sample. Work every figure yourself before reading EXPECTED OUTPUT, then compare line by line and print MATCH or MISMATCH for E1 to E7. Grade on substance (figures, tags, moves, status), not layout. If any line mismatches, say which and STOP: do not load real deal material until every line matches.</task>

<sample>
Test deal: Calder Tooling, a private precision parts maker, buyout of 100 percent. Buyer thesis: "a steady industrial business bought at about 8.0x real EBITDA". Buyer has a buy-side RWI quote.
S1 CIM (Tier 3): adjusted EBITDA 12.0 ($m), price EV 96.0 at 8.0x. "Our top customer renewed through 2029."
S2 AUDITED FY2025 (Tier 1): revenue 80.0, operating income 7.0, depreciation and amortisation 2.5.
S3 SELLER QoE (Tier 2), FY2025 add-backs: owner salary above a market salary, 0.5, with a market pay survey attached; integration costs of an add-on closed in March 2025, 0.8; "one-time" consulting 1.2 (the QoE shows the same line at 1.0 in FY2023 and 1.1 in FY2024).
S4 AR AGEING EXPORT (Tier 2): top customer 31 percent of FY2025 revenue. The customer contract is not in the room.
S5 CALL TRANSCRIPT, AI written (Tier 3): the CFO says "the renewal is signed".
S6 CREDIT AGREEMENT (Tier 1): term loan balance 30.0 at the start of FY2025 and 27.0 at the end, 3.0 of scheduled amortisation.
S7 QoE tax section (Tier 2): state sales tax exposure from nexus in two states, estimated 0.6, not accrued.
</sample>

<expected_output>
E1 MATERIAL BOUNDARY: S2 and S6 executed or audited, Tier 1; S3 and S4 Tier 2; S1 and S5 Tier 3. The renewal claim appears only in S1 and S5, so it is a management claim, not a fact.
E2 BRIDGE: reported EBITDA 7.0 + 2.5 = 9.5, Tier 1. Owner salary 0.5 accepted with the survey. Integration 0.8 accepted, EXPLAINED BY CONTEXT (first year after the add-on). Consulting 1.2 not accepted: recurs three years, so a cost. Accepted EBITDA 9.5 + 0.5 + 0.8 = 10.8. The CIM's 12.0 minus 10.8 = 1.2, the consulting line.
E3 PRICE: 96.0 / 12.0 = 8.0x CIM, UNVERIFIED. 96.0 / 10.8 = 8.9x accepted. At the thesis 8.0x, 8.0 x 10.8 = 86.4. Tag CHANGES THE DECISION. Move: REPRICE to about 86.4, a gap of 9.6.
E4 TOP CUSTOMER: 31 percent of revenue, contract absent. Tag: OPEN, and it bears on the thesis because the change of control and term clauses sit only in that contract. Move: CLOSING CONDITION, the executed contract in the room and any consent obtained before signing. Not a walk.
E5 SALES TAX: 0.6 found in diligence, so a known matter that the RWI policy will exclude. Move: SPECIFIC INDEMNITY with an escrow sized to at least 0.6 on the QoE estimate, pending a tax adviser's number. Answering "the RWI covers it" is a MISMATCH.
E6 NORMAL BAIT: the term loan falling from 30.0 to 27.0 is scheduled amortisation, EXPLAINED BY CONTEXT. The integration add-back is EXPLAINED BY CONTEXT. Tagging either CHANGES THE DECISION or WORTH A QUESTION is a MISMATCH.
E7 VERDICT: PROCEED WITH MOVES: reprice, the customer contract condition, the tax indemnity and escrow. Default if nothing changes: do not sign at 96.0.
</expected_output>

<review_gate>Print MATCH or MISMATCH for E1 to E7. E4 must read OPEN with a condition, never an invented renewal date: that is the stop path firing once, in safety. Only after seven MATCH lines does the human load real material. Next step: 03.</review_gate>
Click to copy
<task>Before any check runs, set out the deal in plain words. Use the material from prompt 01.
1. What the company does and how it makes money, in four sentences, each with its source and tier.
2. The seller's or sponsor's story as the CIM tells it, labelled TIER 3.
3. The human's thesis from block 4, rewritten as three or four statements of what must be true for the return, each one testable against a document (for example "top five customers stay through the hold", "EBITDA can carry 5x debt in a down year").
4. The deal context: type, stage, price, how the price was set (auction, bilateral, public offer and premium), and which moves exist at this stage (see deal_moves; a take-private has no post close indemnity).
5. The five questions to send the seller today, ranked by which must-be-true statement they test. Name the document you expect back.
</task>

<trap>A review that starts by reading the data room front to back finds a hundred things and weighs none of them. The must-be-true statements are the filter: a finding that bears on none of them goes to "Checked, normal" or WORTH A QUESTION, however odd it looks.</trap>

<stop>If the room holds no audited accounts and no tax filings, say so and do not run the price steps (05, 07): ask for them first on the question list. Everything that does not depend on them still runs.</stop>

<output_format>One screen: the five sections as short paragraphs. End with CONTINUE or ASK FOR TIME, and why, in one sentence. Next step: 04.</output_format>
Click to copy
<task>Work from the data source chosen in prompt 01.
1. INVENTORY every document: name, type (executed agreement, audited accounts, draft, management schedule, system export, third party report, meeting notes or transcript, unopened attachment), date, tier. With the skill installed, use its basic information extraction and inventory tables.
2. CONFLICTS: where two documents state the same fact differently (price, share count, a customer's term, a date), show both, name which controls (executed over draft, later signed over earlier), never average.
3. EVIDENCE MATRIX, only for the claims that carry the must-be-true statements from 03: claim, evidence, source and tier, status (confirmed, calculated, management claim, third party, open), gap, deal implication. Ten rows at most; the rest are not load-bearing.
4. For each open gap, the single document that would close it.
</task>

<trap>A claim that appears in the CIM, the management call and the model looks confirmed three times. It is one source repeated. Status stays "management claim" until a TIER 1 or TIER 2 document outside the seller's narrative supports it.</trap>

<stop>If a document is referenced but not provided (an exhibit, a side letter, a disclosure schedule), list it as missing by name and do not describe its contents from other documents' summaries of it.</stop>

<output_format>Three tables: inventory, conflicts, evidence matrix. Then the gap list. Next step: 05.</output_format>
Click to copy
<task>Work from the data source chosen in prompt 01.
1. FIXED POINT: audited operating income plus depreciation and amortisation for the latest full year, Tier 1.
2. BRIDGE to the CIM's adjusted EBITDA, one line per add-back: amount, support document, recurs (yes/no, years seen), accepted or not, tag. Accepted EBITDA is the fixed point plus accepted add-backs only.
3. REVENUE CHAIN for the top customers or a sample: order or contract, delivery or acceptance, invoice, receivable, cash collected. Note breaks, do not assume them away.
4. CASH: operating cash flow less capex and capitalised development, against accepted EBITDA, for each year you have. Conversion under 50 percent in a business that does not say it is investing is WORTH A QUESTION.
5. WORKING CAPITAL: monthly net working capital for the last twelve months if you have it; the average is the starting point for the peg; name month-end or year-end entries that distort it. Debt-like items listed separately: deferred revenue, customer deposits, accrued bonuses, income tax payable, deferred employee liabilities.
6. RESTATEMENT or audit findings: period, size, whether the current opinion is clean, whether a material weakness is still open.
</task>

<trap>Last month's working capital is the number a seller can dress. A peg set on it transfers cash to the seller at closing. Use the normalised twelve month average, and say which months you could not normalise.</trap>

<stop>If audited accounts are absent, say so and stop steps 1, 2 and 4; do not use the CIM's EBITDA as the fixed point. If monthly balance sheets are absent, mark the peg OPEN and do not estimate it from one year-end.</stop>

<output_format>The bridge table with arithmetic, the revenue chain notes, the cash table, the working capital line and debt-like list, the restatement line. Each flag tagged. Next step: 06.</output_format>
Click to copy
<task>Work from the data source chosen in prompt 01.
1. TOP CONTRACTS (customers and suppliers above 10 percent, key licences, main lease): term and expiry, change of control or assignment consent, termination for convenience, exclusivity, price reset. Quote the clause and page.
2. IP: who owns the core product (code, patents, brands), whether founder or university ownership or an inbound licence is involved, and whether it transfers.
3. LITIGATION, TAX, REGULATORY, ENVIRONMENTAL, LABOUR: what the documents disclose, the amount if stated, the specialist question to ask.
4. For each finding: tag, and the move it points to from deal_moves.
</task>

<trap>A specialist's summary saying "no material issues" is reliance, not evidence, when the underlying contracts are not in the room. Record it as TIER 2 reliance and list the contracts it covered, so the IC knows what nobody on the deal team has read.</trap>

<stop>If the top customer contract is not provided, do not state its term or its change of control position from the CIM or a call: mark it OPEN and name the contract as a closing condition candidate.</stop>

<output_format>A contract table (party, share, expiry, consent, termination, source), an IP line, a legal and tax list with specialist questions, each finding tagged with a move. Next step: 07.</output_format>
Click to copy
<task>Work from the data source chosen in prompt 01 and the accepted figures from 05.
1. PRICE: enterprise value over CIM EBITDA (UNVERIFIED) and over accepted EBITDA; the price the thesis multiple implies on accepted EBITDA; the gap.
2. PLAN AGAINST HISTORY: revenue growth and EBITDA margin in the plan against the last three reported years. Name the step change and what must happen for it.
3. LEVERAGE if debt is known: funded debt over accepted EBITDA; interest at the stated rate and at +200bp; interest cover. If debt is not in the room, OPEN.
4. DOWNSIDE: accepted EBITDA down 15 percent (or the human's figure): cover, leverage, and whether the plan can still be funded.
</task>

<trap>A price that looks fair on the CIM multiple can sit a full turn higher on accepted EBITDA. Every price conclusion is stated on accepted EBITDA, with the CIM multiple shown beside it as UNVERIFIED.</trap>

<stop>If accepted EBITDA could not be built in 05, do not compute price or leverage multiples; say which document is missing and stop this prompt.</stop>

<output_format>A short table with arithmetic, then two lines: does the deal work at this price on the thesis, and what must change if not. Tag each finding. Next step: 08.</output_format>
Click to copy
<task>Collect every flag still open after 03 to 07. For each:
1. Retest it once against NORMAL PATTERNS and any document or human answer received since. Closed flags go to one "Closed" list with the reason and are not discussed again.
2. For each surviving flag: tag, the must-be-true statement it bears on, and exactly one move from deal_moves, with the arithmetic or the basis for any amount.
3. Remedy check: a matter found in diligence is a known matter, so buy-side RWI will exclude it: the move is a specific indemnity, an escrow, a price change or a condition, never "RWI covers it". In a take-private, drop indemnity and escrow: price, pre-signing condition or walk.
4. DEFAULT: what happens if nothing is resolved by {{DECISION_DATE}}.
</task>

<trap>A register with twenty P1 items reads like diligence and decides nothing. If more than five flags survive as CHANGES THE DECISION, re-read each against the must-be-true statements; most will be WORTH A QUESTION.</trap>

<stop>If a move needs an amount that no document supports (an escrow for an unquantified claim), do not invent it: write the move with "amount OPEN" and name the specialist or document that sets it.</stop>

<output_format>The red flag register: flag, tag, evidence and tier, must-be-true link, move, owner, what closes it. Then the Closed list, then the default. Next step: 09.</output_format>
Click to copy
<task>Without reusing earlier outputs, re-derive from the source documents: the fixed point, accepted EBITDA, the price multiples, leverage and cover, the reprice amount, and any escrow amount. Compare each with the figure in 05, 07 and 08 at full precision, rounding only at the end. Print TIE or BREAK for each, like for like on the same basis and period.</task>

<trap>Two figures can differ because they measure different things (enterprise value against equity value, ASC 605 against 606, fiscal against calendar year). Before calling a BREAK, confirm the basis matches. A break on display rounding is not a break.</trap>

<stop>Any BREAK above 1 percent blocks the verdict in 10: do not produce the memo's verdict line until a document or {{APPROVER}} resolves it. Keep the rest of the memo running and print the break at the top.</stop>

<review_gate>This gate covers arithmetic only. It never reopens a judgment flag closed in 08. PASS or BLOCK, with the list of breaks. Next step: 10.</review_gate>
Click to copy
<task>Write the one-page memo for {{APPROVER}}.
1. VERDICT: PROCEED, PROCEED WITH MOVES, PROCEED ONLY ON CHANGED TERMS (name the terms: price, leverage, structure), PAUSE (name the document and the date), or WALK. PAUSE is only for a decision that rests on a document not yet in the room. A CHANGES THE DECISION flag already proven by documents in the room (disclosed debt against audited EBITDA, a plan that breaks from reported history) is not paused to wait for the other side's own model: that model can argue for the deal but cannot change what the room already shows. Such a flag gives WALK, or PROCEED ONLY ON CHANGED TERMS. If 09 is BLOCK, print BLOCKED and the breaks instead of a verdict.
2. The thesis and whether each must-be-true statement is supported, open or contradicted, one line each.
3. The moves, in the order they would go into the term sheet or SPA markup.
4. What we did not read or could not verify.
5. DEFAULT if nothing changes by {{DECISION_DATE}}.
Every figure carries its tier; any figure not tied to TIER 1 or TIER 2 has UNVERIFIED beside it.
</task>

<trap>A contradicted thesis is not the same as a bad asset. If the human's reason for the deal fails but the asset is sound at a lower price, say both: no action on this thesis, and the price at which the asset still works.</trap>

<stop>Do not write "risk is manageable" or "no material issues" unless the managing move is named in 08. "No view because the future is uncertain" is not a verdict: PAUSE needs a named question that would flip it.</stop>

<output_format>One page, plain words, no more than 400 words. Next step: 11.</output_format>
Click to copy
<task>Build a self-contained HTML file, flag-board.html, from the register in 08 and the memo in 10: verdict banner, the must-be-true statements with status, a table of surviving flags (tag, move, owner), the Closed list folded, and the default. No external scripts, fonts or network calls; inline CSS only; readable on a phone. In Claude Code write it to disk next to the outputs and print the path. In the Claude app, output it as one HTML block. With the skill installed, you may follow its HTML report specification instead, keeping the verdict banner and the moves table.</task>

<trap>A board that shows every flag in red reads as "walk" to a committee that will not read the memo. Colour by tag: only CHANGES THE DECISION is red; WORTH A QUESTION is amber; closed items are grey and folded.</trap>

<stop>If 09 returned BLOCK, the banner says BLOCKED with the breaks, and the board does not show a verdict.</stop>

<output_format>The HTML file or block, then one line: open it and check the verdict banner matches the memo. Next step: send the memo and the board to {{APPROVER}}.</output_format>
Source repo
https://github.com/noahnan-max/private-equity-investment-dd-skill ↗

The code is public and free. The setup instruction above installs and wires it for you. You never need to open this link.

Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.

Book the free audit

Rent it forever, or own it once.

For PE deal teams and family office direct investors: a structured review that sorts signed from draft, builds the evidence matrix, and gives every red flag one deal move, from reprice to escrow to walk.

Path A · free

You just did it

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts ↑
Path B · done with you

We wire it into your business

This review is about 70 percent of a buy-side red flag pass. Consultance wires the rest into your deal process: one folder run per deal, outputs landing in your IC pack, and an approval trail your auditors accept. Reply "wire it" for a 30 minute slot.

Book a build call →
data safety

Before you use live numbers

  • • 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.
  • • Wiring the open-source piece to real systems? Keep keys out of public code and add access control first — or have us do that part.
the fine print

Credit the original author

The vault is free to use on your own deals. The GitHub skill it builds on is all rights reserved and licensed for private, internal use only; clone it for yourself, do not redistribute it. Materials go only to your own Claude account, or your own Claude tenant on a Team or Enterprise plan, never to us. A structured review and decision support, not legal, tax or investment advice. A named human owns the decision.

Want this running in your business, not just your laptop? We build it and hand you the keys.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

the newsletter

AI news worth opening.

The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.

100% freeNo paywall, everUnsubscribe anytime

More like this

Other builds worth a weekend

All repos →
Finance and data

Free Portfolio Quant Research Desk

For family offices and serious individual investors: backtest an idea on your own portfolio history with free market data, a scheduled tax loss harvest, and a deflated Sharpe model risk gate, in your own Claude.

Setup guide →
Finance and data

Private Equity Deal Sourcing Playbook

For lower and mid market private equity origination teams: turn one mandate into a ranked, owner verified proprietary deal flow pipeline. Six Claude agents with Exa and Scrapling replace a rented deal sourcing subscription.

Setup guide →
Finance and data

Free Jira Alternative for Deal Teams

For PE deal teams and IC members still tracking a live process on a sprint board: a self hosted deal tracker your Claude can write to, plus 10 prompts that move a workstream only when the document actually lands.

Setup guide →
Get the free kitBook a call

Forward this to whoever owns the workflow.

The person drowning in this every week is the one who'll actually want it.

Forward by email
in one line

What is Deal Red Flag Structured Review?

Deal Red Flag Structured Review is a finance and data build in the consultance.ai AI Build Library. For PE deal teams and family office direct investors: a structured review that sorts signed from draft, builds the evidence matrix, and gives every red flag one deal move, from reprice to escrow to walk. It fits PE buyout deal teams, family office direct investment leads, independent sponsors and corporate development teams with a data room, a thesis and a decision date on a buyout or take-private (growth minority and carve-out deals are out of scope). Setup difficulty is Medium, with 4 plain-English steps.

What does Deal Red Flag Structured Review do?

For PE deal teams and family office direct investors: a structured review that sorts signed from draft, builds the evidence matrix, and gives every red flag one deal move, from reprice to escrow to walk.

Who is Deal Red Flag Structured Review for?

It fits PE buyout deal teams, family office direct investment leads, independent sponsors and corporate development teams with a data room, a thesis and a decision date on a buyout or take-private (growth minority and carve-out deals are out of scope).

How hard is Deal Red Flag Structured Review 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?

This review is about 70 percent of a buy-side red flag pass. Consultance wires the rest into your deal process: one folder run per deal, outputs landing in your IC pack, and an approval trail your auditors accept. Reply "wire it" for a 30 minute slot.

What are the licensing terms?

The vault is free to use on your own deals. The GitHub skill it builds on is all rights reserved and licensed for private, internal use only; clone it for yourself, do not redistribute it. Materials go only to your own Claude account, or your own Claude tenant on a Team or Enterprise plan, never to us. A structured review and decision support, not legal, tax or investment advice. A named human owns the decision.

Want this built into your workflow?

Deal Red Flag Structured Review is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book your free AI audit