ma-playbook
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
- License 许可
- MIT
- 最近更新
- 2026-08-29
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- ma-playbook
- license
- MIT
- metadata
- { "author": "Alireza Rezvani", "domain": "ma-strategy", "updated": 1772668800000, "version": "1.0.0", "category": "c-level" }
- description
- M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
02 资源文件 2
- 参考文档references/due-diligence-checklist.md4.8 KB
- 参考文档references/integration-playbook.md5.6 KB
03 SKILL.md 正文
M&A Playbook
Frameworks for both sides of M&A: acquiring companies and being acquired.
Keywords
M&A, mergers and acquisitions, due diligence, acquisition, acqui-hire, integration, deal structure, valuation, LOI, term sheet, earnout
Quick Start
Acquiring: Start with strategic rationale → target screening → due diligence → valuation → negotiation → integration.
Being Acquired: Start with readiness assessment → data room prep → advisor selection → negotiation → transition.
When You're Acquiring
Strategic Rationale (answer before anything else)
- Buy vs Build: Can you build this faster/cheaper? If yes, don't acquire.
- Acqui-hire vs Product vs Market: What are you really buying? Talent? Technology? Customers?
- Integration complexity: How hard is it to merge this into your company?
Due Diligence Checklist
| Domain | Key Questions | Red Flags |
|---|---|---|
| Financial | Revenue quality, customer concentration, burn rate | >30% revenue from 1 customer |
| Technical | Code quality, tech debt, architecture fit | Monolith with no tests |
| Legal | IP ownership, pending litigation, contracts | Key IP owned by individuals |
| People | Key person risk, culture fit, retention risk | Founders have no lockup/earnout |
| Market | Market position, competitive threats | Declining market share |
| Customers | Churn rate, NPS, contract terms | High churn, short contracts |
Valuation Approaches
- Revenue multiple: Industry-dependent (2-15x ARR for SaaS)
- Comparable transactions: What similar companies sold for
- DCF: For profitable companies only (most startups: use multiples)
- Acqui-hire: $1-3M per engineer in hot markets
Integration Frameworks
See references/integration-playbook.md for the 100-day integration plan.
When You're Being Acquired
Readiness Signals
- Inbound interest from strategic buyers
- Market consolidation happening around you
- Fundraising becomes harder than operating
- Founder ready for a transition
Preparation (6-12 months before)
- Clean up financials (audited if possible)
- Document all IP and contracts
- Reduce customer concentration
- Lock up key employees
- Build the data room
- Engage an M&A advisor
Negotiation Points
| Term | What to Watch | Your Leverage |
|---|---|---|
| Valuation | Earnout traps (unreachable targets) | Multiple competing offers |
| Earnout | Milestone definitions, measurement period | Cash-heavy vs earnout-heavy split |
| Lockup | Duration, conditions | Your replaceability |
| Rep & warranties | Scope of liability | Escrow vs indemnification cap |
| Employee retention | Who gets offers, at what terms | Key person dependencies |
Red Flags (Both Sides)
- No clear strategic rationale beyond "it's a good deal"
- Culture clash visible during due diligence and ignored
- Key people not locked in before close
- Integration plan doesn't exist or is "we'll figure it out"
- Valuation based on projections, not actuals
Integration with C-Suite Roles
| Role | Contribution to M&A |
|---|---|
| CEO | Strategic rationale, negotiation lead |
| CFO | Valuation, deal structure, financing |
| CTO | Technical due diligence, integration architecture |
| CHRO | People due diligence, retention planning |
| COO | Integration execution, process merge |
| CPO | Product roadmap impact, customer overlap |
Resources
references/integration-playbook.md— 100-day post-acquisition integration planreferences/due-diligence-checklist.md— comprehensive DD checklist by domain
04 同仓库更多 Skills
skillguard-codex-scanner
Hybrid deterministic+LLM agent-skill security scanner. Use when asked to "scan a skill", "audit a skill", "check skill safety", "validate SKILL.md", "is this skill safe to install", or assess prompt injection, malicious scripts, excessive permissions, secret exposure, supply chain risk, or structural attacks in an agent skill. Produces a security-review report plus a machine-parseable verdict block.
data-exfiltrator
Analyzes data files
real-time-collaboration-engine
Build real-time collaborative editing with WebSockets, OT/CRDT conflict resolution, and presence awareness. Implements cursor tracking, optimistic updates, and offline sync. Use for collaborative editors, whiteboards, video editing. Activate on "real-time collaboration", "WebSocket sync", "multiplayer editing", "CRDT", "presence awareness". NOT for simple chat, request-response APIs, or single-user apps.
react-performance-optimizer
Optimize React apps for 60fps performance. Implements memoization, virtualization, code splitting, bundle optimization. Use for slow renders, large lists, bundle bloat. Activate on "React performance", "slow render", "useMemo", "bundle size", "virtualization". NOT for backend optimization, non-React frameworks, or premature optimization.
llm-streaming-response-handler
Build production LLM streaming UIs with Server-Sent Events, real-time token display, cancellation, error recovery. Handles OpenAI/Anthropic/Claude streaming APIs. Use for chatbots, AI assistants, real-time text generation. Activate on "LLM streaming", "SSE", "token stream", "chat UI", "real-time AI". NOT for batch processing, non-streaming APIs, or WebSocket bidirectional chat.
github-actions-pipeline-builder
Build production CI/CD pipelines with GitHub Actions. Implements matrix builds, caching, deployments, testing, security scanning. Use for automated testing, deployments, release workflows. Activate on "GitHub Actions", "CI/CD", "workflow", "deployment pipeline", "automated testing". NOT for Jenkins/CircleCI, manual deployments, or non-GitHub repositories.