AGENT SKILL

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
所属仓库
ASoudy/AGS
最近更新
2026-05-23
Stars
★ 0
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

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)

  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

04 同仓库更多 Skills

ASoudy
ASoudy/AGS

web-typography

Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", or "typographic scale". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.

★ 0
ASoudy
ASoudy/AGS

ux-heuristics

Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "usability testing". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.

★ 0
ASoudy
ASoudy/AGS

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "Entrepreneurial Operating System", or "business operating system". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.

★ 0
ASoudy
ASoudy/AGS

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "premium website", "portfolio site", "scroll animations", "Awwwards quality", "brand experience", "cinematic web design", "parallax storytelling", or "agency-quality site". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.

★ 0
ASoudy
ASoudy/AGS

system-design

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.

★ 0
ASoudy
ASoudy/AGS

storybrand-messaging

Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.

★ 0