[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DRYZ3CHPA5SPQVEK48BWAW":3,"skill-same:01M6DRYZ3CHPA5SPQVEK48BWAW":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6DRYZ3CHPA5SPQVEK48BWAW","ma-playbook",null,"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.","zhangzhang-111-i\u002Fclaude-skills111","zhangzhang-111-i","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F251344927?v=4","01M6DRBP4NCM1ZCHTT0FW0SQHD","lixiying","01M6DRBPAMFDJSGQ69XPK9KM9J",4,"MIT","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fma-playbook\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"playbook","ma playbook","valuation","planning","negotiation","integration","acquisition","strategy","use","structure","2026-11-10 10:12:30",false,"---\nname: \"ma-playbook\"\ndescription: \"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.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: ma-strategy\n  updated: 2026-03-05\n---\n\n# M&A Playbook\n\nFrameworks for both sides of M&A: acquiring companies and being acquired.\n\n## Keywords\nM&A, mergers and acquisitions, due diligence, acquisition, acqui-hire, integration, deal structure, valuation, LOI, term sheet, earnout\n\n## Quick Start\n\n**Acquiring:** Start with strategic rationale → target screening → due diligence → valuation → negotiation → integration.\n\n**Being Acquired:** Start with readiness assessment → data room prep → advisor selection → negotiation → transition.\n\n## When You're Acquiring\n\n### Strategic Rationale (answer before anything else)\n- **Buy vs Build:** Can you build this faster\u002Fcheaper? If yes, don't acquire.\n- **Acqui-hire vs Product vs Market:** What are you really buying? Talent? Technology? Customers?\n- **Integration complexity:** How hard is it to merge this into your company?\n\n### Due Diligence Checklist\n| Domain | Key Questions | Red Flags |\n|--------|--------------|-----------|\n| Financial | Revenue quality, customer concentration, burn rate | >30% revenue from 1 customer |\n| Technical | Code quality, tech debt, architecture fit | Monolith with no tests |\n| Legal | IP ownership, pending litigation, contracts | Key IP owned by individuals |\n| People | Key person risk, culture fit, retention risk | Founders have no lockup\u002Fearnout |\n| Market | Market position, competitive threats | Declining market share |\n| Customers | Churn rate, NPS, contract terms | High churn, short contracts |\n\n### Valuation Approaches\n- **Revenue multiple:** Industry-dependent (2-15x ARR for SaaS)\n- **Comparable transactions:** What similar companies sold for\n- **DCF:** For profitable companies only (most startups: use multiples)\n- **Acqui-hire:** $1-3M per engineer in hot markets\n\n### Integration Frameworks\nSee `references\u002Fintegration-playbook.md` for the 100-day integration plan.\n\n## When You're Being Acquired\n\n### Readiness Signals\n- Inbound interest from strategic buyers\n- Market consolidation happening around you\n- Fundraising becomes harder than operating\n- Founder ready for a transition\n\n### Preparation (6-12 months before)\n1. Clean up financials (audited if possible)\n2. Document all IP and contracts\n3. Reduce customer concentration\n4. Lock up key employees\n5. Build the data room\n6. Engage an M&A advisor\n\n### Negotiation Points\n| Term | What to Watch | Your Leverage |\n|------|--------------|---------------|\n| Valuation | Earnout traps (unreachable targets) | Multiple competing offers |\n| Earnout | Milestone definitions, measurement period | Cash-heavy vs earnout-heavy split |\n| Lockup | Duration, conditions | Your replaceability |\n| Rep & warranties | Scope of liability | Escrow vs indemnification cap |\n| Employee retention | Who gets offers, at what terms | Key person dependencies |\n\n## Red Flags (Both Sides)\n\n- No clear strategic rationale beyond \"it's a good deal\"\n- Culture clash visible during due diligence and ignored\n- Key people not locked in before close\n- Integration plan doesn't exist or is \"we'll figure it out\"\n- Valuation based on projections, not actuals\n\n## Integration with C-Suite Roles\n\n| Role | Contribution to M&A |\n|------|-------------------|\n| CEO | Strategic rationale, negotiation lead |\n| CFO | Valuation, deal structure, financing |\n| CTO | Technical due diligence, integration architecture |\n| CHRO | People due diligence, retention planning |\n| COO | Integration execution, process merge |\n| CPO | Product roadmap impact, customer overlap |\n\n## Resources\n- `references\u002Fintegration-playbook.md` — 100-day post-acquisition integration plan\n- `references\u002Fdue-diligence-checklist.md` — comprehensive DD checklist by domain\n","# M&A Playbook\n\nFrameworks for both sides of M&A: acquiring companies and being acquired.\n\n## Keywords\nM&A, mergers and acquisitions, due diligence, acquisition, acqui-hire, integration, deal structure, valuation, LOI, term sheet, earnout\n\n## Quick Start\n\n**Acquiring:** Start with strategic rationale → target screening → due diligence → valuation → negotiation → integration.\n\n**Being Acquired:** Start with readiness assessment → data room prep → advisor selection → negotiation → transition.\n\n## When You're Acquiring\n\n### Strategic Rationale (answer before anything else)\n- **Buy vs Build:** Can you build this faster\u002Fcheaper? If yes, don't acquire.\n- **Acqui-hire vs Product vs Market:** What are you really buying? Talent? Technology? Customers?\n- **Integration complexity:** How hard is it to merge this into your company?\n\n### Due Diligence Checklist\n| Domain | Key Questions | Red Flags |\n|--------|--------------|-----------|\n| Financial | Revenue quality, customer concentration, burn rate | >30% revenue from 1 customer |\n| Technical | Code quality, tech debt, architecture fit | Monolith with no tests |\n| Legal | IP ownership, pending litigation, contracts | Key IP owned by individuals |\n| People | Key person risk, culture fit, retention risk | Founders have no lockup\u002Fearnout |\n| Market | Market position, competitive threats | Declining market share |\n| Customers | Churn rate, NPS, contract terms | High churn, short contracts |\n\n### Valuation Approaches\n- **Revenue multiple:** Industry-dependent (2-15x ARR for SaaS)\n- **Comparable transactions:** What similar companies sold for\n- **DCF:** For profitable companies only (most startups: use multiples)\n- **Acqui-hire:** $1-3M per engineer in hot markets\n\n### Integration Frameworks\nSee `references\u002Fintegration-playbook.md` for the 100-day integration plan.\n\n## When You're Being Acquired\n\n### Readiness Signals\n- Inbound interest from strategic buyers\n- Market consolidation happening around you\n- Fundraising becomes harder than operating\n- Founder ready for a transition\n\n### Preparation (6-12 months before)\n1. Clean up financials (audited if possible)\n2. Document all IP and contracts\n3. Reduce customer concentration\n4. Lock up key employees\n5. Build the data room\n6. Engage an M&A advisor\n\n### Negotiation Points\n| Term | What to Watch | Your Leverage |\n|------|--------------|---------------|\n| Valuation | Earnout traps (unreachable targets) | Multiple competing offers |\n| Earnout | Milestone definitions, measurement period | Cash-heavy vs earnout-heavy split |\n| Lockup | Duration, conditions | Your replaceability |\n| Rep & warranties | Scope of liability | Escrow vs indemnification cap |\n| Employee retention | Who gets offers, at what terms | Key person dependencies |\n\n## Red Flags (Both Sides)\n\n- No clear strategic rationale beyond \"it's a good deal\"\n- Culture clash visible during due diligence and ignored\n- Key people not locked in before close\n- Integration plan doesn't exist or is \"we'll figure it out\"\n- Valuation based on projections, not actuals\n\n## Integration with C-Suite Roles\n\n| Role | Contribution to M&A |\n|------|-------------------|\n| CEO | Strategic rationale, negotiation lead |\n| CFO | Valuation, deal structure, financing |\n| CTO | Technical due diligence, integration architecture |\n| CHRO | People due diligence, retention planning |\n| COO | Integration execution, process merge |\n| CPO | Product roadmap impact, customer overlap |\n\n## Resources\n- `references\u002Fintegration-playbook.md` — 100-day post-acquisition integration plan\n- `references\u002Fdue-diligence-checklist.md` — comprehensive DD checklist by domain\n",{"name":5,"license":15,"metadata":34,"description":7},{"author":35,"domain":36,"updated":37,"version":38,"category":39},"Alireza Rezvani","ma-strategy",1772668800000,"1.0.0","c-level","main","c0a12fc98d85642fa8893e31fc5cf5dfad879de6","c-level-advisor\u002Fma-playbook",0,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i","2026-03-13 21:49:18",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill ma-playbook",{"tool":53,"command":54},"bunx","bunx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill ma-playbook",{"tool":56,"command":57},"pnpm","pnpm dlx skills add zhangzhang-111-i\u002Fclaude-skills111 --skill ma-playbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fma-playbook\u002FSKILL.md",true,[61,67],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fdue-diligence-checklist.md","REFERENCE","参考文档",4943,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fma-playbook\u002Freferences\u002Fdue-diligence-checklist.md",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fintegration-playbook.md",5733,"https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fc-level-advisor\u002Fma-playbook\u002Freferences\u002Fintegration-playbook.md",[72,98,122,153,173,196],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":29},"01M6DSNYM8PZKEXGYMRX53PVPH","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[79,80,81,82,83,84,85,86,87,88,89,90,27,91,92,93,94,95,96,97],"risk","risk management specialist","management","risk management","risk analysis","risk evaluation","product","Evaluation","Production","lifecycle","analysis","user","risk matrix","Market","device","control","iso","medical","iso 14971",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":29},"01M6DSNSRBGVZWS23TK0ZQ52QC","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[105,106,107,108,109,110,22,111,112,113,114,26,115,116,117,118,119,120,96,121],"regulatory affairs head","regulatory","head","documentation","documents","packages","devices","plan","access","write","evidence","standards","manage","intelligence","across","strategies","clinical",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":138,"publishedAt":29},"01M6DSNN7GNR2HZE66S4D31EP8","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[128,133],{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[139,140,141,142,143,144,108,145,146,147,148,149,27,106,150,151,152,94,95,96],"quality manager qms iso13485","quality","design","review","support","workflows","audit","actions","compliance","system","process","up","maintenance","document",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":162,"publishedAt":29},"01M6DSNE5PQM106PM4EDGPBWGZ","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[159],{"categoryNo":160,"categoryName":161,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000037","律师与法务",[163,140,142,164,165,166,167,147,168,148,81,169,106,170,171,172,95],"quality manager qmr","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":183,"publishedAt":29},"01M6DSN7MYXB6X42TB1GH2TNSB","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[179,182],{"categoryNo":180,"categoryName":181,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":160,"categoryName":161,"taxonomyType":136,"taxonomyTypeDesc":137},[108,184,140,142,185,186,145,88,187,148,188,189,27,190,191,192,96,193,194,195],"quality documentation manager","workflow","change","document lifecycle","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":29},"01M6DSN3R749H3R20K15QE8X8W","qms-audit-expert","ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management.","https:\u002F\u002Fgithub.com\u002Fzhangzhang-111-i\u002Fclaude-skills111\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fqms-audit-expert\u002FSKILL.md",[],[145,203,204,22,205,206,207,208,81,27,209,93,95,96],"qms audit expert","expert","verification","execution","classification","schedule","checklist"]