Skip to content

indranilbanerjee/digital-marketing-pro / skills/growth-engineering

growth-engineering

Verified

Engineer growth systems: PLG motions, referrals, viral and retention loops. "design a referral program"

FileKindSize
SKILL.mdskill md16.6 KB
affiliate-marketing.mdmarkdown15.0 KB
experimentation-frameworks.mdmarkdown20.6 KB
launch-strategy.mdmarkdown12.0 KB
product-led-growth.mdmarkdown8.4 KB
referral-systems.mdmarkdown10.5 KB
retention-loops.mdmarkdown13.2 KB
viral-loops.mdmarkdown10.9 KB

referral-systems.md

View on GitHub
# Referral Systems — Program Design & Optimization

> A structured referral program turns satisfied customers into a scalable, low-CAC acquisition channel. The best programs align incentives for both referrer and referee.

---

## Referral Program Templates

### Template Comparison

| Model | How It Works | Best For | Example |
|---|---|---|---|
| Double-Sided | Both referrer and referee get rewarded | SaaS, fintech, marketplaces | Dropbox — both get extra storage |
| Single-Sided (Referrer) | Only the referrer is rewarded | High-consideration purchases | Amex — referrer gets bonus points |
| Single-Sided (Referee) | Only the new user gets a benefit | Low-friction trials, e-commerce | "Give your friend $20 off" |
| Tiered | Rewards escalate with number of referrals | Community-driven products | Morning Brew — unlock swag at milestones |
| Milestone | Unlock rewards at specific referral counts | Waitlist and launch campaigns | Harry's pre-launch — 5, 10, 25, 50 referral tiers |
| Leaderboard | Top referrers win premium rewards | Time-bound campaigns, contests | Launch competitions with grand prizes |
| Embedded / Native | Referral is built into the product UX | Collaboration and network tools | Calendly — every link is a referral |

### Double-Sided Program Design

```
Referrer Action → Unique Link/Code Generated → Referee Signs Up →
Referee Qualifies (activation event) → Both Parties Rewarded
```

| Component | Decision | Recommendation |
|---|---|---|
| Referrer reward | Cash, credit, free months, points | Match to what users already value in your product |
| Referee reward | Discount, extended trial, bonus | Remove friction for first purchase/activation |
| Qualification event | Sign-up, activation, purchase, retention | Tie to meaningful value moment, not just registration |
| Reward timing | Instant vs delayed | Instant for referrer motivation; delayed for fraud prevention |
| Cap per referrer | Unlimited vs capped | Cap at 10-20 initially; raise for power referrers |

---

## Incentive Design Principles

### Reward Type Selection

| Reward Type | Pros | Cons | Best For |
|---|---|---|---|
| Account credit | High perceived value, keeps users in ecosystem | No value if user churns | SaaS, platforms |
| Cash / gift cards | Universally appealing, easy to understand | Expensive, attracts fraud | Fintech, high-ACV products |
| Free months | Low marginal cost, extends retention | Only valuable if user is paying | Subscription products |
| Feature unlocks | Zero marginal cost, drives engagement | Limited appeal if features aren't compelling | Freemium products |
| Physical goods / swag | Tangible, shareable, social proof | Logistics complexity, cost | Brand-driven companies |
| Charitable donation | Aligns with values, positive brand | Lower direct motivation | Mission-driven brands |

### Incentive Calibration Checklist

- [ ] Reward value is 10-25% of customer LTV (ensures positive ROI)
- [ ] Reward is immediately understandable (no complex calculations)
- [ ] Reward matches user motivation (intrinsic vs extrinsic)
- [ ] Double-sided rewards are roughly balanced (neither party feels shortchanged)
- [ ] Escalating rewards exist for power referrers (5+ successful referrals)
- [ ] Reward fulfillment is automated (no manual approval bottleneck)
- [ ] Tax implications are documented for cash rewards above reporting thresholds
- [ ] Reward expiration policy is clearly communicated

---

## Referral Mechanics

### Tracking Infrastructure

| Mechanism | How It Works | Strengths | Weaknesses |
|---|---|---|---|
| Unique referral link | URL with referrer ID parameter | Easy to share, trackable | Can be lost if user clears cookies |
| Referral code | Alphanumeric code entered at sign-up | Works offline, memorable | Requires manual entry, friction |
| Email invite | Direct email sent from product | High intent signal, personalized | Limited reach vs social sharing |
| In-app invite | Share directly within product UI | Contextual, low friction | Requires active product usage |
| QR code | Scannable code linking to referral URL | Works for physical/event contexts | Niche use case |

### Link Architecture

```
https://yourapp.com/invite?ref=USER_ID&campaign=CAMPAIGN_NAME

Parameters tracked:
- ref: unique referrer identifier
- campaign: which referral program variant
- channel: where the link was shared (email, social, direct)
- timestamp: when the link was generated
```

### Attribution Rules

| Scenario | Recommended Rule |
|---|---|
| Multiple referral links clicked | Last-click attribution within 30-day window |
| Referral link + paid ad touchpoint | Referral takes priority (reward the advocate) |
| User signs up without link but enters code | Code attribution honored |
| Cookie expires before conversion | No attribution (extend cookie to 90 days) |
| Referred user already exists in system | No reward (de-duplicate on email) |

---

## Fraud Prevention Tactics

### Common Fraud Patterns

| Fraud Type | Description | Detection Method |
|---|---|---|
| Self-referral | User creates multiple accounts to refer themselves | IP matching, device fingerprinting, email domain analysis |
| Referral rings | Groups of users refer each other in circles | Network graph analysis, timestamp clustering |
| Incentive abuse | Users sign up solely for the reward, then churn | Require activation event before reward; monitor 7-day retention |
| Bot-generated signups | Automated account creation to claim rewards | CAPTCHA, behavioral analysis, signup velocity monitoring |
| Fake email accounts | Disposable emails used for referee accounts | Block disposable email domains, require email verification |

### Fraud Prevention Checklist

- [ ] Require a meaningful activation event before issuing rewards (not just sign-up)
- [ ] Implement device fingerprinting to detect multi-accounting
- [ ] Set velocity limits (max 5 referrals per day, 20 per week)
- [ ] Block known disposable email domains
- [ ] Hold rewards for 7-14 day cooling period before payout
- [ ] Monitor referral-to-activation ratio by referrer (flag if <20%)
- [ ] Review top referrers manually each month
- [ ] Build an automated flagging system for anomalous patterns
- [ ] Include anti-fraud terms in referral program T&Cs
- [ ] Reserve the right to revoke rewards retroactively

---

## Launch Playbook

### Pre-Launch (2-4 Weeks Before)

| Week | Action | Owner |
|---|---|---|
| -4 | Define program goals, KPIs, and budget | Growth / Marketing |
| -4 | Select referral platform or build in-house tracking | Engineering |
| -3 | Design reward structure and fraud prevention rules | Growth / Finance |
| -3 | Create referral landing page and email templates | Design / Content |
| -2 | Build referral dashboard (referrer view + admin view) | Engineering |
| -2 | Write program terms and conditions | Legal / Marketing |
| -1 | QA referral flow end-to-end (link generation → reward fulfillment) | QA |
| -1 | Seed program with 50-100 power users for soft launch | Growth |

### Launch Day Checklist

- [ ] Referral widget or page is live in product
- [ ] Triggered email sent to top 20% most active users announcing program
- [ ] In-app notification or banner promoting referral program
- [ ] Social media announcement with shareable assets
- [ ] Support team briefed on program details and FAQ
- [ ] Analytics dashboards confirmed working (referrals, conversions, rewards)
- [ ] Fraud monitoring active and alerting configured
- [ ] Referral link generation tested across all platforms (web, mobile, email)

### Post-Launch (First 30 Days)

| Day | Action |
|---|---|
| 1-3 | Monitor conversion rates, fix broken flows, address support tickets |
| 7 | First performance review — referral rate, share rate, conversion rate |
| 14 | A/B test reward messaging and CTA placement |
| 21 | Identify and engage top referrers with personalized outreach |
| 30 | Full program review — ROI analysis, fraud audit, optimization plan |

---

## Benchmarks

### Key Metrics

| Metric | Formula | Good | Great | Elite |
|---|---|---|---|---|
| Referral Rate | Referrers / Total active users | 2-5% | 5-15% | 15%+ |
| Share Rate | Users who share link / Users who see referral prompt | 10-15% | 15-25% | 25%+ |
| Invite Conversion Rate | Referred sign-ups / Total invites sent | 5-10% | 10-20% | 20%+ |
| K-Factor | Invites per user x conversion rate | 0.1-0.3 | 0.3-0.7 | 0.7+ |
| CAC Reduction | (Standard CAC - Referral CAC) / Standard CAC | 30-50% | 50-70% | 70%+ |
| Referral LTV vs Organic LTV | Referred user LTV / Organic user LTV | 1.0x | 1.1-1.25x | 1.25x+ |
| Time to Referral | Median days from sign-up to first referral | 30-60 days | 14-30 days | <14 days |

### K-Factor Calculation

```
K = i × c

Where:
  i = average number of invites sent per user
  c = conversion rate of those invites

Example:
  Each user sends 5 invites, 10% convert → K = 5 × 0.10 = 0.5
  (Each user brings 0.5 new users — not viral, but contributes to growth)
```

---

## Integration Points

### Where to Surface Referrals in the Product

| Touchpoint | Timing | Why It Works |
|---|---|---|
| Post-activation prompt | After user completes key action | User just experienced value — peak motivation |
| Settings / Account page | Persistent, always accessible | Power users seek it out |
| Post-purchase confirmation | After payment or upgrade | Buyer's high — social proof motivation |
| Share / Export flow | When user shares content externally | Natural sharing moment, embedded referral |
| Milestone celebrations | After achievement or usage milestone | Emotional high, gratitude response |
| NPS follow-up | After user rates 9-10 on NPS | Promoters are pre-qualified referrers |
| Billing / invoice page | During renewal or plan review | Budget-conscious moment, credit appeals |
| Help / Support resolution | After successful support interaction | Gratitude and relief drive advocacy |

### Tech Stack Considerations

| Approach | Pros | Cons | Best For |
|---|---|---|---|
| In-house build | Full control, deep integration | Engineering time, maintenance burden | Products with unique referral mechanics |
| Referral SaaS (ReferralCandy, Friendbuy) | Fast to launch, proven UX | Monthly cost, limited customization | E-commerce, standard programs |
| Affiliate platform (Impact, PartnerStack) | Scales to partners + affiliates | Complexity, cost | B2B SaaS with partner channels |
| CRM integration (HubSpot, Salesforce) | Links referrals to sales pipeline | Requires CRM maturity | Sales-assisted referral programs |

---

*The best referral programs don't feel like marketing programs. They feel like one friend helping another discover something valuable. Design for that.*
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall