agentleFS
darkweb19darkweb19/skills/ma-playbook/SKILL.md

ma-playbook

Skill0 starsChanged 28 days agoApache-2.0View on GitHub

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.

4 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Acquiring: Start with strategic rationale → target screening → due diligence → valuation → negotiation → integration.

    line 22
  2. Distinctive:

    Being Acquired: Start with readiness assessment → data room prep → advisor selection → negotiation → transition.

    line 24
  3. Distinctive:

    Document all IP and contracts

    line 67
  4. Distinctive:

    No clear strategic rationale beyond "it's a good deal"

    line 84

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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

DomainKey QuestionsRed Flags
FinancialRevenue quality, customer concentration, burn rate>30% revenue from 1 customer
TechnicalCode quality, tech debt, architecture fitMonolith with no tests
LegalIP ownership, pending litigation, contractsKey IP owned by individuals
PeopleKey person risk, culture fit, retention riskFounders have no lockup/earnout
MarketMarket position, competitive threatsDeclining market share
CustomersChurn rate, NPS, contract termsHigh 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

TermWhat to WatchYour Leverage
ValuationEarnout traps (unreachable targets)Multiple competing offers
EarnoutMilestone definitions, measurement periodCash-heavy vs earnout-heavy split
LockupDuration, conditionsYour replaceability
Rep & warrantiesScope of liabilityEscrow vs indemnification cap
Employee retentionWho gets offers, at what termsKey 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

RoleContribution to M&A
CEOStrategic rationale, negotiation lead
CFOValuation, deal structure, financing
GCLOI/term sheet review, contract risk scan, regulatory triggers
CDOData diligence: training-data rights, data-asset valuation
CTOTechnical due diligence, integration architecture
CHROPeople due diligence, retention planning
COOIntegration execution, process merge
CPOProduct 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.