Generated banner for Referrals
Generated logo for Referrals

Referrals

Corey HainesCommunityCreated by Corey Haines

  • Skill
  • Guidelines
  • Business and productivity
  • MIT
  • No issues found

From the author

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,' 'affiliate payout,' 'get more reviews,' 'G2 reviews,' 'review campaign,' or 'respond to a bad review.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.
— the description by Corey Haines

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a comprehensive framework for building viral growth through referral and affiliate marketing. It guides users through the strategic design of referral loops, incentive structures, and affiliate management, while emphasizing the importance of product-led virality. It covers the entire lifecycle from identifying trigger moments and selecting the right tools to measuring program health and preventing fraud.

What it does

  • Helps design customer referral and partner affiliate programs.
  • Provides frameworks for incentive structures and reward sizing.
  • Offers guidance on identifying high-intent trigger moments for referrals.
  • Includes a launch checklist and email templates for program promotion.
  • Outlines strategies for program optimization and A/B testing.
  • Provides best practices for affiliate recruitment and enablement.

When to use it

  • When you want to incentivize existing users to refer new customers.
  • When you need to build or scale an affiliate or partner program.
  • When you want to improve word-of-mouth or viral growth metrics.
  • When you need to manage reviews or reputation campaigns.
  • When you are evaluating tools for referral or affiliate tracking.

Advantages

  • Provides a structured approach to distinguish between referral and affiliate strategies.
  • Focuses on product-embedded virality to reduce reliance on paid incentives.
  • Includes actionable templates for outreach and program communication.
  • Offers clear metrics to measure ROI and program health.
  • Provides specific guidance on fraud prevention and program rules.

Usage examples

“How do I set up a referral program for my B2C SaaS product?”
The agent will guide you through identifying your product's shareability, choosing between single or double-sided rewards, and selecting the right trigger moments for prompts.
“We want to start an affiliate program for our high-ticket software. Where do we begin?”
The agent will help you define commission structures, identify potential partner types, and provide an outreach template to recruit your first affiliates.
“Our referral conversion rate is low. How can we improve it?”
The agent will suggest A/B tests for your landing page, incentive types, and placement of referral prompts to reduce friction and increase participation.
“How do I handle a bad review on G2?”
The agent will provide guidance on reputation triage and best practices for responding to reviews while adhering to platform-specific rules.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/coreyhaines31/referrals/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip referrals.zip -d .agents/skills

Documentation by Corey Haines

Referral & Affiliate Programs

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

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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?


Should You Engineer Virality First?

Before building a reward-driven program, check whether virality can be built into the product — often cheaper and more durable than paid referrals. But don't force virality where it doesn't naturally fit.

Place the product on the Viral Potential Spectrum:

  • Natural (build for it): collaboration tools, communication tools, user-facing outputs — every use exposes the product to non-users.

  • Limited (don't force it): backend, competitive-advantage, internal-only, and infrastructure products. Invest in referral programs, content, and partnerships instead.

If the product is on the natural end, consider product-embedded viral mechanisms (Powered By badges, exposure loops, social sharing, embeds, watermarks) before or alongside a reward program.

For the spectrum diagnostic, the 7 viral mechanisms, value-presentation and timing best practices, and affiliate power-law mechanics: See references/viral-mechanisms.md


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

For partner recruitment/activation, cohort economics, executable terms, reconciliation, and measured incremental growth, load the operating playbook. This expands the existing affiliate branch instead of creating an overlapping skill.

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

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

Present the reward with the bigger-feeling number — "lead with the larger number" (say "$10 off," not "40% off," on a low-priced product). Reward at the aha moment or milestone, not signup. Reduce friction: one-click share, pre-written messages.

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

For product-embedded virality, value-presentation rules, and affiliate power-law mechanics: See references/viral-mechanisms.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

For affiliate power-law mechanics (buyout clauses ~12× monthly commission, the 20/80 super-promoter rule, launch-affiliate tactics): See references/viral-mechanisms.md


Review Programs

Reviews are the other half of customer advocacy. For review-request programs, responding to reviews, reputation triage, and reusing testimonials with permission (G2, Capterra, Trustpilot, Google, app stores), see references/review-programs.md. Platform rules differ, so check references/review-platform-rules.md before proposing incentives or automation.

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

  • launch: For launching referral program effectively

  • emails: For referral nurture campaigns

  • marketing-psychology: For understanding referral motivation

  • analytics: For tracking referral attribution

Files

references/review-program-operations.md

Review Program Operations

Use for a repeatable invitation or reputation-triage program. Start with the smallest useful cohort and the user's existing tools; avoid building a sending system for a one-off request.

Invitation Cohort

Define eligibility before looking at predicted sentiment:

  • Genuine experience milestone and minimum time needed to evaluate it.

  • Product/service/account boundary and region/channel authorization.

  • Deduplication key and last-invited window.

  • Opt-out, delivery failure, or documented platform ineligibility.

  • Request/reminder limits, owner, and stop condition.

For example: "customers who completed their first project in the past seven days, not previously invited in this campaign, with an authorized contact channel." Include dissatisfied customers who meet the same rule. Route their service issues separately. Do not add an NPS/CSAT cutoff to create a favorable public-review cohort.

Review recipients and content before a send or workflow configuration unless those exact actions are already authorized. Use the platform's supported invitation mechanism. A read-only CLI result is not evidence of invitation permission.

Neutral Invitation Draft

Subject: Share your experience with [Product]

You've completed [real experience milestone] with [Product]. If you'd like, please share an honest review at [verified platform/profile link]. Positive, neutral, and critical feedback all help people evaluate whether we're a fit. Thanks for your time.

Keep the invitation factual. Avoid prewritten customer claims, five-star requests, guilt, or a service remedy tied to reviewing. For an incentive permitted by the selected platform, use that platform's approved terms/disclosures; do not improvise a generic reward footer.

A bounded reminder can repeat the same neutral request for eligible nonresponders after a stated interval. Deduplicate actual prior invitations, honor opt-outs, and stop after the agreed limit. Don't interpret lack of response as permission for more channels.

Reputation Queue

FieldPurpose
Review URL, platform, dateSource and scope
Customer assertionExact relevant claim, separate from internal facts
Evidence statusVerified, unverified, or conflicting
Issue classService, product gap, misunderstanding, privacy/safety, suspected policy breach
Owner and next stepSpecific accountable follow-up
Public response statusDraft, authorized, published with link, or deferred
Resolution statusOpen, investigated, action agreed, resolved with evidence

Use urgency proportional to the actual allegation. Safety/security or disclosure of private information needs the responsible team's handling; a disliked opinion does not become an emergency. Record what is uncertain, and do not assert that the business has fixed an issue merely because a reply was sent.

Quote Permission Ledger

Record: source URL/date, exact quote, customer-approved attribution, consent evidence, allowed channels, permitted edits, material-connection disclosure, validity window, and withdrawal/update status. Proposed use stays unpublished when permission or platform rights are unknown. Redact private records from shared marketing briefs.

Example reuse packet:

  • Quote: [exact, permissioned words]

  • Source: [URL and date]

  • Claim boundary: [what the quote supports; what it does not]

  • Rights: [specific allowed channel and approval]

  • Attribution/disclosure: [approved text]

  • Proposed placement: [page/ad/sales asset]

Do not manufacture a "4.7 converts better than 5.0" rule. If testing proof placement, use a defined hypothesis and the actual conversion data; ratings, source mix, sample size, and selection all affect interpretation.

Program Dashboard

Start with a private sheet or existing CRM/support workflow. Track unique eligible customers, unique invitations, delivery, published-review source/window, recurring issues, response latency, and evidence-backed resolution. Report unknowns rather than joining unrelated review growth to a campaign denominator.

An initial program proposal should fit one page: cohort, platform method and policy check, request/reminder draft, permissions, owner, review cadence, success measure, and stop condition. Use a separate sending/automation implementation only when requested and authorized.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Corey Haines
Publisher
Corey Haines (Community)
Source
coreyhaines31/marketingskills · skills/referrals · commit 96798cf
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Corey Haines.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download referrals.zip