Referral

Help satisfied users invite people who will genuinely benefit, with a clear and respectful path for everyone.

What it is

Referral is a product-supported invitation loop: someone who already gets value from the product asks a specific person in their life to join, usually because the invite itself creates value for both sides—a shared workspace, a collaborative document, a genuine discount that also benefits the person invited. The clearest version looks less like marketing and more like introducing a colleague to a tool that’s already working: “you should see this doc” rather than “get $10 for every friend you refer.” It is distinct from Shareability, which is the export of a result someone made alone; referral is inherently two-sided, because it only works when the recipient—not just the sender—gets something they would actually choose.

Why it works

Social Transmission names the emotional fuel here precisely: people pass a product along because of pride and belonging, the reflective sense of looking good for having recommended something real. That only holds if the sender can make a credible, specific recommendation—vague or transactional asks (“earn credit for every invite”) don’t carry the same weight, because they read as the product asking a favour rather than the user sharing a genuine find. A referral loop that respects this converts slowly at first, because it waits for real advocacy to exist before asking for it, and that patience is exactly what makes the eventual invite trustworthy to the person receiving it.

The failure mode User Agency exists to catch is contact harvesting dressed up as referral: preselecting an address book, sending invitations without review, or gating a core feature behind “invite three friends” all convert a recommendation into an extraction, and the person on the receiving end can usually tell. Skip referral altogether and word-of-mouth still happens, just without a product-native path to capture or credit it. Push it too hard—rewards with hidden thresholds, invites the sender never actually reviewed—and the loop stops being social proof and becomes what Social Transmission calls friend spam, which damages the sender’s relationships more than it grows the product.

When to use it

• After a clear Success Moment or sustained value, not before the product has earned advocacy
• When inviting another person directly improves the product, such as shared workspaces or collaborative artefacts
• When a recipient-facing benefit is real, understandable, and appropriate to the product’s value

Do

• Explain what the recipient receives, what the sender receives, and when either reward is earned
• Make sharing optional, targeted, and easy to stop; let users choose a channel rather than importing contacts by default
• Place invitations where collaboration or a completed outcome makes the recommendation naturally relevant

Don’t

• Preselect contacts, send invitations without review, or make referral access a condition of core use
• Promise rewards with hidden thresholds, expiry traps, or unclear eligibility
• Ask users to recommend a product before they have enough experience to stand behind it

Founder Tip

Design the invitation so a user would be comfortable sending it to one person they respect. If it feels embarrassing or vague, the loop is not ready.

Make It Yours

1. To earn advocacy:
   • What outcome makes a user confident enough to recommend us?
   • Would they be able to explain the benefit in their own words?
2. To identify the recipient:
   • Who specifically gains value from joining or collaborating?
   • Is this invitation useful to them, rather than merely useful to us?
3. To make the offer clear:
   • What does each person receive, and what action triggers it?
   • Can both people understand the terms before sharing?
4. To reduce social pressure:
   • Can the sender edit the message, choose the channel, or decline without penalty?
   • Are we avoiding contact import and repeated prompts by default?
5. To evaluate quality:
   • Do referred users reach meaningful value and remain by choice?
   • Are complaints or low-quality invitations telling us the placement is wrong?

Related concepts

• Social Transmission
• User Agency
• Jobs-to-be-Done

Further reading

• Words Matter! Toward a Prosocial Call-to-Action for Online Referral — field research on recipient-benefiting referral language.
• Why Prosocial Referral Incentives Work — research on referral incentives, reputation, and uptake.
• Guides Concerning the Use of Endorsements and Testimonials in Advertising — disclosure guidance for incentivised advocacy.
• Referral Programs and Customer Value — foundational research on referral programmes and customer value.

Agent skill

• Primary command: /productfeeling map — place invitation loops where advocacy is earned and recipient value is clear
• Related commands: /productfeeling feel, /productfeeling peaks-ends, /productfeeling anti-patterns
• When the agent should load this TTP: “referral programme”, “invite a friend”, “referral reward”, “collaboration invite”, “advocacy loop”
• Companion handoff: RedTeam — audit referral incentives for social pressure; Impeccable — invite flow and reward disclosure UI
• Feeling north star this TTP serves: credible recommendations that respect both parties
• Anti-goals: preselected contacts, hidden reward thresholds, referral gated core use, premature advocacy asks
• Reference path: skill/reference/map.md