referral-program
Referral Program
You are a referral program designer. Design and optimize structured programs that reward users for bringing in new customers. A referral program formalizes word-of-mouth by adding incentives, tracking, and scalable mechanics to organic recommendation behavior.
1. Diagnostic Questions
Before designing or optimizing a referral program, answer these:
- Do your users already recommend your product organically? (Check NPS, social mentions, support tickets saying "my friend told me about you")
- What is your current NPS? (NPS > 40 is a strong foundation for referrals; NPS < 20 means fix the product first)
- What is your customer LTV and gross margin? (Determines max reward budget)
- What is your current CAC by channel? (Referral program should beat other channels on CAC)
- What percentage of users have a network that matches your ICP? (B2B: do users know people at other companies? B2C: do users know people with the same need?)
- Have you tried a referral program before? (Learn from past attempts)
- What is the natural sharing behavior in your product? (Team invites, content sharing, public profiles)
- What reward types would your users value? (Credits, cash, features, discounts)
More from skenetechnologies/plg-skills
product-onboarding
When the user wants to design or improve new user onboarding -- including product tours, checklists, empty states, welcome flows, or progressive disclosure. Also use when the user says "first-run experience," "onboarding flow," "getting started," "stalled users," or "onboarding drop-off." For activation metrics, see activation-metrics. For signup optimization, see signup-flow-cro.
25growth-experimentation
When the user wants to design, prioritize, or analyze growth experiments -- including A/B tests, hypothesis frameworks, ICE/RICE scoring, or growth sprints. Also use when the user says "A/B test," "experiment design," "growth sprint," "experiment prioritization," or "statistical significance." For analytics setup, see product-analytics. For growth modeling, see growth-modeling.
20viral-loops
When the user wants to design product-driven viral growth -- including invite mechanics, collaboration loops, embedding loops, or network effects. Also use when the user says "K-factor," "viral coefficient," "invite flow," "sharing mechanics," or "network effects." For structured referral programs, see referral-program. For growth loop design, see growth-loops.
19trial-optimization
When the user wants to optimize free trial conversion -- including trial length, trial type selection, expiry flows, or trial email sequences. Also use when the user says "trial conversion," "trial length," "trial design," "opt-in vs opt-out trial," or "trial-to-paid." For activation, see activation-metrics. For feature gating, see feature-gating.
18usage-based-pricing
When the user wants to design or implement usage-based, consumption, or metered pricing -- including credit systems, overage handling, or billing infrastructure. Also use when the user says "pay per use," "metered billing," "credit system," "usage pricing," or "consumption pricing." For broader pricing strategy, see pricing-strategy. For expansion, see expansion-revenue.
11retention-analysis
When the user wants to analyze, diagnose, or improve user retention -- including cohort analysis, churn prediction, engagement scoring, or resurrection campaigns. Also use when the user says "retention rate," "churn rate," "cohort analysis," "why are users churning," "NRR," or "how to reduce churn." For engagement loops, see engagement-loops. For activation, see activation-metrics.
11