BookCreatorStudio Referral Program

Customer referral + affiliate growth strategy — program design, benchmarks, and implementation plan
Draft v1.0 August 2026 Internal — share with team

Executive Summary

This document outlines a dual-track growth program for BookCreatorStudio: a credit-based referral program for existing customers, and a cash-commission affiliate program for external promoters. The design is based on analysis of 15+ AI media creation platforms and 10+ SaaS case studies with verified results.

30%
Avg user activation in embedded referral programs
2–3x
Higher conversion from two-sided rewards vs one-sided
50%
Lower CAC from referral channels vs paid ads

Why Run Two Separate Programs

Referral and affiliate programs serve different people with different motivations. Combining them into one "partner program" underpays affiliates and over-engineers referrals. Every high-performing SaaS case study runs them as distinct tracks.

Referral Customer Referral Program

  • Promoter: Existing paying customer
  • Motivation: Help friends + earn credits
  • Reward: Platform credits (non-cash)
  • Reach: Their personal network
  • Trust level: High — personal recommendation
  • Tracking: Simple in-app link

Affiliate Affiliate Partner Program

  • Promoter: Creator, blogger, agency, influencer
  • Motivation: Commission economics
  • Reward: Cash (recurring % of revenue)
  • Reach: Their audience (unlimited scale)
  • Trust level: Lower — commercial relationship
  • Tracking: Cookies, postbacks, coupon codes

Key principle: Pay referrers in credits (keeps them on-platform) and affiliates in cash (the only thing external promoters will accept). The moment you let customers earn cash for casual referrals, you've accidentally launched a second affiliate program with worse controls.

Program 1 — Customer Referral Program

The Offer

Referrer Gets
50 BCS Credits
Added to account balance, stackable, never expires while subscribed
Friend Gets
50 BCS Credits
Applied on signup, usable on any generation feature

Based on industry data, equal two-sided rewards perform best (Smoobu/Cello benchmark: 25% activation, 17% sharing rate). Unequal rewards confuse users about which side they're on.

Reward Trigger

Credits are awarded when the referred friend signs up and verifies their account. We do NOT gate on purchase — early-stage products need maximum friction removal. You can tighten to "first purchase" later once conversion rates are established.

Counter-pattern we're choosing to ignore: Creator AI gates rewards on first purchase. This makes sense at their scale (100K+ users) but is too restrictive for BCS's current stage. Runway gates on 2 months of paid subscription — too aggressive for early growth.

How It Works — User Flow

User generates content
Sees referral prompt at moment of delight
Copies share link or enters friend's email
Friend signs up via link
Both get 50 credits

No Cap

Users can refer unlimited friends. Genspark capped at 20 months free; most AI tools (Manus, RunningHub, Viyou) have no cap. Uncapped referrals signal confidence and drive network effects.

UI Placement Critical

Placement Why Expected Impact
Main nav / sidebar — always visible Moss case study: showing reward amount in menu increased activation 140% Primary discovery channel
Post-generation success screen Xentral data: surfacing at "moments of delight" = 3.4x higher sharing Highest-intent trigger
Settings → Referrals tab Standard location users look for it Baseline discovery
Email nudge after 7 days active Catches users who haven't discovered the feature in-app Secondary activation

Stackable Credits

Credits accumulate — they don't replace each other. Refer 5 friends = 250 bonus credits. This was Thinx's biggest unlock: stackable credits increased referral revenue 114% month-over-month because users could build toward larger purchases instead of using single-use codes.

Anti-Fraud

Program 2 — Affiliate Partner Program

The Offer

Commission Rate
25%
Recurring for first 12 months of each referred subscription
Cookie Window
60 Days
Standard for SaaS; Safari caps at 7 days via ITP
Payout
Monthly
Via PayPal or Stripe Connect, minimum $50 threshold

25% recurring is competitive for SaaS (industry range: 20–30%). Melies, ImagineArt, and TopMediai all land in this range. Higher than 25% compresses margins at BCS's price points; lower than 20% won't attract serious promoters.

Who Qualifies

Affiliates must apply and be approved. This is not open to all customers by default. Ideal affiliates:

Creative Partners Tier Phase 2

For top-performing affiliates who also create BCS content. Modeled after ImagineArt and Melies partner programs:

Commission
30%
Upgraded from 25% base tier
Monthly Credits
250
For creating BCS tutorials, demos, and showcases
Perks
Early Access
New features before public launch + featured showcase

Tracking Stack

Layer Purpose Recommended Tool
Referral link (?via= param) Primary attribution Rewardful or FirstPromoter
Coupon code Catches podcast/YouTube where nobody clicks Same platform
Stripe webhook Confirms real payment, renewal, refund Native Stripe integration
First-party cookie (60-day) Cross-session attribution Rewardful/FirstPromoter

Anti-Fraud

Attribution — Preventing Double-Pay

When both programs run, the same person could trigger both a referral and affiliate conversion. One attribution layer, one reward per conversion.

Scenario Who Gets Credit Why
User enters a referral code manually Referral program (credits) Typed code = strongest intent signal
User clicks affiliate link, no referral code Affiliate program (commission) Last-click via tracked link
User clicks affiliate link THEN enters referral code Referral program (credits) Manual code overrides stored cookie
User enters referral code THEN clicks affiliate link Referral program (credits) First-touch referral wins

Rule: An entered referral code always beats a stored affiliate cookie. Typing a code is a deliberate action; clicking a link is passive. This prevents the most common attribution conflict.

Implementation Roadmap

Phase 1 — Referral Program Launch Weeks 1–4

Month 1
  • Build in-app referral link generator (unique per user)
  • Implement two-sided credit award system (50 each)
  • Add referral prompt on post-generation success screen
  • Add referral widget to main navigation with visible reward
  • Build referral dashboard (my link, credits earned, friends invited)
  • Anti-fraud: self-referral blocking, device fingerprinting

Success metric: 20%+ activation rate (users engaging with referral feature within 30 days)

Phase 2 — Affiliate Program Launch Weeks 5–8

Month 2
  • Integrate Rewardful or FirstPromoter with Stripe
  • Set 25% recurring commission, 60-day cookie, 45-day hold
  • Create affiliate application form and approval workflow
  • Build affiliate resource kit (banners, email copy, demo videos)
  • Recruit first 10–20 affiliates from existing user base + outreach
  • Set up attribution dedup logic (referral code > affiliate cookie)

Success metric: 10+ active affiliates, first commission payouts processed

Phase 3 — Optimize & Scale Months 3–6

Months 3–6
  • A/B test referral trigger placements and copy
  • Test personalized referral landing pages (mention referrer's name — Cello data: +50% conversion)
  • Launch Creative Partners tier for top affiliates
  • Add branded share watermarks to generated content
  • Email nurture sequence for dormant referrers
  • Monthly review: referral activation, sharing rate, conversion rate, CAC by channel

Success metric: 15%+ of new signups from referral channel, CAC 30%+ below paid channels

Benchmark Targets

Based on verified SaaS case studies, these are realistic targets for the first 6 months:

Metric Target Industry Benchmark Source
Referral activation rate 20–30% 25% (Smoobu), 30% (Shore) Cello data
Sharing rate (of activated) 15–20% 17% (Smoobu), 50% (Sagetap) Cello data
Referred signup conversion 20–30% 23% (Shore), 66% (B2B financial) Multiple
Free-to-paid conversion (referred) 40–55% 55% (Smoobu), 62% (Shore) Cello data
% of new signups from referrals 10–15% 16% (RealtyNinja), 25% (Unbounce via partners) Impact, PartnerStack
CAC reduction vs paid channels 30–50% 33% (Shore), 50% (Moss) Cello data

What Competitors & AI Platforms Do

Platform Referrer Gets Friend Gets Trigger Cap
RunningHub 500 RH Coins 500 RH Coins Signup None
Manus 500 Credits 500 Credits Signup None
Genspark 1,000 Credits 1,000 Credits Signup + phone verify 5,000 credits
Runway 1,000 Credits 1,000 Credits 2 months paid None
Viyou AI 500 Credits 500 Credits Signup 100 friends
Blaze.ai 200 Credits Friend subscribes None
Creator AI 1,000 Credits 1,000 Credits First purchase None
MotionGen 20 Credits 20 Credits Signup None

Recommended Tooling

Need Tool Cost Notes
Referral tracking + rewards Build in-app (Convex + Stripe) $0 (engineering time) Simple enough for a two-sided credit system; no third-party needed at this stage
Affiliate tracking Rewardful $49/mo (Starter) Stripe-native, handles cookies + coupons + payouts. FirstPromoter is the alternative ($49/mo)
Affiliate payouts Via Rewardful (PayPal/Stripe) Included Automated monthly payouts, no manual invoice processing
Email notifications Customer.io (already have) $0 Referral nudges, reward confirmations, dormant referrer re-engagement

Risks & Mitigations

Risk Impact Mitigation
Low activation — users don't discover the referral feature Program dead on arrival Embed in main nav with visible reward amount (Moss: +140% activation). Trigger at moments of delight.
Self-referral / gaming Credits given for fake signups Device fingerprint + payment method matching. Flag, review, don't auto-reject.
Credit inflation — too many free credits diluting paid value Users stop paying Referral credits are bonus, not enough to replace a subscription. Monitor credit redemption vs paid usage ratio monthly.
Affiliate program too small to matter Wasted tooling investment Start with manual outreach to 10–20 creators before automating. Only upgrade to Rewardful once there's proven demand.
Attribution disputes Double-pay or angry partners Single attribution layer with clear precedence rules (referral code > affiliate cookie). Document in both program ToS.

Sources & Case Studies