borghei/Claude-Skills / business-growth/partnerships-architect
partnerships-architect
VerifiedDesign 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.5 KB |
| references/partner-program-design.md | markdown | 14.2 KB |
| references/partnership-deal-structures.md | markdown | 14.6 KB |
| references/partnership-types.md | markdown | 13.1 KB |
| scripts/partner_evaluation_scorer.py | script | 10.1 KB |
| scripts/partner_program_designer.py | script | 12.0 KB |
| scripts/partnership_roi_modeler.py | script | 10.1 KB |
references/partner-program-design.md
View on GitHub# Partner Program Design
Reference for designing and scaling a partner program: program structure (recruitment, enablement, activation), tier matrices, benefits and requirements per tier, channel manager ratios, Year-1 to Year-3 maturity model, and the metrics that determine program health.
---
## The three pillars of a partner program
### Pillar 1: Recruitment
**Goal:** Sign the right partners (not the most partners).
**Components:**
- **Target Partner Profile (TPP)**: ideal partner attributes — size, vertical, region, capabilities, existing customer base
- **Outreach motion**: inbound (partner finds you via marketplace listing / content) + outbound (you identify + pursue specific targets)
- **Intake / qualification**: partner application + scoring → decision
- **Onboarding**: first-30-days experience for new partners
**Avoid:** Signing every partner that asks. Quality > quantity. 10 productive partners > 100 zombies.
### Pillar 2: Enablement
**Goal:** Make partners successful with your product.
**Components:**
- **Training program**: self-paced LMS + instructor-led for advanced topics
- **Certification**: tested verification of competency; required for higher tiers
- **Technical resources**: API docs, code samples, demo environments, sandbox
- **Partner portal**: central hub for deal reg, training, materials, MDF
- **Sales enablement**: pitch decks, competitive intel, ROI calculators
**Avoid:** Partner program with no enablement. Partners can't sell what they don't understand.
### Pillar 3: Activation
**Goal:** Drive partner-led / partner-influenced revenue.
**Components:**
- **Deal registration**: protects partner-developed opportunities
- **Lead sharing**: leads you can't pursue → routed to partners (geographic, vertical, size fit)
- **MDF (Marketing Development Funds)**: co-funded marketing campaigns
- **Co-selling**: joint pursuit of mutual prospects
- **Quarterly Business Reviews (QBRs)**: tier-appropriate cadence with each partner
**Avoid:** Partner signed, never activated. Active engagement separates productive partners from theater.
---
## Standard tier structure
Most programs use 3-4 tiers. Higher tiers = higher partner investment + higher vendor investment.
### Tier matrix (typical)
| Element | Authorized | Silver | Gold | Platinum |
|---------|------------|--------|------|----------|
| **Required revenue (annual)** | None | $100k | $500k | $2M |
| **Required certifications** | 1 | 3 | 5 | 10 |
| **Required customer wins** | 0 | 2 | 5 | 10 |
| **Required renewal rate** | None | 70% | 80% | 90% |
| **Discount** | 10% | 15% | 20% | 25% |
| **Rebate (back-end)** | 0% | 0% | 5% | 7% |
| **MDF (% of partner revenue)** | 0 | 1% | 2% | 3% |
| **Deal registration** | Standard | Standard | Priority | Priority |
| **Channel manager** | Shared pool | Shared pool | Dedicated CM | Dedicated CM + Sr. Strategic |
| **Lead sharing** | Limited | Eligible | Active | Priority |
| **Co-marketing** | Limited | Eligible | Active | Featured |
| **Joint roadmap input** | No | No | Annual | Quarterly |
| **Advisory board seat** | No | No | No | Yes |
| **Press release on logo** | No | No | Yes | Yes |
| **Annual conference invite** | Yes (paid) | Yes (paid) | Yes (discounted) | Yes (free + speaking slot) |
### Tier design principles
1. **Outcome-based, not effort-based.** Tier requirements should be revenue / retention metrics, not training hours.
2. **Benefits worth the requirements.** Each tier benefit should be substantial enough to motivate the tier requirement.
3. **Achievable but stretching.** 12-18 months from one tier to the next.
4. **Downgradeable.** Status re-evaluated annually. Partners can move down if requirements not maintained.
5. **Visible status.** Public tier badges (silver / gold / platinum) — partners use for marketing.
---
## Partner program scope (start small, expand)
### Year 1 (foundation)
| What to build | Why |
|--------------|-----|
| Basic partner agreement | Legal foundation |
| 2 tiers (Authorized, Silver) | Don't over-engineer; expand later |
| Partner portal (minimum: deal-reg + standard docs) | Operational basics |
| Self-paced training (1 course: product fundamentals) | Get partners productive |
| Channel manager (1 FTE) | Run pilot with 3-5 partners |
| Standard MDF process | Co-marketing capability |
**Goal:** Onboard 5-10 productive partners. Learn what works.
### Year 2 (scale)
| What to add | Why |
|------------|-----|
| 3rd tier (Gold) | Differentiate top performers |
| Certification program | Quality control |
| Co-sell program with cloud marketplaces | Leverage existing motion |
| Lead-sharing process | Activate partners |
| Quarterly Business Reviews (QBRs) | Engagement cadence |
| Channel team grows (3-5 FTEs) | One per 10-15 active partners |
**Goal:** 25-50 active partners. 15-25% of total revenue partner-attributed.
### Year 3 (mature)
| What to add | Why |
|------------|-----|
| 4th tier (Platinum) | Reward top strategic partners |
| Advisory board | Strategic input from partners |
| Specialization programs (vertical, technology) | Differentiate by partner type |
| Annual partner conference | Community + recognition |
| Robust partner portal (training LMS, marketing co-op, MDF self-service) | Self-service efficiency |
| Channel team: 8-15 FTEs | Scale + specialization |
**Goal:** 100+ active partners. 25-40% of total revenue partner-attributed (or appropriate per channel strategy).
---
## Channel manager (CM) ratios
| Partner tier | Partners per CM |
|--------------|-----------------|
| Authorized | 30-50 (light touch) |
| Silver | 15-25 (standard cadence) |
| Gold | 8-15 (active engagement) |
| Platinum | 3-5 (strategic ownership) |
Most programs use a hybrid: junior CMs cover Authorized/Silver in bulk; senior CMs cover Gold; dedicated strategic alliance managers for Platinum.
---
## Partner intake / qualification process
### Standard application flow
1. **Partner applies** via web form (auto-screened: company name, size, region, primary business)
2. **Qualification call** with channel manager (30-min discovery): fit assessment
3. **Internal review**: scoring against TPP; competitor / conflict check
4. **Decision**: approve / decline / approve-conditional
5. **Onboarding kickoff**: assigned CM; sandbox access; training schedule; quarterly target setting
### Application form (minimum fields)
- Company name + URL
- Company size (employees, revenue)
- Years in business
- Headquarters + service regions
- Primary business / vertical / sub-industries
- Existing vendor relationships (especially in your category)
- Reason for interest in this partnership
- Estimated pipeline (next 12 months)
- Decision-maker for partnership
- Technical lead
### Scoring rubric
| Dimension | Score 1-5 |
|-----------|-----------|
| Strategic fit (TPP match) | |
| Pipeline potential | |
| Technical capability | |
| Commercial sophistication | |
| Cultural / operational fit | |
**Total 18-25**: approve standard
**Total 13-17**: approve with pilot scope
**Total < 13**: decline
---
## Onboarding journey
### First 30 days
- [ ] Sign partner agreement
- [ ] Assign channel manager
- [ ] Partner portal access provisioned
- [ ] Sandbox / dev environment access
- [ ] Required certification(s) scheduled
- [ ] Quarterly kickoff with CM
- [ ] First 90-day target set
### First 90 days
- [ ] Required certifications completed
- [ ] First customer pursuit registered
- [ ] First marketing co-op activity planned
- [ ] CM check-in cadence established
### First 12 months
- [ ] First deal closed
- [ ] First QBR completed
- [ ] Eligible for next tier (if applicable)
- [ ] Annual planning session
---
## Deal registration process
The mechanism that prevents channel conflict (per [channel-economics/references/channel-conflict-resolution.md](../../channel-economics/references/channel-conflict-resolution.md)).
### Registration policy template
```
1. Partner identifies opportunity
2. Partner submits via partner portal
3. Vendor reviews within 3 business days:
- Approve: protected for 180 days
- Deny: account already direct OR registered by another partner OR insufficient evidence
4. During protected period:
- Direct sales does not pursue without partner consent
- Other partners cannot register same account
5. Partner closes (or registration expires)
6. If closes: partner discount applies; commission tracked
7. If expires: account becomes open; can be re-registered
```
---
## MDF (Marketing Development Funds)
### MDF allocation
| Tier | MDF as % of partner revenue |
|------|----------------------------|
| Silver | 1% (small budget) |
| Gold | 2% |
| Platinum | 3% |
### Approved MDF activities
- Joint events (you sponsor partner-led event in your category)
- Co-branded content (whitepapers, webinars, case studies)
- Paid advertising in partner's channels
- Trade show booth space
- Partner-led demand-gen campaigns
### MDF anti-patterns
- MDF spent on partner's general marketing (not co-branded; no measurable pipeline)
- MDF approved without ROI commitment
- MDF used to subsidize partner's discount (effectively just another discount)
### MDF approval flow
```
1. Partner submits MDF request: activity, budget, expected outcomes
2. Channel manager reviews against MDF eligible activities + ROI criteria
3. Approved (with reporting requirements) or counter-proposed or declined
4. Activity executes; partner reports outcomes
5. Reimbursement (or pre-pay arrangement) per agreement
6. Quarterly MDF utilization + ROI review with partner
```
---
## Quarterly Business Review (QBR) framework
For Gold + Platinum partners; quarterly cadence.
### Standard QBR agenda
```
1. Review previous quarter
- Revenue + pipeline performance vs target
- Wins + losses (lessons)
- MDF activities + outcomes
- Channel conflict items (if any)
2. Current quarter outlook
- Pipeline / forecast review
- Resource needs
- Active deals + risks
3. Next quarter planning
- Targets (revenue, pipeline, certifications, joint activities)
- MDF requests / approvals
- Joint planning (campaigns, events, customer wins targeted)
4. Strategic items
- Roadmap input
- Market intelligence (competitive, vertical, regulatory)
- Relationship escalations
5. Action items
- Each: owner, due date, success criteria
```
### QBR cadence by tier
| Tier | QBR frequency | Format |
|------|--------------|--------|
| Authorized | Annual (light) | Async survey + brief call |
| Silver | Bi-annual | 60-min video call |
| Gold | Quarterly | 90-min video call OR in-person if regional |
| Platinum | Monthly check-in + quarterly strategic | Quarterly always in-person if possible |
---
## Program metrics
### Health metrics (track monthly)
| Metric | Healthy |
|--------|---------|
| Active partners (% of total signed) | > 60% |
| Partner-sourced revenue % of total | varies; typically 15-50% mature |
| Partner-influenced revenue (broader: deals where partner touched) | typically 2x sourced |
| Average revenue per active partner | growing year-over-year |
| Tier distribution (% in each tier) | most partners in Authorized; pyramid up |
| Tier upgrades per quarter | > 0; movement = healthy |
| Tier downgrades per quarter | < 10%; some movement expected |
| New partners onboarded per quarter | varies; aligned with capacity |
| Partner satisfaction (NPS, annual survey) | > 40 |
### Operational metrics
- Deal registration response time (target: < 3 BD)
- MDF approval response time (target: < 5 BD)
- Certification completion rate
- Partner portal usage
- QBR attendance + satisfaction
### Investment ROI
- Per-partner investment (CM hours, MDF, enablement amortized) / per-partner revenue contribution
- Tier-by-tier ROI: are Gold partners worth the dedicated CM?
- Bottom-quartile review: which partners get cut?
---
## Common program mistakes
### Mistake 1: Tier requirements too easy
If 80% of partners are Gold within 6 months, tiers don't differentiate. Reset or raise.
### Mistake 2: Tier benefits not worth it
If Gold partners don't perceive benefits as worth the requirements, they won't push for Gold. Surveys help diagnose.
### Mistake 3: MDF as subsidy
MDF that doesn't drive incremental pipeline isn't MDF — it's discount. Require ROI.
### Mistake 4: Recruitment ahead of enablement
Signing 50 partners in Q1; certification program ready in Q3 → partners idle for 6 months → many disengage.
### Mistake 5: One-size-fits-all program
Standard reseller + OEM + ISV all in same tier matrix. Different partner types need different programs. Specialize.
### Mistake 6: Channel manager too thin
1 CM for 50 partners → CM is reactive only; no proactive engagement; partners drift.
### Mistake 7: No partner advisory board
Top partners have signals (market, competitor, customer) you don't have. Use them.
### Mistake 8: Annual conference as theater
Conference with no concrete output (training, planning, deal advancement) wastes everyone's time.
---
## Program design checklist
Before launching:
- [ ] Target Partner Profile defined
- [ ] Tier structure: 2-4 tiers with explicit requirements + benefits
- [ ] Partner agreement drafted (legal-reviewed)
- [ ] Deal registration process designed
- [ ] Onboarding journey documented (30-60-90-day milestones)
- [ ] Training program: at minimum, 1 self-paced course
- [ ] Partner portal: deal-reg + standard documents at minimum
- [ ] MDF program (if applicable): eligible activities + approval flow
- [ ] Channel manager(s) hired
- [ ] Pilot cohort: 3-5 partners identified
- [ ] Metrics dashboard: health + operational metrics
- [ ] Internal stakeholder communication: sales (deal-reg respect), legal (agreement), finance (rev rec for partner deals)
---
## Cheat sheet
| Question | Answer |
|----------|--------|
| Where to start? | 2 tiers, 3-5 pilot partners, 1 CM, standard agreement |
| When to add a tier? | When existing top tier feels under-differentiated |
| How many partners can we support? | Per CM: 10-15 active engaged; expand CM team to grow |
| Certification required for what tier? | Silver and above (some baseline competency) |
| MDF: per-partner or pooled? | Per-partner allocation tracked; pooled budget approval |
| When to kill a tier? | When < 5% of partners are in it OR it's not driving differentiation |
| When to revamp program? | Every 18-24 months; markets / partner expectations shift |
| Best signal of program health? | Partner-sourced revenue % growing year-over-year |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |