Know which loop you are building
Loops fail when you copy the mechanic without the motive. There are only a few that work, and which one fits depends on whether your product is better with other people in it, or just better talked about:
- Collaboration loop: the product needs a second person (a shared doc, a review, an approval). The invite is the feature, not a growth tactic.
- Artefact loop: the product makes something the user publishes anyway. Every artefact is an ad seen by exactly the right audience.
- Incentive loop: both sides get something real for the referral. Works when the reward is the product itself, rarely when it is cash.
- Status loop: using the product publicly says something flattering about the user. Leaderboards, badges, streaks, public profiles.
If none of these fit honestly, skip this chapter and spend the time on distribution. A bolted-on referral program with nothing behind it is the single most common dead feature in SaaS.
Brand the output, carefully
Anything your product generates that leaves the product should say where it came from: a corner mark on an exported video, a "Made with ___" footer on a shared page, a signature line on outbound email. This is the cheapest loop to build and the easiest to overdo.
- Make the mark small, legible and clickable, and put a real URL behind it
- Free tier carries it, paid tier removes it. Removing the badge is a genuine reason to upgrade
- Never brand something the user would be embarrassed to publish; that trades their credibility for your reach
- Track it as a channel with its own UTM, or you will never know whether it works
Make the invite the shortest path
For collaboration loops, the invite has to be easier than the workaround. If sending a link is slower than screenshotting the thing into Slack, the loop never starts. Invited users should land on the exact object they were invited to, already in context, with signup happening after the value, not before it.
Count how many clicks and how many seconds it takes to get a second person looking at something in your product. That number is the loop's real growth rate.
Referrals: give the product, not cash
Cash rewards attract people who want cash and churn immediately. Credits, extra usage, a free month or an unlocked feature attract people who want the product, and they cost you margin rather than money. Reward both sides: the sender needs a reason to send, the receiver needs a reason to accept from someone who just pitched them.
- Ask for the referral at the moment of delight, right after the product worked, never on signup
- One click to send: pre-written message, pre-filled link, no dashboard to visit
- Show the reward status in the product, so a pending referral nags gently
- Cap or verify to stop the obvious self-referral loop before it starts
Ship public artefacts
Anything the product can publish to a URL is a page that can rank, be shared and be found: public profiles, shared results, embeddable widgets, leaderboards. The user gets a link worth sending; you get an indexed page you did not have to write. This is where the growth-loop chapter and the SEO chapter meet, and the pages compound the same way.
Make the public version genuinely public: no signup wall to view, noindex off, and a title that reads as a real page. A shared link that demands an account converts nobody and ranks for nothing.
Instrument it or you are guessing
A loop is a number: how many new users each existing user brings, and how long they take to do it. Track invites sent per active user, acceptance rate, and time from signup to first invite. If invites sent per user is under a few percent, the loop is decoration and the honest move is to cut it rather than keep tuning the button.
Key moves
0/7Reading is warm-up. Check these off as you actually ship them; progress saves in your browser.
Loops need traffic to loop
A referral engine with nobody in it does nothing. Viraloop keeps the top of the funnel full, so the loops you build have users to compound.