Purpose
Produce a structured, defensible synergy estimate for a proposed transaction — breaking total synergy potential into cost and revenue categories, each with a dollar range, confidence level, time-to-realize, and cost-to-achieve — so corporate development teams can pressure-test the deal thesis and feed credible numbers into valuation and the investment committee memo.
When to Use
Invoke this skill when the user asks to:
- Estimate synergies for a proposed acquisition or merger
- Build a synergy case for an investment committee or board deck
- Validate or challenge a banker's or target's synergy claims
- Quantify cost takeout and revenue cross-sell from combining two businesses
- Model how much synergy value can be added to a target's valuation
- Compare synergy potential across multiple acquisition candidates
Inputs Required
Before starting, collect:
- Acquirer profile: Revenue, EBITDA, employee count, primary cost categories, market/geography
- Target profile: Revenue, EBITDA, employee count, primary cost categories, market/geography
- Strategic rationale: Why this deal — consolidation, market entry, capability acquisition, scale
- Functional overlap: Where the two organizations duplicate (sales, G&A, ops, facilities, tech stack)
- Revenue interaction: Product/customer overlap, cross-sell potential, channel access either side gains
- Integration constraints: Regulatory, contractual, cultural, or geographic limits on combining operations
- Deal size / purchase price: Enterprise value or expected multiple, if available
If EBITDA or detailed cost breakdowns are missing, estimate from revenue using industry-standard ratios and flag every assumption explicitly.
Instructions
Step 1: Establish the Synergy Baseline
Anchor the analysis before estimating anything.
- Compute combined revenue, combined EBITDA, and combined headcount as the denominator for benchmark ratios.
- Identify which business is the "platform" (operating model that survives) vs. the absorbed entity — synergies are extracted against the absorbed side's cost base.
- State the realism frame: cost synergies are 70–90% achievable when well-managed; revenue synergies are historically far softer (typically 30–60% of claimed). Apply this skepticism throughout.
- Note overlap intensity: high overlap (same market, same functions) drives larger cost synergies; low overlap drives larger revenue synergies but lower cost takeout.
Step 2: Estimate Cost Synergies by Category
For each category, produce a low–high dollar range, the % of relevant cost base it represents, a confidence level (High / Medium / Low), and time-to-realize (0–12mo / 12–24mo / 24mo+).
Category 1 — Procurement & Vendor Consolidation Combined purchasing power on shared inputs, software licenses, freight, and raw materials.
- Benchmark: 3–8% reduction on combined addressable spend (not total spend).
- Confidence: typically High — contractual, verifiable, fast.
- Time-to-realize: 6–18 months as contracts renew.
Category 2 — Headcount & Organizational Overlap Eliminating duplicate roles, primarily in G&A, finance, HR, IT, and redundant management layers.
- Benchmark: 15–30% of the absorbed entity's overlapping function headcount; rarely touches frontline revenue-generating roles.
- Confidence: High for back-office, Medium for field/ops (regulatory and morale risk).
- Time-to-realize: 0–12 months, but net of severance.
Category 3 — Facilities & Footprint Consolidating offices, plants, warehouses, and distribution centers in overlapping geographies.
- Benchmark: rationalize 10–25% of combined facility cost where geographic overlap exists.
- Confidence: Medium — lease terms, exit costs, and operational continuity constrain timing.
- Time-to-realize: 12–36 months as leases expire.
Category 4 — Technology & Systems Retiring duplicate platforms, consolidating ERP/CRM/infrastructure, eliminating redundant licenses.
- Benchmark: 10–20% of combined IT opex after migration, offset by significant one-time integration cost.
- Confidence: Medium — frequently over-promised and under-delivered; migrations slip.
- Time-to-realize: 18–36 months.
Step 3: Estimate Revenue Synergies by Category
Apply heavier discounting here. State each as a low–high range with explicit haircut from the gross potential.
Category 5 — Cross-Sell & Upsell Selling acquirer products into target's customer base and vice versa.
- Method: (relevant customer base) × (realistic attach rate, 5–15%) × (average deal value) × (achievability haircut, 30–50%).
- Confidence: Low to Medium — ramps slowly and depends on sales-force motivation.
- Time-to-realize: 18–48 months.
Category 6 — Channel & Market Access New geographies, distribution channels, or segments one side unlocks for the other.
- Method: size the newly accessible market, apply a conservative penetration assumption over 3 years.
- Confidence: Low — slowest and most uncertain category.
- Time-to-realize: 24–60 months.
Category 7 — Pricing & Bundling Power (include only if market position supports it) Combined entity's ability to improve pricing or bundle offerings; note antitrust sensitivity if relevant.
Step 4: Net the Synergies
- Sum gross annual run-rate synergies (cost + discounted revenue) at the expected (mid) case.
- Subtract one-time costs to achieve: severance, system migration, lease exits, retention bonuses, integration team cost — typically 1.0–2.0× the first-year run-rate synergy.
- Present run-rate synergy net of dis-synergies (revenue leakage, customer churn, attrition of key talent — assume 2–5% revenue dis-synergy on the absorbed entity).
Step 5: Translate to Valuation Impact
- Apply the deal's EBITDA multiple to the expected net run-rate synergy to express synergy value as enterprise value added.
- State how much of the purchase price premium is justified by synergies vs. requires belief in revenue upside.
Output Format
- Structure: Baseline summary → cost synergy table (4 categories) → revenue synergy table (2–3 categories) → net synergy bridge → valuation impact → confidence summary
- Length: 900–1,300 words plus tables
- Format: Two structured tables (cost and revenue) with columns for Category, Low, High, Expected, Confidence, Time-to-Realize; narrative for baseline, netting, and valuation
- Sections: Synergy Baseline → Cost Synergies → Revenue Synergies → Costs to Achieve & Dis-Synergies → Net Synergy Summary → Valuation Impact → Key Assumptions & Risks
- Tone: M&A analyst — quantitative, conservative, assumption-explicit; no advocacy, no rounding toward the deal
Quality Checklist
Before delivering output, verify:
- [ ] Every synergy category has a low–high range, an expected value, a confidence level, and a time-to-realize estimate
- [ ] Revenue synergies are discounted more heavily than cost synergies — never presented at gross potential
- [ ] One-time costs to achieve and revenue dis-synergies are subtracted to reach a net figure
- [ ] Every estimate cites the cost/revenue base and ratio it was derived from — no unsourced dollar figures
- [ ] The net run-rate synergy is translated into enterprise value using the deal multiple
- [ ] All assumptions made due to missing inputs are flagged explicitly in the Key Assumptions section
Notes
- The most common failure mode is over-crediting revenue synergies — when in doubt, haircut harder and put the burden of proof on the deal team.
- Cost synergies that survive scrutiny are procurement and back-office headcount; treat facilities and tech consolidation timelines with built-in slippage.
- If the purchase premium can only be justified by aggressive revenue synergies, say so plainly — that is the single most decision-relevant finding for a CFO or IC.
- Present three cases (conservative / expected / optimistic) only if the user requests scenario analysis; otherwise lead with the expected case and show ranges.
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:
- Drag this file into a new chat, or copy and paste its contents
- 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