The Problems
01
The reward wasn't worth it.
The old incentive was weak. The team's working assumption: users saw the reward, didn't feel it justified the effort of referring someone, and moved on without sharing.
02
There was no tracking — at all.
Users couldn't see who they'd referred, which referrals were active or expired, or how much they'd earned. Without a feedback loop, the program had no way to build momentum. Users referred once, saw nothing, never came back.
03
It ignored how Xflow users actually work.
Xflow accounts have owners and employees. Both could refer — but the old program had no concept of individual rewards. An employee who made a successful referral had no way to receive anything for it.
Industry Research: What 12 platforms taught me about selling a referral.
I reviewed 12 platforms, ranging from B2C products like INDmoney and Uber to B2B competitors including Skydo - a direct parallel to Xflow in the cross-border payments space. Three patterns stood out:
Key Takeaways
Sell it, don't just show it
Every platform that drove high referral adoption used bold illustrations and prominently displayed the reward amount — large, impossible to miss. The referral section wasn't treated like a feature; it was treated like an ad. This was true even on platforms whose core product UI was minimal or utilitarian - including Skydo.
Show "How it works"
Every platform included a clear step-by-step section explaining how to earn. The copy was doing heavy lifting here - efficient enough that users wouldn't skip it, specific enough to remove doubt about when and how they'd get paid. The goal wasn't to be thorough, it was to be trusted quickly.
Most Competitors only showed totals earnings
Across both B2C and B2B platforms, the pattern was the same: total earned, total successful referrals. A reasonable baseline — but it doesn't answer the questions users actually have. Who specifically referred someone? Which referrals are still active? Which ones expired before hitting the threshold?
Before Successful Referral
“How do I refer my friend?”
“How do I know my friend signed up?”
“How do I know that I’ve earned a reward?”
After Successful Referral
“How do I know which friends led me the rewards?”
“How do I know the Payment Method?”
“How do I change the Payment Method”
“How do I change the email id for Amazon Gift Card?”
“How do I know, when will my Payment will be Processed?”
“How do I know, if my rewards have initiated?”
“How do I know, if my rewards have processed?”
After Rewards are Processed
“How do I know how much I have earned in previous month?”
“How do I know which friends led me the rewards in previous month?”
“How do I know, through which method I got paid?”
Information Architecture
Refer a Friend
Referral Link
Email Input Field
How Referrals Work
Terms and Conditions
Earnings Details
Total Earnings
Processed Earnings
To-be Processed
Referral Metrics
Referrals Signed up
Referrals Earned
Referrals Expiring Soon
Referral Expired
Friends Details
Friends Nick Name
Friends Email
Signed up Date
Earned on Date
Status
Monthly Earnings Metrics
Month Cycle
Month Drop-down
Monthly Earning
Current Payment Method
Update Payment Method
Rewards Processing Date
Initiated Date
Processed Date
Wireframes
A dedicated tab for tracking referrals and earnings supports the transparency and scalability of the program. Users can view their current and past monthly earnings, along with their payment destinations.
BEFORE
25th–25th
Initiation on the 25th, processing on the 28th. Cycle straddled two calendar months. Users would see month labels change inside the product while their actual calendar hadn't moved — disorienting and easy to misread.
AFTER
Calendar Month
Cycle realigned to the standard calendar month. Initiation moved to the 1st of the following month, processing to the 3rd. Eliminated the overlap and removed the program's biggest source of confusion.
ORIGINAL
INR 3,000.00
Original reward value. Real-term value would drift with currency fluctuation, creating an inconsistent perceived reward across users and over time.
FINAL
USD 30.00
Aligned with backend, product and business teams. Resolved tracking complexity, kept the reward structure intact — a copy-level fix because the underlying IA was solid.
