partner-affiliate

tech-leads-club/agent-skills · updated May 23, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/tech-leads-club/agent-skills --skill partner-affiliate
0 commentsdiscussion
summary

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.

skill.md
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

DimensionTraditional Reseller ModelCo-Creation Ecosystem Model
Partner roleResells your product as-isBuilds on your product, extends it for their vertical
CompensationMargin-based (15-25% discount)Performance-based revenue share (10-40%)
Partner enablementTrain partner on your productPartner has API access, sandbox, and GTM support
Post-sale alignmentLow - partner moves to next dealHigh - shared revenue creates ongoing alignment
Integration depthWhite-label or bundleNative API integration, joint product development
ScalabilityLinear - each deal requires partner effortCompounding - integration drives organic adoption
Data sharingMinimal - lead handoff onlyBi-directional - shared customer insights via Crossbeam
Time to first revenue3-6 months (training + pipeline build)6-12 months (integration + GTM ramp)
Long-term valueFlat - margin stays constantGrowing - deeper integration increases switching cost

When to Use Each Model

ScenarioRecommended ModelRationale
Product under $500/mo ACVAffiliate/referralLow deal value cannot support partner training overhead
Complex enterprise productIntegration + solution partnerHigh ACV justifies deep partner investment
Platform with APICo-creation ecosystemPartners extend the platform, creating network effects
Vertical SaaSSolution partner with vertical specializationPartners bring domain expertise you lack
Horizontal toolAffiliate + integration partner mixBroad 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)

ElementDetails
Compensation10-15% of first-year revenue per referred customer
RequirementsSigned partner agreement, completed onboarding module
Support providedReferral link, basic marketing assets, monthly newsletter
Expected volume1-5 referrals per quarter
Partner typeConsultants, freelancers, happy customers, content creators
TrackingUTM links, referral codes, cookie-based attribution
Payout timingNet-30 after customer payment clears, with 60-day clawback on churn

Tier 2: Integration Partner (Mid Level)

ElementDetails
Compensation20-25% of joint customer revenue, ongoing for customer lifetime
RequirementsLive integration, 3+ joint customers, co-marketing commitment
Support providedAPI sandbox, dedicated partner manager, co-marketing budget ($2K-$10K/quarter), joint case study
Expected volume5-20 joint customers per quarter
Partner typeComplementary SaaS products, platforms, workflow tools
TrackingAPI usage monitoring, Crossbeam overlap reporting, deal registration
Payout timingMonthly revenue share, no clawback after 90-day retention threshold

Tier 3: Solution Partner (Top Level)

ElementDetails
Compensation30-40% of revenue from their customer base, shared product roadmap influence
Requirements10+ joint customers, dedicated team member, quarterly business review
Support providedPriority API access, engineering office hours, joint GTM planning, executive sponsor, early feature access
Expected volume20+ joint customers per quarter
Partner typeSystem integrators, vertical platforms, agencies with deep client relationships
TrackingFull CRM integration, joint pipeline reviews, Crossbeam account mapping
Payout timingMonthly revenue share with quarterly true-up, no clawback

Commission Structures by Revenue Model

Your Revenue ModelReferral CommissionIntegration CommissionSolution Commission
Monthly subscription15% of month-1 revenue, or 10% recurring for 12 months20% recurring for customer lifetime30-40% recurring for customer lifetime
Annual subscription10-15% of first-year ACV20-25% of ACV, renewed annually30-40% of ACV, renewed annually
Usage-based10% of first 12 months usage20% of ongoing usage30% of ongoing usage
Outcome-based10% of first outcome payment20% of ongoing outcome payments35% of ongoing outcome payments

Clawback and Protection Policies

PolicyReferral TierIntegration TierSolution Tier
Clawback window60 days90 daysNone
Customer churn triggerFull commission returnedPro-rated returnNo return, partner helps with retention
Deal overlap resolutionFirst-touch attributionMulti-touch with registration priorityJoint pipeline, split credit
Direct sale overlapPartner loses if deal registered after direct contactDeal registration within 14 days protects partnerProtected account list reviewed quarterly

3. Affiliate Program Design and Tooling

Platform Selection Framework

PlatformBest ForPricing (Starting)Key StrengthsLimitations
PartnerStackB2B SaaS, multi-partner-type programsCustom (mid-market+)Manages affiliates, referrals, and resellers in one platform. Automated global payouts. Large B2B marketplace network.Higher cost. Overkill for simple referral programs.
Impact.comEnterprise, large-scale affiliate programsCustom (enterprise)Vast partner network, granular attribution, custom recurring commissions.Steep learning curve. Requires dedicated admin.
RewardfulEarly-stage SaaS, Stripe-first companies$49/monthFast Stripe integration, simple setup, affordable. 30+ integrations.No built-in email automation. Limited as programs scale.
FirstPromoterGrowth-stage SaaS, MRR-focused teams$99/monthStrong recurring billing tracking, 18+ detailed metrics, built-in fraud protection, email automation.Higher price than Rewardful. Fewer marketplace features.
RefgrowBootstrapped SaaS$0-49/monthFree tier available, simple widget-based setupLimited features at lower tiers

Platform Decision Tree

START: What is your monthly revenue?
  |
  +--> Under $10K MRR
  |      |
  |      +--> Using Stripe? --> Rewardful ($49/mo)
  |      +--> Not using Stripe? --> Refgrow (free tier)
  |
  +--> $10K-$100K MRR
  |      |
  |      +--> Need email automation? --> FirstPromoter ($99/mo)
  |      +--> Stripe-only, keep it simple? --> Rewardful ($49/mo)
  |
  +--> $100K-$500K MRR
  |      |
  |      +--> Multi-partner-type program? --> PartnerStack
  |      +--> Affiliate-only focus? --> FirstPromoter
  |
  +--> $500K+ MRR
         |
         +--> Enterprise, complex attribution? --> Impact.com
         +--> B2B SaaS ecosystem play? --> PartnerStack

Affiliate Program Launch Checklist

PhaseActionTimeline
Week 1Define commission structure (flat vs. recurring, percentage, tiers)Day 1-3
Week 1Choose and configure affiliate platformDay 3-5
Week 1Create affiliate agreement (terms, payment, clawback, brand guidelines)Day 5-7
Week 2Build affiliate portal: signup page, dashboard, asset libraryDay 8-10
Week 2Create marketing assets: banners, email templates, social copy, landing page copyDay 10-14
Week 3Recruit first 10-20 affiliates from existing customers, advisors, content creatorsDay 15-18
Week 3Send onboarding sequence (welcome, platform walkthrough, first campaign guide)Day 18-21
Week 4Monitor first conversions, adjust tracking if attribution gaps appearDay 22-28
Month 2Analyze top performer patterns, create case study from first successful affiliateDay 30-60
Month 3Scale recruitment, launch tiered commission structure based on performance dataDay 60-90

4. Integration Partnership Strategy

Why Integration Partnerships Win in 2025-2026

Integration partnerships have become the fastest-growing partnership category because they create product-level lock-in, not just commercial relationships. When your product is deeply integrated with a partner's product, joint customers have higher retention, higher NPS, and higher LTV.

Integration Partner Prioritization

Use this scoring model to decide which integrations to build first.

FactorWeightScoring Criteria
Customer overlap30%Crossbeam or manually surveyed overlap. 50+ shared accounts = 100pts, 20-49 = 75pts, 10-19 = 50pts, under 10 = 25pts
Strategic fit25%Adjacent in the workflow (100pts), complementary but separate (60pts), tangential (25pts)
Partner GTM commitment20%Co-marketing budget committed (100pts), willing to co-market (60pts), integration-only (25pts)
Technical feasibility15%API available, under 2 weeks to build (100pts), API available, 2-8 weeks (60pts), no API or 8+ weeks (25pts)
Market signal10%Customers actively requesting (100pts), competitor has it (60pts), nice-to-have (25pts)

Score = Sum of (Factor Weight x Points). Prioritize integrations scoring 70+.

Integration Partner Onboarding Process

Step 1: Discovery Call (Week 1)
  - Validate customer overlap via Crossbeam or manual account mapping
  - Confirm technical feasibility (API docs, sandbox access)
  - Align on GTM commitment level
  |
Step 2: Technical Build (Weeks 2-6)
  - Exchange API credentials and sandbox environments
  - Build integration (bidirectional data flow preferred)
  - QA testing with 2-3 beta customers
  |
Step 3: GTM Launch (Weeks 7-8)
  - Co-authored blog post or case study
  - Joint webinar or demo video
  - Listing in each other's integration directory/marketplace
  - Email announcement to overlapping customer base
  |
Step 4: Ongoing Optimization (Monthly)
  - Monthly partner sync on pipeline and adoption metrics
  - Quarterly co-marketing campaign (webinar, content, joint offer)
  - Annual partnership review with executive sponsors

For integration strategy, marketplace, recruitment, co-marketing, attribution, channel conflict, AI partnerships, operations, and implementation playbook read references/implementation-guide.md.

Examples

  • User says: "We want to start a partner program" → Result: Agent asks current referral/integration usage and margin; recommends model (referral 10–15%, integration 20–25%, solution 30–40%); suggests Rewardful/FirstPromoter for early stage or PartnerStack/Impact for growth; outlines deal registration and 30-day time-to-first-referral target.
  • User says: "How do we recruit integration partners?" → Result: Agent identifies tools customers use daily; recommends API/sandbox readiness and co-marketing budget ($2K–10K/quarter); suggests activation target (20–30% of onboarded) and QBR cadence for Tier 2/3.
  • User says: "Partner revenue is flat" → Result: Agent checks activation rate and top-performer concentration (10–20% drive 80%+); suggests recruiting from existing referrers, tightening enablement, and protected-account limits (e.g. 50); ties to expansion-retention for partner-sourced expansion.

Troubleshooting

  • Low partner activationCause: Onboarding friction or weak incentive. Fix: Time-to-first-referral under 30 days; clear commission and cookie window (90d); enablement kit and deal registration (14d first-mover).
  • Channel conflictCause: Direct and partner competing. Fix: Deal registration and 120-day close window; protected account list; clear conflict rules and comp for overlay.
  • Attribution unclearCause: No CRM field or UTM. Fix: Required UTM on partner links; CRM field for source; report partner-sourced vs partner-influenced; target 15–30% partner-sourced at maturity.

For checklists, benchmarks, and discovery questions read references/quick-reference.md when you need detailed reference.


Related Skills

SkillWhen to Cross-Reference
expansion-retentionWhen designing partner retention incentives and expanding partner-sourced accounts
multi-platform-launchWhen coordinating partner program launch across channels and marketplaces
sales-motion-designWhen aligning partner-sourced leads with your sales process and deal stages
content-to-pipelineWhen building co-marketing content that generates pipeline through partner channels
gtm-metricsWhen measuring partner program ROI, attribution, and revenue contribution
ai-pricingWhen designing commission structures that account for AI model costs and margin
lead-enrichmentWhen enriching partner-referred leads with firmographic and intent data
gtm-engineeringWhen automating partner attribution, deal registration, and commission calculations
positioning-icpWhen ensuring partner messaging aligns with your positioning and targets the right ICP
how to use partner-affiliate

How to use partner-affiliate on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add partner-affiliate
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/tech-leads-club/agent-skills --skill partner-affiliate

The skills CLI fetches partner-affiliate from GitHub repository tech-leads-club/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/partner-affiliate

Reload or restart Cursor to activate partner-affiliate. Access the skill through slash commands (e.g., /partner-affiliate) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.461 reviews
  • Pratham Ware· Dec 24, 2024

    I recommend partner-affiliate for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Hana Rao· Dec 16, 2024

    Keeps context tight: partner-affiliate is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Mateo Martin· Dec 16, 2024

    I recommend partner-affiliate for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mateo Smith· Dec 12, 2024

    Useful defaults in partner-affiliate — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aditi White· Dec 12, 2024

    Solid pick for teams standardizing on skills: partner-affiliate is focused, and the summary matches what you get after install.

  • Xiao Abbas· Dec 4, 2024

    Registry listing for partner-affiliate matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Amelia Kapoor· Nov 23, 2024

    partner-affiliate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Jin Khan· Nov 19, 2024

    partner-affiliate reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sophia Sethi· Nov 7, 2024

    partner-affiliate is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Sophia Reddy· Nov 3, 2024

    We added partner-affiliate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 61

1 / 7