agentleFS
mia-pppmia-ppp/PMM-Skills/skills/referral-program/SKILL.md

referral-program

Skill2 starsChanged 27 days agoMITView on GitHub

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch-strategy.

55 other projects use a version of this, 41 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use site-architecture, churn-prevention and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    site-architecture

    Use when planning or restructuring what pages a site has and how they connect: hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Not for XML sitemaps, which are in seo-audit.

    Also in 18 projects that use this

  • ukunal91appSkill

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

    Also in 17 projects that use this

  • ukunal91appSkill

    ai-seo

    When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.

    Also in 22 projects that use this

  • +1 more from ukunal91app

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 7 are common, 3 are distinctive, and 3 are very specific to this project.

  • 7

    Common

    Most of the 54 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the company SSOT when present: follow ../_shared/ssot-consumption.md and the project manifest to load only relevant approved context.

    line 11
  2. Very specific:

    Load the evidence labels: read ../_shared/evidence-gaps.md (relative to this skill's folder) and follow it.

    line 17
  3. Very specific:

    If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions.

    line 20
  4. Common:

    Do customers naturally talk about it?

    line 38
  5. Distinctive:

    Keep referrer and referred-buyer needs distinct when selecting incentives and invitation mechanics.

    line 76
  6. Common:

    After achieving a milestone

    line 89
  7. Common:

    After renewing or upgrading

    line 91
  8. Common:

    Ask at better moments

    line 119
  9. Common:

    Test different incentive types

    line 121
  10. Common:

    Ensure referrer's endorsement is visible

    line 127
  11. Common:

    After milestone: "You achieved [X]!

    line 223
  12. Distinctive:

    No em dashes in output.

    line 262
  13. Distinctive:

    Keep any short summary or open-questions list separate from the Evidence gaps lists.

    line 266

“Common” is measured: kept by at least 6 in 10 of the 54 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Referral & Affiliate Programs

Use the company SSOT when present: follow ../_shared/ssot-consumption.md and the project manifest to load only relevant approved context. Preserve covered strategic meaning while keeping this skill’s existing scope and frameworks.

You are an expert in viral growth and referral marketing. Your goal is to help design and optimize programs that turn customers into growth engines.

Before Starting

Load the evidence labels: read ../_shared/evidence-gaps.md (relative to this skill's folder) and follow it. Label every claim, benchmark, and number Sourced, Assumed, or Gap. Never drop an item because proof is missing: label it and name how to get the proof.

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Program Type

  • Customer referral program, affiliate program, or both?
  • B2B or B2C?
  • What's the average customer LTV?
  • What's your current CAC from other channels?

2. Current State

  • Existing referral/affiliate program?
  • Current referral rate (% who refer)?
  • What incentives have you tried?

3. Product Fit

  • Is your product shareable?
  • Does it have network effects?
  • Do customers naturally talk about it?

4. Resources

  • Tools/platforms you use or consider?
  • Budget for referral incentives?

Referral vs. Affiliate

Customer Referral Programs

Best for:

  • Existing customers recommending to their network
  • Products with natural word-of-mouth
  • Lower-ticket or self-serve products

Characteristics:

  • Referrer is an existing customer
  • One-time or limited rewards
  • Higher trust, lower volume

Affiliate Programs

Best for:

  • Reaching audiences you don't have access to
  • Content creators, influencers, bloggers
  • Higher-ticket products that justify commissions

Characteristics:

  • Affiliates may not be customers
  • Ongoing commission relationship
  • Higher volume, variable trust

Referral Program Design

Keep referrer and referred-buyer needs distinct when selecting incentives and invitation mechanics.

The Referral Loop

Trigger Moment → Share Action → Convert Referred → Reward → (Loop)

Step 1: Identify Trigger Moments

High-intent moments:

  • Right after first "aha" moment
  • After achieving a milestone
  • After exceptional support
  • After renewing or upgrading

Step 2: Design Share Mechanism

Ranked by effectiveness:

  1. In-product sharing (highest conversion)
  2. Personalized link
  3. Email invitation
  4. Social sharing
  5. Referral code (works offline)

Step 3: Choose Incentive Structure

Single-sided rewards (referrer only): Simpler, works for high-value products

Double-sided rewards (both parties): Higher conversion, win-win framing

Tiered rewards: Gamifies referral process, increases engagement

For examples and incentive sizing: See references/program-examples.md


Program Optimization

Improving Referral Rate

If few customers are referring:

  • Ask at better moments
  • Simplify sharing process
  • Test different incentive types
  • Make referral prominent in product

If referrals aren't converting:

  • Improve landing experience for referred users
  • Strengthen incentive for new users
  • Ensure referrer's endorsement is visible

A/B Tests to Run

Incentive tests: Amount, type, single vs. double-sided, timing

Messaging tests: Program description, CTA copy, landing page copy

Placement tests: Where and when the referral prompt appears

Common Problems & Fixes

ProblemFix
Low awarenessAdd prominent in-app prompts
Low share rateSimplify to one click
Low conversionOptimize referred user experience
Fraud/abuseAdd verification, limits
One-time referrersAdd tiered/gamified rewards

Measuring Success

Key Metrics

Program health:

  • Active referrers (referred someone in last 30 days)
  • Referral conversion rate
  • Rewards earned/paid

Business impact:

  • % of new customers from referrals
  • CAC via referral vs. other channels
  • LTV of referred customers
  • Referral program ROI

Typical Findings

  • Referred customers have 16-25% higher LTV
  • Referred customers have 18-37% lower churn
  • Referred customers refer others at 2-3x rate

Launch Checklist

Before Launch

  • Define program goals and success metrics
  • Design incentive structure
  • Build or configure referral tool
  • Create referral landing page
  • Set up tracking and attribution
  • Define fraud prevention rules
  • Create terms and conditions
  • Test complete referral flow

Launch

  • Announce to existing customers
  • Add in-app referral prompts
  • Update website with program details
  • Brief support team

Post-Launch (First 30 Days)

  • Review conversion funnel
  • Identify top referrers
  • Gather feedback
  • Fix friction points
  • Send reminder emails to non-referrers

Email Sequences

Referral Program Launch

Subject: You can now earn [reward] for sharing [Product]

We just launched our referral program!

Share [Product] with friends and earn [reward] for each signup.
They get [their reward] too.

[Unique referral link]

1. Share your link
2. Friend signs up
3. You both get [reward]

Referral Nurture Sequence

  • Day 7: Remind about referral program
  • Day 30: "Know anyone who'd benefit?"
  • Day 60: Success story + referral prompt
  • After milestone: "You achieved [X]! Know others who'd want this?"

Affiliate Programs

For detailed affiliate program design, commission structures, recruitment, and tools: See references/affiliate-programs.md


Task-Specific Questions

  1. What type of program (referral, affiliate, or both)?
  2. What's your customer LTV and current CAC?
  3. Existing program or starting from scratch?
  4. What tools/platforms are you considering?
  5. What's your budget for rewards/commissions?
  6. Is your product naturally shareable?

Tool Integrations

For implementation, see the tools registry. Key tools for referral programs:

ToolBest ForGuide
RewardfulStripe-native affiliate programsrewardful.md
ToltSaaS affiliate programstolt.md
Mention MeEnterprise referral programsmention-me.md
Dub.coLink tracking and attributiondub-co.md
StripePayment processing (for commission tracking)stripe.md
IntrowChannel partner programs with tiers, deal registration, QBRsintrow.md
PartnerStackEnterprise partner and affiliate programspartnerstack.md

Output Rules

  • No em dashes in output.
  • Open with the "Inputs and assumptions" note from ../_shared/evidence-gaps.md.
  • Label every claim, benchmark, and number Sourced, Assumed, or Gap.
  • End with the Evidence gaps section: the top five in the body, the rest in an appendix.
  • Keep any short summary or open-questions list separate from the Evidence gaps lists.

Related Skills

  • launch-strategy: For launching referral program effectively
  • email-sequence: For referral nurture campaigns
  • analytics-tracking: For tracking referral attribution

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.