The 3-link cap we got wrong

The logic that seemed sound

When we designed the free tier, the thinking felt obvious: you give people unlimited links and they'll spam. Three links felt like a fair trial. Test the platform. See the dashboard. Earn a bit. Then upgrade to Pro if they wanted more.

It made sense in spreadsheets. It made sense in conversation. "We need to encourage conversion," we said. "Free users should see enough to understand value but not enough to sustain themselves without paying." Classic freemium thinking. Reasonable. Safe.

We weren't wrong about spam risk, exactly. But we were wrong about who our free tier actually was.

What we missed about real communities

The people signing up for Rippl weren't casuals looking for side money. They were Discord moderators with 2,000 engaged members. WhatsApp group founders who'd built trust over years. Telegram channel owners with niche audiences that actually cared about recommendations. These weren't influencers chasing followers. They were community builders protecting reputation.

The ones who hit that three-link limit first weren't spammers. They were exactly the people we wanted most. A student ambassador promoting a product to her cohort. A Discord mod who believed in a SaaS tool and wanted to share it with his server. A Telegram founder with a financial-independence community spotting relevant brands.

They did what we wanted: they tried the platform, saw it worked, earned a payout. Then they ran into the wall. And many just... left. Didn't upgrade. Went quiet. Not because Rippl failed them, but because the friction of adding a subscription to test something felt too high.

The moment we changed our minds

By week eight we were seeing the pattern. Users with the highest engagement rates, the ones generating trackable, verified clicks, were the ones most likely to churn after exhausting their three links. They weren't the problem. They were the solution wearing a constraint we'd invented.

We sat down and asked ourselves a harder question: why do we actually have a cap? The real answer wasn't to prevent spam. We have verification, click tracking, and fraud detection for that. The cap was there as a sales mechanism, and an honest one, but a mechanism nonetheless.

Yasmin didn't need to be convinced Rippl was valuable. She'd already decided. She just needed permission to use it.

So we changed it. The free tier still exists, still has limits, still encourages people toward Pro's unlimited links and priority campaign access. But it's not a hard stop anymore. It's an invitation to grow.

What changed, and what stayed

We kept the free tier itself. We kept Pro at £9.99 a month with unlimited promotional links. We kept the identity verification (either free over time or £9.99 to fast-track). We kept the founding-promoter tiers in the MRVL 500 program for serious builders. Nothing about Rippl's core model changed.

What changed was us removing an artificial barrier that was stopping good people from doing good work. The kind of barrier that felt smart until real users showed us it was just noise.

The lesson wasn't that paywalls are bad. It was that paywalls should solve actual problems, not create them to sell solutions to those problems.

Why this matters for how we build

This is the kind of thing that doesn't make headlines. No feature launch. No big announcement. But it mattered to us because it changed how we think about the people who use Rippl. Not as users on a funnel, but as community owners with real stakes in authenticity and trust. If they're recommending something to their group, they've already made a choice about quality. Our job isn't to convince them a second time with friction.

Most of what we've shipped in the months since has come from listening harder to that type of feedback. The earnings dashboard that shows real-time payouts. The campaign priority system that rewards consistent performers. The ability to track conversions, not just clicks, so a promoter can prove value to their community. These came from real messages, not from roadmap meetings.