Referral programs occupy a strange place in growth: everyone knows the legendary cases — Dropbox's two-sided storage bonus is the canonical one — and almost everyone's own referral program quietly produces 2% of signups and gets forgotten in the footer. The difference between the legend and the footer is design. This guide covers the mechanics, the incentive science, and the pitfalls.

When a referral program can work at all

A referral program is an amplifier on existing word of mouth, not a generator of it. Preconditions:

Users already recommend you occasionally. If organic word of mouth is zero, an incentive will not create love; fix the product first.
Retention is solid. Referred users inherit your retention curve; amplifying a leaky product amplifies leaks.
The value story is tellable in one sentence. Referrers are volunteer salespeople; give them a pitch they can repeat.

The core mechanics

Every referral program is five decisions:

1. Who can refer? Everyone, or proven users only? Restricting to activated users (or measuring by them) keeps the program honest: happy users refer better and commit less fraud.

2. What does the referrer share? A personal link is the baseline. Better: a shareable artifact with standalone value (a report, an invite into a shared workspace) — the referral rides on something the recipient actually wants.

3. Single-sided or double-sided? Double-sided — both referrer and referred get something — consistently outperforms, for a social reason more than an economic one: it converts the referral from "I profit from you" into "I'm giving you a gift." The referrer spends social capital more willingly when the friend benefits visibly.

4. What is the reward? The most important design decision (next section).

5. When does the reward trigger? Pay on meaningful action, not on signup: activation, first project, or first payment. Signup-triggered rewards buy you fraud and tourists; action-triggered rewards buy you users.

Incentive design: the reward is the message

Product-denominated rewards beat cash for SaaS. Extra storage, extra credits, free months, unlocked features. Three reasons:

They select for people who want the product (cash attracts anyone).
Their perceived value exceeds their marginal cost (a free month costs you near zero; it feels like a full price unit).
They deepen engagement: a referrer sitting on earned credits has a new reason to stay.

The Dropbox pattern is the template: both sides received storage — the product's core scarce resource — so every reward made both parties more invested users, not just richer ones.

Cash and gift cards fit when your product has no natural consumable (e.g., flat-price tools) or when referring users cannot use more product (already on the top plan). If you pay cash, pay on first payment by the referred account, and cap it.

Sizing, illustratively: a sensible reward budget is a fraction of your blended CAC. If a paid customer costs you 300 units to acquire through ads, a two-sided reward totalling 50–100 units for a converted referral is a bargain at half your usual CAC — and referred customers typically retain as well or better than paid-channel ones, since they arrive pre-trusted by a friend.

Tiers and gamification, carefully. Milestone tiers (refer 3, get X; refer 10, get Y) extend power-referrers. Leaderboards work in communities, feel gimmicky in sober B2B. Always cap total earnings per user — uncapped programs are fraud invitations.

Placement: the moment matters more than the button

Referral prompts convert when they land at peak satisfaction moments:

Right after the aha moment or a completed job (report generated, project shipped)
After a positive rating or high NPS response
On milestone screens ("you've saved 12 hours this month — know someone drowning in this?")

They die in the footer and the settings page. Also: make the referred person's landing warm — name the referrer, state the gift, one clear action. A referral link that dumps the friend on the generic homepage wastes the trust that got them there.

Measurement: the numbers that tell the truth

Instrument the whole chain, per cohort:

Participation rate: % of active users who ever refer. Illustratively, healthy programs see 5–15%; below 2% means the offer or placement is wrong.
Invites per referrer and invite conversion rate (to signup, then to activation).
Referral share of new signups: the headline. A program contributing 10–30% of signups is a real channel.
Quality delta: activation, retention and conversion of referred users versus other channels. This is where good programs shine and bribed programs collapse.
Effective CAC: total rewards paid / converted referred customers. Compare to paid channels monthly.

Fraud: assume it, design for it

Where there is a reward, there is self-referral. Standard defenses: reward on qualifying action rather than signup; cap rewards; flag same-device/same-card/disposable-email patterns; delay payouts past the refund window; and reserve the right to claw back. None of this needs to be adversarial in tone — it just needs to exist before you scale the program, not after the incident.

Launch plan: crawl, walk, run

Referral programs benefit from staged rollouts:

Crawl (weeks 1–4): invite-only pilot with your happiest 100–500 users (high NPS, high usage). Manual reward fulfillment is fine. You are testing the offer and the message, not the plumbing. Success signal: participation above ~10% in this warm group.
Walk (months 2–3): open to all activated users, automate rewards, place the prompt at one peak-satisfaction moment, and stand up the fraud checks. Compare referred-cohort activation and retention to your paid channels.
Run (month 4+): add a second placement, test reward size and framing as proper experiments, and consider tiers for power referrers. Review quarterly like any product line: participation, quality delta, effective CAC.

If the crawl stage shows near-zero participation among your happiest users, stop — the problem is not mechanics, and scaling will not fix it. That early no is one of the cheapest strategic signals in growth.

The classic failure modes

Launching to a product without word of mouth. The program amplifies silence.
Rewarding signups. You will hit your referral KPI and fill the base with ghosts.
One-sided greed. Referrer-only rewards make sharing feel like selling out a friend; participation stalls.
Set-and-forget. Referral programs decay: creatives fatigue, placements get banner-blind, incentives drift out of sync with pricing. Treat it as a product with a roadmap, reviewed quarterly.
Judging it by volume alone. A program can boost signups while dragging activation and retention down. Judge referred cohorts, end to end.

One structural point that separates durable programs from decorative ones: the best referral motion is usually inside the product, not beside it. A standalone "refer a friend" page competes for attention with everything else; a referral that rides an existing workflow — sharing a report, inviting a collaborator, sending a client a link — inherits the workflow's frequency. Before building a formal program, audit whether your product already has such a carrier behavior; if it does, instrument and reward that instead of inventing a parallel one.

A referral program is, structurally, a growth loop: user → invitation → new user → invitation. Which means the right way to plan one is loop math — participation rate × invites × conversion, cycle time included — and the right way to run one is cohort tracking against your other channels. Modeling that loop before launch and watching referred cohorts flow through your AAARRR funnel afterwards is precisely what Growth Pilot's loop simulator and cockpit are built to do.