Product Requirements Document · v1.3

Referral Program v2

Double-sided incentives with fraud-aware payouts

In review
Owner
AMAlex Morgan
Version
v1.3
Target release
Sep 15, 2026
Last updated
7/5/2026
Contributors
PSNCSR
Linked roadmap

Overview & Vision

The current referral loop was built in 2023 for a self-serve audience and no longer reflects our multi-product portfolio. This PRD redefines the referral experience as a native part of the product, with contextual invitations, transparent reward tracking, and safeguards against abuse.

Turn every satisfied customer into a growth channel by making it effortless to invite peers, receive shared value, and understand the impact of their advocacy.

Objectives & Business Goals

  • 1Lift K-factor from 0.28 to 0.45 within one quarter of GA.
  • 2Reduce referral fraud rate to under 1.5% of activated invites.
  • 3Attribute at least 18% of new self-serve signups to referrals by Q4 2026.
  • 4Create a reusable rewards service other product areas can plug into.

Personas

M
Maya, the Senior PM
Senior Product Manager at a Series B SaaS
32, urban, 8 yrs in product, remote-first
Goals
  • •Ship a validated PRD every two weeks
  • •Align engineering and design early
  • •Track KPI movement per initiative
Pain points
  • •PRDs sprawl across Notion pages
  • •Stakeholders miss key context
  • •No consistent template across squads
Motivations
  • •Career growth
  • •Team velocity
  • •Clear ownership
J
Jordan, the Founder
Solo technical founder, pre-seed
28, moved fast from engineering into product
Goals
  • •Pitch investors with a crisp product plan
  • •Turn ideas into scoped documents in minutes
Pain points
  • •No PM background
  • •Struggles to structure requirements
  • •Wastes weekends rewriting docs
Motivations
  • •Speed
  • •Fundraising
  • •Learning by example
R
Rania, the Business Analyst
BA at a healthcare enterprise
40, hybrid, 15 yrs in banking + health
Goals
  • •Translate business needs into requirements
  • •Maintain traceability from goal to acceptance criteria
Pain points
  • •Compliance overhead
  • •Long approval cycles
  • •Fragmented tooling across teams
Motivations
  • •Quality
  • •Traceability
  • •Stakeholder trust

Requirements

IDRequirementPriorityOwner
R-01Users can generate personalised referral links from any workspace.
Must
AMAlex
R-02Invitees see a co-branded landing page with the referrer's name and reward.
Must
NCNaomi
R-03Rewards are queued and released only after fraud checks pass.
Must
SRSam
R-04Admins can configure reward amounts and eligibility windows.
Should
PSPriya
R-05Support agents can revoke rewards with a full audit trail.
Should
DADiego
R-06Referral dashboard shows per-user attribution and payout state.
Should
AMAlex
R-07Localised copy in EN, ES, DE, and FR at launch.
Could
NCNaomi
R-08Native mobile share-sheet integration.
Could
SRSam

User Stories

  • As a customer, I want to invite a peer in under 15 seconds so I can share a tool I love.
  • As an invitee, I want to see who invited me and what I unlock so I trust the offer.
  • As an admin, I want to tune reward amounts by segment so I can control unit economics.
  • As a support agent, I want to inspect a reward's status so I can resolve disputes quickly.
  • As a finance lead, I want a monthly export of paid rewards so I can reconcile accounts.

Acceptance Criteria

Generate a referral link
Given
a signed-in user on any workspace page
When
they open the referral panel
Then
a unique link is generated, copied to the clipboard, and preview cards render in <300 ms.
Fraud gate
Given
an invitee completes signup
When
the fraud service flags the account as high risk
Then
the reward moves to a 'held' state and no payout is released until a reviewer approves it.
Reward payout
Given
an approved reward reaches its release date
When
the payout worker runs
Then
the reward is credited within 60 seconds and both parties receive an email confirmation.

KPIs & Success Metrics

MetricBaselineTargetTimeframe
K-factor0.280.4590 days post-GA
Fraud rate3.9%<1.5%30 days post-GA
Referral attribution9%18%Q4 2026
Time-to-share42s<15sat GA

Risks

RiskLikelihoodImpactMitigation
Reward abuse via disposable emails
High
High
Layered fraud checks + hold period.
Regulatory constraints on incentives (EU)
Medium
High
Legal review per market, feature flags per region.
Third-party payout provider downtime
Low
Medium
Failover provider + queued retries.
Brand confusion on co-branded landing
Medium
Low
Design QA and A/B test hero copy.

Dependencies

  • Fraud scoring service
    Owner: Trust & Safety team
    Tech
  • Payouts provider contract
    Owner: Finance
    Vendor
  • Reward T&Cs review
    Owner: Legal counsel
    Legal
  • Growth analytics dashboards
    Owner: Data platform
    Team

Release Plan

Alpha
8/4/2026
  • •Internal dogfood on Skyline workspace
  • •Web-only invitation flow
  • •Manual reward approval
Beta
8/25/2026
  • •Opt-in for 20 friendly customers
  • •Automated fraud gate
  • •Admin config UI
GA
9/15/2026
  • •All plans
  • •Native mobile share sheet
  • •Localised copy in EN/ES/DE/FR

Open Questions

  • Do we allow stacking of referral rewards with account credits?
  • What is the SLA for fraud-review turnaround?
  • Should Enterprise customers get a self-serve reward configuration or a services-led one?

Change Log

VersionDateAuthorNotes
v1.32026-07-05Alex MorganAdded fraud-gate acceptance criteria and payout SLA.
v1.22026-06-28Priya ShahReframed objectives around K-factor and attribution.
v1.12026-06-19Naomi ChenNew personas and updated landing-page requirements.
v1.02026-06-10Alex MorganInitial draft.