partner-affiliate
# partner-affiliate This Claude Code skill guides the design and launch of partner and affiliate programs, including referral structures, integration partnerships, and distribution channels. Use it when planning program strategy, defining compensation models, selecting partner platforms like PartnerStack or Impact.com, or optimizing partner recruitment and performance workflows. Do not use it for technical implementation, code reviews, or software architecture decisions.
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/partner-affiliate && cp -r /tmp/partner-affiliate/packages/skills-catalog/skills/(gtm)/partner-affiliate ~/.claude/skills/partner-affiliateSKILL.md
# 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 customer base, shared product roadmap influence | | Requirements | 10+ joint customers, dedicated team member, quarterly business review | | Support provided | Priority API access, engineering office hours, joint GTM planning, executive sponsor, early feature access | | Expected volume | 20+ joint customers per quarter | | Partner type | System integrators, vertical platforms, agencies with deep client relationships | | Tracking | Full CRM integration, joint pipeline reviews, Crossbeam account mapping | | Payout timing | Monthly revenue share with quarterly true-up, no clawback | ### Commission Structures by Revenue Model | Your Revenue Model | Referral Commission | Integration Commission | Solution Commission | |---|---|---|---| | Monthly subscription |
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to price an AI product, choose a charge metric, design pricing tiers, or optimize margins. Also use when the user mentions 'AI pricing,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'BYOK,' 'bring your own key,' 'per-seat pricing,' 'pricing tiers,' 'AI margins,' 'cost per token,' or 'pricing model.' This skill covers pricing strategy, packaging, and margin management for AI-native products. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to deploy AI sales development reps, automate sales qualification, build signal-to-action routing, or design AI agent architecture for sales. Also use when the user mentions 'AI SDR,' 'AI sales agent,' 'automated qualification,' 'signal routing,' 'sales automation,' '11x,' 'Artisan,' 'AiSDR,' 'AI BDR,' or 'autonomous sales.' This skill covers AI SDR deployment, qualification automation, and agent architecture for sales development. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production. Also use when the user mentions 'SEO,' 'programmatic SEO,' 'AI content,' 'competitor alternative pages,' 'AI Overviews,' 'search optimization,' 'DataForSEO,' 'content at scale,' 'keyword strategy,' or 'organic traffic.' This skill covers AI-powered SEO strategy from keyword research through programmatic page generation. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to create UGC ad campaigns, recruit UGC creators, generate AI UGC content, or scale with user-generated content. Also use when the user mentions 'UGC,' 'user-generated content,' 'creator ads,' 'Spark Ads,' 'whitelisting,' 'AI UGC,' 'Arcads,' 'Creatify,' 'creator brief,' or 'UGC testing.' This skill covers the UGC growth framework from creator recruitment through AI-powered scaling. Do NOT use for technical implementation, code review, or software architecture.
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities". Do NOT use for accessibility (use web-accessibility), SEO (use seo), performance (use core-web-vitals), or comprehensive multi-area audits (use web-quality-audit).