referral-mechanics
Referral Mechanics
Build sharing into the product without it feeling forced.
How to use
/referral-mechanicsApply referral constraints to this conversation.
Constraints
Timing
- MUST ask for referrals at moments of peak value (after a win, not before)
- NEVER ask for a referral before the user has experienced core value
- SHOULD identify the natural "sharing moments" in the product flow
- NEVER interrupt a task flow with a referral prompt
Incentive Structure
- Two-sided rewards beat one-sided (both referrer and referred get value)
- MUST make the incentive relevant to the product (credits > cash > swag)
- SHOULD make the reward immediate, not delayed
- NEVER create incentives that reward volume over quality
- MUST set clear terms and honor them consistently
Mechanics
- Share link must be short, clean, and preview well on social
- MUST show the referrer their impact (how many people signed up through them)
- SHOULD pre-write the share message but let users customize it
- NEVER auto-post to social media without explicit user action
- MUST make invite flows work across all channels (email, link, messaging apps)
Anti-Patterns
- Aggressive pop-ups asking for referrals
- Requiring invites to access features (hostage mechanics)
- Referral programs with confusing or changing rules
- Gamifying referrals to the point where users spam their contacts
- Not tracking or attributing referrals properly
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1