Referral Program

Track referral invitations, conversion, rewards, top advocates, fraud checks, and campaign performance for a product-led referral program. This example brings Overview and Referrals together so administrators and growth teams can find the next task without losing context.

It includes representative records such as Product-team referrals · 31% and Customer-success referrals · 26%. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Referral Program

Template facts

Screen

Analytics

Primary action

Invite friends

Pattern

Analytics

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product and growth teams need to invite friends while keeping invites, activated and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Overview gives users an obvious place to start.
  • Supporting view: Referrals keeps the related context close.
  • Primary action: Invite friends stays visible when people need it.
  • First signal: Invites shows a useful value (1.8k).
  • Second signal: Activated gives additional context (428).
  • Sample record: Product-team referrals · 31%.
  • Next record: Customer-success referrals · 26%.

States worth designing

  • No results for the selected range: say what changed, protect progress, and offer a clear next step.
  • Refreshing with old values visible: say what changed, protect progress, and offer a clear next step.
  • Metric source unavailable: say what changed, protect progress, and offer a clear next step.
  • Filter changed the interpretation: say what changed, protect progress, and offer a clear next step.
  • Export preparing: say what changed, protect progress, and offer a clear next step.
  • Restricted data hidden: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Overview → Referrals → Invite friends → Review outcome

Patterns used

Analytics, Overview, Referrals, contextual actions, error recovery

Why these choices work

Keep the time range and metric definition visible. Let people see which segment or filter produced the result, then explain missing or delayed data.

Pay attention to overview and referrals. People need to distinguish Product-team referrals · 31% from Customer-success referrals · 26%. Keep invites visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Invite friends”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Workspace Transfer, Loyalty Program, Webhook Settings.

Start from this in Figr

Design a referral program screen inside our existing product. Use our current components, tokens and content language. Include Overview and Referrals views, credible records like Product-team referrals · 31%, and a clear “Invite friends” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr