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
| ID | Requirement | Priority | Owner |
|---|---|---|---|
| R-01 | Users can generate personalised referral links from any workspace. | Must | AMAlex |
| R-02 | Invitees see a co-branded landing page with the referrer's name and reward. | Must | NCNaomi |
| R-03 | Rewards are queued and released only after fraud checks pass. | Must | SRSam |
| R-04 | Admins can configure reward amounts and eligibility windows. | Should | PSPriya |
| R-05 | Support agents can revoke rewards with a full audit trail. | Should | DADiego |
| R-06 | Referral dashboard shows per-user attribution and payout state. | Should | AMAlex |
| R-07 | Localised copy in EN, ES, DE, and FR at launch. | Could | NCNaomi |
| R-08 | Native 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
| Metric | Baseline | Target | Timeframe |
|---|---|---|---|
| K-factor | 0.28 | 0.45 | 90 days post-GA |
| Fraud rate | 3.9% | <1.5% | 30 days post-GA |
| Referral attribution | 9% | 18% | Q4 2026 |
| Time-to-share | 42s | <15s | at GA |
Risks
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| 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 serviceOwner: Trust & Safety teamTech
- Payouts provider contractOwner: FinanceVendor
- Reward T&Cs reviewOwner: Legal counselLegal
- Growth analytics dashboardsOwner: Data platformTeam
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
| Version | Date | Author | Notes |
|---|---|---|---|
| v1.3 | 2026-07-05 | Alex Morgan | Added fraud-gate acceptance criteria and payout SLA. |
| v1.2 | 2026-06-28 | Priya Shah | Reframed objectives around K-factor and attribution. |
| v1.1 | 2026-06-19 | Naomi Chen | New personas and updated landing-page requirements. |
| v1.0 | 2026-06-10 | Alex Morgan | Initial draft. |