PRD Template for Referral Program
A complete product requirements template for building a referral program. Pre-filled with examples for reward structures, attribution tracking, fraud prevention, and viral loop optimization.
What makes referral program PRDs different
Referral programs sit at the intersection of product, growth, and finance. Unlike most features where you optimize for user satisfaction, referral programs must optimize for a business outcome: cost-effective, high-quality user acquisition. Every design decision — the reward amount, the activation criteria, the sharing mechanism — has a measurable financial impact.
The biggest referral program mistake is launching without fraud prevention. Referral rewards create a financial incentive to game the system. Without proper detection, you will end up paying rewards for fake accounts, self-referrals, and referral rings. The cost of fraud can exceed the value of legitimate referrals if left unchecked.
The template below covers the full referral lifecycle: incentive design, sharing mechanics, attribution tracking, fraud prevention, and program analytics. It is designed for SaaS products but the principles apply to any product with a user account.
Referral Program PRD template
Eight sections covering every aspect of a referral program.
Problem Statement
Referral programs harness your happiest users to acquire new customers at a fraction of paid acquisition costs. The problem they solve is not just acquisition — it is qualified acquisition. Users referred by existing customers convert better, retain longer, and have higher lifetime value than users from any other channel.
Example: "Our customer acquisition cost (CAC) via paid channels is $180 and rising 15% quarter-over-quarter as competition for ad inventory increases. Users acquired through word-of-mouth (tracked via 'How did you hear about us?' surveys) have a 40% higher retention rate and 2.3x higher lifetime value than paid-channel users. However, only 4% of our users have ever shared the product with someone else. We have no structured referral program — sharing is entirely organic with no tracking, no incentive, and no optimized flow."
Tips
- Calculate your CAC from paid channels and compare to the cost of a referral incentive
- Measure the retention and LTV difference between referred and non-referred users
- Survey existing users about willingness to refer and what incentive would motivate them
- Analyze organic sharing patterns: how do users currently share your product?
Goals and Objectives
Referral goals should address acquisition efficiency (lower CAC), referral volume (percentage of users who refer), and referral quality (do referred users convert and retain?).
Example: "Primary: 15% of active users share a referral link within 6 months (currently 4% share organically). Conversion: 25% of referred visitors sign up (benchmark for B2B SaaS). Cost efficiency: Referral CAC under $60 (vs. $180 for paid channels). Quality: Referred users retain at the same or higher rate as organically acquired users. Revenue: Referral program generates 20% of new user signups within 12 months."
Tips
- Set a sharing rate target: percentage of active users who share a referral link
- Define conversion targets for each stage: share > visit > signup > activate
- Compare referral CAC to paid channel CAC to validate cost efficiency
- Include quality metrics: retention and LTV of referred users
User Stories
Referral stories span the referrer (who shares), the referee (who receives the referral), and the admin (who manages the program). Each needs a seamless experience with clear incentives.
Example: "As an active user, I want to share a personalized referral link with colleagues so that we both receive a reward when they sign up and become active. Acceptance criteria: I can access my referral link from the dashboard or settings; the link is short and shareable via email, Slack, or social media; I can see how many people have clicked, signed up, and activated through my link; my reward is credited automatically when the referee meets the activation criteria."
Tips
- Write separate stories for the referrer (sharing, tracking, reward) and referee (landing, signup, reward)
- Include a story for the referral dashboard: tracking shares, clicks, signups, and rewards
- Add a story for reward fulfillment: how and when rewards are delivered
- Cover the admin story: configuring incentives, monitoring fraud, and adjusting the program
Functional Requirements
Referral requirements must define the sharing mechanism, reward structure, attribution logic, fraud prevention, and program management. The devil is in the attribution — how do you correctly credit the referrer when the referee signs up?
Example: "FR-1: Each user must have a unique referral link and referral code. FR-2: Referral attribution must track the click > signup > activation chain and credit the referrer. FR-3: Rewards must be double-sided: referrer receives 1 month free, referee receives 1 month free. FR-4: Rewards are credited only when the referee completes the activation criteria (defined as completing 3 core actions within 14 days). FR-5: Users must be able to share via email invite (pre-populated message), copy link, or social media sharing buttons. FR-6: The referral dashboard must show referral link, total shares, clicks, signups, activations, and rewards earned."
Tips
- Define reward structure clearly: one-sided vs. double-sided, reward type (credit, cash, free months)
- Specify activation criteria that trigger reward — signup alone is too easy to game
- Include multiple sharing mechanisms: link, email, social, in-app invite
- Define attribution window: how long after a click does the referral count?
Non-Functional Requirements
Referral systems must be resilient to fraud (fake signups, self-referrals, referral rings) and must track attribution accurately across sessions and devices.
Example: "NFR-1: Referral attribution must persist across sessions using a combination of URL parameters and cookies (30-day attribution window). NFR-2: The system must detect and prevent self-referrals (same email domain, same device, same IP). NFR-3: Referral rewards must be processed within 24 hours of activation criteria being met. NFR-4: The referral program must support A/B testing different reward structures. NFR-5: Referral links must load the landing page within 2 seconds with the referral context preserved."
Tips
- Define the attribution window: 7 days, 30 days, or first-touch forever
- Include fraud prevention rules: self-referral blocking, velocity limits, referral ring detection
- Support A/B testing for reward structures from the start
- Ensure referral attribution works across devices and sessions
Success Metrics
Referral success is measured through a funnel: share rate > click rate > signup rate > activation rate > reward rate. Track each stage independently.
Example: "Metric 1: Share rate (users who share / active users). Target: 15%. Metric 2: Referral signup conversion (signups / referral link clicks). Target: 25%. Metric 3: Referral activation rate (activated referees / signed up referees). Target: 50%. Metric 4: Referral CAC (total program cost / activated referral users). Target: under $60. Metric 5: Referred user 90-day retention vs. non-referred. Target: equal or higher."
Tips
- Track the full referral funnel: share > click > signup > activate > retain
- Calculate referral CAC and compare to paid channel CAC
- Measure referred user quality: retention and LTV vs. other channels
- Monitor fraud rate: rejected referrals as a percentage of total
Technical Considerations
Referral architecture requires reliable attribution tracking, fraud detection, reward processing, and analytics. The attribution system must work across referral link clicks, email invites, and social shares.
Example: "Each user gets a unique referral code stored in the database. Referral links use a short URL format (/r/CODE) that redirects to the signup page with a referral parameter. The referral code is stored in a cookie (30-day expiry) and in localStorage for cross-session persistence. On signup, the system checks for a referral code and creates a referral record linking referrer and referee. Activation criteria are evaluated asynchronously — when the referee completes the required actions, a background job credits the reward. Fraud detection rules run before reward credit."
Tips
- Use both cookies and URL parameters for attribution persistence
- Process rewards asynchronously to decouple from user actions
- Implement fraud detection as a pre-reward check, not a post-reward cleanup
- Design the referral data model to support analytics on every funnel stage
Risks and Mitigations
Referral risks include fraud (gaming the system for rewards), cannibalization (rewarding users who would have signed up anyway), and program costs exceeding value.
Example: "Risk: Users create fake accounts to earn referral rewards. Likelihood: High. Impact: Medium (financial loss). Mitigation: Require referee activation (not just signup) before rewarding. Block referrals from the same IP or device. Implement velocity limits (max 10 referral rewards per month). Risk: The program rewards users who would have signed up organically, inflating costs without incremental growth. Likelihood: Medium. Impact: Medium. Mitigation: Compare signup rates and channels before and after program launch. Exclude users who visited the product before the referral click."
Tips
- Require meaningful activation before rewarding, not just email signup
- Implement velocity limits to cap reward-gaming risk
- Track organic vs. referral signups to measure incrementality
- Set a program budget cap and review ROI monthly
Related templates
Frequently asked questions
Generate your referral program PRD from real data
Connect your analytics and billing data. Vantage generates a referral PRD with actual CAC comparisons and user sharing patterns.
Free to start. No credit card required.