synergy-analysis
Synergy Analysis
Synergy underwriting provides the mathematical and strategic justification for paying an acquisition premium. Cost synergies — headcount rationalization, facility closures, vendor consolidation — are the most reliable forms of value creation, but identifying them requires mapping two complex organizations.
When to Use
- Quantifying cost synergies to justify an acquisition premium
- Mapping organizational overlaps between buyer and target
- Identifying vendor consolidation and contract renegotiation opportunities
- Building a cost-takeout plan for lender validation
- Generating the Synergy and Cost Savings Analysis Report
The /synergy-map Protocol
How It Works
- Ingest the target's employee census, benefits data, and third-party spend
- Compare against the acquirer's operating model and vendor lists
- Identify overlapping functions:
- Duplicate back-office roles (dual ERP teams, redundant HR, overlapping finance)
- Redundant regional sales coverage
- Duplicated vendor relationships (same cloud provider, same audit firm)
- Quantify savings with confidence ratings
- Estimate costs to achieve (severance, lease breaks, migration costs)
Time saved: 15+ hours per synergy model.
Output Format
## Synergy Map — [Target] + [Acquirer]
### Summary
| Category | Identified Run-Rate Savings | Costs to Achieve | Net Year 1 Impact |
|----------|---------------------------|-------------------|-------------------|
| Headcount | $[X]M | $[X]M | $[X]M |
| Third-Party Spend | $[X]M | $[X]M | $[X]M |
| Facilities | $[X]M | $[X]M | $[X]M |
| Technology | $[X]M | $[X]M | $[X]M |
| **Total** | **$[X]M** | **$[X]M** | **$[X]M** |
### Headcount Overlap
| Function | Target FTEs | Acquirer FTEs | Redundant | Savings | Confidence |
|----------|-------------|---------------|-----------|---------|------------|
| Finance & Accounting | [N] | [N] | [N] | $[X]K | High |
| IT Operations | [N] | [N] | [N] | $[X]K | Medium |
| Sales (Regional) | [N] | [N] | [N] | $[X]K | Low |
### Vendor Consolidation
| Vendor/Category | Target Spend | Acquirer Spend | Estimated Saving | Mechanism |
|----------------|-------------|----------------|-----------------|-----------|
| Cloud hosting | $[X]K | $[X]K | $[X]K | Volume renegotiation |
| Audit/Tax | $[X]K | $[X]K | $[X]K | Consolidate to single firm |
### Costs to Achieve
| Item | Estimate | Timing |
|------|----------|--------|
| Severance (redundant FTEs) | $[X]M | Months 1-6 |
| Lease termination penalties | $[X]K | Months 3-9 |
| IT migration costs | $[X]K | Months 1-12 |
| Retention bonuses (key talent) | $[X]K | Months 1-24 |
Synergy and Cost Savings Report
The formal deliverable that moves beyond the mapping to a validated, defended analysis:
| Section | Focus |
|---|---|
| Synergy Thesis & Strategy | Strategic rationale and integration philosophy |
| Headcount & Organizational Overlap | Quantified role-level redundancies |
| Third-Party Spend Rationalization | Vendor pricing leverage and consolidation |
| Technology & Infrastructure | ERP migration, license elimination, real estate |
| Costs to Achieve | One-time expenditures: severance, lease breaks, IT migration |
Operating Guidelines
- Synergies are notoriously overestimated — apply conservative assumptions
- Distinguish between run-rate savings (annual) and one-time gains
- Always include costs to achieve — synergies without execution costs are misleading
- Confidence ratings: High (contractual/observable), Medium (benchmarked), Low (estimated)
- Lenders demand third-party validation — ensure the analysis is independently defensible
- Revenue synergies are speculative and should be separated from cost synergies
- Flag any synergy that depends on retaining key personnel who may have flight risk
Examples
Input: "Estimate synergies from acquiring a 200-person SaaS company."
Quick synergy model output:
| Category | Run-Rate Savings | Costs to Achieve | Net Year-1 |
|---|---|---|---|
| Headcount (G&A overlap) | $8.4M | $3.2M | $5.2M |
| Software/vendor consolidation | $1.8M | $0.3M | $1.5M |
| Facilities (office consolidation) | $0.9M | $0.4M | $0.5M |
| Total | $11.1M | $3.9M | $7.2M |
Confidence: Medium (benchmarked against 12 comparable SaaS acquisitions).
Troubleshooting
| Problem | Cause | Fix |
|---|---|---|
| Synergy estimates rejected by lenders | No third-party validation | Reference comparable transaction benchmarks; show methodology |
| Revenue synergies overstated | Optimism bias | Separate cost and revenue synergies; apply 50% haircut to revenue synergies |
| Costs to achieve underestimated | Missing one-time items | Use M&A database benchmarks for severance ($X per redundant FTE) |
| Model doesn't account for dis-synergies | One-sided analysis | Explicitly model customer churn risk and key-man retention cost |
More from lauraflorentin/skills-marketplace
multi-agent-collaboration
A structural pattern where multiple specialized agents communicate and coordinate to solve a problem that is too complex for a single agent. Use when user asks to "build a multi-agent system", "agents working together", "agent collaboration", or mentions team of agents, distributed agents, or swarm.
21reflection
A recursive pattern where an agent evaluates and critiques its own output to iteratively improve quality and catch errors. Use when user asks to "add self-reflection", "agent introspection", "self-critique", or mentions self-evaluation, meta-cognition, or quality self-assessment.
18human-in-the-loop
A hybrid pattern where the system pauses execution to request human approval, input, or disambiguation before proceeding with critical actions. Use when user asks to "add human approval", "require human review", "human-in-the-loop", or mentions approval workflows, human oversight, or escalation.
16planning
A high-level cognitive pattern where an agent formulates a structured sequence of actions (a plan) before executing any of them, ensuring goal-directed behavior. Use when user asks to "add planning to my agent", "task planning", "agent planning", or mentions plan generation, plan execution, or step-by-step planning.
14parallelization
A concurrency pattern where multiple agent tasks are executed at the same time to speed up processing or gather diverse perspectives. Use when user asks to "run agents in parallel", "parallelize tasks", "concurrent execution", or mentions parallel processing, fan-out, or batch execution.
13routing
A control flow pattern where a central component classifies an input request and directs it to the most appropriate specialized agent or tool. Use when user asks to "route between agents", "agent routing", "task dispatch", or mentions classifier routing, intent detection, or agent selection.
12