jpskill.com
💼 ビジネス コミュニティ 🟡 少し慣れが必要 👤 経営者・事業責任者・マーケ

💼 Ma Playbook

ma-playbook

「Ma Playbook」に関する Skill。ビジネス・経営に活用したい人向け。

⏱ 議事録 30分 → 3分

📺 まず動画で見る(YouTube)

▶ 【自動化】AIガチ勢の最新活用術6選がこれ1本で丸分かり!【ClaudeCode・AIエージェント・AI経営・Skills・MCP】 ↗

※ jpskill.com 編集部が参考用に選んだ動画です。動画の内容と Skill の挙動は厳密には一致しないことがあります。

📜 元の英語説明(参考)

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.

🇯🇵 日本人クリエイター向け解説

一言でいうと

「Ma Playbook」に関する Skill。ビジネス・経営に活用したい人向け。

※ jpskill.com 編集部が日本のビジネス現場向けに補足した解説です。Skill本体の挙動とは独立した参考情報です。

⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。

🎯 このSkillでできること

下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。

📦 インストール方法 (3ステップ)

  1. 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
  2. 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
  3. 3. 展開してできたフォルダを、ホームフォルダの .claude/skills/ に置く
    • · macOS / Linux: ~/.claude/skills/
    • · Windows: %USERPROFILE%\.claude\skills\

Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。

詳しい使い方ガイドを見る →
最終更新
2026-05-17
取得日時
2026-05-17
同梱ファイル
3

💬 こう話しかけるだけ — サンプルプロンプト

  • Ma Playbook で、私のビジネスを分析して改善案を3つ提案して
  • Ma Playbook を使って、来週の会議用の資料を作って
  • Ma Playbook で、現状の課題を整理してアクションプランに落として

これをClaude Code に貼るだけで、このSkillが自動発動します。

📖 Claude が読む原文 SKILL.md(中身を展開)

この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。

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

同梱ファイル

※ ZIPに含まれるファイル一覧。`SKILL.md` 本体に加え、参考資料・サンプル・スクリプトが入っている場合があります。