Public number: 67 weekly users. So I built a tool for myself instead

Before treating 67 WAU as traction, I’d break source: GA4 sessions vs Search Console clicks (you mentioned ~2–3/week) vs direct/referral. That tells you whether the public number is product use or just noise. For Triage, optimize week-2 return and one successful export over install count. Time-box any “tool for myself” side bet to 1–2 days with a kill rule, or it quietly eats the main loop.

Checking Markers' 266 users before expecting anything is the most underrated move in this post. Most people build first and look at the competitor's numbers after launch.

I'd run the same reality check on ResuHive, because it's the one with a real market behind it. Resume tools is a category where plenty of companies clearly pay to acquire users: you can see their active Facebook/Instagram ads for free in the Meta Ad Library, and their pricing pages tell you what a user is worth to them. If the big players are spending on ads for keywords close to yours, your 354 impressions aren't a demand problem, they're a distribution problem, and that changes what you work on next.

Good luck with the Web Store review.

Something in your numbers doesn't line up, and I think it's the most useful thing to look at. 10 Search Console clicks in 28 days is roughly 2-3 a week, but GA4 shows 67 active users in 7 days. So most of your traffic isn't coming from Google.

Have you checked the GA4 traffic source breakdown? It could be direct visits or a referral you didn't know about, or it could be bots or your own visits inflating the count. If it's a real channel, that's the thing to double down on before Triage even clears review.

The asset here isn't Triage, it's that your extension template turns a one-day build into a repeatable way to show up inside someone else's ecosystem — Markers' 266-in-4-years ceiling matters a lot less when the cost of each attempt is a day.

Your 354 impressions / 10 clicks resonates. We run an SEO tool — 4 visits a month right now, DA 3. Sharing real numbers is uncomfortable but it's the only way to build in public honestly.

The "bugged me every single day" line is the most reliable product signal I've seen. Market research, surveys, competitor analysis — none of them match the certainty of scratching your own itch daily. If you're the first power user and you can't stop using it, the product-market question becomes distribution, not validation.

The 266 users after 4 years for Markers is actually useful data. When you can see the ceiling clearly, you stop optimizing for growth anxiety and start shipping for utility. That's a better headspace for building. One-day build on a SaaS template plus real competitor benchmarking — that's a more honest launch process than most Series A decks describe.

The one-day build is the right cost for this kind of bet — the danger with "built it for myself" tools is they quietly eat weeks. My rule: side bets get time-boxed to a day or two; anything longer has to earn a slot on the main roadmap. And the metric that matters isn't install count, it's whether Triage feeds ResuHive: if one Triage user a month turns into a real conversation about your main product, the extension pays for itself even at 50 installs. At 67 weekly users you can still talk to everyone, so pair the public number with one user conversation a week — the scoreboard is good content, but the interviews are the strategy.

thats intresting. i love building my own tools also to solve my problems. i remember when i built an automation tool because doing it with python became a long task i started with minor task and bam it became a huge project and a serious automation tool

"This is such a relatable journey! Building a tool out of personal need is often how the best solutions are born. Moving past the initial review hurdles and focusing on actual user engagement makes all the difference. Wishing you great success with it!"

Install count may be the wrong next number. For a triage tool, I’d watch how many people classify a few products, export once, then come back the next week. One install proves curiosity. A second session proves the workflow found a place.

I actually like the way you're tracking the numbers honestly. With 67 active users, I'd be more interested in understanding where those users came from and what made them stick than chasing bigger traffic immediately. That could reveal the most repeatable acquisition channel before you scale anything.

Once Triage is live, what result would make the ecosystem exposure worth maintaining—new ResuHive visits, signups, or something beyond installs for the extension itself?

Respect for the honest number. With 67 weekly users you can still ask every one of them something. A single question after they finish a resume ("what almost made you leave?") would tell you more than the Search Console numbers right now.

respect for posting the real number. 10 clicks off 354 impressions is about 2.8%, which isn't bad at all for a brand new site, so the bigger lever is probably getting more impressions in the first place. building something you use every day is a good call too, you'll hit every annoying edge before a user does

Love this angle. Building Xstream4K right now so this hits close to home — what made you look into it in the first place?