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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
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.
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
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
Recruit first 10-20 affiliates from existing customers, advisors, content creators
Day 15-18
Week 3
Send onboarding sequence (welcome, platform walkthrough, first campaign guide)
Day 18-21
Week 4
Monitor first conversions, adjust tracking if attribution gaps appear
Day 22-28
Month 2
Analyze top performer patterns, create case study from first successful affiliate
Day 30-60
Month 3
Scale recruitment, launch tiered commission structure based on performance data
Day 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.
Factor
Weight
Scoring Criteria
Customer overlap
30%
Crossbeam or manually surveyed overlap. 50+ shared accounts = 100pts, 20-49 = 75pts, 10-19 = 50pts, under 10 = 25pts
Strategic fit
25%
Adjacent in the workflow (100pts), complementary but separate (60pts), tangential (25pts)
Partner GTM commitment
20%
Co-marketing budget committed (100pts), willing to co-market (60pts), integration-only (25pts)
Technical feasibility
15%
API available, under 2 weeks to build (100pts), API available, 2-8 weeks (60pts), no API or 8+ weeks (25pts)
Market signal
10%
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
5. Marketplace and Directory Strategy
Building a marketplace or listing in partner marketplaces creates compounding distribution. Salesforce AppExchange has over 7,000 apps with 10M+ installs. Atlassian Marketplace has 5,000+ integrations and pushed $4B in lifetime sales by 2024.
Marketplace Decision Framework
Strategy
When to Use
Expected Outcome
Investment Level
List on partner marketplaces
You integrate with established platforms
Inbound leads from marketplace discovery
Low - marketing asset creation
Build your own marketplace
You are a platform with 10+ integrations
Partner ecosystem creates competitive moat
High - engineering + partner management
App store listing
Your product extends a major platform (Salesforce, HubSpot, Shopify)
Distribution through the platform's customer base
Medium - listing development + maintenance
Marketplace Listing Optimization
Element
Best Practice
Title
Include the primary use case, not just your product name. "[Product]: [Use Case] for [Platform]"
Description
Lead with the outcome, not the feature. First 160 characters appear in search results.
Screenshots
Show the integration in action within the partner platform, not your standalone UI
Reviews
Proactively ask joint customers to leave reviews within 7 days of integration activation
Categories
List in every relevant category the marketplace allows. More categories = more discovery.
Pricing
Free tier or free trial converts 3-5x better than paid-only listings
Building Your Own Integration Directory
If you have 5+ integrations, build a public integration directory. This serves three purposes: SEO (integration pages rank for "[partner] + [your category]" searches), social proof (prospects see their stack is supported), and partner recruitment (potential partners see the ecosystem and want to join).
Minimum viable integration directory structure:
/integrations (landing page with search/filter)
/integrations/[partner-name] (individual integration page)
- What it does (2-3 sentences)
- How it works (data flow diagram)
- Setup instructions (link to docs)
- Joint customer quote
- CTA: "Connect [Partner] to [Your Product]"
6. Partner Recruitment and Activation
The Recruitment Funnel
Most partner programs fail at activation, not recruitment. Signing partners is easy. Getting them to generate their first referral is hard. Focus your energy on activation metrics, not partner count.
Stage
Target Metric
Benchmark
Identified
Total addressable partner list
100-500 potential partners
Recruited
Partners who signed up
30-40% of identified
Onboarded
Partners who completed setup (tracking link, portal access)
60-70% of recruited
Activated
Partners who generated first referral or lead
20-30% of onboarded
Performing
Partners generating 3+ referrals per quarter
10-15% of activated
Top performers
Partners in top 10% by revenue
2-5 partners driving 50%+ of partner revenue
The 80/20 rule holds: expect 10-20% of partners to drive 80%+ of partner-sourced revenue.
Recruitment Channels by Partner Type
Partner Type
Best Recruitment Channel
Approach
Existing customers
In-app prompt + email campaign
"You already get results, earn by sharing"
Content creators / influencers
Direct outreach based on content alignment
"We love your content on [topic], here is how we can work together"
Complementary SaaS companies
Crossbeam overlap analysis + warm intro
"We share 47 customers, let us formalize this"
Consultants / agencies
Industry events + LinkedIn outreach
"Your clients already need this, earn recurring revenue"
System integrators
RFP responses + executive networking
"We want you in our recommended implementation partners"
Activation Sequence
The first 14 days after signup determine whether a partner will ever generate revenue. Use an automated sequence to drive first action.
Day
Action
Channel
Goal
0
Welcome email with portal login and quick-start guide
Email
Confirm setup
1
Video walkthrough: "Generate your first referral in 10 minutes"
Email + portal
Show the path to first commission
3
Share top-performing partner case study
Email
Social proof that the program works
5
Check-in: "Have you shared your link yet?" with templated social posts
Partial commission (25-50% of sourced rate) or bonus
Attribution Decision Tree
Did the partner introduce the lead?
|
+--> YES: Was the lead in your CRM before partner contact?
| |
| +--> NO --> PARTNER-SOURCED (100% credit)
| +--> YES --> Was the lead actively engaged with sales?
| |
| +--> NO (dormant/stale) --> PARTNER-SOURCED (100% credit)
| +--> YES (active opp) --> PARTNER-INFLUENCED (partial credit)
|
+--> NO: Did the partner contribute to the deal?
|
+--> YES (demo, reference, co-sell) --> PARTNER-INFLUENCED (partial credit)
+--> NO --> NO PARTNER CREDIT
Attribution Windows
Event Type
Lookback Window
Rationale
Referral link click to signup
90 days
Cookie-based, covers longer B2B sales cycles
Deal registration to close
120 days
Protects partner investment in the pipeline
Partner-influenced touchpoint
90 days before close
Must be within active deal cycle
Renewal attribution
Partner retains credit for customer lifetime if ongoing engagement
Incentivizes partner retention involvement
Metrics to Track
Metric
Definition
Target Benchmark
Partner-sourced revenue
Revenue from deals where partner was first touch
15-30% of total revenue at maturity
Partner-influenced revenue
Revenue from deals where partner contributed but was not first touch
10-20% of total revenue
Partner-sourced pipeline
Open pipeline from partner referrals
2-3x of partner-sourced revenue target
Partner attach rate
% of deals with at least one partner touchpoint
30-50% at maturity
Partner activation rate
% of signed partners who generated at least one lead
20-30%
Average partner revenue
Revenue per active partner per quarter
Varies by tier - track trend
Time to first referral
Days from partner signup to first qualified lead
Under 30 days for referral partners
Partner-sourced win rate
Close rate on partner-sourced deals vs. direct
Partner-sourced should be 1.5-2x higher
9. Channel Conflict Management
Channel conflict kills partner programs faster than bad economics. Prevent it with clear rules, not retroactive arbitration.
Common Conflict Types
Conflict Type
Description
Prevention
Partner vs. direct sales
Your sales team and a partner pursue the same account
Deal registration system with 14-day first-mover protection
Partner vs. partner
Two partners claim the same deal
Account mapping via Crossbeam, territory or vertical assignment
Pricing conflict
Partner offers discount your direct channel does not
Protected accounts are excluded from direct outbound for the quarter
Protection requires active pipeline movement - stale protected accounts lose protection at quarterly review
No partner can protect more than 50 accounts simultaneously
Pricing Rules:
All partners sell at published pricing. No unauthorized discounts.
Partners may offer their own services (implementation, consulting) at any price
Bundle pricing with partner services requires approval from partner manager
MAP violations result in written warning (first), commission hold (second), program removal (third)
10. AI-Specific Partnership Models
Partnership Categories in the AI Stack
Partnership Type
Your Role
Partner Role
Revenue Model
Example
Model provider
Application layer
Provides underlying AI model
API usage fees, revenue share on model costs
Your app uses OpenAI/Anthropic, negotiate volume pricing
Data partner
Application layer
Provides training or enrichment data
Data licensing, per-query pricing
Your AI product uses industry-specific data sets
Infrastructure partner
Application layer
Provides compute/hosting
Cloud credits, co-sell referrals
Joint GTM with AWS, GCP, or Azure
Vertical solution partner
Platform
Builds vertical solutions on your platform
Revenue share on vertical customers
Partner builds "AI for healthcare billing" on your platform
Distribution partner
Application layer
Embeds your AI in their product
Per-seat or per-API-call embed pricing
CRM vendor embeds your AI writing assistant
AI Partnership Pricing Models
Model
Structure
When to Use
Risk
Per-API-call revenue share
Partner earns % of API revenue from their referred users
High-volume, low-ACV integrations
Revenue unpredictability
Flat referral fee
Fixed payment per referred customer
Simple referral relationships
Under-compensates for high-value referrals
Recurring revenue share
Partner earns % of customer MRR for lifetime
Deep integration partnerships
Margin compression on thin-margin AI products
Outcome-based split
Revenue shared based on measurable outcome delivered
Joint solutions with quantifiable ROI
Complex attribution and measurement
Embed licensing
Partner pays per-seat or per-call to embed your AI
OEM/white-label relationships
Partner controls the customer relationship
AI-Specific Partnership Considerations
Factor
Impact on Partnership Design
Model cost passthrough
AI products have variable COGS. Commission structures must account for model API costs. A 30% revenue share on a product with 40% model costs leaves 30% gross margin.
Data sharing agreements
AI partnerships often require data exchange. Define data ownership, usage rights, and privacy compliance upfront.
Model version dependencies
Partner integrations may depend on specific model versions. Establish SLAs for model change notifications (minimum 30 days).
Accuracy guarantees
Partners selling your AI solution need confidence in output quality. Provide accuracy benchmarks by use case.
Compliance requirements
Enterprise AI partnerships require SOC2, GDPR, and increasingly AI-specific compliance (EU AI Act). Build compliance into the partner onboarding checklist.
11. Partner Program Operations
PRM Tool Selection
Tool Category
Options
Purpose
Partner Relationship Management
PartnerStack, Allbound, Channeltivity, Impartner
Central hub for partner portal, deal registration, content sharing
Account Mapping
Crossbeam, Reveal
Identify overlapping customers and prospects between you and partners
Attribution Tracking
Impact.com, PartnerStack, FirstPromoter
Track referrals, clicks, conversions, and commission payouts
Co-Selling Coordination
Crossbeam, Tackle (for cloud marketplaces)
Coordinate joint selling on specific accounts
Partner Enablement
WorkRamp, Seismic, partner portal
Training, certification, asset distribution
Quarterly Business Review (QBR) Template
Run QBRs with Tier 2 and Tier 3 partners quarterly. Keep them to 45 minutes.
Section
Time
Content
Performance review
10 min
Revenue sourced, pipeline generated, deals closed, leads referred
Account mapping update
10 min
New overlapping accounts, joint opportunity identification
Co-marketing review
10 min
Campaigns run, results, next quarter plan
Product roadmap preview
5 min
Upcoming features relevant to the partnership
Action items and commitments
10 min
Specific deliverables with owners and deadlines
Partner Program Maturity Model
Stage
Timeline
Partner Count
Revenue Contribution
Key Activities
Foundation
Months 0-6
5-20 partners
Under 5% of revenue
Launch affiliate program, sign first integration partners, build partner portal
Growth
Months 6-18
20-100 partners
5-15% of revenue
Tier structure live, co-marketing running, deal registration working
