E-Commerce Tips
Why Friends & Family Loyalty Mechanics Drive Referral Growth
60% of one loyalty app's signups came directly through a Friends & Family invite. Here's how that mechanic out-paced an established, multi-year programme.

Danny Khow, Co-Founder & Managing Director5 min read
Most loyalty programmes grow the same way: sign up, get points, maybe tell a friend if you happen to think of it. A Friends & Family mechanic changes that by making the invite itself part of how the programme works, not an afterthought bolted onto marketing. We wanted to know whether that actually shows up in the growth numbers, so we compared two loyalty programmes we've built: one with the mechanic, one without.
The mechanic, in plain terms
A Friends & Family group lets a member invite others into a shared group and earn loyalty points together. Instead of one account collecting points in isolation, a household or a friend group pools progress collectively. That one design choice changes the underlying incentive: inviting someone isn't just a favour, it's the fastest way to make your own points balance grow faster. The member is motivated to recruit, not just to redeem.
Two real programmes, compared anonymously
To keep this comparison fair to both clients, we're not naming either programme here; the underlying data is real.
Programme A is an established, multi-year retail loyalty programme without a Friends & Family mechanic. Over two years, it built a large membership base at a steady, sustained daily signup pace, backed by an already well-known, trusted retail brand with an existing customer base to draw from.
Programme B is a newly launched loyalty app, built around a Friends & Family mechanic from day one, with no existing digital membership base to migrate in. Within its first two months, it grew at a daily signup pace roughly 15% faster than Programme A's two-year average.
| Programme A | Programme B | |
|---|---|---|
| Friends & Family mechanic | None | Built in from day one |
| Time running | Over two years | First two months |
| Starting base | Existing customer base to draw from | No digital membership base |
| Brand recognition at launch | Established and trusted | Newly launched |
| Daily signup pace | The two-year baseline | Roughly 15% faster |
| Signups arriving via invite | Not applicable | 60% |
Put side by side, a brand-new programme with zero starting base didn't just keep pace with an established, multi-year programme, it grew modestly faster, on a daily basis, in a fraction of the time. That's not a small result. Programme A had every structural advantage: an existing customer relationship, brand recognition, and two years to compound. Programme B had none of that going in, and still out-paced it, largely on the strength of a mechanic that turns every member into a recruiter.
Programme A isn't an isolated comparison point either. Outside this pair, Bridzia has built standard loyalty programmes, without a Friends & Family mechanic, for four other retailers. We don't have the same early-adoption-window pace data for all of them that we do for Programme A specifically, so we're not claiming the 15% gap holds identically across every one. What it does mean is this comparison isn't drawn from a single convenient pair; it sits against a broader base of programmes built the standard way.
We want to be honest about what this comparison can and can't prove. These are two different brands, two different industries, and two different marketing budgets, so we can't isolate the Friends & Family mechanic as the sole cause with scientific certainty. What we can say is that the direction and the size of the gap are exactly what you'd expect if a referral mechanic were doing real work, and that's consistent with what we'd predict from how the mechanic is actually designed to function.
That prediction holds up against a more direct number too: 60% of Programme B's signups came directly through a Friends & Family invite. That's not a side effect of the mechanic, it's the majority of how the programme actually grew. The pace comparison above shows the outcome; this is the mechanism producing it.
Why it works
A referral built into the product itself has two advantages over a referral bolted onto a marketing campaign. It reaches people through a channel with far higher trust than an ad, a message from a friend rather than a brand. And it's ongoing rather than a one-time push, since the incentive to invite doesn't disappear after a launch campaign ends; it's structurally part of how the programme works every day.
There's a retention side-effect too, one that's easy to miss. A member in a shared points group isn't just deciding whether to keep using the app. They're deciding whether to keep using it along with the people they invited, which raises the cost of walking away.

The governance problems nobody thinks about until they hit them
A Friends & Family mechanic sounds simple in a pitch deck: invite people, pool points, done. What actually makes or breaks it in production is a set of edge cases that have nothing to do with the reward logic and everything to do with what happens when real people behave like real people. We've already built the rules to handle each of these.
What has to be decidedWhat goes wrong if it isn't
Group admin
Who holds authority
A group with no designated owner has no clear authority to add or remove members, or to make decisions on the group's behalf. Every group needs a defined admin from the moment it's created, not as an afterthought once a dispute forces the question.
Forced removal
How a dispute ends
Friend groups and families fall out. The system needs a way for the admin to forcibly remove a member, not just a way to invite one in, or the mechanic quietly becomes something members feel stuck in rather than something they chose to join.
Points on exit
What leaves with them
If points are pooled, a member leaving (voluntarily or removed) raises an immediate question: do their earned points stay with the group, or does some portion follow them out? Leave this undefined and you'll find out the hard way, through a support ticket, which answer your members expected.
Admin succession
What happens when the owner quits
If the admin leaves the app or deletes their account, the group needs a defined succession path, whether that's auto-promoting another member, requiring the group to nominate a replacement, or a clear dissolution process, rather than being left in a broken, ownerless state.

None of these are reward-logic problems. They're product-governance problems, and they're exactly the kind of thing that looks like a minor detail in a planning meeting and becomes a real support burden within weeks of launch if it isn't decided upfront.
What this means if you're designing a loyalty programme
A few practical things worth getting right before launch, not after:
- Decide how points are shared. Fully pooled group points, a bonus only for the person who invited, or a hybrid, all create different incentives, and the choice should match how your product is actually used.
- Set a sensible group size limit. Uncapped groups invite abuse; too small a cap limits the mechanic's reach before it gets going.
- Build fraud prevention in from the start, particularly if points convert to real monetary value, since a referral mechanic is also the most obvious thing to try to game.
- Make the invite flow itself frictionless. A mechanic this effective can still underperform if inviting someone takes more than a couple of taps.
- Resolve the four governance questions above before launch, not after the first support ticket forces the decision.
If you're building or rethinking a loyalty programme and want a referral mechanic that's actually structured to work, talk to us about Loyalty CRM.
Keep reading
Related articles
More on platforms, integration, and how buyers find brands.

E-Commerce Tips
AI Discovery Starts on Your Own Site, Not ChatGPT
74% of Malaysian shoppers already use AI while shopping. What Adobe Commerce Live Search and AI recommendations delivered across 4 real implementations.
Read the article
E-Commerce Tips
Upgrading to Adobe Commerce 2.4.8: What Actually Breaks
Across 4 upgrades to Adobe Commerce 2.4.8, 9 out of 10 installed extensions needed patching — Firebear and Amasty included. Here's what to plan for.
Read the article
E-Commerce Tips
How to Launch an Adobe Commerce Store in Malaysia Faster
What actually compresses an Adobe Commerce launch — scope discipline, localisation decided early, and integration proven first — without shipping regret.
Read the article
