- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add borghei/Claude-Skills --skill partnerships-architect -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add borghei/Claude-Skills --skill partnerships-architect -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add borghei/Claude-Skills --skill partnerships-architect -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add borghei/Claude-Skills --skill partnerships-architect -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/borghei/Claude-Skills/tree/HEAD/business-growth/partnerships-architectVom Herausgeber
End-to-end strategic partnership design and scaling: partnership type selection (tech integration vs channel vs OEM vs strategic), deal structures, partner program design (tiers, benefits, requirements), partner evaluation, and ROI modeling that justifies (or kills) a partnership investment.
This skill is provider-agnostic and works across SaaS, infrastructure, marketplace, and platform companies.
Five primary partnership types. Different goals; different structures; different success metrics.
What's the primary goal of this partnership?
Grow our distribution reach
├── Customer-pays-them, they-pay-us → Reseller / Distributor / VAR
├── Customer-pays-us, we-pay-them → Affiliate / Referral
└── Joint sale to mutual customer → Co-sell
Embed our product in their offering
├── Customer doesn't see us (white-label) → OEM
├── Customer sees us as embedded → Embedded ISV / Powered-by
└── We're an option in their marketplace → Marketplace listing
Combine our product with theirs (better together)
├── Pre-integrated, certified → Tech / Integration Partner
├── Bundled offering → Solution Partner
└── Joint product (rare) → Joint Venture
Build market presence together
├── Joint events, content, PR → Co-marketing Partner
├── Industry positioning → Strategic Alliance
└── Standards / consortium → Standards Partner
Achieve a specific strategic goal
├── Block a competitor → Defensive partnership
├── Enter a new market → Market entry partnership
└── Acquire capability → Strategic alliance (often pre-acquisition)
See references/partnership-types.md for each type in depth: economic structure, contract patterns, KPIs, when each works / fails.
Not every potential partner is worth the investment. Use this framework before committing.
Total 25-30: green-light; invest with confidence Total 18-24: yellow; structure carefully; small pilot first Total < 18: red; decline or substantially restructure
Use scripts/partner_evaluation_scorer.py --partner partner.yaml to score a specific potential partner.
Before signing any significant partnership:
If you can't get clear answers, the partnership is wishful thinking.
Different deal types call for different structures. Standard patterns:
See references/partnership-deal-structures.md for the full deal-structure templates with negotiation guides.
When you scale beyond a few partners, you need a program.
See references/partner-program-design.md for the full program template including tier definitions, benefit / requirement matrices, and the "Year 1 / Year 2 / Year 3" maturity model.
Use scripts/partner_program_designer.py --org-spec org.yaml to generate a baseline program design based on company stage + ICP + target partner volume.
Partnerships consume real investment. Headcount, MDF, technology, executive time. Model the ROI before committing.
3-year cumulative partnership P&L
Year 1 (investment year):
Revenue from partnership: $X
Costs:
Partnership manager headcount: $200k
Engineering integration (one-time): $300k
Marketing / co-launch: $50k
Partner enablement (content, training): $50k
Travel / events: $30k
TOTAL Y1 cost: $630k
Y1 net: $X - $630k
Year 2:
Revenue from partnership: $Y (growth)
Costs:
Partnership manager: $200k
Engineering ongoing: $100k
Marketing: $80k
Enablement: $30k
Travel / events: $40k
TOTAL Y2 cost: $450k
Y2 net: $Y - $450k
Year 3:
Revenue: $Z (mature)
Costs: $400k (stable)
Y3 net: $Z - $400k
3-year cumulative net: ($X + $Y + $Z) - $1,480k
If 3-year cumulative net is negative, the partnership doesn't pay back. Common reasons:
Use scripts/partnership_roi_modeler.py --partnership partnership.yaml for the full model.
Before designing the partnership, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
scripts/partner_evaluation_scorer.pyscripts/partner_program_designer.pyscripts/partner_evaluation_scorer.pyscripts/partnership_roi_modeler.pybusiness-growth/contract-and-proposal-writerscripts/partner_evaluation_scorer.pyAll scripts: stdlib only, argparse CLI, JSON or markdown output.
In Scope:
scripts/partner_evaluation_scorer.pyscripts/partner_program_designer.pyscripts/partnership_roi_modeler.pyOut of Scope:
business-growth/channel-economics/)business-growth/deal-desk/)business-growth/contract-and-proposal-writer/)business-growth/referral-program/)Important Caveats:
business-growth/channel-economics — per-deal financial mechanics underneath partnership structurebusiness-growth/deal-desk — per-deal approval mechanics for partner-mediated dealsbusiness-growth/pricing-strategy — pricing flexibility / floor for partner dealsbusiness-growth/contract-and-proposal-writer — partner contracts (MSA, partner agreement, OEM agreement)c-level-advisor/cs-cro-advisor — strategic-level partnership decisionsc-level-advisor/cs-ceo-advisor — board-level alliance decisions>
---name: partnerships-architectdescription: >---# business-growth/partnerships-architect/SKILL.mdFAQ
Laden Sie business-growth/partnerships-architect/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/borghei/Claude-Skills.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.