April 12, 2026
Why We Killed the 7-Day Free Trial
By Chaminda · 5 min read
Two weeks ago, ReplyWisely had a 7-day free trial on every plan. No credit card required. Sign up with your email, get a verification code, get an activation token, install the extension, use it free for 7 days, then pick a plan.
Over those 14 days, zero people converted to paid.
Not "a handful." Zero.
That is the cleanest signal I have ever gotten that a funnel is broken. This post is about what I think was wrong, what I changed, and the thing I am most proud of: how the new paywall handles the moment you stop paying.
The diagnosis: friction before value
The old flow made you do four things before you ever saw ReplyWisely working on a real tweet:
- Click "Start Free Trial" on the website
- Enter your email and wait for a 6-digit code
- Copy the activation token from the dashboard
- Paste the token into the extension, then go find X.com
By step 4, a meaningful chunk of people had already bounced. The ones who made it through were already filtered for "people who are patient with signup flows." That is not the same population as "people who will love ReplyWisely."
Worse: the trial clock started before they had replied to a single tweet with the extension. Day 1 of the trial was them figuring out what the green dots meant. Day 7 was them deciding whether to pay. There was no day where the value was obvious and the ask was small.
The new flow: install first, pay when the value is obvious
Here is what ReplyWisely does now:
Install the Chrome extension. No signup, no email, no credit card.
Open x.com or pro.x.com. A quick in-feed tour walks you through every mode and asks for your X handle so reply tracking works.
Reply to tweets with the extension active. Highlight, Score, and All modes all work immediately. Green triangles on high-potential tweets, keyword glow on your niche conversations, checkmarks on tweets you replied to.
After a handful of replies, a side panel slides in. That is the paywall. Pick a plan to keep scoring and highlighting. Or drop to Track-only and keep the checkmarks on what you already replied to.
The trial clock is replaced by a reply counter. The counter only ticks when you actively post a reply through the X compose box — not when you scroll, not when you idle, not when you open the Hub. It counts what matters: you used the extension to do the thing.
The paywall fires after you have already seen what the extension does on tweets you actually cared about. That is when "should I pay $5.75/month" becomes answerable.
The honest part: ghost triangles
Here is the part I am proud of. When the paywall fires, you can dismiss it ("Remind me later") and keep using X — but the extension degrades visibly.
Any tweet that would have gotten a colored VPS triangle now shows a grey dotted triangle instead. Same size, same position, but no color, no score number, no factor breakdown. Hover over it and the tooltip says "ReplyWisely score is hidden — click the triangle to choose a plan."
Keyword highlighting — the glow on your niche terms — goes away entirely.
Checkmarks on tweets you already replied to stay, in full color. That is your history. I am not holding it hostage to make you pay.
The reason I did this instead of just removing all the triangles: if the extension silently stopped working, you would forget it was there. And you would feel tricked when you eventually noticed. Ghost triangles are the honest answer: the scores are there, but you have to pay to see them. No sleight of hand.
It also means: every high-value tweet in your feed shows you a dotted outline. Every "I could be replying to this one" moment is visible. The paywall is not "a wall" — it is a running reminder of what you are leaving on the table.
What happens when you actually pay
Stripe Checkout collects your email inside Checkout itself (which you were going to give Stripe anyway). After you pay, the extension polls every 5 seconds — within 10 seconds, all the ghost triangles flip back to real colored ones, the keyword highlights come back, and the side panel auto-dismisses.
Your account is created automatically from the email you gave Stripe. There is no second signup. No activation token to copy. No "check your inbox to verify" step. You pay, the extension works, done.
What if you uninstall?
This was the edge case I spent the longest on. Your install is identified by a random UUID stored locally in Chrome. If you uninstall, switch browsers, or clear browser data, that UUID is gone.
So: after you pay, Stripe has your email. If you reinstall on any browser on any device, you can go to replywisely.com/recover, enter that email, and get a 6-digit code (not a magic link — codes are less likely to get flagged as phishing). Enter the code in the browser you want to use, and the new install is bound to your account. You can do this once every 7 days.
That is the entire recovery flow. Three fields on one page.
What I am watching now
The uncomfortable version of this decision: it is possible the new model also converts at 0%. If the value isn't there, a better funnel won't rescue it — it will just let more people discover the gap.
But I believe the opposite. I think the old funnel was filtering out the people who would have loved ReplyWisely before they got to see it. The ones who made it through were the patient, process-oriented signup-completers, not the fast-movers who are actually trying to grow on X this week.
Over the next 30 days I will be watching: install rate, replies per install, paywall trigger rate, paywall → checkout click rate, checkout → paid conversion, and paid → 30-day retention. If the numbers don't move, the problem isn't the funnel.
If you have been on the fence, now is a genuinely low-risk time to try it. Install, use it for a week on your own feed, decide if the scores match your intuition about which tweets were worth replying to. If yes, pay. If no, you have lost nothing.
Current pricing:
- Monthly: $9.99/month, cancel anytime
- Annual: $69/year ($5.75/month) — best value
Install and try it on your feed
Free to install. No signup, no credit card. Paywall fires after your first handful of real replies.
Try for FreeQuestions or feedback: reply to me on @chams_builds. I read everything.