The 30-day trial trap
Most SaaS trials follow the same script: 30 days, full feature access, then you either pay or get shut off. The conversion game is "get them hooked before day 30." But that framing pushes the user toward a quick "no" — they're evaluating, not committing.
For ScsDriver (a Windows service that maps WebDAV / Nextcloud / Aliyun / Google Drive into a real drive letter) we tried something different this quarter.
How the new program is structured
- 7-day full-feature trial on signup — every user gets it
- Referral unlocks: every friend who joins with your invite code adds +7 days to your own trial (uncapped)
- Lifetime license holders can share invite codes too, but don't gain days for themselves (already paid); they benefit by giving their trial-stage friends more time to evaluate
- Pricing after trial: $1.99/month or $9.99/year
So instead of "30 days then you decide," you have "7 days that grows with every friend you bring in."
What changed for us
- Onboarding got social. Users have a reason to talk about the product with their friends — the invite link is a feature, not a marketing afterthought.
- Comparison windows naturally extended. A solo user gets 7 days. A user with 5 friends who also signed up has 5 × 7 = 35 days. That's enough to A/B test against RaiDrive, CloudDrive2, native WebDAV, etc.
- Lower-friction conversions. People who hit a paywall after 60 days of free use are much more likely to pay than people who hit one after 7 days. They're invested; they've already integrated the tool.
What surprised us
The biggest surprise: people on extended trials convert at a lower rate, not higher, because they're locked into a comfortable no-payment groove. We offset that by sending reminders at day 21 / 49 / 77 of the cumulative trial, with side-by-side comparisons vs the paid tier (e.g. "this many files you've mounted, this many GB transferred").
Is this right for your product?
It works for us because:
- The product is sticky once installed (drive letter = OS-level integration)
- Friends of friends tend to be in the same tech circles (self-hosters, NAS admins)
- The cost of an extra 30 days of trial is low (server CPU, no per-user license fees)
It probably wouldn't work if your product is one-shot (a calculator, a PDF converter) — there's no compound engagement from the second user.
If you're thinking about restructuring your trial, the two design questions that matter most:
- What's the smallest "social unit" that pays the referral? Friend pairs? Friend chains? (we picked pairs, no chaining, no cash kickbacks — too much gaming risk)
- What's the cap on extended trials? Infinite feels generous but lets users park forever; 90 days forces a decision; 30 days defeats the purpose
Curious how other teams are handling this — anyone running a referral-extended trial in production? What broke?
Top comments (4)
@elijahbrown great question — uncapped is the riskiest part. So far we've seen:
The defensive design: invites must be from a unique email AND that email must verify before days are added. Each invite = one verified human.
Your two suggestions are sharper than what we have:
Thanks for the feedback — we'll ship at least the first one in the next iteration.
The thing I'd expect to break first is the uncapped part. Anyone can invite themselves with a few throwaway inboxes and get another week each time, so the "friend" is really the same person. Two cheap fixes: only add the days once the invited account actually mounts a drive, not at signup, and count a referral once per machine, since a Windows service can usually read a stable machine ID. Checking the invitee's email domain against a known throwaway list catches the lazy version too. Your day 21 / 49 / 77 reminders with real usage numbers are a nice touch.
Thanks for the question. Let me share what we kept vs. removed.
What we kept:
The 7-day trial itself. Enough time for real evaluation of a WebDAV mount tool.
Quality scoring on the invitee side. We track whether the invitee actually uses the product, not just that they clicked the link.
Cap = 3 daily limit. Single biggest quality lever (covered in a separate post).
What we removed in v3.0:
What I'd add next:
A "referral cooldown" — credit the inviter 3-7 days after the invitee activates, not instantly. Filters out one-click-delete invitee accounts.
Cap=3 has been the single most important decision. Every public metric becomes an attack surface — default to hidden, expose only what users need to make decisions.
Hiding the invite counter and the leaderboard makes a lot of sense. The delayed credit is the one I'd ship first, since it costs almost nothing and kills the create-then-delete invitee accounts. A cap of 3 a day limits each inviter, but one person with a few accounts can still invite themselves, so tying the credit to the invitee actually using the product is what does most of the work, and it sounds like your quality scoring already gets you there.