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.
Best use case
ma-playbook is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using ma-playbook should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ma-playbook/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ma-playbook Compares
| Feature / Agent | ma-playbook | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# 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) 1. Clean up financials (audited if possible) 2. Document all IP and contracts 3. Reduce customer concentration 4. Lock up key employees 5. Build the data room 6. 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 plan - `references/due-diligence-checklist.md` — comprehensive DD checklist by domain
Related Skills
wiki-query
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"
wiki-log
Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized
wiki-lint
Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]
wiki-init
Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates. Usage /wiki-init <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]
wiki-ingest
Ingest a source file from raw/ into the LLM Wiki — read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log. Usage /wiki-ingest <path-to-source>
tc
Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]
tc-tracker
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
llm-wiki
Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
karpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.
karpathy-check
Run Karpathy's 4-principle review on staged changes or the last commit. Checks complexity, diff noise, hidden assumptions, and goal verification. Usage /karpathy-check [--last-commit]
cs-wiki-linter
Dispatched sub-agent that runs a periodic health check on an LLM Wiki vault. Runs mechanical checks via scripts (orphans, broken links, stale pages, missing frontmatter, duplicate titles, log gaps), does semantic checks (contradictions, stale claims, cross-reference gaps, concepts missing their own page), and produces a markdown report with suggested actions. Spawn weekly, after batch ingests, or when the user says "check the wiki" / "lint my wiki" / "audit the vault".
cs-wiki-librarian
Dispatched sub-agent that answers queries against an LLM Wiki vault. Reads index.md first, drills into 3-10 relevant pages across categories, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back into the wiki as a new comparison or synthesis page. Spawn when the user asks a substantive question the wiki might answer, says "what does the wiki say about X", "compare A and B across my sources", or wants to explore a topic.