38 founders told me what was wrong with my Chrome extension. Here's what I learned.
Three weeks ago I posted honestly about FocusForge. 18 installs, 0 signups, no idea why. I expected a few polite responses. I got 38 comments from founders who had clearly been through the same wall.
Here's what they actually told me.
The free tier wasn't the problem.
My first instinct was that the free tier was too generous. Founders pushed back immediately. RebeccaGaskell put it cleanly, if people install it once and disappear, a paywall won't fix anything. The real question is whether they're coming back at all. At 18 installs I had no data to answer that. I was diagnosing the wrong problem.
The activation event is missing.
Strategy_master introduced a frame I hadn't used before the activation event. The specific moment after which the product has started working for the user. Without defining that moment, there's no onboarding goal to optimise toward. For FocusForge I eventually landed on it the first time the extension actually blocks you from a site you were about to waste time on. Everything before that is setup. That moment is the product.
Ask when they have something to lose.
BoringMoney said something I wrote down immediately. Don't ask for account creation before the value moment. Ask right after it. When someone has just saved 23 minutes or got blocked from Reddit for the first time that's when "create an account to save your progress" makes emotional sense. Right now my signup prompt appears before any of that happens. Completely backwards.
The 48 hour window is everything.
GrowthWithShehroz and hilgard both pointed to the same thing from different angles. Most churn happens before the user forms a mental model of what the product is for. If someone doesn't come back within 48 hours of installing they almost certainly never will. That window is the entire game for Chrome extensions and I had no visibility into whether people were returning or not.
Utility before identity.
Aryan_sinh's diagnosis was the sharpest on the product positioning side. Users install FocusForge, use the free layer, and mentally file it as a blocker. A blocker is something you install and forget. A personal execution system is something you check in with daily. Those are completely different products even if the features overlap. The AI coaching layer is supposed to be the identity piece something that knows your patterns and talks to you about them. But if nobody signs up they never reach it.
What I'm building next based on all of this.
Jaisree suggested locking focus history and streaks behind an account not as a paywall but as a reason to save progress. The value of the account grows with usage rather than being a gate before usage. That's the conversion mechanic I'm implementing next.
The post-install "what brought you here today" question from hilgard is going into the next update. Five real answers will reshape the Chrome Store description more than any analytics.
The first block triggered event is the north star metric I'm instrumenting. Not installs, not opens the moment the product actually did something.
The honest state of things.
FocusForge now has 39 installs. Prompt Helix has 55. Both £0 revenue still. But I understand the problem more clearly than I did three weeks ago and I have a specific list of things to build that came directly from founders who've been through the same wall.
That's worth more than another week of guessing.
If you're building a Chrome extension or any freemium product and hitting the same activation problem. what was the thing that actually moved the needle for you?
helixlabs.studio
The pattern I'd flag on any 38-founders-feedback exercise is that the feedback you get is almost never about the thing the founders think they're giving feedback on. They're answering a different question than the one you asked, and the gap between those two questions is the actual signal.
What people will tell you in a feedback call is what they noticed in the first 90 seconds. That's the answer to "what was your first impression," which is a useful question but a very different question from "what would make you a daily user." The first-90-seconds feedback skews toward visual / onboarding / first-action issues, because those are the things that have happened to the person by the time the call started. The daily-use issues are invisible to feedback calls because the feedback caller has not lived with the product.
So 38 founders giving you the same three complaints means you have a strong signal about the first 90 seconds. It does not mean you have a strong signal about the product. You usually also need a second feedback round that asks the people who actually use the extension for two weeks straight what almost made them quit on day 8, and that round will produce a totally different list of issues that none of the 38 first-impression founders mentioned.
The other thing I'd watch for is the rank-order trap. When 12 of 38 founders mention the same issue, it feels like the top priority. Sometimes it is. But sometimes it's just the most articulable issue, and the actual blocker is something harder to put into words, which is why nobody mentioned it. The 1-of-38 weird-specific complaint is worth taking seriously if it explains why someone churned.
Curious which of the 38 pieces of feedback was the one you almost dismissed and then ended up acting on. Those are usually the most expensive lessons in feedback rounds, and they're the ones I'd want to read.
This update actually makes the Xevoa question more urgent, not less.
Almost everything you’re building next points beyond “blocker”:
activation event
48-hour habit loop
saved progress
streaks
AI coaching
something that knows your patterns over time
That is not Chrome extension positioning. That is personal execution system positioning.
FocusForge explains the first utility, but it may keep anchoring users to the wrong mental model: “site blocker.”
Xevoa fits the product you’re moving toward: cleaner, broader, more software-native, and not trapped inside the first feature.
The risk now is that you keep improving the product while the name keeps training users to remember the old category.
That’s why I’d pressure-test it seriously before the next update ships, not after.
you're making the argument more precisely each time and I hear it. the product is moving toward personal execution system territory. the streak, the coaching, the pattern recognition over time. FocusForge as a name does anchor people to blocker territory before they reach any of that.
I'm going to be honest.. I'm not ready to commit to Xevoa yet but I'm taking the category shift argument seriously. the real test is whether the product experience can make users feel "this knows me" before they mentally file it as a blocker. if the activation fixes work and people reach the AI coaching layer the name might matter less than the experience. if they don't reach it the name is the least of my problems.
going to keep building and revisit this properly before the next major update ships.
That’s fair.
I wouldn’t ask you to commit before you’ve pressure-tested the product experience.
But I also wouldn’t wait until after the next major update to decide whether the name is helping or fighting the shift.
The practical question is simple:
Before the next update ships, should the product be introduced as a stronger FocusForge, or as the beginning of a broader personal execution system?
That decision affects onboarding, copy, account creation, coaching language, and what users think they’re signing up for.
So even if you don’t rename today, I’d separate the decision into two parts:
does the product direction need a broader brand?
if yes, is Xevoa the right one to secure before the update makes FocusForge more fixed?
Happy to pressure-test that privately and keep it practical.
This comment was deleted 4 months ago
This comment was deleted 4 months ago