M&A strategy for acquiring companies or being acquired. Use when evaluating acquisitions, preparing to be acquired, conducting due diligence, planning integration, or negotiating deal terms (valuation, LOI, earnout, deal structure).
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
M&A strategy for acquiring companies or being acquired. Use when evaluating acquisitions, preparing to be acquired, conducting due diligence, planning integration, or negotiating deal terms (valuation, LOI, earnout, deal structure).
license
MIT + Commons Clause
metadata
{"version":"2.0.0","author":"borghei","category":"c-level","domain":"ma-strategy","updated":"2026-03-09T00:00:00.000Z","frameworks":["acquisition-playbook","due-diligence-framework","valuation-methods","integration-100-day","being-acquired-playbook","deal-structure"],"triggers":["M&A","merger","acquisition","acquire","acqui-hire","due diligence","valuation","LOI","letter of intent","term sheet","earnout","integration","deal structure","buy a company","being acquired","selling the company","exit strategy","data room"]}
M&A Playbook
Frameworks for both sides of M&A: acquiring companies and being acquired. Every M&A decision starts with strategic rationale -- without it, you are buying problems.
Keywords
M&A, mergers and acquisitions, due diligence, acquisition, acqui-hire, integration, deal structure, valuation, LOI, term sheet, earnout, data room, strategic rationale, post-merger integration, buyer, seller, exit
Clarify First
Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Which side of the deal (acquiring vs. being acquired) — the entire playbook, checklists, and red flags differ by side
Which deliverable is needed (strategic rationale, due diligence, valuation, deal structure, 100-day integration, or sell-side prep) — each has its own framework
What you are really buying or selling (talent, technology, customers, or market access) — drives the rationale test, the buy-vs-build call, and where DD focuses
The target's core financials (ARR, growth rate, NRR, customer concentration) — valuation multiples and adjustment factors are keyed to these
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Acquiring: Decision Framework
Strategic Rationale Decision Tree
START: Acquisition opportunity identified
|
v
[What are you really buying?]
|
+-- TALENT (acqui-hire)
| Cost: $1-3M per key engineer
| Timeline: 1-3 months
| Risk: Key people leave after lockup
|
+-- TECHNOLOGY (product/IP)
| Cost: Revenue multiple or technology valuation
| Timeline: 3-6 months
| Risk: Technology doesn't integrate, team leaves
|
+-- CUSTOMERS (market share)
| Cost: Revenue multiple (higher for sticky customers)
| Timeline: 3-6 months
| Risk: Customers churn during transition
|
+-- MARKET ACCESS (geographic or vertical)
Cost: Strategic premium
Timeline: 6-12 months
Risk: Market assumptions wrong, cultural clash
For ALL types, ask:
"Can we build this faster and cheaper?" If YES --> Don't acquire.
"Is integration complexity worth the shortcut?" If NO --> Don't acquire.
Buy vs. Build Analysis
Factor
Buy
Build
Time to market
Fast (months)
Slow (years)
Cost
Higher upfront, uncertain total
Lower upfront, predictable
Risk
Integration risk, culture clash, key person departure
Execution risk, market timing
Control
Lower (inheriting systems and culture)
Higher (building from scratch)
Team
Get experienced team immediately
Build team to your culture
Decision rule: Buy when time-to-market matters more than cost. Build when control and culture matter more than speed.
Technical due diligence, architecture assessment, integration plan
CHRO (chro-advisor)
People DD, retention planning, culture assessment
COO (coo-advisor)
Integration execution, process merge, operational DD
CPO (cpo-advisor)
Product roadmap impact, customer overlap analysis
CISO (ciso-advisor)
Security posture assessment, compliance DD
Culture Architect (culture-architect)
Culture clash detection, integration culture plan
Output Artifacts
Request
Deliverable
"Should we acquire [company]?"
Strategic rationale assessment with buy vs. build analysis
"Run due diligence on [target]"
Due diligence checklist by domain with priority matrix
"Value this acquisition"
Valuation analysis using multiple methods
"Structure this deal"
Deal term recommendations with negotiation strategy
"Plan the integration"
100-day integration plan with owners and milestones
"Prepare to be acquired"
Readiness assessment + 6-month preparation plan
"Build the data room"
Complete data room checklist with document list
Troubleshooting
Problem
Likely Cause
Resolution
Due diligence keeps surfacing new issues after expected completion
DD scope not defined upfront; no priority matrix followed
Use the Priority Matrix strictly: deal-breakers in Week 1-2, valuation impact in Week 2-4; new findings after Week 4 go to post-close optimization
Key employees leaving within 6 months of acquisition
Retention agreements insufficient or culture integration failed
Structure retention bonuses with 24-month cliff; conduct Day 1 welcome meetings; include acquired team in integration decisions
Synergy targets missed at 100-day mark
Synergies were aspirational projections, not auditable targets
Require each synergy to have a specific metric, owner, and measurement method before deal close; track quarterly
Integration stalls with no clear ownership
No Integration Management Office (IMO) or named integration lead
Appoint dedicated integration lead from Day 0; establish IMO with cross-functional representatives and weekly cadence
Earnout disputes destroying the relationship
Metrics not clearly defined or seller lacks control over outcomes
Define earnout metrics that are measurable, auditable, and within seller's meaningful control; include dispute resolution mechanism
Valuation gap between buyer and seller too large to bridge
Different methodologies or growth assumptions
Use multiple valuation methods and present range; bridge with earnout structure tied to the gap assumptions
Post-acquisition customer churn spike
Customer communication delayed or inadequate; service disruption during integration
Execute customer communication on Day 1; maintain service continuity as Phase 1 priority; assign dedicated CS contact
Success Criteria
Strategic rationale articulated in one paragraph before any DD begins; "buy vs. build" analysis completed with clear justification
Due diligence completed within 8-week timeline with all Priority 1 items cleared by Week 2
Integration plan documented before deal close, not after, with named owners for every workstream
Day 1 checklist 100% executed: CEO welcome, customer communication, key person meetings, systems access, reporting structure
100-day integration milestones met: 90%+ key person retention, zero customer churn attributable to integration, systems integrated per plan
Synergy targets tracked quarterly with variance < 15% from projections
Data room (if selling) complete and organized 30 days before process begins
Scope & Limitations
In scope: Strategic rationale assessment, buy vs. build analysis, due diligence frameworks (financial, technical, legal, people, market, product, security), valuation methodologies, deal structure negotiation, integration planning and execution, preparation for being acquired, data room construction
Out of scope: Legal document drafting (use M&A legal counsel); tax structure optimization (use tax advisors); regulatory antitrust filings (use specialized counsel); investment banking services (engage M&A advisor for process management)
Limitation: Valuation multiples are market-dependent and change with conditions; ranges provided are indicative benchmarks, not appraisals
Limitation: Framework optimized for technology company M&A (SaaS, software); manufacturing, retail, and regulated industry M&A have additional complexities
Limitation: Integration success depends heavily on cultural compatibility, which is difficult to assess fully during DD
Integration Points
Skill
Integration
Data Flow
ceo-advisor
M&A is a CEO strategic decision requiring board alignment
CEO strategy → M&A strategic rationale
cfo-advisor
Valuation, deal structure, financial DD, and financing
M&A financials → CFO valuation model
cto-advisor
Technical DD, architecture assessment, integration plan
M&A tech assessment → CTO integration roadmap
chro-advisor
People DD, retention planning, culture assessment
M&A people risks → CHRO retention strategy
coo-advisor
Integration execution, process merge, operational DD
M&A integration plan → COO execution
culture-architect
Culture clash detection and integration culture plan
