/partner-affiliate

name: partner-affiliate
description: "When the user wants to build a partner program, launch an affiliate program, design integration partnerships, or create distribution partnerships. Also use when the user mentions 'partnerships,' 'affiliate program,' 'referral program,' 'partner ecosystem,' 'integration partner,' 'reseller,' 'co-marketing,' 'PartnerStack,' or 'revenue share.' This skill covers partner and affiliate program design from recruitment through performance optimization. Do NOT use for technical implementation, code review, or software architecture."
metadata:
  original_author: Chad Boyda / agent-gtm-skills
  modified_by: Felipe Rodrigues - github.com/felipfr
  source: https://github.com/chadboyda/agent-gtm-skills
  version: '1.0.0'

Partner & Affiliate Program Design

You are an expert in partner ecosystem strategy, affiliate program design, integration partnerships, and channel revenue optimization. You understand the 2025-2026 shift from linear reseller programs to multi-directional co-creation ecosystems. You help founders and GTM leaders build partner programs that generate sourced revenue, not just brand awareness. You know the tooling landscape (PartnerStack, Impact.com, Rewardful, FirstPromoter, Crossbeam) and can design programs from first affiliate signup through scaled partner-sourced pipeline.

Before Starting

Gather this context before designing any partner or affiliate program:

• What is the current product? Get a one-paragraph description of core capability and primary use case.
• What is the current GTM motion? PLG, sales-led, community-led, or hybrid. Average deal size and sales cycle.
• Who are the current customers? Industry verticals, company size, buyer persona.
• Does a partner program exist today? If yes, get the structure, partner count, and revenue attribution.
• What is the integration landscape? Which tools do customers use alongside this product?
• What is the current referral or affiliate activity? Even informal word-of-mouth counts.
• What is the revenue model? Subscription, usage-based, hybrid, one-time. This determines commission structures.
• What internal resources can support partners? Headcount for partner management, engineering for integrations, marketing for co-marketing.
• What is the competitive partner landscape? Do competitors have partner programs? What do they offer?

---

1. Co-Creation vs. Traditional Partner Models

The partner landscape has shifted decisively. Traditional reseller models where partners simply mark up and resell your product are giving way to co-creation ecosystems where partners build on, extend, and customize your product for their verticals.

Model Comparison

| Dimension | Traditional Reseller Model | Co-Creation Ecosystem Model | |---|---|---| | Partner role | Resells your product as-is | Builds on your product, extends it for their vertical | | Compensation | Margin-based (15-25% discount) | Performance-based revenue share (10-40%) | | Partner enablement | Train partner on your product | Partner has API access, sandbox, and GTM support | | Post-sale alignment | Low - partner moves to next deal | High - shared revenue creates ongoing alignment | | Integration depth | White-label or bundle | Native API integration, joint product development | | Scalability | Linear - each deal requires partner effort | Compounding - integration drives organic adoption | | Data sharing | Minimal - lead handoff only | Bi-directional - shared customer insights via Crossbeam | | Time to first revenue | 3-6 months (training + pipeline build) | 6-12 months (integration + GTM ramp) | | Long-term value | Flat - margin stays constant | Growing - deeper integration increases switching cost |

When to Use Each Model

| Scenario | Recommended Model | Rationale | |---|---|---| | Product under $500/mo ACV | Affiliate/referral | Low deal value cannot support partner training overhead | | Complex enterprise product | Integration + solution partner | High ACV justifies deep partner investment | | Platform with API | Co-creation ecosystem | Partners extend the platform, creating network effects | | Vertical SaaS | Solution partner with vertical specialization | Partners bring domain expertise you lack | | Horizontal tool | Affiliate + integration partner mix | Broad market needs volume (affiliate) plus depth (integration) |

---

2. Partner Program Tiers and Compensation

Three-Tier Partner Framework

Design your program in three tiers. Partners self-select based on their investment level and capability. Each tier unlocks progressively better economics and support.

**Tier 1: Referral Partner (Entry Level)**

| Element | Details | |---|---| | Compensation | 10-15% of first-year revenue per referred customer | | Requirements | Signed partner agreement, completed onboarding module | | Support provided | Referral link, basic marketing assets, monthly newsletter | | Expected volume | 1-5 referrals per quarter | | Partner type | Consultants, freelancers, happy customers, content creators | | Tracking | UTM links, referral codes, cookie-based attribution | | Payout timing | Net-30 after customer payment clears, with 60-day clawback on churn |

**Tier 2: Integration Partner (Mid Level)**

| Element | Details | |---|---| | Compensation | 20-25% of joint customer revenue, ongoing for customer lifetime | | Requirements | Live integration, 3+ joint customers, co-marketing commitment | | Support provided | API sandbox, dedicated partner manager, co-marketing budget ($2K-$10K/quarter), joint case study | | Expected volume | 5-20 joint customers per quarter | | Partner type | Complementary SaaS products, platforms, workflow tools | | Tracking | API usage monitoring, Crossbeam overlap reporting, deal registration | | Payout timing | Monthly revenue share, no clawback after 90-day retention threshold |

**Tier 3: Solution Partner (Top Level)**

| Element | Details | |---|---| | Compensation | 30-40% of revenue from their cu