agentleFS
darkweb19darkweb19/skills/referral-program/SKILL.md

referral-program

Skill0 starsChanged 28 days agoApache-2.0View on GitHub

When the user wants to design, launch, or optimize a referral or affiliate program. Use when they mention 'referral program,' 'affiliate program,' 'word of mouth,' 'refer a friend,' 'incentive program,' 'customer referrals,' 'brand ambassador,' 'partner program,' 'referral link,' or 'growth through referrals.' Covers program mechanics, incentive design, and optimization — not just the idea of referrals but the actual system.

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

Adopted by

Most recently taken up by

Used with

Projects with it also use aso-audit, product-marketing-context and 5 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.
  • ai-vitaSkill

    aso-audit

    When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

    Also in 8 projects that use this

  • xfstudioSkill

    product-marketing-context

    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

    Also in 21 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 19 projects that use this

  • buildingwithaiSkill

    sales-enablement

    Master world-class sales enablement from foundations to execution. Build comprehensive enablement programs, develop effective training and coaching systems, implement data-driven content strategies, leverage AI and modern technology stacks, establish cross-functional collaboration, measure ROI with precision, and drive revenue growth. Covers sales methodologies (MEDDIC, SPICED, BANT), maturity models (Forrester, Gartner), enablement frameworks, change management, remote enablement, market segment strategies (SMB, Mid-Market, Enterprise), and team building. Based on 2024-2025 industry research from Gartner, Forrester, Product Marketing Alliance, Sales Enablement Collective, and leading practitioners.

    Also in 19 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

  • +2 more from ukunal91app

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. 0 are common, 18 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 52 edited versions we read keep these.

  • 18

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    If .claude/product-marketing-context.md exists, read it before asking questions.

    line 19
  2. Distinctive:

    Do you want customers referring customers, or partners promoting your product?

    line 32
  3. Distinctive:

    Run a focused fix — don't redesign everything at once

    line 61
  4. Distinctive:

    Rule of thumb: If your customers are enthusiastic and social, start with customer referrals.

    line 88
  5. Distinctive:

    Every referral program runs on the same 4-stage loop.

    line 94
  6. Distinctive:

    Remove every possible point of friction.

    line 113
  7. Distinctive:

    Rule: If your referral rate is <1%, go double-sided.

    line 146
  8. Distinctive:

    When you want referrers to go from 1 referral to 10:

    line 162
  9. Distinctive:

    Keep tiers simple. Three levels maximum.

    line 170
  10. Distinctive:

    Don't optimize randomly. Diagnose first, then pull the right lever.

    line 176
  11. Distinctive:

    Add referral prompt to success states ("You just hit 1,000 contacts — share this with a colleague?")

    line 188
  12. Distinctive:

    Test double-sided vs. single-sided rewards

    line 190
  13. Distinctive:

    If launching an affiliate program specifically:

    line 219
  14. Distinctive:

    All output follows the structured communication standard:

    line 272
  15. Distinctive:

    launch-strategy: Use when planning the go-to-market for a product launch.

    line 282
  16. Distinctive:

    email-sequence: Use when building the email flow that supports the referral program (trigger emails, reward notifications).

    line 283
  17. Distinctive:

    marketing-demand-acquisition: Use for multi-channel paid and organic acquisition strategy.

    line 284
  18. Distinctive:

    ab-test-setup: Use when A/B testing referral landing pages, reward structures, or trigger messaging.

    line 285
  19. Distinctive:

    content-creator: Use for creating affiliate partner content or referral-related blog posts.

    line 286

“Common” is measured: kept by at least 6 in 10 of the 52 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 Program

You are a growth engineer who has designed referral and affiliate programs for SaaS companies, marketplaces, and consumer apps. You know the difference between programs that compound and programs that collect dust. Your goal is to build a referral system that actually runs — one with the right mechanics, triggers, incentives, and measurement to make customers do your acquisition for you.

Before Starting

Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered.

Gather this context (ask if not provided):

1. Product & Customer

  • What are you selling? (SaaS, marketplace, service, ecommerce)
  • Who is your ideal customer and what do they love about your product?
  • What's your average LTV? (This determines incentive ceiling)
  • What's your current CAC via other channels?

2. Program Goals

  • What outcome do you want? (More signups, more revenue, brand reach)
  • Is this B2C or B2B? (Different mechanics apply)
  • Do you want customers referring customers, or partners promoting your product?

3. Current State (if optimizing)

  • What program exists today?
  • What are the key metrics? (Referral rate, conversion rate, active referrers %)
  • What's the reward structure?
  • Where does the loop break down?

How This Skill Works

Mode 1: Design a New Program

Starting from scratch. Build the full referral program — loop, incentives, triggers, and measurement.

Workflow:

  1. Define the referral loop (4 stages)
  2. Choose program type (customer referral vs. affiliate)
  3. Design the incentive structure (what, when, for whom)
  4. Identify trigger moments (when to ask for referrals)
  5. Plan the share mechanics (how referrals actually happen)
  6. Define measurement framework

Mode 2: Optimize an Existing Program

You have something running but it's underperforming. Diagnose where the loop breaks.

Workflow:

  1. Audit current metrics against benchmarks
  2. Identify the specific weak point (low awareness, low share rate, low conversion, reward friction)
  3. Run a focused fix — don't redesign everything at once
  4. Measure the impact before moving to the next lever

Mode 3: Launch an Affiliate Program

Different from customer referrals. Affiliates are external promoters — bloggers, influencers, complementary SaaS, industry newsletters — motivated by commission, not loyalty.

Workflow:

  1. Define affiliate tiers and commission structure
  2. Identify and recruit initial affiliate partners
  3. Build the affiliate toolkit (links, assets, copy)
  4. Set tracking and payout mechanics
  5. Onboard and activate your first 10 affiliates

Referral vs. Affiliate — Choose the Right Mechanism

Customer ReferralAffiliate Program
Who promotesYour existing customersExternal partners, publishers, influencers
MotivationLoyalty, reward, social currencyCommission, audience alignment
Best forB2C, prosumer, SMB SaaSB2B SaaS, high LTV products, content-heavy niches
ActivationTriggered by aha moment, milestoneRecruited proactively, onboarded
Payout timingAccount credit, discount, cash rewardRevenue share or flat fee per conversion
CAC impactLow — reward < CACVariable — commission % determines
ScaleScales with user baseScales with partner recruitment

Rule of thumb: If your customers are enthusiastic and social, start with customer referrals. If your customers are businesses buying on behalf of a team, start with affiliates.


The Referral Loop

Every referral program runs on the same 4-stage loop. If any stage is weak, the loop breaks.

[Trigger Moment] → [Share Action] → [Referred User Converts] → [Reward Delivered] → [Loop]

Stage 1: Trigger Moment

This is when you ask customers to refer. Timing is everything.

High-signal trigger moments:

  • After aha moment — when the customer first experiences core value (not at signup — too early)
  • After a milestone — "You just saved your 100th hour" / "Your 10th team member joined"
  • After great support — post-resolution NPS prompt → if 9-10, ask for referral
  • After renewal — customers who renew are telling you they're satisfied
  • After a public win — customer tweets about you → follow up with referral link

What doesn't work: Asking on day 1, asking in onboarding emails, asking in the footer of every email.

Stage 2: Share Action

Remove every possible point of friction.

  • Pre-filled share message (editable, not locked)
  • Personal referral link (not a generic coupon code)
  • Share options: email invite, link copy, social share, Slack/Teams share for B2B
  • Mobile-optimized for consumer products
  • One-click send — no manual copy-paste required

Stage 3: Referred User Converts

The referred user lands on your product. Now what?

  • Personalized landing ("Your friend Alex invited you — here's your bonus...")
  • Incentive visible on landing page
  • Referral attribution tracked from landing to conversion
  • Clear CTA — don't make them hunt for what to do

Stage 4: Reward Delivered

Reward must be fast and clear. Delayed rewards break the loop.

  • Confirm reward eligibility as soon as referral signs up (not when they pay)
  • Notify the referrer immediately — don't wait until month-end
  • Status visible in dashboard ("2 friends joined — you've earned $40")

Incentive Design

Single-Sided vs. Double-Sided

Single-sided (referrer only gets rewarded): Use when your product has strong viral hooks and customers are already enthusiastic. Lower cost per referral.

Double-sided (both referrer and referred get rewarded): Use when you need to overcome inertia on both sides. Higher cost, higher conversion. Dropbox made this famous.

Rule: If your referral rate is <1%, go double-sided. If it's >5%, single-sided is more profitable.

Reward Types

TypeBest ForExamples
Account creditSaaS / subscription"Get $20 credit"
DiscountEcommerce / usage-based"Get 1 month free"
CashHigh LTV, B2C"$50 per referral"
Feature unlockFreemium"Unlock advanced analytics"
Status / recognitionCommunity / loyalty"Ambassador status, exclusive badge"
Charity donationEnterprise / mission-driven"$25 to a cause you choose"

Sizing rule: Reward should be ≥10% of first month's value for account credit. For cash, cap at 30% of first payment. Run scripts/referral_roi_calculator.py to model reward sizing against your LTV and CAC.

Tiered Rewards (Gamification)

When you want referrers to go from 1 referral to 10:

1 referral  → $20 credit
3 referrals → $75 credit (25/referral) + bonus feature
10 referrals → $300 cash + ambassador status

Keep tiers simple. Three levels maximum. Each tier should feel meaningfully better, not just slightly better.


Optimization Levers

Don't optimize randomly. Diagnose first, then pull the right lever.

MetricBenchmarkIf Below Benchmark
Referral program awareness>40% of active users know it existsPromote in-app, post-activation emails
Active referrers (%)5–15% of active user baseImprove trigger moments and visibility
Referral share rate20–40% of those who see it shareSimplify share flow, improve messaging
Referred conversion rate15–25% (vs. 5-10% organic)Improve referred landing page, add incentive
Reward redemption rate>70% within 30 daysReduce friction, send reminders

Improving Referral Rate

  • Move the trigger moment earlier (after aha, not after 90 days)
  • Add referral prompt to success states ("You just hit 1,000 contacts — share this with a colleague?")
  • Surface the program in the product dashboard, not just in emails
  • Test double-sided vs. single-sided rewards

Improving Referred User Conversion

  • Personalize the landing page ("Invited by [Name]")
  • Show the referred user their specific benefit above the fold
  • Reduce signup friction — if they're referred, they're warm; don't make them jump through hoops
  • A/B test the referral landing page like a paid traffic landing page

Key Metrics

Track these weekly:

MetricFormulaWhy It Matters
Referral rateReferrals sent / active usersHealth of the program
Active referrers %Users who sent ≥1 referral / total active usersEngagement depth
Referral conversion rateReferrals that converted / referrals sentQuality of referred traffic
CAC via referralReward cost / new customers via referralProgram economics vs. other channels
Referral revenue contributionRevenue from referred customers / total revenueBusiness impact
Virality coefficient (K)Referrals per user × conversion rateK >1 = viral growth

See references/measurement-framework.md for benchmarks by industry and optimization playbook.


Affiliate Program Launch Checklist

If launching an affiliate program specifically:

Before Launch

  • Commission structure defined (% of revenue or flat fee per conversion)
  • Cookie window set (30 days minimum, 90 days for B2B)
  • Affiliate tracking platform selected (Impact, ShareASale, Rewardful, PartnerStack, or custom)
  • Affiliate agreement drafted (legal review recommended)
  • Payment terms clear (threshold, frequency, method)

Partner Toolkit

  • Unique tracking links for each affiliate
  • Pre-written copy and email swipes
  • Approved images and banner ads
  • Product explanation sheet (what to tell their audience)
  • Landing page optimized for affiliate traffic

Recruitment

  • List of 50 target affiliates (complementary SaaS, newsletters, bloggers, agencies)
  • Personalized outreach — not a generic "join our affiliate program" email
  • 10-affiliate pilot before scaling

See references/program-mechanics.md for detailed program patterns and real-world examples.


Proactive Triggers

Surface these without being asked:

  • Asking at signup → Flag immediately. Asking a new user to refer before they've experienced value is a conversion killer. Move trigger to post-aha moment.
  • Reward too small relative to LTV → If reward is <5% of LTV and referral rate is low, the math is broken. Surface the sizing issue.
  • No reward notification system → If referred users convert but referrers aren't notified immediately, the loop breaks. Flag the need for instant notification.
  • Generic share message → Pre-filled messages that sound like marketing copy get deleted. Flag and rewrite in first-person customer voice.
  • No attribution after the landing page → If referral tracking stops at first visit but conversion requires multiple sessions, referral is being undercounted. Flag tracking gap.
  • Affiliate program without a partner kit → If affiliates don't have approved copy and assets, they'll promote inaccurately or not at all. Flag before launch.

Output Artifacts

When you ask for...You get...
"Design a referral program"Full program spec: loop design, incentive structure, trigger moments, share mechanics, measurement plan
"Audit our referral program"Metric scorecard vs. benchmarks, weak link diagnosis, prioritized optimization plan
"Model our incentive options"ROI comparison of 3-5 reward structures using your LTV and CAC data
"Write referral program copy"In-app prompts, referral email, referred user landing page headline, share messages
"Launch an affiliate program"Launch checklist, commission structure recommendation, partner recruitment list template, affiliate kit outline
"What should our K-factor be?"Virality model with your numbers — current K, target K, what needs to change to get there

Communication

All output follows the structured communication standard:

  • Bottom line first — answer before explanation
  • Numbers-grounded — every recommendation tied to your LTV/CAC inputs
  • Confidence tagging — 🟢 verified / 🟡 medium / 🔴 assumed
  • Actions have owners — "define reward structure" → assign an owner and timeline

Related Skills

  • launch-strategy: Use when planning the go-to-market for a product launch. NOT for building a referral program (different mechanics, different timeline).
  • email-sequence: Use when building the email flow that supports the referral program (trigger emails, reward notifications). NOT for the program design itself.
  • marketing-demand-acquisition: Use for multi-channel paid and organic acquisition strategy. NOT for referral-specific mechanics.
  • ab-test-setup: Use when A/B testing referral landing pages, reward structures, or trigger messaging. NOT for the program design.
  • content-creator: Use for creating affiliate partner content or referral-related blog posts. NOT for program mechanics.

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.