Agent skill · product strategy · borghei
ma-playbook
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).
Why this skill is useful
Provides a comprehensive framework for M&A strategy that includes specific decision trees and due diligence checklists not commonly found in public resources.
What it needs
About 12k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
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 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/ma-playbook