partner-affiliate
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.
What this skill does
# 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 | 15% of month-1 revenue, or 10% recurring for 12 months | 20% recurring for customer lifetime | 30-40% recurring for customer lifetime | | Annual subscription | 10-15% of first-year ACV | 20-25% of ACV, renewed annually | 30-40% of ACV, renewed annually | | Usage-based | 10% of first 12 months usage | 20% of ongoing usage | 30% of ongoing usage | | Outcome-based | 10% of first outcome payment | 20% of ongoing outcome payments | 35% of ongoing outcome payments | ### Clawback and Protection Policies | Policy | Referral Tier | Integration Tier | Solution Tier | |---|---|---|---| | Clawback window | 60 days | 90 days | None | | Customer churn trigger | Full commission returned | Pro-rated return | No return, partner helps with retention | | Deal overlap resolution | First-touch attribution | Multi-touch with registration priority | Joint pipeline, split credit | | Direct sale overlap | Partner loses if deal registered after direct contact | Deal registration within 14 days protects partner | Protected account list reviewed quarterly | --- ## 3. Affiliate Program Design and Tooling ### Platform Selection Framework | Platform | Best For | Pricing (Starting) | Key Strengths | Limitations | |---|---|---|---|---| | PartnerStack | B2B SaaS, multi-partner-type programs | Custom (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.com | Enterprise, large-scale affiliate programs | Custom (enterprise) | Vast partner network, granular attribution, custom recurring commissions. | Steep learning curve. Requires dedicated admin. | | Rewardful | Early-stage SaaS, Stripe-first companies | $49/month | Fast Stripe integration, simple setup, affordable. 30+ integrations. | No built-in email automation. Limited as programs scale. | | FirstPromoter | Growth-stage SaaS, MRR-focused teams | $99/month | Strong recurring billing tracking, 18+ d
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.