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
所属仓库
TehutiRaEl/THEHIVE
最近更新
2026-11-15
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

The ranges below are illustrative, not current market data — always verify against current market comps before using them in a model or negotiation.

  • Revenue multiple: Industry-dependent (illustrative range: 2-15x ARR for SaaS, varying with growth rate, NRR, and rate environment)
  • Comparable transactions: What similar companies sold for — the most defensible anchor
  • DCF: For profitable companies only (most startups: use multiples)
  • Acqui-hire: Illustrative range: $1-3M per engineer in hot talent markets

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.

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

Verification Loop (before any LOI or signature)

This skill frames the deal; two sibling skills verify it. Hand off — don't duplicate:

  1. Legal terms → 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.
  2. Data diligence → 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.
  3. Valuation math → 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.

Integration with C-Suite Roles

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

Resources

  • references/integration-playbook.md — 100-day post-acquisition integration plan
  • references/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 valuation

04 同仓库更多 Skills

TehutiRaEl
TehutiRaEl/THEHIVE

preamble-gate

Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent/subagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI/triggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log/diff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

visionary-recommender

暂无简介

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

syllabus

Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

research

Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

pulse

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

patent

Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.

★ 0