c-level-advisor/skills/ma-playbook/SKILL.md
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.
npx skillsauth add alirezarezvani/claude-skills ma-playbookInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Frameworks for both sides of M&A: acquiring companies and being acquired.
M&A, mergers and acquisitions, due diligence, acquisition, acqui-hire, integration, deal structure, valuation, LOI, term sheet, earnout
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.
| 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 |
The ranges below are illustrative, not current market data — always verify against current market comps before using them in a model or negotiation.
Sources to verify against (check the latest edition): the SaaS Capital Index (private SaaS revenue multiples, updated monthly), Software Equity Group (SEG) Annual/Quarterly SaaS M&A Reports (transaction multiples), and Aventis Advisors' SaaS valuation multiples reports. Cross-check at least two before anchoring a price.
See references/integration-playbook.md for the 100-day integration plan.
| 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 |
This skill frames the deal; two sibling skills verify it. Hand off — don't duplicate:
general-counsel-advisor: run the LOI/term sheet through ../general-counsel-advisor/scripts/term_sheet_analyzer.py (12-dimension 0-100 score) and the definitive docs through ../general-counsel-advisor/scripts/contract_risk_scanner.py (12 founder-killer patterns: earnout traps, uncapped indemnity, vague IP, etc.). Any 🔴 finding goes to outside counsel before signing.chief-data-officer-advisor: run ../chief-data-officer-advisor/scripts/ai_training_data_audit.py (training-data rights, GDPR Art. 6 basis) and ../chief-data-officer-advisor/scripts/data_asset_valuator.py (data-asset value, M&A multiplier with carve-out penalties) on the target's data estate. Undocumented consent provenance is a price-reduction or walk-away item.cfo-advisor tools for the quantitative model; this playbook stays qualitative.Loop the findings back into the negotiation-points table above before the next counter.
| Role | Contribution to M&A | |------|-------------------| | CEO | Strategic rationale, negotiation lead | | CFO | Valuation, deal structure, financing | | GC | LOI/term sheet review, contract risk scan, regulatory triggers | | CDO | Data diligence: training-data rights, data-asset valuation | | CTO | Technical due diligence, integration architecture | | CHRO | People due diligence, retention planning | | COO | Integration execution, process merge | | CPO | Product roadmap impact, customer overlap |
references/integration-playbook.md — 100-day post-acquisition integration planreferences/due-diligence-checklist.md — comprehensive DD checklist by domain../general-counsel-advisor/SKILL.md — term sheet analyzer + contract risk scanner../chief-data-officer-advisor/SKILL.md — data diligence + data-asset valuationdevelopment
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.