After shipping a referral extension for the trial of my WebDAV mount tool, I started getting invitations from people I barely knew. Most I accepted. Some I declined. Here's the pattern.
Invitation 1: The cold LinkedIn pitch
"Hi! I see we both work in developer tools. I'd love to extend your trial if you try my new SaaS product."
I declined. The exchange felt transactional, not relationship-driven. The ask was: "give me your email, install my tool, and I'll click yours." No context, no shared interest, no follow-up plan.
What made it decline-worthy
The ask was framed as a favor to me, but the underlying transaction was clearly beneficial to them. No effort to build actual connection first.
What I'd accept instead
"Hi, I'm building X, saw your post about WebDAV mounts, think we have overlap. Would love to chat, no strings." Then later: "BTW, I extended my trial with your tool — happy to extend yours if you want."
The relationship comes first. The referral is a byproduct.
Invitation 2: The colleague from 8 years ago
"Long time! Saw your post about ScsDriver. I'll download it if you do the same with my new product."
I accepted. We had shared history (worked together at a startup that failed). The relationship was real even if faded.
Why it worked
- Reciprocity wasn't the basis of the original relationship
- The exchange acknowledged shared history
- Both sides genuinely wanted to try the other's product
Invitation 3: The stranger who read my blog posts
"Hey, I've been reading your posts for 6 months. Your WebDAV tool solved a real problem for me. I'd love to extend your trial."
I accepted. The referral was unsolicited but the relationship was real — they were a regular reader.
Why it worked
- No immediate ask
- Specific reference to past value (your posts)
- No quid pro quo framing
Invitation 4: The "I have 50 friends who need this"
"I can refer 50 people from my Discord. Each one will get +14 days for both of us."
I declined. Bulk invitations feel gamified, not authentic.
What made it decline-worthy
- Treating referrals as a quantity game
- Discord-style community invites often don't convert to real users
- Suggests the inviter doesn't care about who actually uses the product
Invitation 5: The person who asked me first
"I'd love to extend your trial. Can I also get your feedback on my product?"
I accepted. They asked for value (feedback) without demanding reciprocity. The frame was collaborative, not transactional.
The pattern I noticed
Accept when:
- Real relationship exists (even if dormant)
- The ask is specific and contextual
- Reciprocity is implied, not demanded
- Both sides get value beyond +14 days
Decline when:
- Cold outreach with no prior context
- Bulk / gamified framing
- Pure quid pro quo with no relationship
- Asks feel spammy
What this means for product design
If you're building a referral extension, the temptation is to optimize for invite volume. Resist. Optimize for invite quality.
Two patterns that work:
- Cap rewards at 5-10 invites per user (limits spam behavior)
- Highlight when someone has been invited multiple times (signals spam)
Two patterns that hurt:
- Unlimited invites (the "social network" trap)
- Bonuses for high-volume inviters (creates spam)
For ScsDriver specifically
We cap the visible daily limit to 3 invites. Some power users work around it by waiting 24h between batches. That's fine — they're being respectful of the system. The ones who spam it get rate-limited silently.
The takeaway
A referral extension is a relationship tool, not a growth hack. Treat it accordingly. Decline invitations that feel transactional. Accept ones that build on real context.
Your trial extension budget is limited. Spend it on people who would also recommend you in a forum, not just click your link.
Top comments (0)