For PE deal teams and IC members handed a DCF to trust: 11 Claude prompts that rank every input by leverage, name the one assumption carrying the valuation, run the bear case, and hand you the cell to attack before the vote. On your own data, inside Claude.
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.
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.
Free account, no card, 30 seconds. This tab stays open so you can come back.
Open claude.ai ↗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.
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/dcf-attack-kit#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 DCF Attack Kit inside my own Claude and run it on a real DCF this week. Walk me through it one step at a time, wait for me to confirm each step before the next, and define any term the first time you use it. Treat me like a PE deal lead, IC member, or CFO who reviews valuations but has never wired up a Claude Project. This is NOT a Terminal install. There is nothing to install from a command line. It is all done by clicking inside Claude and pasting prompts. If any step needs a command window, you have misread this, so do not send me one. Do not tell me this is "not possible" inside Claude, because it is, so if you hit a wall, ask me a question instead. One honest thing before we start, so you know the ceiling: this vault is about 60 percent of the build. It gets a real DCF onto the table, finds the assumption doing the lifting, runs the bear case, and writes the one page attack memo. The last 40 percent, wiring live data into your model and data room, role based permissions so the right people see the right cells, an audit trail your reviewer will accept, and running this across many deals at once, is implementation work consultance wires into production with you. That is the honest ceiling of any prompt bundle. When you want that part, reply "wire it" for a 30 minute slot. Ask me this ONE question first, then stop and wait: **Where does the DCF you want to attack live right now?** - (A) An Excel or Google Sheets model somebody sent me - (B) A PDF or a CIM with the DCF and its outputs inside it - (C) A data room I would have to export the model from - (D) I only have the headline number and a few assumptions, I will paste them raw Once I answer, walk me through the setup in this order, one step at a time: 1. **Open Claude and pin the model.** Tell me to go to claude.ai (or the desktop app), start a new chat, and set the model to Claude Fable 5 for the whole session. Define: pinning the model means picking Claude Fable 5 from the model dropdown so every prompt in this session uses the same one and the numbers do not drift. 2. **Create a private Project.** Click "Projects" in the left sidebar, then "New project", name it something like "DCF Attack — [target]". Explain why: a Project keeps my data in my own tenant. Nothing I load is uploaded to consultance.ai, stored by us, or seen by us. That is the whole reason this is safe to run on a live deal. 3. **Load the DCF the way that fits my answer above.** If (A) or (B), tell me exactly how to upload the file into the Project knowledge, or how to use the Claude Excel add-in to read the workbook in place. If (C), tell me to export first and then upload. If (D), tell me to have the headline EV, the WACC, the terminal method and input, and the forecast horizon ready to paste when prompt 01 asks. 4. **Paste prompt 01, the setup router.** It will ask me what type of DCF I am attacking and where my data lives, then confirm the setup back to me. Define: the router is the first prompt, it sets the whole session up so every later prompt works off the same setup. Tell me not to run anything else until 01 confirms. Then, once setup is done, run the first-session drill on the highest-value prompts, one at a time: - **Prompt 02 (rebuild the model).** Tell me what good output looks like: a clean driver table and a UFCF bridge that TIES to the source model. If it does not tie, it stops and lists the lines that do not, which is correct, not a failure. Do not trust anything downstream until 02 ties. - **Prompt 03 (rank inputs by leverage) and 04 (name the load-bearing assumption).** This is the heart of the kit. Good output is a leverage table sorted by how much each input moves the answer, then ONE named assumption the whole valuation rests on. If it hedges into three equal candidates, tell it to pick one and defend the pick. - **Prompt 07 (the reconciliation gate).** Run this before the memo. It re-derives the value a second, independent way and prints RECONCILED or NOT RECONCILED. If it prints NOT RECONCILED, the model is wrong until proven otherwise, so do not write the memo yet. Define: reconciliation here means getting to the number a different way and checking the two agree. - **Prompt 09 (the attack memo).** Good output is one page a partner can act on: the number, the assumption doing the lifting, the bear case, the one or two cells to attack, and the reconciliation status. If it buries the point under caveats, tell it to lead with the cell to attack. Bonus path, never required: the library page and the bonus-extras file (reverse DCF, WACC forensics, the assumption log) are there when I want them, but I do not need any repo, any install, or any third-party tool to run the vault. Everything runs inside my own Claude. Before I trust any output: check that every figure traces to a source cell or a labeled assumption, that prompt 07 printed RECONCILED, and that a named human (me or my reviewer) signs off the load-bearing assumption before the number goes to the IC.
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.
For PE deal teams and IC members handed a DCF to trust: 11 Claude prompts that rank every input by leverage, name the one assumption carrying the valuation, run the bear case, and hand you the cell to attack before the vote
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 ↑The vault is about 60% of the build. We wire the last 40% into production in your own environment, deal data never leaving the building: live data wiring into your model and data room, role based permissions so the right people see the right cells, a retained audit trail your reviewer will accept, and the reconciliation gate as a standing pre vote control across every deal at scale. Done with you, then handed over so you own it.
Book a build call →Prompt set authored by consultance.ai. A DCF attacked here produces a first draft valuation read, not a fairness opinion or investment advice. Your data stays in your own Claude tenant; we never see it. Fair value work maps to ASC 820 and IFRS 13, valuation performance to AICPA SSVS No. 1 and IVS 105, and estimate auditing to PCAOB AS 2501; a named human signs off every figure against source before it reaches an investment committee, a board, or a counterparty. Not legal or investment advice.
Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.
The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.
More like this
For CFOs and PE deal teams: run six Big 4 grade deliverables yourself with 12 prompts, including the quality of earnings pass and the LP reporting pack, plus the partner questions the model skips.
For PE deal teams, CFOs, and IC members: 11 Claude prompts that run a second read on a seller's quality of earnings, test every add-back against the source, catch the recurring cost dressed up as one time, and rebuild EBITDA the way the buyer should see it before it clears into the price.
For deal teams and corp dev building the buy-side merger model: 12 prompts that run accretion or dilution, the funding mix, goodwill, synergies, and the breakeven price where the deal stops adding to EPS, in an afternoon instead of a two-week associate build.
The person drowning in this every week is the one who'll actually want it.
DCF Assumption Attack Kit is a finance and data build in the consultance.ai AI Build Library. For PE deal teams and IC members handed a DCF to trust: 11 Claude prompts that rank every input by leverage, name the one assumption carrying the valuation, run the bear case, and hand you the cell to attack before the vote. On your own data, inside Claude. It fits PE deal teams and principals, investment committee members, corporate development, family office principals, and CFOs who receive a DCF and have to decide whether to trust the number. Setup difficulty is Medium, with 4 plain-English steps.
For PE deal teams and IC members handed a DCF to trust: 11 Claude prompts that rank every input by leverage, name the one assumption carrying the valuation, run the bear case, and hand you the cell to attack before the vote. On your own data, inside Claude.
It fits PE deal teams and principals, investment committee members, corporate development, family office principals, and CFOs who receive a DCF and have to decide whether to trust the number.
Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 11 ready-to-run prompts on the resource page.
The vault is about 60% of the build. We wire the last 40% into production in your own environment, deal data never leaving the building: live data wiring into your model and data room, role based permissions so the right people see the right cells, a retained audit trail your reviewer will accept, and the reconciliation gate as a standing pre vote control across every deal at scale. Done with you, then handed over so you own it.
Prompt set authored by consultance.ai. A DCF attacked here produces a first draft valuation read, not a fairness opinion or investment advice. Your data stays in your own Claude tenant; we never see it. Fair value work maps to ASC 820 and IFRS 13, valuation performance to AICPA SSVS No. 1 and IVS 105, and estimate auditing to PCAOB AS 2501; a named human signs off every figure against source before it reaches an investment committee, a board, or a counterparty. Not legal or investment advice.
DCF Assumption Attack Kit 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.