Engineer the Loop: Building a Referral Program from Trigger to Incentive
Objective: Design a complete referral loop, trigger, mechanic, and incentive, for a real product scenario, instead of leaving word-of-mouth to chance.
Warby Parker's home try-on program has high satisfaction but almost no structured referral flow. You're asked to design one before the next quarter's growth review.
Referral doesn't happen by accident. Specify exactly when you ask, what gets shared, and why someone would bother sharing it.
Before you start
What you'll need
Free path (everything below is enough to finish)
Enough structure to force all three components to be filled in before calling it done
The process
1 step
Step 01 of 01
The lesson names three required components of a real referral loop: a trigger (when you ask), a mechanic (what gets shared), and an incentive (why someone shares it). Missing any one of the three means the loop won't run.
Warby Parker's home try-on box arrives, the customer picks their favorite pair, and orders it. At what exact moment should the referral ask fire, and what should the customer actually share?
Procedure
- Row 1, Trigger: pick the moment of peak satisfaction, right after the customer completes checkout on their favorite pair from the try-on box, not at delivery or account creation
- Row 2, Mechanic: define exactly what gets shared, a personal referral link plus a photo of the customer's chosen frame, not a generic 'invite friends' button
- Row 3, Incentive: specify a two-sided reward, $20 off for the friend's first pair, $20 store credit for the referrer once the friend orders
- Write one justification line per row explaining why that specific choice beats the obvious alternative
Warby Parker referral loop spec Trigger: Fires at checkout completion after the try-on box, satisfaction is highest here (not at delivery, before frames are seen) Mechanic: Personal link + photo of the chosen frame (social proof beats a bare 'invite friends' button) Incentive: Two-sided, $20 off friend's first pair / $20 credit to referrer (matches the lesson's Dropbox two-sided model)
Healthy
The referral ask fires at the single highest-satisfaction moment and gives the sharer something specific and personal to post, not a generic invite link.
Unhealthy
A referral button sits permanently in account settings where almost nobody who is satisfied right now will ever see it.
What this means
A referral loop is a specification, not a feature checkbox. All three parts have to be deliberately designed together.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| Referral rate is under 2% despite high satisfaction scores | Move the ask from account settings to the moment right after checkout completion | half day |
Final deliverable
A three-part referral loop spec (trigger, mechanic, incentive) with a one-line justification for each choice, ready to hand to a developer.
See a reference example
Allbirds referral loop spec Trigger: Fires 14 days after first wear, once the customer has posted a repeat purchase or a 5-star review (proven satisfaction signal, not just a completed order) Mechanic: A shareable 'my pair' referral link pre-filled with the exact shoe color and size Incentive: $25 credit both ways, redeemable only on a second pair, ties the reward to the retention goal
Success criteria
You're done when you can:
- All three components (trigger, mechanic, incentive) are specified, not just one or two
- The trigger is tied to a real satisfaction moment, not an arbitrary time delay
- The incentive is two-sided, matching the lesson's stated best-practice pattern