Launched FocusForge today! Product two of HelixLabs. Here's what I learned building it.
Two products live now. Here's the honest state of things.
Prompt Helix: 95 total installs, 3 signups, 1 weekly active user, £0 revenue. Conversion mechanics went live April 3rd with a 25 query daily limit.
FocusForge live today. AI powered doomscrolling intervention tool. Time tracking, site blocking, grayscale mode, AI coaching via BYOK, and a Nuclear Option that locks every distracting site for up to 8 hours with zero bypass.
What building product two taught me — the infrastructure compounds. Same Vercel backend, same Clerk auth, same Stripe setup, same BYOK model. FocusForge launched with production ready infrastructure on day one because Prompt Helix already built it. The marginal cost of each new product drops significantly.
FocusForge also launched with proper freemium from day one because Prompt Helix taught me the hard way that unlimited free with no conversion trigger is a hobby not a business.
Next up: CookieNuke in May.
The ecosystem thesis is that each product makes the others more valuable and cheaper to acquire. Tokyolore articulated it better than I have in the comments on my last post which is worth reading if you're building a multi-product suite.
First paying user is still the milestone I'm chasing. Two products with conversion mechanics now means two chances at it.
Chrome Store: chromewebstore.google.com/detail/focusforge/hdkabchfflgnnonnhffkcmhgbenfoaci
Website:
helixlabs.studio
Happy to answer questions about the BYOK model, the ecosystem strategy, or the freemium mechanics.
Shipping product two is the right move.
But the real signal here is not “two products live.”
It’s that you’re already learning distribution, conversion, and monetization at the system level instead of per-product.
That’s the compounding asset.
Most indie builders launch product two as another bet.
This is stronger because product two is improving the acquisition and monetization logic of product one.
That said, “HelixLabs” still sounds like the holding company.
The products are getting sharper faster than the brand frame is.
Once one of them starts converting, the parent brand probably needs to feel more like a real product system and less like an internal studio label.
Xevoa.com would carry that much better if the suite becomes the actual business.
This is the most useful framing I've gotten on the brand question. You're right that HelixLabs reads as an internal studio label right now rather than a product system people opt into.
The honest answer is I've been heads down on shipping products and haven't stress tested the brand at the system level. The individual products have clear value props but the parent brand doesn't yet have a "why would I think of myself as a HelixLabs user" answer.
I think that answer emerges when ClarityOS bundles Prompt Helix, FocusForge and CookieNuke together. at that point HelixLabs stops being where the products live and starts being the thing people subscribe to. But you're right that the brand needs to get there before the product does or the conversion moment gets lost.
On Xevoa interesting. What's the thinking behind that name specifically?
Because it reads like product infrastructure, not a side-project lab.
HelixLabs sounds like where things get built.
Xevoa sounds like the thing customers actually buy into.
That matters once the value shifts from:
“here are my tools”
to
“this is the system these tools belong to”
You already have product-level value.
The next layer is making the parent brand feel like the operating system, not the workshop.
That’s where Xevoa fits better.
Short, ownable, software-native, and broad enough to hold multiple products without sounding like an internal dev label.
genuinely useful framing, the shift from workshop to operating system is exactly what ClarityOS is supposed to do. that's the moment where the parent brand needs to feel like something customers buy into rather than where products get made.
not going to change the name right now. too much infrastructure tied to HelixLabs and the products are still proving themselves. but the operating system framing is how I'm thinking about ClarityOS and ClarityEngine. those bundles are where HelixLabs stops being a label and starts being the thing.
Xevoa is interesting though its short, ownable, software native. bookmarking that thinking for when the suite is further along
That’s fair, but this usually slips faster than founders expect.
The moment ClarityOS becomes the thing users evaluate, HelixLabs stops reading like the product and starts reading like the company behind it.
That gap gets expensive fast.
You can defer the rename.
You usually cannot defer the perception shift once users start buying the system instead of the tools.
That’s the point where the parent brand starts affecting conversion, not just aesthetics.
Xevoa is less about “later rebrand” and more about not letting the suite outgrow the wrapper right as it starts compounding.
you're making a more urgent version of the argument and I hear it. the perception shift happening before the rename does is the real risk. not the rename itself.
honest answer is I'm watching for the signal you're describing. the moment users start evaluating ClarityOS as the thing rather than the individual tools is when the parent brand becomes a conversion variable. I don't think that moment has arrived yet but you're right that I won't see it coming until it's already happening.
keeping Xevoa in the back pocket. if ClarityOS starts converting and the parent brand becomes a friction point that's the trigger to move fast on it.
what made you land on Xevoa specifically as the name?
Because Xevoa has the opposite read of HelixLabs.
HelixLabs sounds like the place where products are made.
Xevoa sounds like the product layer users buy into.
It has that short, software-native feel without locking you into one feature, one workflow, or one category.
That matters if ClarityOS becomes the front door.
You don’t want the parent brand to sound like a builder studio while the suite is trying to feel like an operating layer.
The reason I’d think about it earlier is simple:
by the time the signal is obvious, the name decision gets more expensive.
If Xevoa is the direction you’d want once the suite starts compounding, it’s worth securing before that moment, not after.
the builder studio versus operating layer distinction is the clearest version of the argument you've made and it lands. HelixLabs does read as where things get made rather than what users buy into.
I'm going to be honest. The question is whether securing Xevoa now is worth the operational cost before there's revenue to justify it. Domain, rebranding the Chrome Store listings, updating every platform. That's real work at a stage where shipping products matters more than brand architecture.
What would you do in my position. secure the name now and sit on it, or wait until ClarityOS has its first paying customers?
One quick follow-up on this.
I still think the cleanest move is not “rebrand now,” but “control the option now.”
If ClarityOS starts getting paid users and Xevoa is still the direction you’d want for the operating-layer brand, owning it early removes a future constraint without forcing any immediate change.
The actual rebrand can wait.
But the name decision becomes harder once revenue, listings, users, and public perception start compounding around the suite.
If you want, we can talk privately and I can keep the Xevoa side very simple.
This comment was deleted 2 days ago.
BYOK means your users need to use their own API key, right?
Isn't this introducing friction and making it harder for end users to use all features of your products?
Yes BYOK does add friction. I won't pretend otherwise. You need an API key from Anthropic or OpenAI before the AI features work.
The tradeoff is privacy and cost transparency. Your API key never touches my servers, your conversations go directly from your browser to the AI provider, and you pay your provider directly at cost rather than paying a markup through me. For privacy conscious users that's actually a selling point not a barrier.
The target user is someone who already uses ChatGPT or Claude and has or can get an API key. That's not everyone but it's a real and growing segment. Total beginners who've never touched an API are probably not my primary market right now.
That said it's a real limitation and something I think about.
The free tier features being time tracking, site blocking, grayscale mode, daily reports all work without any API key. You only need BYOK for the AI coaching layer. So most of the core value is accessible immediately with zero setup.