Referral Program (RIPPLE Framework)
Design a referral program with a real viral mechanic - not a "refer a friend" button buried in settings. RIPPLE forces explicit design of who refers, why they refer, what the receiver gets, where the program lives, and how it's measured against a viral coefficient.
Core Principle
Referral programs fail because they optimize for the sender's reward and ignore the receiver's trust. A high-K loop requires both. RIPPLE designs both sides of the exchange and instruments the loop end-to-end.
The RIPPLE Framework
| Letter |
Stage |
The Question |
| R |
Reward Architecture |
What does the referrer get, what does the referee get, and when? |
| I |
Invite Mechanic |
How is the invite sent, and how low-friction is the share? |
| P |
Placement |
Where in the product / journey does the ask appear? |
| P |
Proof |
What social proof and trust signals accompany the invite? |
| L |
Loop Math |
What's the viral coefficient target, and which lever moves it? |
| E |
Evaluate & Defend |
How is fraud, cannibalization, and incremental lift measured? |
Reward Architecture
The most common failure mode is single-sided rewards.
| Type |
Pattern |
Best For |
| Double-sided |
Both referrer and referee get reward |
Most consumer / SMB programs |
| Single-sided (referrer) |
Only referrer rewarded |
Pure-advocacy programs (low conversion lift) |
| Single-sided (referee) |
Only referee rewarded |
When referrer reward feels mercenary (e.g., enterprise) |
| Tiered |
Reward escalates with N successful referrals |
Power-user motivation |
Reward type considerations:
| Reward |
Pros |
Cons |
| Cash / credit |
Simple, easy attribution |
Attracts abuse, low brand lift |
| Product credit |
Reinforces product use |
Less appealing if not active user |
| Account upgrade |
Aligns with retention |
Limited liability cap |
| Cause donation |
High-trust, brand-aligned |
Smaller activation lift |
| Exclusive access |
Status-driven, low cost |
Niche appeal |
Invite Mechanic
Friction is the silent killer of K-factor:
| Lever |
High-Friction |
Low-Friction |
| Channel |
Email-only |
Email + SMS + share link + native share sheet |
| Personalization |
Generic copy |
Pre-filled referrer name + custom note field |
| Tracking |
Manual code |
Auto-attributed unique link |
| Recipient onboarding |
Standard signup |
Landing page with referrer context |
Placement
Placement determines who sees the ask and when.
| Placement |
When It Works |
| Post-aha moment |
After the first clear value event - referrer is intrinsically motivated |
| Account / settings page |
Permanent home, low discoverability |
| Email lifecycle |
Anniversary, milestone, or NPS positive |
| In-app banner |
High visibility; must be dismissible |
| CSM / sales triggered |
B2B; manual but high quality |
Loop Math
| Metric |
Definition |
Target |
| Referral rate |
% of eligible customers who refer at least once in window |
5-15% strong |
| Invites per referrer |
Average invites sent by active referrer |
3-8 strong |
| Conversion rate |
% of invitees who become customers |
5-25% varies by motion |
| K-factor |
Referral rate × Invites × Conversion |
> 1.0 = self-sustaining loop |
| Cycle time |
Days from invite to converted referee |
Shorter = faster compounding |
Fraud & Cannibalization Controls
| Risk |
Control |
| Self-referral |
Device / IP / payment-instrument matching |
| Fake account farms |
Rate limits + manual review thresholds |
| Reward abuse |
Cap rewards per referrer per window |
| Cannibalization |
Match referrer-influenced cohort against organic; measure incrementality |
| Channel arbitrage |
Block paid-media referrers if program is meant for organic |
Output
Save to outputs/referral-program-[motion]-[YYYY-MM-DD].md
| Artifact |
Description |
| Reward Design |
Sender + receiver rewards, tier escalation, liability cap |
| Invite Spec |
Channels, copy, personalization, tracking |
| Placement Map |
Where the ask appears across product / lifecycle |
| Loop Math Model |
K-factor projection with sensitivity analysis |
| Fraud Controls |
Detection rules and reward holds |
| Attribution Spec |
Tracking schema, incrementality test design |
| KPIs Dashboard |
Referral rate, invites/referrer, conversion, K-factor, fraud rate |
Process
- Pick reward architecture with sender + receiver explicit
- Strip friction from the invite mechanic; benchmark every step
- Place the ask at intrinsic-motivation moments (post-aha is gold)
- Add proof - testimonials, "X people have invited friends," referrer endorsement
- Model the loop math with sensitivities; identify the binding constraint
- Instrument fraud and incrementality before launching, not after
Tips
- K-factor < 1 is fine if it lowers blended CAC; don't only chase virality
- Reward at successful action, not invite, to align with revenue
- Run a holdout to prove incrementality - most teams skip this
- Refresh rewards quarterly; novelty drives participation
- B2B referrals often work better as advocacy plays than cash bounties
Pairs With
- customer-advocacy - Top advocates are the highest-K referrers
- community-catalyst - Communities amplify referral loops
- loyalty-lifecycle - Tiered status integrates with referral milestones
- demand-engine - Channel mix that promotes the program
1---2name: referral-program3description: Referral program design - referrer / referee incentive structure, viral mechanics, fraud and abuse controls, attribution, and channel placement. Use when: referral program, refer a friend, viral loop design, K-factor, advocacy referrals, partner referrals, customer referral incentives, referral attribution, viral coefficient.4---56# Referral Program (RIPPLE Framework)78Design a referral program with a real viral mechanic - not a "refer a friend" button buried in settings. RIPPLE forces explicit design of who refers, why they refer, what the receiver gets, where the program lives, and how it's measured against a viral coefficient.910## Core Principle1112**Referral programs fail because they optimize for the *sender's* reward and ignore the *receiver's* trust.** A high-K loop requires both. RIPPLE designs both sides of the exchange and instruments the loop end-to-end.1314## The RIPPLE Framework1516| Letter | Stage | The Question |17|--------|-------|--------------|18| **R** | Reward Architecture | What does the referrer get, what does the referee get, and when? |19| **I** | Invite Mechanic | How is the invite sent, and how low-friction is the share? |20| **P** | Placement | Where in the product / journey does the ask appear? |21| **P** | Proof | What social proof and trust signals accompany the invite? |22| **L** | Loop Math | What's the viral coefficient target, and which lever moves it? |23| **E** | Evaluate & Defend | How is fraud, cannibalization, and incremental lift measured? |2425## Reward Architecture2627The most common failure mode is **single-sided** rewards.2829| Type | Pattern | Best For |30|------|---------|----------|31| **Double-sided** | Both referrer and referee get reward | Most consumer / SMB programs |32| **Single-sided (referrer)** | Only referrer rewarded | Pure-advocacy programs (low conversion lift) |33| **Single-sided (referee)** | Only referee rewarded | When referrer reward feels mercenary (e.g., enterprise) |34| **Tiered** | Reward escalates with N successful referrals | Power-user motivation |3536Reward type considerations:3738| Reward | Pros | Cons |39|--------|------|------|40| **Cash / credit** | Simple, easy attribution | Attracts abuse, low brand lift |41| **Product credit** | Reinforces product use | Less appealing if not active user |42| **Account upgrade** | Aligns with retention | Limited liability cap |43| **Cause donation** | High-trust, brand-aligned | Smaller activation lift |44| **Exclusive access** | Status-driven, low cost | Niche appeal |4546## Invite Mechanic4748Friction is the silent killer of K-factor:4950| Lever | High-Friction | Low-Friction |51|-------|---------------|--------------|52| **Channel** | Email-only | Email + SMS + share link + native share sheet |53| **Personalization** | Generic copy | Pre-filled referrer name + custom note field |54| **Tracking** | Manual code | Auto-attributed unique link |55| **Recipient onboarding** | Standard signup | Landing page with referrer context |5657## Placement5859Placement determines who sees the ask and when.6061| Placement | When It Works |62|-----------|---------------|63| **Post-aha moment** | After the first clear value event - referrer is intrinsically motivated |64| **Account / settings page** | Permanent home, low discoverability |65| **Email lifecycle** | Anniversary, milestone, or NPS positive |66| **In-app banner** | High visibility; must be dismissible |67| **CSM / sales triggered** | B2B; manual but high quality |6869## Loop Math7071| Metric | Definition | Target |72|--------|------------|--------|73| **Referral rate** | % of eligible customers who refer at least once in window | 5-15% strong |74| **Invites per referrer** | Average invites sent by active referrer | 3-8 strong |75| **Conversion rate** | % of invitees who become customers | 5-25% varies by motion |76| **K-factor** | Referral rate × Invites × Conversion | > 1.0 = self-sustaining loop |77| **Cycle time** | Days from invite to converted referee | Shorter = faster compounding |7879## Fraud & Cannibalization Controls8081| Risk | Control |82|------|---------|83| **Self-referral** | Device / IP / payment-instrument matching |84| **Fake account farms** | Rate limits + manual review thresholds |85| **Reward abuse** | Cap rewards per referrer per window |86| **Cannibalization** | Match referrer-influenced cohort against organic; measure incrementality |87| **Channel arbitrage** | Block paid-media referrers if program is meant for organic |8889## Output9091Save to `outputs/referral-program-[motion]-[YYYY-MM-DD].md`9293| Artifact | Description |94|----------|-------------|95| **Reward Design** | Sender + receiver rewards, tier escalation, liability cap |96| **Invite Spec** | Channels, copy, personalization, tracking |97| **Placement Map** | Where the ask appears across product / lifecycle |98| **Loop Math Model** | K-factor projection with sensitivity analysis |99| **Fraud Controls** | Detection rules and reward holds |100| **Attribution Spec** | Tracking schema, incrementality test design |101| **KPIs Dashboard** | Referral rate, invites/referrer, conversion, K-factor, fraud rate |102103## Process1041051. **Pick reward architecture** with sender + receiver explicit1062. **Strip friction** from the invite mechanic; benchmark every step1073. **Place the ask** at intrinsic-motivation moments (post-aha is gold)1084. **Add proof** - testimonials, "X people have invited friends," referrer endorsement1095. **Model the loop math** with sensitivities; identify the binding constraint1106. **Instrument fraud and incrementality** before launching, not after111112## Tips1131141. **K-factor < 1 is fine** if it lowers blended CAC; don't only chase virality1152. **Reward at successful action**, not invite, to align with revenue1163. **Run a holdout** to prove incrementality - most teams skip this1174. **Refresh rewards** quarterly; novelty drives participation1185. **B2B referrals** often work better as advocacy plays than cash bounties119120## Pairs With121122- **customer-advocacy** - Top advocates are the highest-K referrers123- **community-catalyst** - Communities amplify referral loops124- **loyalty-lifecycle** - Tiered status integrates with referral milestones125- **demand-engine** - Channel mix that promotes the program
varunk130