Explore the build library
consultance.ai
Deal Copilot
Build libraryControlsAboutCase studiesBlogBook an audit
consultance.ai

Systems

WorkflowsDeal CopilotPrivate knowledgeFinance automationBuild library

Company

About usCase studiesBlogContact

Start a conversation

Free AI auditfounder@consultance.ai

Teams

Investment bankingCFOs & financePrivate equityPrivate creditReal estateProperty managementProfessional servicesOther industriesAll industries

Legal

Privacy policyTerms of service

Our approach

Audit the workflow.Build in your environment.Hand over a system you own.
Build something useful © 2026 consultance.ai
Build library/Private Equity Co Invest Screening Desk

Finance and data

Private Equity Co Invest Screening Desk

For LPs and family offices screening a PE co-invest: an independent base case, add-back test, downside, fees and carry priced in dollars, and a one-page memo with unverified figures marked.

Medium setup4 steps10 prompts
Open the setup guide Discuss an implementation
Private Equity Co Invest Screening Desk coverFinance and data

Start with the guided setup

Follow the setup below in your own workspace. For a demonstration of the prompt-copying process, open the optional walkthrough.

Watch the setup walkthrough
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. 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.

    Open claude.ai
  4. Paste, send, and answer one question

    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)
Click to copy
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 `#the-vault` anchor): https://consultance.ai/library/coinvest-screening-desk#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 Co Invest Screening Desk so Claude helps me screen a private equity co-investment on the documents the sponsor sent me, in my own Claude, inside my response window. Walk me through it one step at a time and wait for me to confirm each step. Treat me like an LP, a family office principal or an endowment investment officer who may never have built a Claude Project, and define every term once.

For most people this is NOT a Terminal or coding install. It is a private Claude Project with my documents in it. Only if my data room is a large folder do I need Claude Code, and you will tell me. Do not tell me something is "not possible" because it is not a code install; if a step is unclear, ask me one question.

Set expectations once, up front. The desk builds a simple base case from the audited numbers, tests the add-backs, runs a downside, prices the vehicle terms in dollars, and writes a one-page memo. Any figure that does not tie to a file in the data room is marked UNVERIFIED. It does not replace a full buy-side diligence, it does not check the documents against the outside world, and it does not sign anything. A named person signs. If I want this wired into a standing process, the reply is "wire it" and consultance.ai sends a 30 minute slot.

Privacy, said plainly: the 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 (Settings, then Privacy, then turn off "Help improve our AI models").

Ask me ONE question first and wait: where are my documents right now? (A) a handful of files I can upload: the deck, 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

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 deck, the model, the audited accounts, the QoE if I have it, the debt papers and the co-invest term sheet to the Project's knowledge, its file area.
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 "how much of the price rests on add-backs?", and the desk runs only the steps that bear on it. Or a full run: 03 to 10 in order, following the day plan prompt 01 gives me.

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

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; the free plan does not include it. It reads the files in a folder on my machine and writes its outputs beside them. A terminal is the text window where commands are typed. The install page is https://code.claude.com/docs/en/setup . On macOS, Linux or WSL the install line from that page is:
   ```
   curl -fsSL https://claude.ai/install.sh | bash
   ```
   On Windows PowerShell it is:
   ```
   irm https://claude.ai/install.ps1 | iex
   ```
   I do not paste an install command from anywhere else. If the command fails, I copy the error to you and you help me read it.
2. **Open it in the folder.** In the terminal, go to the data room folder and type `claude` to start it there.
3. **Paste prompt 01** and choose option C in block 3, a folder on disk. Then run 02, then conversation mode or 03 to 10. In prompt 05 Claude Code writes a small Python script and runs it if Python 3 is installed, so the base case arithmetic is computed rather than typed. Without Python 3 it shows the arithmetic line by line.

## First session drill

Start with prompt 02 and check the six MATCH lines. Then run prompt 03 on the real offer and send its five questions to the sponsor the same day. Then run prompt 04 and read one line: the entry multiple on deck, accepted and reported EBITDA. That line shows how much of the price rests on adjustments.

Good output: every figure has a document and page, some figures say UNVERIFIED or OPEN with the missing document named, and normal features of a co-invest (no fee and no carry, a cov-lite loan, stock compensation added back in software) are listed once as "explained by context" and then left alone. Bad output: every number is filled from the deck, or the memo lists every concern it can think of. If I see bad output, rerun prompt 08.

Before I trust anything, I check one figure by hand: reported EBITDA from the audited accounts, operating income plus depreciation and amortisation.

## Bonus path, never required

The bonus prompts in the download (portfolio fit, the deal-team call script, first-year reporting rights, and the sell-down notice read) are for after the core ten feel familiar. No third-party repository or tool is required for anything on this page.
Step 2 · run it on your data

Step 1 set it up. These 10 prompts do the work.

the vault

The 10 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 10 prompts, numbered, in order · nothing left out.
Click to copy
<role>A colleague who has screened many private equity co-investments for LPs. Neutral: not sceptical of the sponsor by default and not persuaded by the deck. You work for the LP writing the cheque, and your job is to help them decide inside their window.</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 deck, 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 screen for every offer: Claude Code pointed at the folder. 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>

<onboarding>
Ask each block, wait for the answer, never assume.
1. WHO: (A) family office (B) endowment or foundation (C) co-invest programme or fund of funds (D) pension or insurer.
2. THE OFFER: {{SPONSOR}} {{TARGET}} {{TICKET}} and whether it is fixed or "up to", {{DEADLINE}}, today's date, and timing: (A) before signing, co-underwrite (B) after signing (C) after closing, a sell-down. Are you in the sponsor's main fund, {{MAIN_FUND}}?
3. MATERIAL: (A) uploaded to this Project (B) pasted (C) a folder on disk, so Claude Code (D) a mix. Tick what you hold: deck, model with formulas, audited accounts (how many years), management accounts, QoE and who commissioned it, credit agreement or debt commitment papers, co-invest term sheet or vehicle LPA, main fund LPA and side letter, customer data.
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 (add-backs: 04; price: 04 and 05; downside: 06; terms: 07), show the map, run only those. (B) FULL RUN: 02, then 03 to 10 in order.
</onboarding>

<window_plan>From {{DEADLINE}} and today's date, lay out the days: day 1 run 03 and send its questions to the sponsor the same day; then 04 and 05; then 06 and 07; then 08; the memo the day before the deadline. With under two working days, run 03, 04, 07 and 09 only, and the memo lists what was not run. A window too short to read the vehicle documents is a reason to ask for time or a smaller ticket, not to lower the bar.</window_plan>

<evidence_tiers>
TIER 1: audited financial statements, executed or final credit agreement and commitment papers, the co-invest vehicle LPA or signed term sheet, the main fund LPA and side letter. In a public filing, only the audited statements and the executed agreements are TIER 1; an unaudited earnings release is TIER 2, and projections in any document are the sponsor's case, TIER 3 until tied.
TIER 2: management accounts, the QoE report, the sponsor model where a cell has a visible formula, customer data exports.
TIER 3: the deck, 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>

<tie_out_rule>No figure from the deck or the model counts until it ties to a TIER 1 or TIER 2 file in the data room on the same basis and period. A figure that does not tie is printed with UNVERIFIED beside it, in every output and in the memo margin. UNVERIFIED is a label, not an accusation.</tie_out_rule>

<flag_discipline>
1. Big picture first. No flag is raised before prompt 03 has set out the thesis.
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. 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 in the downside from 06.
4. A missing document is a question, not a verdict, unless the decision rests on what that document alone would show.
5. A flag the human or a document explains is closed and never colours a later prompt.
6. Arithmetic that does not tie (prompt 08) blocks the verdict until a document or a named human resolves it. This rule covers numbers only, never judgment flags.
7. A block stops the verdict, not the analysis. Keep running the other steps and print what happens by default if nobody acts.
</flag_discipline>

<normal_patterns>
Looks wrong, is normal, unless the stated condition holds.
- No management fee and no carry on the vehicle: common. About two thirds of recent deal-by-deal co-invests charge no fee, and close to half charge neither fee nor carry. Abnormal if the sponsor takes transaction or monitoring fees from the company that are not offset or shared.
- A small fee and reduced carry, about 0.75 to 1 percent and 7.5 to 15 percent: common where charged. Abnormal if carry is at or above the main fund's, or has no hurdle.
- Sponsor sells down after signing or closing: standard syndication. Abnormal if the fund's own hold is cut to a token or the sell-down window has no end.
- An "up to" allocation cut back: at the sponsor's discretion unless a side letter says otherwise. Abnormal if it contradicts the written allocation policy.
- The QoE was commissioned by the seller or the sponsor: standard in a sizeable sale. Abnormal if its scope leaves out the adjustments that drive the price, or its EBITDA does not tie to the model.
- A cov-lite term loan with only a springing revolver test: the large majority of syndicated loans. Abnormal if the business routinely draws its revolver hard.
- Broken-deal costs shared pro rata: ILPA calls this appropriate in most cases. Abnormal if uncapped, charged to post-closing co-investors, or inconsistent with how break fees are shared.
- Fewer information rights than the main fund: passive co-investors sit one level up. Abnormal if there are no company-level financials at all.
- Stock compensation added back in a software company: standard. Abnormal if the debt or the equity value is sized on it with no charge for dilution.
- Acquisition and integration costs added back after an add-on: normal in the year after that deal. Abnormal if the company buys every year so the cost recurs: then it is a cost of the growth strategy, and the accepted EBITDA deducts it.
- Adjusted EBITDA well above GAAP in the first year after a deal: purchase accounting and deal costs. Abnormal if the gap does not narrow.
- Negative working capital in a subscription business: upfront billing. Abnormal if deferred revenue shrinks while revenue grows.
- High leverage on a recurring-revenue loan sized on ARR: normal with a liquidity covenant. Abnormal if there is no path to positive EBITDA before the loan flips to EBITDA tests.
- Projected margin expansion: normal when the actions are named and already started. Abnormal if nothing has started or the savings exceed the historical cost base.
- Entry multiple above public trading comps: a control premium. Abnormal if the premium is not explained by growth or margin.
- Equity worth less than cost in a downside case with exit at the entry multiple: true of almost any equity. Abnormal if the debt cannot be serviced or the plan cannot be funded in that case.
- Management projections revised during the sale process: normal when they follow new actuals. Abnormal if the deck still shows the old case.
</normal_patterns>

<how_to_adapt>Offer and thesis: blocks 2 and 4. Evidence standard: the tier block. Your house view on fees or leverage: add a line to NORMAL PATTERNS with its abnormal condition. Your committee format: prompt 09 only. House questions: add a numbered item to any task list.</how_to_adapt>

<rules>Never invent a figure, a term, a comp, a covenant 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 deck's adjusted EBITDA is the number every multiple on the page is built on. Before anything else, find the audited operating income and depreciation for the same period, so every later figure has a fixed point that the sponsor did not adjust.</trap>

<review_gate>Confirm the surface call 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 desk 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 E6. Grade on substance (figures, tags, 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: Harlow Systems, vertical software, sponsor sell-down after signing. LP thesis: "a steady software business bought at about 12x EBITDA". Ticket 10.0 ($m).
S1 DECK (Tier 3): adjusted EBITDA 40.0, entry EV 480.0 at 12.0x, leverage 5.0x, net revenue retention 104 percent.
S2 AUDITED FY2025 (Tier 1): revenue 250.0, operating income 18.0, depreciation and amortisation 10.0.
S3 SELLER QoE (Tier 2), FY2025 add-backs: stock compensation 3.0; restructuring 4.0 (the QoE shows restructuring of 3.0 in FY2023 and 3.5 in FY2024); integration costs of an add-on closed in 2025, 2.0; run-rate cost savings 3.0, no action started, no support document.
S4 DEBT COMMITMENT PAPERS (Tier 1): term loan 200.0, all-in rate 9.0 percent, no maintenance covenant, springing revolver test only. The credit agreement with its EBITDA definition is not in the room.
S5 CO-INVEST TERM SHEET (Tier 1): no management fee, no carry, vehicle expenses capped at 0.05. Main fund terms from the LPA (Tier 1): 2 percent a year on committed capital, 20 percent carry.
Assume 2.5x gross over five years, fees and carry paid out of the 25.0 of gross proceeds, carry on all profit after fees. For the downside line, take accepted EBITDA down 15 percent.
</sample>

<expected_output>
E1 BRIDGE: reported EBITDA 18.0 + 10.0 = 28.0, ties to S2, Tier 1. SBC 3.0 accepted, EXPLAINED BY CONTEXT, shown in a cash view. Integration 2.0 accepted, EXPLAINED BY CONTEXT (first year after the add-on). Restructuring 4.0 not accepted, recurs 3 years, WORTH A QUESTION. Run-rate savings 3.0 not accepted, UNVERIFIED. Accepted EBITDA 28.0 + 3.0 + 2.0 = 33.0.
E2 PRICE AND LEVERAGE: EV 480.0 is 12.0x deck 40.0 (UNVERIFIED), 480.0 / 33.0 = 14.5x accepted, 480.0 / 28.0 = 17.1x reported. Leverage 200.0 / 40.0 = 5.0x, / 33.0 = 6.1x, / 28.0 = 7.1x. Against a thesis of about 12x: CHANGES THE DECISION on price.
E3 NET TERMS: vehicle 25.0 - 0.05 = 24.95, 2.50x net (2.495). Main fund fees 2 percent x 10.0 x 5 = 1.0; carry 20 percent x (25.0 - 10.0 - 1.0) = 2.8; net 21.2, 2.12x. Vehicle terms worth 3.75 on 10.0. No fee no carry: EXPLAINED BY CONTEXT.
E4 DOWNSIDE: accepted EBITDA down 15 percent, 33.0 x 0.85 = 28.05. Interest 200.0 x 9.0 percent = 18.0, cover 1.56x; rate +200bp, 22.0, cover 1.28x. Leverage 200.0 / 28.05 = 7.1x. Cov-lite: EXPLAINED BY CONTEXT; the test is liquidity, request the revolver size and cash.
E5 OPEN AND UNVERIFIED: net revenue retention 104 percent is deck only, UNVERIFIED. Covenant EBITDA and any cap on cost-save add-backs: OPEN, request the credit agreement. Nothing is estimated for either.
E6 NORMAL BAIT: SBC, integration costs, no fee no carry and cov-lite are all EXPLAINED BY CONTEXT. Tagging any of them CHANGES THE DECISION is a MISMATCH.
</expected_output>

<review_gate>Print MATCH or MISMATCH for E1 to E6. E5 must read OPEN for the credit agreement, never a number: that is the stop path firing once, in safety. Only after six 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, then decide whether it is worth the window. Use the material from prompt 01.
1. What the company does and how it makes money, in four sentences, each with its source.
2. The sponsor's thesis and the two or three things that must be true for its return, as the deck states them (Tier 3 until tied).
3. The human's thesis from block 4, and where it agrees or differs with the sponsor's.
4. Why there is a co-invest tranche: the sponsor's stated reason (fund concentration limit, deal size, a syndicate that fell away), the fund's hold after sell-down, and whether the co-investors get the same security at the same price.
5. Fit: is this deal the size, sector and type the sponsor usually does, from its own materials?
6. The five questions to send the sponsor today, ranked by what the answer could change. Ask open questions and name the document you expect back.
</task>

<trap>A sell-down reads like the sponsor offloading its weakest deal. Large-sample research finds the main driver of a co-invest offer is deal size against the fund, and gross returns similar to the fund's other deals. What deserves attention is a deal outside the sponsor's usual strategy, or a fund hold cut to a token.</trap>

<stop>If the room holds no audited accounts, say so and stop the price and bridge steps (04, 05, 06): ask for them first on the day-one list. Everything that does not depend on them still runs.</stop>

<output_format>A one-screen picture: the four sections as short paragraphs, the tranche and fit lines, the five questions. End with CONTINUE or ASK FOR TIME, and why, in one sentence. Next step: 04.</output_format>
Click to copy
<task>Build the bridge from the audited numbers to the EBITDA the price is quoted on, and test each add-back. Use the material from prompt 01.
1. TIE-OUT: last fiscal year and LTM revenue, operating income, depreciation and amortisation, and net debt, from the audited accounts and management accounts. Place the deck's and the model's figure beside each. Same basis and period, or say why not.
2. BRIDGE, one line per step: operating income, reported EBITDA, management adjusted, QoE adjusted, covenant EBITDA if the credit agreement is in the room.
3. ADD-BACK TABLE, one row each: item, category (non-recurring, owner comp, run-rate, cost save, synergy, SBC, restructuring, acquisition, other), amount, recurs in prior years (which), support document, who supports it (management, seller QoE, sponsor QoE, none), realised to date for run-rate items, tag, amount accepted.
4. Accepted EBITDA, and entry multiple and leverage on three bases: deck, accepted, reported.
5. Who commissioned the QoE, its scope, and whether the co-investor can rely on it.
</task>

<trap>A charge called one-off that appears in three straight years is a cost of running the business. Pull the same line for every year in the room before accepting it. The recurrence test outranks the normal patterns: a roll-up that acquires every year has deal costs every year. The reverse also holds: a single integration cost in the year after one add-on is normal.</trap>

<stop>If the room has adjusted EBITDA but no bridge from audited operating income, say so and stop steps 3 and 4. Ask for the bridge. Do not reverse-engineer add-backs from the difference.</stop>

<output_format>The tie-out table with UNVERIFIED beside every deck or model figure that does not tie; the add-back table; the three-basis line with arithmetic; one sentence on how much of the price rests on add-backs you did not accept. Tag only what bears on the thesis or the price. Next step: 05.</output_format>
Click to copy
<task>Build an independent base case from the accepted EBITDA, not the sponsor's case. This is a check on the sponsor's model, not a new LBO. Use the material from prompt 01.
1. Inputs, each with its source: accepted EBITDA from 04, revenue growth and margin anchored to the audited history (state the years), capex, working capital, cash taxes, cash interest on the debt terms (if the base rate is not in the room, run the loan floor and +200bp, label the rate OPEN, and say which one the base case uses), entry EV and equity cheque, hold period, exit multiple equal to entry on the accepted basis.
2. Year by year: EBITDA, free cash flow after capex, working capital, taxes and interest, net debt.
3. Exit equity, gross MOIC and IRR. Then the same with the sponsor's exit multiple and growth, side by side.
4. RETURNS BRIDGE: how much of the sponsor's gross return comes from EBITDA growth, from multiple change, and from debt paydown.
5. The two sponsor inputs that move the return most, their source, and the return if each is cut by half.
In Claude Code: write the inputs to base_case.csv and a short standard-library Python script rebuild.py that reads it and prints the table; run the script with python3 rebuild.py and paste its output. If python3 is not installed, say so and show every line of arithmetic instead. In the Claude app, show every line of arithmetic.
</task>

<trap>A return that works only with exit above entry is a bet on the market, not on the company. Always print the case with exit multiple equal to entry, and say what share of the sponsor's return the multiple carries.</trap>

<stop>If the audited history in the room is under two years, say so and stop the growth anchor: label the base case SPONSOR-ANCHORED and ask for three to five years of accounts. Do not invent a history.</stop>

<output_format>Input table with sources; the yearly table; base versus sponsor returns; the returns bridge; the two sensitivities. Every sponsor input with no data room support carries UNVERIFIED. Next step: 06.</output_format>
Click to copy
<task>Stress the base case from 05. Use the material from prompt 01.
1. Anchor the downside to evidence: apply the worst year-on-year fall in revenue and EBITDA in the audited history, or a stated sector trough with its source, in year one; then resume the historical growth rate from the lower base, unless the latest actuals show no recovery. State the anchor.
2. Downside and severe cases, year by year: EBITDA, free cash flow, cash interest at the stated rate and at +200bp, interest cover, net leverage.
3. The debt terms that matter under stress: maintenance covenant level and headroom if one exists, or for a cov-lite loan the revolver size, the springing test trigger, and cash. Liquidity runway in months.
4. The equity outcome in each case: exit value at the entry multiple and at one turn lower, and whether the equity cheque is lost.
5. What would have to happen for the co-investor to be asked for more money, and what the vehicle documents say about follow-on.
</task>

<trap>No maintenance covenant does not mean no risk. On a cov-lite loan the early warning is gone, so the question is how many months of cash and revolver the business has at downside EBITDA with rates higher.</trap>

<stop>If the debt terms are not in the room, say so and stop the cover and headroom lines: label leverage SPONSOR-STATED if a sponsor or filed document states it, otherwise OPEN, and ask for the commitment papers or credit agreement. Never take covenant levels or pricing from the deck.</stop>

<output_format>The downside table (columns: base, sponsor case, downside, severe; last row the equity outcome); the liquidity line; one sentence on whether the downside changes the decision. Equity below cost in a downside is normal for any equity and is not by itself a decision flag. CHANGES THE DECISION when, in the history-anchored downside, cash flow after interest cannot service the debt or fund the sponsor's plan without new money, or the equity is wiped out. Next step: 07.</output_format>
Click to copy
<task>Read the co-invest term sheet or vehicle LPA, and the main fund LPA and side letter if the human is in the fund. Use the material from prompt 01.
1. One line per term, vehicle beside main fund, with the clause: management fee and its base, carry, hurdle, catch-up, vehicle expense cap, broken-deal cost share, transaction, monitoring and director fees paid by the company to the sponsor and how they are offset or shared.
2. Net dollars to the human on {{TICKET}} at the base case from 05 and at the sponsor's case: under the vehicle terms, and, if they are in the main fund, the same dollars through it. Arithmetic shown.
3. Governance: information rights, tag and drag, transfer, follow-on and dilution, continuation vehicle clause, the sponsor's right to cut the allocation.
4. The one term worth pushing on before the deadline, and the wording to propose.
</task>

<trap>Carry on the vehicle with no hurdle can pay the sponsor carry on your money in a case where main fund investors pay none. Find the hurdle line in both documents before pricing anything.</trap>

<stop>If the term sheet or vehicle LPA is not in the room, say so and stop the pricing: TERMS NOT PROVIDED, first item on the question list. Do not assume market terms, and do not price terms taken from a cover email.</stop>

<output_format>The terms table with clauses; the net dollars table; the governance lines tagged; the one push-back. Next step: 08.</output_format>
Click to copy
<task>Act as a second reader with no view on the deal. From the documents alone, re-derive and compare with prompts 04 to 07:
1. Reported EBITDA for the last fiscal year from the audited accounts.
2. Accepted EBITDA and the entry multiple on it.
3. Leverage at close on the accepted basis.
4. Downside interest cover at +200bp.
5. Net dollars to the human under the vehicle terms at the base case.
6. The list of figures marked UNVERIFIED, each checked against the room once more.
</task>

<trap>A figure copied through four prompts can look confirmed because it appears everywhere. Re-derive it from the source document, not from the earlier outputs.</trap>

<stop>Compare like with like: two figures that measure different things (funds needed including fees, and equity value) are not a disagreement, and where a document gives only an approximate figure, use the most precise figure a document supports and state the range. Then any difference over 1 percent on a dollar figure on the same basis, any figure with no source, or a deck figure used as load-bearing without a tie is a BLOCK on the verdict. Do not argue it away. Keep the analysis, name the item, state what resolves it (a document, or {{APPROVER}} correcting the figure), and print the default if nothing is resolved by {{DEADLINE}}: no commitment. A line whose source document is not in the room reads OPEN, not BLOCK; it reaches the memo as a condition.</stop>

<output_format>Six lines: earlier value, re-derived value, difference, PASS or BLOCK. One verdict line: PASS, or BLOCK with the item numbers and the default. Next step: 09.</output_format>
Click to copy
<task>Write one page for {{APPROVER}}, who has fifteen minutes. Use only the outputs of 03 to 08.
1. Verdict: PROCEED, PROCEED WITH CONDITIONS, or DECLINE, the one reason with a number in it, and the default if nobody acts by {{DEADLINE}}. If 08 returned BLOCK, the verdict line reads BLOCKED and names the item; the rest of the page is still written.
2. The deal and the human's thesis in three sentences, and whether the documents support it.
3. Why the tranche exists and the fit, one sentence.
4. Price: entry multiple on deck, accepted and reported EBITDA.
5. Returns: base case against the sponsor's case, and the share carried by multiple change.
6. Downside: interest cover and liquidity, the equity outcome.
7. Terms: net dollars against the main fund, and the one push-back.
8. Only the CHANGES THE DECISION flags. Then a short list headed "Checked and explained", one line each, never raised again.
9. Open questions: sent, answered, unanswered, and what each unanswered one means for the verdict.
10. What was not run for time.
A right-hand margin column carries UNVERIFIED or OPEN beside every figure that did not tie.
</task>

<trap>A memo written the night before the deadline tends to become a list of every concern. Keep it to the few items that move the decision or the price; the rest were closed in the earlier prompts and belong in "Checked and explained".</trap>

<stop>If a figure on the page is not in an earlier output, remove it and name it. Do not add new analysis here. A PROCEED on a driver marked UNVERIFIED says so in the verdict line and needs {{APPROVER}} to accept it in writing.</stop>

<output_format>One page, about 450 words, the ten blocks in order, the margin column, and a sign-off line for {{APPROVER}} with the date and the prompt 08 result. Next step: 10, if a screen for the committee helps.</output_format>
Click to copy
<task>Generate one self-contained HTML file, screen-board.html, from the outputs of 04 to 09 only. No network calls, no external scripts, no fetched fonts. In Claude Code, write it to disk beside the outputs and print its path. In the Claude app, return it as a single file.
Content: header with {{SPONSOR}}, {{TARGET}}, {{TICKET}}, {{DEADLINE}}, the verdict and the prompt 08 result. Tiles: entry multiple on three bases, leverage on accepted EBITDA, base and sponsor gross MOIC, downside interest cover, net dollars against the main fund. A bar for the returns bridge. The CHANGES THE DECISION flags. Open questions. Footer: what was not run and the sign-off line.
</task>

<trap>A board filled from the deck looks exactly like a board filled from the audited accounts. Every tile carries a small source tag, and any figure marked UNVERIFIED or OPEN shows that label at the same size as the number.</trap>

<stop>If prompt 09 has not been produced, stop and say so. Do not build the board from earlier drafts.</stop>

<output_format>The complete HTML, then one line listing tiles that show UNVERIFIED or OPEN.</output_format>

From a working build to an operating system.

For LPs and family offices screening a PE co-invest: an independent base case, add-back test, downside, fees and carry priced in dollars, and a one-page memo with unverified figures marked.

Path A · free

Run the build independently

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

Connect it to your operation

This desk is about 70 percent of an LP's co-invest screen. Consultance wires the rest into a standing process: one folder run per offer, the outputs landing in your committee pack, and an approval trail your auditor accepts. 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.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Free to use on your own opportunities. Materials go only to your own Claude account, or your own Claude tenant on a Team or Enterprise plan, never to us. Screening and decision support, not investment advice. A named human owns the commitment.

Bring this workflow into your operation.

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.

Newsletter

New builds, as they ship

One short note when a new build ships: what it does, who it is for, and how to run it in your own Claude.

Free. One email a week at most. Unsubscribe in one click.

More like this

Related builds

All builds
Finance and data
Finance and data

Month End Close AI Agent Team

For controllers and CFOs: a 12 agent month end close team in your own Claude that preps reconciliations, accruals, entries and flux notes as a structured review. You approve every ledger post.

Setup guide
Finance and data
Finance and data

Ramp Claude Connector Setup Guide

For controllers and finance ops teams on Ramp: Claude setup steps plus 12 read only prompts for spend baseline, close readiness, accruals and flux. Replaces the manual Ramp export to Excel.

Setup guide
Finance and data
Finance and data

Claude and NetSuite Setup Guide

For controllers, CFOs and FP&A leads on NetSuite: the setup steps for Oracle's Claude connector plus 12 read only prompts for close, receivables, payables and cash.

Setup guide
Get the free kitBook a call

Share with your workflow owner.

Bring the relevant team into the conversation with the build and setup guide.

Forward by email
in one line

What is Private Equity Co Invest Screening Desk?

Private Equity Co Invest Screening Desk is a finance and data build in the consultance.ai AI Build Library. For LPs and family offices screening a PE co-invest: an independent base case, add-back test, downside, fees and carry priced in dollars, and a one-page memo with unverified figures marked. It fits LPs offered a co-invest alongside a fund commitment who must answer within days, family offices and single-deal allocators without a dedicated deal team, small endowments and foundations where one person covers private markets, and fund of funds or outsourced CIO teams running a co-invest sleeve. Setup difficulty is Medium, with 4 plain-English steps.

What does Private Equity Co Invest Screening Desk do?

For LPs and family offices screening a PE co-invest: an independent base case, add-back test, downside, fees and carry priced in dollars, and a one-page memo with unverified figures marked.

Who is Private Equity Co Invest Screening Desk for?

It fits LPs offered a co-invest alongside a fund commitment who must answer within days, family offices and single-deal allocators without a dedicated deal team, small endowments and foundations where one person covers private markets, and fund of funds or outsourced CIO teams running a co-invest sleeve.

How hard is Private Equity Co Invest Screening Desk to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 10 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

This desk is about 70 percent of an LP's co-invest screen. Consultance wires the rest into a standing process: one folder run per offer, the outputs landing in your committee pack, and an approval trail your auditor accepts. Reply "wire it" for a 30 minute slot.

What are the licensing terms?

Free to use on your own opportunities. Materials go only to your own Claude account, or your own Claude tenant on a Team or Enterprise plan, never to us. Screening and decision support, not investment advice. A named human owns the commitment.

Connect this build to your workflow.

Discuss how Private Equity Co Invest Screening Desk fits your systems, controls, and team. We define the integration, review process, and deployment requirements with you.

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 an audit