referral-program
# ClaudeWave Entry: referral-program The referral-program skill guides strategy for referral initiatives in AI and SaaS products, covering reward structures, mechanism types like link-based and code-based systems, and tracking methods. Use this skill when users ask about implementing or optimizing referral programs, refer-a-friend campaigns, referral incentives, or leveraging existing users for growth, particularly in overseas markets where referral programs are essential rather than optional.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/referral-program && cp -r /tmp/referral-program/skills/channels/partnerships/referral-program ~/.claude/skills/referral-programSKILL.md
# Channels: Referral Guides referral program strategy for AI/SaaS products. Leverage existing users to drive growth; 3%-5% conversion vs 1%-2% for ads; CAC 50%-70% lower; referred users LTV 30%-50% higher, retention 20%-30% higher. Referral is necessity in overseas markets, not alternative. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and value proposition. Identify: 1. **Product type**: SaaS, AI tool, subscription 2. **User base**: Size, engagement, retention 3. **Goal**: Signups, purchases, or both ## Referral vs. Affiliate vs. Influencer | Dimension | Referral | Affiliate | Influencer | |-----------|----------|-----------|------------| | **Who** | Existing users | Professional promoters | KOLs | | **Incentive** | Discounts, credits | Commission | Fees, product | | **Barrier** | Low (all users) | Medium | High | | **Conversion** | 3%-5% | Varies | Varies | **Referral vs affiliate**: Referral needs no landing page or application; integrated in dashboard. Affiliate requires landing page and approval. ## Reward Models | Model | Use | |-------|-----| | **Two-way** | Both referrer and referee get rewards; highest participation | | **One-way** | Only referrer rewarded; cost control | | **Tiered** | Rewards increase with referral count (e.g. $10 for 1-5, $15 for 6-10, $20 for 11+); incentivizes volume | **Benchmark**: Rewards typically 10%-30% of product price; ~11% off or ~$21 value; weak incentives = low participation. Triggers: signup, purchase, activation, or sustained use. ## Mechanism Types | Type | Use | |------|-----| | **Link-based** | Unique referral link; easy to implement; accurate tracking; share via email, social, SMS; works for web and app | | **Code-based** | Referral code (e.g. FRIEND20); memorable; offline events; mobile-friendly input | | **Social referral** | Share buttons (Facebook, X, LinkedIn); viral spread; friend trust; young users | ## Tracking & Attribution | Method | Use | |-------|-----| | **Cookie** | Web apps; 30-90 day window | | **URL params** | All platforms; persistent in link | | **Referral code** | Mobile, offline; manual entry | | **Account association** | Long-term tracking; subscription products | **Attribution window**: 30-90 days typical; 180 days for subscription. First-touch attribution to avoid double-counting. ## Fraud Prevention | Risk | Action | |------|--------| | **Self-referral** | Detect same device, payment, IP | | **Fake accounts** | Validate email, payment; monitor patterns | | **Bulk/automation** | Rate limits; anomaly detection | | **Per-user cap** | e.g. Max 10 referrals per user | Use tool anti-fraud features; audit referrals regularly. ## Design Framework 1. **Reward structure**: Type (cash, discount, credits, free service); amount (10%-30% of price); trigger; cap 2. **Tracking**: Choose method; set attribution window; first-touch rule 3. **UX**: One-click share; clear rules; dashboard with referral data; notify on success 4. **Fraud prevention**: See above 5. **Monitor & optimize**: Referral rate, conversion, CAC, LTV; A/B test rewards and flow ## Best Practices - **Run multiple programs**: Target different audiences, stages, goals - **Tiered rewards**: Motivate top performers; progressive incentives - **Friction-free sharing**: Mobile-friendly; one-click share - **Time-boxed incentives**: "Refer this week for $15 off" creates urgency - **Placement**: Web, email, app, in-product touchpoints; dashboard integration primary ## Implementation | Approach | Use | |----------|-----| | **Self-build** | Full control; low cost; URL params or cookie + reward logic + fraud checks; open-source (e.g. RefRef) for faster start | | **Third-party** | Fast launch; Cello, Viral Loops, ReferralCandy (e-commerce), Impact (enterprise); monthly fee | **Placement**: Most programs integrate in product dashboard; no landing page or application needed. Optional landing page for value prop, rewards, and case studies. **Startup cost**: Typically hundreds for tools + dev. ## Tools | Tool | Use | |------|-----| | **Cello** | SaaS; AI-driven automation | | **Viral Loops** | Referral + waitlist + contests | | **ReferralCandy** | Shopify, e-commerce | | **Impact** | Enterprise; unified platform | | **RefRef** | Open-source; self-hosted | ## KPIs Referral rate, conversion, CAC, LTV of referred users, referred-user retention. ## Output Format - **Reward model** and mechanism type (link/code/social) - **Tracking** approach and attribution window - **Placement** (dashboard vs landing page) - **Fraud prevention** measures - **Tool** selection (self-build vs third-party) - **KPI** framework ## Related Skills - **discount-marketing-strategy**: Referral rewards (discounts, credits); 10–30% benchmark; campaign design - **affiliate-marketing**: Different audience; can run both - **influencer-marketing**: Brand building vs. user-driven growth - **directory-submission**: Directory submission for discovery; referral for user-driven growth - **analytics-tracking**: Referral link tracking, UTM
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.