Partnerships Architect
Design strategic partnerships, technology, channel, co-marketing, and the programs...
Install
npx skills add borghei/Claude-Skills --skill partnerships-architect -g -a claude-code -y- Repository
- borghei/Claude-Skills1k
- Category
- Design
- Updated
- 12d ago
- License
- MIT + Commons Clause
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- Yes, review before use
What it does
Design strategic partnerships, technology, channel, co-marketing, and the programs that scale them. Use when evaluating a partner, picking a partnership type, designing a partner program, structuring a deal, or modeling ROI.
Partnerships Architect
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.
When to use this skill
| Situation | Skill applies |
|---|---|
| Evaluating a potential partner | Yes, use scripts/partner_evaluation_scorer.py + evaluation framework |
| Picking partnership type for a specific opportunity | Yes, see partnership type decision tree |
| Designing a partner program from scratch | Yes, see partner program design + scripts/partner_program_designer.py |
| Structuring a specific partnership deal | Yes, see partnership deal structures |
| Modeling partnership ROI | Yes, scripts/partnership_roi_modeler.py |
| Auditing existing partner portfolio | Yes, use evaluation scorer across all partners |
| Per-deal partner economics | Use business-growth/channel-economics |
| Per-deal partner approval | Use business-growth/deal-desk |
| Writing the partner contract | Use business-growth/contract-and-proposal-writer |
Partnership types, the decision tree
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
