10 weeks in, 95 installs, £0 revenue, second product submitted. HONEST UPDATE
Ten weeks since Prompt Helix launched. Here's where things actually stand.
Prompt Helix has 95 total installs from organic Chrome Store search. 3 real signups. 1 weekly active user. £0 revenue.
The conversion mechanism 25 daily query limit with upgrade prompts went live April 3rd. First real shot at a paying user since then.
FocusForge submitted to the Chrome Store this week. AI powered doomscrolling intervention tool. Time tracking, site blocking, grayscale mode, AI coaching via BYOK, and a Nuclear Option that locks you out of every distracting site for up to 8 hours with zero bypass. Pending review right now.
The honest lesson from week one to ten was that the free tier is everything. Prompt Helix launched with unlimited free usage and nobody upgraded because nobody needed to. FocusForge launched with a proper freemium model from day one. Free tier shows you the value. Paid tier removes the friction of hitting limits.
Building toward 6 Chrome extensions by August then two SaaS bundles — ClarityOS and ClarityEngine. Each extension feeds the next. Each product makes the others more valuable.
Next milestone is getting my first paying user before end of April. That's the only number that matters right now.
What's been the hardest part of your freemium conversion journey?
helixlabs.studio
Respect for the honest update — this level of transparency is underrated.
The “unlimited free → no upgrade pressure” insight is something a lot of early SaaS builders only learn after shipping.
One thing I’ve noticed with freemium products is that conversion isn’t just about limits — it’s also about return behavior. If users don’t come back within the first few days, they never even reach the upgrade moment.
Curious — are you doing anything yet to drive repeat usage, or is that something you’re still experimenting with?
Repeat usage is honestly the thing I haven't solved yet. Right now the only retention mechanic is the query limit itself. hitting it daily means coming back daily. But you're right that if someone doesn't return in the first few days they never reach that moment. Working on a re-engagement email sequence next. What's driving return behaviour for you?
The unlimited free tier lesson is one I nearly made myself. I just launched IronCaption — AI captions for gym creators — and set the free tier to 1 caption per day from day one specifically so people hit the limit quickly and feel the upgrade trigger.
Ten weeks in with honest numbers posted publicly takes guts. The hardest part of freemium conversion for me so far is getting people to even reach the limit — most free users try it once and don't come back the next day.
Trying to solve that with a daily reminder email. Still early days but curious if you found anything that brought free users back consistently?
1 caption per day from launch is smart. you learned the lesson before paying for it. The return behaviour problem is exactly what I'm wrestling with now. The daily limit only works if they come back to hit it. I don't have the email infrastructure set up yet which is probably the gap. How's the daily reminder email performing for you so far?
Honestly the daily reminder email isn't live yet — I mentioned it as something I'm planning to solve the problem rather than something already working. Still in the early days of figuring out the infrastructure side.
But your point about the limit only working if they come back is exactly the problem I'm staring at. The free caption generates fine, the product works — I just can't force people to remember it exists the next day.
I think the email is the obvious fix but I'm also wondering if there's something on the product side — like making the first caption generation feel so good that people want to come back without being reminded. Still figuring that out.
What's your current thinking on solving the return problem — are you leaning toward email or something else?
honestly I don't have the email infrastructure set up yet either so we're in the same boat. the return problem is real. the limit only works if they remember the product exists.
my current thinking is that the daily query counter itself is the nudge. if someone uses it enough to see "18 queries remaining today" they're already in the habit. the people who never come back probably weren't going to convert anyway.
but I think you're right that there's a product side answer too. the first experience has to be good enough that they think about it the next day without being prompted. for Prompt Helix that means the first time it saves them from copy-pasting context has to feel almost magical. if it does that once people remember it exists.
email is the safety net. product experience is the primary fix. at least that's where my head is at right now.
Product experience as the primary fix makes a lot of sense — if the first caption generation feels like a genuine upgrade from what they were doing before, they'll think about it next time they go to post. The magic moment has to do the heavy lifting before the email even matters. Going to focus on making that first output feel like a win rather than just a result. Appreciate the thinking, useful to know someone else is working through the same problem.
exactly. the magic moment has to earn the return visit, not the email. if the first use doesn't feel like a genuine upgrade they're not coming back regardless of how good your re-engagement sequence is.
the tricky part is that the magic moment is different for everyone. for Prompt Helix it's the first time someone asks a question about a page and gets an answer without copying anything. that has to land instantly or they're gone. still figuring out whether that's happening consistently for new installs or whether some people miss it entirely.
good luck with IronCaption im curious how the magic moment lands for gym creators specifically. that's a pretty defined use case which should make it easier to nail.
HelixLabs, moving from an "unlimited free" mistake with Prompt Helix to the "Nuclear Option" friction model in FocusForge is the ultimate validation of the freemium-to-revenue pipeline. By bundling these tools into an interconnected ecosystem like ClarityOS, you're shifting from selling single-use utilities to providing a comprehensive infrastructure for cognitive focus—where each install reduces the acquisition cost of the next.
I’m currently running Tokyo Lore, a project that highlights high-utility logic and validation-focused tools like yours. Since you’re building the definitive suite for digital sovereignty and focus, entering HelixLabs could be the perfect way to turn your "road to the first paying user" into a winning case study while your odds are at their absolute peak.
Thanks for this!! you've articulated the ecosystem thesis better than I have in most of my posts. The acquisition cost reduction per install is exactly the logic behind building 11 products rather than one. Each product makes the others cheaper to acquire and more valuable to keep.
Would love to know what you think of Prompt Helix if you get a chance to try it im always looking for feedback from people who actually understand the product vision. helixlabs.studio
That makes sense — the ecosystem logic is clear 👍
I’ll try Prompt Helix and share feedback.
Quick thought:
making the connection between tools obvious will be key — that’s where the compounding really shows up.
Also, I’m running Tokyo Lore — small round where we test products with real builders and see what actually sticks.
Could be a good fit for what you’re building.
Here’s the link: tokyolore.com 👍
Appreciate you coming back. You're right about making the connection between tools obvious. that's the ClarityOS bundle play eventually. Will check out Tokyo Lore properly.
That makes sense — once the bundle comes together, that’s where the real compounding shows up 👍
Right now each tool proves value individually, but the “why keep all of them” becomes obvious only when the connections are visible.
I’ll check out Prompt Helix and share proper feedback — curious to see how it feels in isolation vs as part of the system.
No rush on Tokyo Lore — take a look when you get time. I think your “ecosystem → lower CAC per product” logic would actually be interesting to test with real builders.
exactly! each tool has to earn its place standalone first. if Prompt Helix isn't useful on its own it doesn't matter that it bundles well with FocusForge later. the ecosystem logic only works if the individual products are genuinely good.
really appreciate you checking out Prompt Helix. and possibly the new focusforge recently released on web store. honest feedback from someone who understands the bigger picture is exactly what I need right now. curious whether the BYOK setup feels intuitive or creates friction on first use. that's the part I'm still not sure lands well for everyone.
will look at Tokyo Lore properly this week.
“Yeah that’s exactly it — bundle only works if each tool earns its place first.
I’ll test Prompt Helix + FocusForge properly and share detailed feedback.
Quick thought on BYOK:
it usually makes sense logically, but first-time users feel friction if the value isn’t obvious before setup.
If you can show:
→ what they’ll get
→ and why their key is needed
before asking for it, conversion usually improves a lot.
Curious to see how it feels in your flow.
And sounds good — whenever you get a chance to check Tokyo Lore.
Given what you’re building, the interesting part would be:
→ seeing which tool people actually adopt first
→ and whether that naturally pulls them into the rest of the ecosystem
That signal alone could be really valuable for your ClarityOS direction 👍”
the BYOK friction point is something I've been thinking about but haven't solved cleanly yet. you're right that asking for an API key before showing value is the wrong order. the current flow shows the sign in prompt before the user has experienced anything which is exactly backwards.
the fix is probably showing a demo or preview of what the AI coaching output looks like before asking them to set up their key. make the value tangible first then the setup feels worth doing.
on the ecosystem adoption sequence. that's actually a really useful research question I haven't thought to track. which product people install first and whether it pulls them into the second. my assumption has been Prompt Helix first because it's been live longer but FocusForge might actually be the better entry point for some users because the problem it solves is more immediately felt.
going to look at Tokyo Lore properly this week. genuinely curious about the methodology.