DEV Community

HelixLabs-dev
HelixLabs-dev

Posted on

18 installs, 0 signups. What Chrome extension onboarding actually looks like.

Two weeks ago I launched FocusForge which is my second Chrome extension. AI powered focus tool with time tracking, site blocking, grayscale mode, and a Nuclear Option that locks every distracting site for up to 8 hours with zero bypass.

18 installs from organic Chrome Store search. 0 signups. 0 revenue.
Here's what that taught me.

The free tier problem. AGAIN

Prompt Helix, my first extension, launched with unlimited free usage. Nobody upgraded because nobody needed to. Fixed that in v1.0.2 with a 25 query daily limit.

FocusForge launched with AI coaching and Nuclear Option locked behind a paywall. Core features — time tracking, site blocking, grayscale mode, daily reports — all free with no account needed.

Same mistake. Different product.

People install it, get real value from the free features, and have zero reason to create an account or upgrade. If the free tier is complete enough to solve the problem, the paid tier is invisible.

The return behaviour problem.

The conversion trigger only works if people come back to hit it. Someone who installs FocusForge, opens it twice, and forgets it exists will never see an upgrade prompt regardless of how well designed it is.

This is the problem I haven't solved yet. The first session has to be compelling enough that they think about it the next day without being reminded. For FocusForge that means the first time someone sets a time limit and gets blocked from a site has to feel genuinely useful — not annoying, not intrusive, actually helpful.

I don't know if that's happening yet. With 0 signups I have no data on what the first session actually looks like for real users.
What I'm building next to fix this.

A proper onboarding sequence. Right now someone installs FocusForge and sees the popup with no guidance on what to do first. The first session needs to walk them through setting their first time limit, show them their first daily report, and give them a reason to come back tomorrow.
The re-engagement email is the other piece but I don't have the email infrastructure set up yet. That's the next technical task.

The honest builder lesson.

Every metric problem in a Chrome extension eventually traces back to one of three things. Not enough installs, not enough return visits, or not enough upgrade triggers. I've been focused on installs through promotion. The return visit and upgrade trigger problems are what actually need solving now.

If you've built a Chrome extension and solved the day 1 to day 7 retention problem I'd genuinely love to know what worked.

Chrome Store: chromewebstore.google.com/detail/focusforge/hdkabchfflgnnonnhffkcmhgbenfoaci

helixlabs.studio

Top comments (0)