The deal flow is real. The thesis is sharp. The board presentation is in 48 hours. You have 200 pages of CIM, 40 pages of management presentation, three years of financials, and a half-drafted investment memo open in a Google Doc. The analytical judgment is done — the question is whether you can get it into a document that the IC can actually read before Thursday morning. That's the gap strategy and corp dev work lives in: not "we don't know what we think" but "we haven't written it clearly yet."
That gap — the investment memo, the board narrative, the integration FAQ, the competitive brief, the outreach rationale — is where Claude is useful. Not because it replaces the analytical work. Because it handles the blank page while you focus on the work that actually requires your judgment: the deal thesis, the synergy model, the strategic recommendation.
Before the use cases: Claude cannot access your VDR. Not Datasite, Intralinks, Firmex, or any equivalent platform. It cannot access financial databases — not PitchBook, Capital IQ, Bloomberg, or FactSet. It cannot pull your CRM, your internal deal pipeline, your historical deal history, your company's financials, or any proprietary data source. It does not know your company's strategic posture unless you tell it. It will not fabricate valuation multiples, synergy estimates, EV/EBITDA comps, or financial projections — and if you ask it to, it will push back. Claude is strictly a drafting and structuring tool. You bring the data, the thesis, and the domain judgment. Claude handles the blank page and the prose.
That constraint is actually the right discipline. The fabricated multiple that makes it into an IC memo is a career event. The invented synergy estimate that gets into a board presentation is worse. Claude's conservatism on financial figures is a feature, not a limitation — it forces the right accountability structure: analyst-sourced data in, structured narrative out, nothing invented. Every use case below reinforces that boundary explicitly.
What Claude Can Do for Strategy and Corp Dev Professionals
1. Investment Memo / Deal Rationale Narrative
The investment memo is the document where "we've done the work" becomes "the IC can make a decision." The analytical judgment is complete — strategic rationale, value drivers, risk factors — but converting three weeks of diligence and dozens of data points into a clean, decision-ready document takes time the deal timeline doesn't always provide.
Claude cannot access your VDR, financial models, or any data room. Paste in the CIM executive summary, your deal overview bullets, your strategic rationale notes, and your preliminary thesis. That's the input. The structured Investment Memo is the output.
I need to draft an Investment Memo for a potential acquisition/investment. Here's my input:
Target company: [company name, description, sector]
CIM executive summary: [paste the relevant section from the CIM — flag that this is CIM-sourced]
Deal overview: [deal structure, estimated size/range, timeline — use only figures I provide, no estimates]
Strategic rationale notes: [your bullet points — why this target, why now, why us as acquirer/investor]
Preliminary thesis: [2–3 sentences on the core investment logic]
Key value drivers: [your notes on what drives value — products, customers, technology, market position, team]
Key risks: [your honest risk list — do not soften these; list them as you see them]
Preliminary financial context: [any figures from the CIM or provided by the target — flag the source of each number]
Write an Investment Memo with the following sections:
- Executive Summary: 1 paragraph, decision-first — state the recommendation and the core rationale before any supporting detail
- Strategic Rationale: why this target, why now, why us as acquirer/investor — framed as a narrative argument, not a bullet list
- Business Overview: description of the target, sourced from the CIM section I provided — flag all content as CIM-sourced
- Key Value Drivers: the 3–5 factors that drive the investment thesis — narrative, not bullets
- Key Risks: the honest risk picture — do not soften or hedge these; a balanced memo is a credible memo
- Preliminary Financial Context: [PLACEHOLDER — note that all projections and valuation must be supplied by the analyst and verified against the data room; do not estimate any figure I haven't provided]
Do not invent financial figures. Any number in the output must come from what I pasted in. Flag any section where my notes are insufficient to write a complete draft rather than approximating.
The "do not invent financial figures" instruction is the most important one. Paste it verbatim. The placeholder financial section is intentional — it creates a visible marker in the draft that forces analyst review before this goes anywhere near an investment committee. A memo that looks complete but has invented context in the financial section is more dangerous than an obvious placeholder.
2. Competitive Landscape and Market Context Brief
The competitive brief is what turns a collection of earnings call excerpts, press releases, and analyst notes into a coherent market picture. The raw material is usually abundant — the synthesis is what takes time. Where is the market consolidating? Who is gaining share and why? What does the competitive dynamic mean for the deal thesis?
Claude cannot access Capital IQ, PitchBook, Bloomberg, or any licensed database. Paste in competitor summaries from public sources — earnings call excerpts, 10-K strategic risk factors, press releases, your own research notes. All data must come from what you provide.
I need to write a competitive landscape and market context brief for [market/sector name]. Here's my input:
Market description: [brief description of the market — size (if known and sourced), key segments, relevant dynamics]
Competitor summaries: [paste your notes on each key player — sourced from public filings, earnings calls, press releases, your research. Include the source for each data point.]
Earnings call excerpts: [paste relevant sections — flag the company and quarter]
Industry dynamics you've observed: [consolidation trends, technology shifts, pricing dynamics, M&A activity — your analyst view, sourced where possible]
Deal thesis context: [how does this market picture connect to the deal you're evaluating?]
Write a competitive landscape brief including:
- Market Overview: 2–3 paragraph narrative — not bullet points; synthesize the market picture, the key dynamics, and where it's heading
- Key Players Summary: structured table — Company / Positioning / Revenue (analyst-sourced, flag if estimated) / Key Differentiator — note explicitly that these are analyst-sourced, not independently verified
- Competitive Dynamics: where is the market consolidating, fragmenting, or shifting — and what's driving it
- Implications for [company/deal thesis]: 1–2 paragraphs connecting the competitive picture to the strategic question at hand
Do not estimate revenue or market share for any company not included in my notes. Do not access Capital IQ, PitchBook, Bloomberg, or any database — use only what I've provided. Flag any company or claim where my notes are insufficient to make a confident assertion.
The explicit "do not estimate revenue or market share" instruction is what prevents the output from looking authoritative when it's guessing. A competitive brief with clearly-flagged sourcing is more useful than one with confident numbers of unclear origin. Business analysts who build market context for internal initiatives use the same approach — the sourcing discipline is identical.
3. Board Strategy Presentation Narrative
The hardest part of the board presentation isn't the analysis. The hard part is the narrative architecture: the assertion-first slide titles that make a clear argument, the transitions that make one slide feel like the inevitable consequence of the previous one, the "spine" — the single argument the whole presentation makes that you could read as a standalone paragraph.
Most strategy decks are a collection of slides that could appear in any order. The board presentation that changes a decision is one where every slide has a clear point and the sequence has a clear logic. That narrative architecture is what Claude produces.
Claude cannot access your financial model, your board materials portal, or any internal data system. Paste in your strategy framework, decision options, supporting data bullets, and recommended path.
I need to build the narrative architecture for a board strategy presentation. Here's my input:
Presentation context: [what decision or update is this presentation for — strategic plan review, M&A recommendation, market entry decision, annual strategy update?]
Key question the board needs to answer or understand: [state this precisely — "Should we pursue [acquisition]?" or "This is our three-year strategic plan"]
Strategy framework / analytical structure: [paste your framework — market opportunity, competitive position, strategic options, recommended path]
Decision options under consideration: [Option A, Option B, Option C — with the key trade-offs for each]
Supporting data bullets: [paste your data points — source each one; do not invent data to fill gaps]
Recommended path: [your recommendation and the core rationale]
Write a board presentation narrative architecture including:
- Presentation spine: 2–3 sentences that state the single argument the full presentation makes — readable as a standalone summary; this is the logic test for the whole deck
- Slide-by-slide storyboard: for each slide, provide:
- Assertion-first title: a complete sentence that states the point of the slide — not a topic label ("Revenue is growing" not "Revenue Update")
- One-sentence "so what": why this slide matters to the argument
- Supporting points: 2–4 bullet points supporting the slide's assertion
- Transition sentence: the one sentence that connects this slide to the next one
- Recommended narrative flow: note if any slides should be reordered for stronger logic
Note: the strategic recommendation is mine to own. Claude produces the narrative structure; the CFO and CEO approve the strategic direction. This is the architecture the deck is built on, not the final board output.
The spine is the single most useful output here. If the spine paragraph doesn't hold together as a standalone argument, the presentation has a logic problem — and it's far easier to fix that in the storyboard than after 40 slides have been built. Management consultants use the same storyboard approach for client presentations; the discipline is the same, the audience is internal.
4. Integration Planning Communication
Day 1 of an integration is the moment where a deal that looked good on paper meets the people it affects. The communication failure mode isn't usually factual inaccuracy — it's the FAQ that doesn't answer the question employees are actually asking, the leadership message that acknowledges uncertainty in a way that creates more anxiety than it resolves, the communication plan that's a table of messages nobody reads.
The integration communication problem is a writing and structure problem. The hard content decisions are yours. Claude handles the drafting.
Claude cannot access your HR systems, HRIS data, org charts, benefits systems, or any employee data. Paste in the integration workstream overview, timeline, key decisions, and stakeholder structure. Role-specific details must come from you and be reviewed by HR and legal before any employee communication is issued.
I need to draft integration planning communications for [acquisition/merger name]. Here's my input:
Deal overview: [acquiring company, target company, deal type, close date]
Integration workstream overview: [key workstreams — HR/People, Finance, IT, Operations, Sales, etc. — and the current status of each]
Timeline: [key milestones — close date, Day 1 activities, 30/60/90-day targets]
Key decisions made: [what's been decided — reporting structures, office locations, systems, roles that are confirmed]
Key decisions still open: [what hasn't been decided yet — be honest about this; employees will ask]
Stakeholder list: [functional areas and leadership involved — no personal names or personal data]
Write the following integration communications:
- Employee FAQ: plain language — What's changing, What's not changing, What happens to [each major function], What the timeline is, Who to contact with questions. Write for an employee who has no context on the deal rationale — assume they saw the announcement and have concerns.
- Leadership communication plan: a structured table — Audience / Key Message / Channel / Timing / Message Owner — covering the first 30 days
- Day 1 leadership message draft: 3–4 paragraphs. Tone: confident and clear, acknowledges what we don't yet know without being vague about it, focuses on what employees can count on. Avoid platitudes ("excited for this next chapter") — they erode trust. State concrete facts where available.
Hard constraint: do not reference specific individuals, compensation details, benefits specifics, or role eliminations — those details must be supplied by HR and reviewed by legal before any communication is issued. Flag any section where I need to supply more detail before this is ready for review.
The "acknowledge uncertainty without being vague" instruction is the hardest thing to execute in a Day 1 message. "We don't yet know the final org structure for the combined sales team; we will communicate that by [date]" is the version that builds trust. "We're working through the details" is the version that makes everyone update their LinkedIn. Claude produces a first draft; the final message requires HR and legal review before distribution.
5. Deal Sourcing and Outreach Narrative
The acquisition/partnership outreach that gets a meeting is not a cold email template. It's a thoughtful, specific articulation of why this conversation makes sense for both sides — why this target, why now, why the conversation is worth an hour of the founder or CEO's time. That framing requires research and strategic judgment. Claude handles the prose once you've done the work.
Claude knows nothing about the specific target company except what you paste in. Any reference to their business, financials, or strategy must come from your research. Claude produces the narrative; the strategic judgment is yours.
I need to draft outreach and sourcing materials for a potential acquisition/partnership with [target company name]. Here's my input:
Our acquisition/partnership thesis: [describe the strategic rationale — why we're pursuing this type of target, what capability or market position we're looking for]
Target company description: [what they do, their approximate scale, their market position — sourced from your research; note the source of each fact]
Strategic fit rationale: [specifically why this target fits the thesis — be concrete, not generic]
What we bring to the conversation: [what value or synergy we can articulate from their perspective — what's in it for them]
Initial management call context: [is this a cold outreach, a warm introduction, or a follow-up to a prior conversation?]
Write the following sourcing materials:
- Outreach narrative: 3–4 paragraphs — not a cold email template, but a strategic framing of why this conversation makes sense for both sides. Specific to this target; not generic. Tone: peer-to-peer, not sales-oriented.
- Internal deal pipeline summary: 1 paragraph for pipeline documentation — describes the target, the thesis, and the rationale for pursuit. Written for an internal audience familiar with the acquisition strategy.
- 5 initial management call questions: specific to this target based on the context I've provided; focused on the strategic questions that matter for the thesis, not generic diligence questions
Hard constraint: any reference to the target's business, financials, or strategy must come from the research I've provided. Do not estimate figures or characterize their business beyond what I've given you.
The distinction between "cold email template" and "outreach narrative" is worth enforcing in the prompt. A template is generic and feels like it. A narrative is specific enough that the recipient can tell you actually know something about their business. That specificity comes from your research — Claude structures it into prose.
6. Post-Merger Integration Retrospective and Lessons-Learned Document
The integration retrospective is the document nobody makes time to write and the one that would most improve the next deal. The lessons are in your head, in stakeholder feedback you collected, in outcome vs. plan data that's sitting in a spreadsheet. The blocker is converting all of that into a document that's actually usable for the next integration team.
Claude cannot access your HR systems, integration management tools, financial systems, or any deal data. Paste in integration milestones, what went well and didn't, stakeholder feedback notes, and outcome vs. plan data. All metric data must come from you.
I need to write a post-merger integration retrospective and lessons-learned document for [deal name]. Here's my input:
Deal overview: [acquiring company, target company, deal type, close date, deal rationale summary]
Integration timeline: [key milestones from close through integration completion — dates and what happened]
What went well: [your notes — specific, theme-based observations from the integration]
What didn't go well: [honest assessment — specific issues, not generalities. Frame as learning, not blame.]
Stakeholder feedback: [paste your notes from feedback sessions, surveys, or conversations — anonymize individual names]
Outcome vs. plan: [for each key integration objective, what was the target and what was the actual outcome — provide the data; do not estimate]
Write a post-merger integration retrospective including:
- Executive Summary: deal overview, integration timeline, high-level outcome vs. objectives — 3–4 paragraphs
- What Went Well: theme-based, not a list — group observations into 3–4 themes with narrative explanation. What drove these outcomes?
- What We'd Do Differently: framed as institutional learning, not a list of failures. For each area, describe what we'd change and why.
- Playbook Updates: 3–5 specific, actionable changes to how we'd run the next integration — concrete enough that the next integration team could actually apply them
- Metric Summary: table — Integration Objective / Target / Actual / Delta / Notes — note explicitly that all data in this table must be supplied by me; do not estimate any figure
This document is internal. The tone should be honest and direct. Its purpose is to improve the next deal, not to document that this one went well.
The "framed as institutional learning, not blame" instruction matters for stakeholder comfort with the document. The retrospective that gets used is the one that's honest without being politically toxic. Claude structures the content you provide into a format that actually improves the playbook — which is the only reason to write it.
Why Claude Over ChatGPT for Strategy and Corp Dev Work
100K+ context window. Paste the full CIM executive summary, the management presentation, your preliminary thesis, and prior deal memos into a single session. Deal work is context-intensive — the CIM alone can run 80–100 pages, and a well-structured investment memo draws on all of it. ChatGPT drops context mid-analysis; Claude holds the full picture. Finance professionals doing internal reporting work have the same problem — the context window is what makes the difference between a tool that helps and one that frustrates.
Conservative and attribution-honest. Claude will not fabricate valuation multiples, synergy estimates, EV/EBITDA comps, or market share numbers. In deal work specifically, a fabricated number that finds its way into an IC memo or a board presentation is not a minor error — it's a credibility event. Claude's tendency to push back on requests for invented figures, and to flag where your notes are insufficient rather than fill the gap with plausible-sounding content, is the behavior you want when you're producing documents that go to investment committees and boards.
Projects per deal. Use Claude's Projects feature to keep one context window per deal thread — from initial thesis articulation through IC memo through integration retrospective. Add your deal thesis notes, prior memos, and company context to the Project at the start. Every session in that Project starts with the full deal context loaded. That's the right unit of work for corp dev: one deal, one project, accumulating context across the full deal lifecycle.
Structured output fidelity. Complex multi-section documents — investment memos, integration FAQs, board narratives — stay structured. Numbered sections stay numbered. Tables stay tables. For documents that go through multiple rounds of internal review and may end up in formatted templates, structural consistency matters. For more context on the direct comparison, see Claude vs ChatGPT.
4 Practical Tips for Strategy and Corp Dev Professionals
One Project per deal or strategic initiative. The context builds from the first thesis articulation through the IC memo through the integration retrospective. Start the Project when the deal enters your pipeline; add your thesis, CIM notes, and strategic rationale as they develop. When you come back to write the next document in the deal lifecycle, the full context is there.
Thesis in / narrative out. The discipline is: you supply the analytical judgment, Claude handles the blank page. Paste your thesis bullets, your risk list, your value driver notes — and Claude converts them into structured prose. Never let the tool do the analytical work. The thesis, the strategic recommendation, and the numbers are yours to own.
Specify the reader explicitly. "Write this investment memo for a CFO who has no prior context on this deal and will read it in 10 minutes on a plane" produces a materially different document than "Write this for the integration team that has been in every workstream kickoff." Executive assistants who prep briefing docs for executives use the same principle — reader specification changes register, assumed vocabulary, and what gets explained vs. assumed.
Use it for the first 80% of the draft, not the final 20%. The hardest part of corp dev writing is the first complete draft — the one where the structure is right, the argument is readable, and you can actually see what needs to change. Claude gets you there in 20 minutes. The final 20% — the strategic recommendation, the financial validation, the judgment calls on risk framing — is yours to own. That's the right division of labor. Startup founders doing investor communications use the same framing: narrative draft out of Claude, founder voice and strategic positioning in the final pass.
The Complete Claude Playbook
The prompts above get you started. The Complete Claude Playbook ($27) goes deeper: prompt architecture for the full deal lifecycle, how to build a deal Project that accumulates context from sourcing through integration, templates for each document type above, and the full framework for high-stakes strategic documents that go to investment committees and boards.
If your job is turning analytical judgment into documents that drive decisions — this is the tool that closes the gap between "we know what we think" and "we have a document that says it clearly."