Skip to content This library is free, offered as dana. If it helps your work, donate here →

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

Deal thesis statement generator

Converts raw inputs about an acquisition or investment target into a crisp, defensible deal thesis statement — one tight paragraph plus supporting structure suitable for internal memos and executive briefings. Use when…

download .md

Purpose

Transform scattered target information — strategic context, financial profile, market position — into a single, defensible deal thesis paragraph that survives executive scrutiny. Solves the recurring corp dev problem of staring at a deal model and a data room without a clear, repeatable way to articulate why this deal, why now, and why us.

When to Use

Invoke this skill when the user asks to:

  • Draft the strategic rationale section of a deal screening or IC memo
  • Write a deal thesis or investment thesis for an acquisition target
  • Summarize why a target is worth pursuing for an executive sponsor or board
  • Pressure-test a rough deal rationale into a tighter, more defensible statement
  • Prepare talking points for a go/no-go decision on a potential transaction
  • Compare the strategic logic of multiple targets in a pipeline review

Inputs Required

Before starting, collect:

  • Target description: What the company does, size, geography, ownership/status
  • Strategic context: Why the acquirer is looking — the gap, capability, or market this addresses
  • Deal rationale type: Scale / Scope (capability or geographic expansion) / Vertical integration / Talent (acqui-hire) / Defensive / Financial
  • Financial profile: Revenue, growth rate, margin profile, and any known multiple or asking range
  • Integration intent: Bolt-on, platform, standalone, or full absorption
  • Key risks or unknowns: The 1–3 things that could break the deal
  • Audience: Internal screening, IC, executive sponsor, or board

If deal rationale type or integration intent is missing, infer the most likely fit from the target and strategic context, and flag the assumption explicitly.

Instructions

Step 1: Classify the Deal Logic

Map the rationale to one dominant archetype — every strong thesis leads with one, not five:

  • Scale: Same business, more of it. Thesis centers on cost synergies, market share, pricing power.
  • Scope (capability/geographic): New capability, product, or market. Thesis centers on revenue synergies and time-to-capability vs. build.
  • Vertical integration: Control over supply chain, distribution, or margin capture. Thesis centers on margin and strategic control.
  • Talent / acqui-hire: People and IP are the asset. Thesis centers on team, technology, and speed.
  • Defensive: Deny a competitor or protect a position. Thesis centers on the cost of not acting.
  • Financial: Multiple arbitrage, cash flow, or platform for future roll-up. Thesis centers on returns and re-rating potential.

Name the dominant logic. Note any secondary logic in one phrase — but do not let it dilute the lead.

Step 2: Establish the "Why Now"

A thesis without timing urgency reads as optional. Identify the trigger from one of:

  • Market window (consolidation underway, regulatory shift, tech inflection)
  • Target availability (founder exit, distressed seller, finite process)
  • Acquirer readiness (balance sheet capacity, strategic mandate, capability gap now acute)
  • Competitive pressure (a rival is circling or has already moved)

State the "why now" in one sentence that a skeptical executive can't easily dismiss.

Step 3: Quantify the Value Logic

Tie the strategic story to numbers without building a model:

  • For revenue synergies: name the cross-sell, new market, or product attach in directional terms (e.g., "access to ~X mid-market accounts")
  • For cost synergies: name the overlap source (overlapping G&A, duplicate infrastructure, procurement scale)
  • For financial returns: reference the entry multiple relative to growth/margin and the path to value (multiple expansion, deleveraging, margin improvement)

Use the financial profile provided. Where a number is unknown, use a directional placeholder framed as an assumption ("assuming low-double-digit revenue growth sustains") — never a bracket placeholder.

Step 4: Name the Critical Risk Honestly

A thesis that hides risk loses credibility. Surface the single most material risk and a one-line view on whether it is diligenceable, mitigable, or structural. This is what separates a thesis from a pitch.

Step 5: Compose the Thesis Statement

Write the core thesis as one paragraph (90–130 words) following this internal logic:

  1. What we're acquiring (one clause — target and what it is)
  2. The strategic gap it closes (the "why us / why this")
  3. The value mechanism (how value is created — synergy, capability, returns)
  4. The timing (why now)
  5. The honest caveat (the risk, stated with confidence, not hedged)

The paragraph must be readable aloud in one breath of executive attention — declarative, specific, no throat-clearing.

Step 6: Add Supporting Structure

Beneath the paragraph, provide:

  • Thesis in one line: A single sentence (≤25 words) for a pipeline tracker or subject line
  • Three pillars: The three supporting points that hold the thesis up, one line each
  • The watch item: The one risk that, if it breaks, breaks the deal

Output Format

  • Structure: Lead thesis paragraph, then a structured support block
  • Length: 300–450 words total (thesis paragraph 90–130 words)
  • Format: One prose paragraph followed by a labeled support block (one-liner, three pillars as a short list, watch item)
  • Sections: Deal Thesis (paragraph) → Thesis in One Line → Three Pillars → Watch Item → Assumptions Flagged
  • Tone: Corp dev voice — declarative, financially literate, unsentimental. No hype adjectives, no hedging filler. Writes the way a deal lead talks to an IC.

Quality Checklist

Before delivering output, verify:

  • [ ] The thesis paragraph is 90–130 words and reads as a single coherent argument
  • [ ] One dominant deal logic is named — the thesis does not try to be three things at once
  • [ ] A specific "why now" is present and is not a generic statement of market growth
  • [ ] At least one number or directional financial anchor appears, tied to the value mechanism
  • [ ] The most material risk is stated openly, not buried or omitted
  • [ ] The one-line version is ≤25 words and could stand alone in a tracker
  • [ ] Any inferred inputs (deal type, integration intent) are explicitly flagged as assumptions

Notes

  • The most common failure is a thesis that lists every reason to do the deal — strength comes from leading with the one reason that matters and subordinating the rest.
  • If the user provides a financial model but no strategic context, push back: a thesis grounded only in returns is a financial bet, not a strategic one, and an IC will ask "why us."
  • For board or executive-sponsor audiences, lead the paragraph with the strategic gap; for IC screening, lead with the deal logic and value mechanism.
  • The "watch item" is deliberately singular — corp dev memos drown in risk lists, and naming the one deal-breaker forces clarity about whether to proceed.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

  • ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
  • <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

  1. Drag this file into a new chat, or copy and paste its contents
  2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills