Claude Projects for Investment Bankers: Build a Persistent Deal Room in 15 Minutes
How persistent AI context eliminates 60% of repetitive deal workflow setup time. A step-by-step guide for live mandates.
The Problem: AI Without Memory Wastes Hours
Every investment banker who uses AI for deal work faces the same friction: each new chat session starts from zero. You re-explain the deal structure, re-upload the CIM, re-establish your preferences. On a live sell-side mandate with daily sessions, this overhead compounds into hours of lost time per week.
Claude Projects solves this with persistent context. Documents, instructions, and deal parameters load automatically into every session. The AI knows the company, the sector, your output format preferences, and the deal timeline before you type your first question.
20–30 minutes re-briefing the AI on deal context before useful analysis begins
Document re-upload every session — CIM, model assumptions, sector report
Inconsistent output quality without standing knowledge of your preferences
Cross-document synthesis impossible when documents are not co-resident in one context
Setup: One Project per Deal, Five Documents Maximum
Name it after the deal or engagement code. Keep it deal-specific — never mix mandates in a single Project.
3–4 sentences covering your role, deal type, target sector, and output format preferences. This loads before every session and is the single highest-leverage setup step.
Annual report or 10-K; CIM or information memorandum; financial model assumptions; industry research; management Q&A. Five documents maximum — more dilutes the context window.
Ask Claude to reconcile revenue assumptions between the CIM and the model. If it reasons across both without prompting, the Project is configured correctly.
Replace documents as they are revised. A live Project should be a living deal room, not a static archive.
What This Unlocks in a Live Mandate
With a properly configured Project, the workflow shift is material. Instead of re-explaining context, you ask operational questions immediately: “Draft a management presentation section on revenue quality given the recurring vs. non-recurring split in the CIM.” Claude already knows the CIM, the sector, and your format preferences.
Common Setup Mistakes
More documents does not equal better output. Upload only what Claude needs to reason across. Five documents maximum.
The highest-leverage setup step and the most commonly skipped. Without it, Claude has no context on your role, deal type, or preferences.
One Project per deal. Mixing mandates produces confused cross-referencing — Claude pulls context from the wrong engagement.
The value is synthesis, not storage. Cross-document reasoning in real time is the core advantage. Force the synthesis.
Replace documents as they are revised. A Project with a six-month-old CIM and current management accounts produces inconsistent analysis.
Setup Checklist
Create a new Project named after the deal
Upload the target annual report or 10-K
Upload the CIM or information memorandum
Upload financial model assumptions
Upload relevant industry research
Write Project instructions: role, deal type, output format
Test with one cross-document analytical question
Confirm Claude reasons across documents simultaneously
Shares what I actually use in live deal workflows — financial modelling, valuation, pitch decks, CIMs, and deal support for PE/VC and boutique IB firms.
Interested in working together?
BH Advisory advises mid-market companies on M&A, capital raises, and valuations across Europe.
Discuss a mandate →