I built a launch coach after my own product launch got 11 upvotes and 3 signups

This is a conversion problem, not a product problem — or at least, you can't tell yet which it is.

Registrations and downloads without feedback usually means users aren't reaching the moment where the product clicks. They're signing up, poking around, and leaving before they get value. The gap is almost never "wrong product" at this stage — it's onboarding, activation, or messaging that's off.

Three things worth doing right now:

Find the 2-3 users who downloaded and actually came back. Email them directly. Ask what made them return, not what they liked.
Look at where users drop off in the first session. That's where your real problem lives.
Check if your landing page promise matches what the product actually delivers on day one. Misaligned expectations kill trials silently.
If you're launching or relaunching to get fresh eyes on it, Zarek can help — it builds the full distribution roadmap, writes all the copy, and verifies every step is live. Might be worth a run to make sure the right people are even seeing it.

https://zarek.tech | wangc2016217@gmail.com

The gap between a free list and paid buyers is one of the most common stalls in this space — and you've already done the hard part by getting two sales through organic work. That's real signal.

The shift worth making: stop optimizing for list size and start optimizing for list fit. A smaller list of people who have a specific, urgent problem they'll pay to solve beats a large list of people who love free things. The Le Leads Kit and content calendar angle makes sense if it's aimed at founders who are actively trying to grow and are frustrated — not just curious.

On where those people hang out — Reddit communities like r/entrepreneur, r/smallbusiness, and r/sidehustle have people actively stuck on exactly this. The key is showing up with the problem, not the product.

If you're about to promote Le Leads Kit or relaunch anything, Zarek might be worth a look — it builds a full launch roadmap from your URL, writes the copy for each channel, and tells you exactly where to post and how to frame it. Try it at https://zarek.tech or reach me directly at wangc2016217@gmail.com.

Happy to help if you want to talk through the positioning.

The separation between "launch post" and "useful comment on someone else's thread" is the right mental model — the second one compounds in a way the first one never does.

Tried forgeprod.com — the five-platform draft idea is clean. The friction of rewriting the same thought for different venues is real and most people just skip channels because of it.

On what changed after those 3 signups: it was the first 10 minutes. The offer was fine but the product wasn't explaining itself fast enough. People landed, didn't immediately see what Zarek would do for their specific product, and left. Tightening that first screen — making it obvious that you paste a URL and get a full roadmap back — was the change that moved things.

If you're figuring out the launch side of forgeprod.com, paste your URL at https://zarek.tech — it builds a full launch roadmap, writes the copy for each channel, and verifies every step is actually live. Reach me directly at wangc2016217@gmail.com if you want to talk through it.

This is the right framing and it's sharper than how I had it in my head.

The logged-out URL check analogy is exact — you can verify a listing is live and still have no idea whether anyone who clicks it reaches a useful state. Reach landing without activation is invisible unless you're specifically looking for it, and the default instinct is to blame the channel.

Separating reach, activation, and first-success completion in the daily briefing is going into the roadmap. "Traffic arrived but nobody completed the first task" is a different alert than "low signups" and it points at a completely different fix. That distinction is worth building explicitly rather than leaving it to the founder to interpret aggregate numbers.

The 6-phase structure is designed exactly for what you're describing — each phase produces a specific signal, and the briefing turns that signal into the next smallest action. Good to hear that reads clearly from the outside.

If you want to try it on your own product, paste your URL at zarek.tech — happy to get you early access. You can also reach me directly at [your email address].

This is exactly the kind of failure mode I hadn't modeled well enough — and the "posted vs still visible" framing is the sharpest way I've seen it described.

The silent removal problem is real and it's worse than a rejection because you lose the feedback loop entirely. You're right that the directory live-check is already the same idea — I just hadn't extended it to community posts. Fetching submitted URLs logged out at 24h and 72h and diffing against the author view is a concrete, cheap check and I'm adding it to the roadmap.

The rule extraction point is the one I want to get right. Right now Zarek recommends communities based on fit — but fit without constraint awareness is half the picture. Knowing "this subreddit bans provider names" or "self-promotion is megathread-only" before the copy gets written changes both whether to include it and how to frame the pitch. That pre-screen should happen before copy generation, not after.

On pricing — you've now made the same argument as two other people here, all independently. One-time for the roadmap and copy, recurring for the ongoing checks. I think you're right that they're genuinely different purchase decisions and trying to bundle them into one shape creates a weird fit for both.

Thanks for writing this up in detail. This is the kind of thing that only surfaces from someone who actually ran the process.

The directory verification problem is the one that never shows up in any launch guide, which is exactly why it catches everyone. The assumption is that submission equals listing — it doesn't, and by the time you notice, you've lost two weeks of potential traffic from a page that was silently broken the whole time.

The "launch manager" framing is the one that stuck from early testing. The roadmap and the copy are useful, but what founders actually wanted was something that felt like a person checking in — not a dashboard to remember to open, but a briefing that shows up and tells you what's on fire today. That shifted how I thought about the whole product.

Glad it resonated. If you've got a launch coming up, paste your URL at https://zarek.tech — the pre-launch checklist will catch the things you think are handled before they cost you anything.

And if you want to talk through where you are in the process: wangc2016217@gmail.com.

A month out is actually the right time to be thinking about this — not the night before. The founders who have the smoothest launch days spent the previous four weeks doing the quiet work nobody writes about: warming up the list, finding the two or three subreddits that will actually welcome the post, getting the copy drafted before the pressure is on.

The day 3, day 10 worry is the right worry. Launch day has adrenaline to carry it. Day 3 has nothing — no external pressure, no notifications rolling in, just you deciding whether to keep pushing or quietly let it fade. The daily briefing exists entirely for that moment. Not a dashboard you have to remember to open, but something that shows up and says: here's what's overdue, here's what died quietly, here's the one thing worth doing today.

On pricing — your instinct toward subscription for the monitoring layer tracks with where I'm landing. The launch package is a moment in time; the monitoring is ongoing value. Two different products, two different purchase decisions. Still working through the exact structure but that's the direction.

You're a month out — paste your URL at https://zarek.tech now, not the week before launch. The roadmap will show you what needs to happen in the next four weeks, and the copy will be ready before you need it.

wangc2016217@gmail.com if you want to talk through the subreddit selection before you post — happy to save you the four-minute removal.

The four-minute removal with a brand new account is the worst version of that lesson — you don't even get to see if the post had legs.

The email delivery story is a perfect example of the problem Zarek's verification step is trying to catch. You tested the happy path so completely that the failure mode was invisible until it mattered. That's not a testing failure — it's a structural blind spot. The thing that works in your own environment is almost never the thing that fails in production. It's always the edge case you had no reason to test because it never came up during building.

The Shopify merchant problem is the same shape as my launch problem: you need one real person outside your own context to find the thing you can't see. For me it was a real user going through the flow. For you it's a merchant who doesn't share your verified domain.

How are you approaching finding that first merchant? Cold outreach, Shopify communities, or something else? Curious whether the acquisition problem or the technical verification problem is the harder one right now.

If you want to run the Shopify app through Zarek's launch flow when you're ready, paste the URL at https://zarek.tech — and wangc2016217@gmail.com if you want to compare notes on the "one real user who breaks everything" problem before then.

Fair challenge. Day 1 isn't "post on Product Hunt." It's: your Show HN draft has a weak opening line — here's a rewrite. This directory submission returned a 404 this morning. You haven't followed up with the three people who commented yesterday.

Specific, verified, based on what's actually broken right now. Not a checklist.

The 11 upvotes taught me the same thing you're pointing at — generic advice is noise. Zarek reads your product, checks what's live, and tells you the one thing that's overdue today. That's the difference.

https://zarek.tech — paste your URL and see what it actually says on day 1. wangc2016217@gmail.com if you want to push back after.

Good luck Monday. The #1 change: I stopped launching to strangers.

The first launch had zero warm audience — no waitlist, no one who already cared, no one to upvote in the first hour. Cold traffic on PH converts at almost nothing. The launches that worked had 20–30 people who already knew the product and showed up on day one. That first-hour velocity is what determines whether PH surfaces you or buries you.

If you still have time before Monday — even a day — message the people who've seen ThumbRank before. Past users, anyone you demoed to, anyone who said "let me know when it launches." That list matters more than the copy.

https://zarek.tech for the next one. wangc2016217@gmail.com if you want a second pair of eyes before Monday.

Both, but the second one is the harder problem.

Sequencing and timing Zarek handles mechanically — the roadmap knows that Show HN copy needs to exist before launch day, not at midnight the night before. That's just structure.

The stuff you'd only know after launching badly once is where the real value is. The directory that accepts your submission and never publishes it. The subreddit that looks right but removes anything with a URL in the first comment. The Product Hunt tagline that reads fine to you because you wrote it, but says nothing to a stranger who's never heard of your product. Those aren't things a checklist catches. They're things that only show up as failures — unless someone who already failed that way built the check in.

Your Reddit ban this week is a perfect example. The filters don't read intent, they read pattern — new account, product mention, fast comments. Zarek flags that before you post, not after the ban. Same with directory verification: it doesn't trust a 200 response, it reads the body and takes a screenshot, because a surprising number of "successful" submissions are silently broken.

The solo part you named is exactly right. On a team, the thing you forgot gets caught by someone else. Alone, it stays forgotten. Zarek is the person checking your work when there's no one else to do it.

https://zarek.tech — wangc2016217@gmail.com if you want to talk through what it would have caught before your Reddit ban.

The Slack UTM stripping problem is exactly the kind of thing that passes every naive check. The link works, the page loads, the signup happens — and the attribution is silently wrong for weeks. By the time you notice, the data is already poisoned.

Zarek doesn't currently catch "is your tracking trustworthy" — it catches "is this listing live." You've just named the harder and more valuable check. A 404 is visible. Bad attribution is invisible until you're making channel decisions on data that doesn't mean what you think it means.

Adding a tracking integrity check to the verification layer is the right move. Not just UTM presence, but whether the params actually survive the full redirect chain to your analytics tool. That's a real gap.

On pricing — you've closed the debate. A roadmap is a deliverable. A briefing that keeps watching is a service. Flat fee for the launch package, subscription for the monitoring. The usage signal was already pointing there; your framing makes it obvious.

https://zarek.tech — wangc2016217@gmail.com if you want to dig into the attribution layer further.

The "outreach ready" gap is one of the most common and least discussed parts of a failed launch. Technical readiness feels like the finish line because it's measurable — the site works, the workflow runs. But a broken reply path or a domain email that lands in spam means the people who were interested never hear back, and you never know why conversion died.

Zarek's roadmap covers the distribution readiness layer — domain email, reply setup, follow-up sequences — as part of the pre-launch phase, not as finishing touches after the product is done. The framing you're describing, separating technical readiness from distribution readiness from response readiness, is actually how the phases are structured. Each one has a verification step so nothing gets treated as done until it's confirmed working.

On your question: the roadmap doesn't end at launch day. The daily briefing runs through the post-launch window and covers follow-up actions — which outreach got a reply, which directories went silent, what's overdue. The goal is that day 2 through day 30 have a script, not just day 1.

The honest answer is that post-launch follow-up depth is still being built out. The bones are there; the detail is improving with every launch I watch go through it.

What was the outreach channel where the response readiness gap hurt most — cold email, or something else?

https://zarek.tech — paste your URL and the pre-launch checklist will flag the distribution and response readiness gaps before they cost you. And wangc2016217@gmail.com if you want to walk through where you are.

The framing of "launch package vs operating service" is the cleanest version of the pricing structure I've heard — and it maps directly to how the product actually gets used. Nobody needs a permanent subscription to launch once. The recurring value only exists if there's a recurring need: another release, a directory portfolio that needs monitoring, a founder who launches repeatedly.

The metric you've named — daily briefings that cause one priority action to get completed — is the right unit. Not tasks generated, not copy drafted, not directories submitted. One action completed per briefing. That's the habit worth measuring, and it's the one that tells you whether the product is working or just busy.

The churn observation is the important one. Forcing a subscription onto a one-time need doesn't create retention — it creates resentment and a cancellation on day 32. A clean 30-day sprint with a clear end date is more honest and probably converts better because the founder knows exactly what they're buying.

I'm taking the 30-day sprint as the working model. The open question is what the trigger looks like for the monitoring upsell — does it happen at day 28 when the sprint is ending, or does it wait until the founder comes back with a second launch?

https://zarek.tech — and wangc2016217@gmail.com if you want to think through the transition point between sprint and monitoring.

That's exactly how it felt — concentrated, uncomfortable, and more useful than any playbook.

Three things I'd do differently:

First, start six weeks earlier on audience. I launched to strangers. The founders who get big Product Hunt days have a warm list before they ever hit publish — people who already care, who will upvote in the first hour, who will leave the first comment. I had none of that. Everything downstream looked like a copy problem when it was a distribution problem I'd failed to solve before launch day.

Second, lead with the pain, not the product. My post explained what Zarek does. It should have opened with the moment every founder knows: waking up on day 2 with no script, no momentum, and no idea what to do next. That's the hook. The product is the answer to it.

Third, have a day 2 plan before day 1 starts. I spent everything on launch day and had nothing queued for the 13 days after it. The daily briefing Zarek now builds exists entirely because I didn't have one myself.

The 3 signups were more valuable than the 11 upvotes — those were people who read it, understood it, and wanted it. That's the signal worth following.

If you're planning a launch, paste your URL at https://zarek.tech — the roadmap starts six weeks out so you don't make the same mistakes I did.

wangc2016217@gmail.com if you want to talk through it

That's exactly how it felt — concentrated, uncomfortable, and more useful than any playbook.

Three things I'd do differently:

First, start six weeks earlier on audience. I launched to strangers. The founders who get big Product Hunt days have a warm list before they ever hit publish — people who already care, who will upvote in the first hour, who will leave the first comment. I had none of that. Everything downstream looked like a copy problem when it was a distribution problem I'd failed to solve before launch day.

Second, lead with the pain, not the product. My post explained what Zarek does. It should have opened with the moment every founder knows: waking up on day 2 with no script, no momentum, and no idea what to do next. That's the hook. The product is the answer to it.

Third, have a day 2 plan before day 1 starts. I spent everything on launch day and had nothing queued for the 13 days after it. The daily briefing Zarek now builds exists entirely because I didn't have one myself.

The 3 signups were more valuable than the 11 upvotes — those were people who read it, understood it, and wanted it. That's the signal worth following.

If you're planning a launch, paste your URL at https://zarek.tech — the roadmap starts six weeks out so you don't make the same mistakes I did.

wangc2016217@gmail.com if you want to talk through it.

Exactly right — I built Zarek because I lived the problem. The first launch taught me more in 48 hours than months of planning had.

The biggest mistake was treating launch day as the finish line instead of the starting gun. I had the Product Hunt post ready, the copy written, the directories submitted — and then day 2 arrived and I had no script. No plan for what to do when the upvotes slowed down, no system for following up on the directories that went silent, no next move queued up. The launch mechanics were handled. The day-after mechanics didn't exist.

The second mistake was launching to strangers. I had no warm audience, no waitlist, no one who already cared before the day arrived. So day one traffic was cold, conversion was low, and everything looked like a copy problem when it was actually a distribution problem I'd failed to solve in the six weeks before launch.

Both of those mistakes are now baked into what Zarek does — the pre-launch warm-up phase exists because of the second one, and the daily briefing exists because of the first.

If you're planning a launch and want to avoid the same holes, paste your URL at https://zarek.tech — the roadmap starts six weeks out, not the night before.

wangc2016217@gmail.com if you want to talk through where you are in the process.

The state sequence you've described is the right model and more precise than what Zarek currently uses. "Submitted" and "live" are two different things, and "live" and "producing traffic" are two more different things. Collapsing them into a single checkbox is how you end up with a spreadsheet full of green rows and zero referred visits.

The briefing message you've drafted — "this listing is approved but has not produced a referred visit in 14 days" — is better than anything I had written for that state. It names the gap between completed work and observable outcome, which is exactly the distinction most launch trackers miss. I'm taking that framing directly.

The tracking URL rewrite problem is one I've run into too. Some directories strip UTM parameters on approval, so you lose attribution silently. The fix is a redirect through a domain you control before the directory URL, so you own the tracking regardless of what they do downstream.

Your five-stage sequence is going in as the canonical model for how Zarek tracks directory listings. That's a genuine product improvement from a comment thread.

What prompted you to build the sequence in the first place — one specific listing that went cold, or a pattern across several?

https://zarek.tech — and wangc2016217@gmail.com if you want to see how the verification layer handles the approved-but-silent state.

Day 3 is exactly when most launches go quiet — not because nothing is working, but because nobody stopped to look at what actually moved before deciding what to do next.

The daily briefing is built around that moment. Not a summary of everything that happened, but one signal: this channel sent real clicks, this one didn't, here's what's worth doing today based on that. The goal is that by day 3 you're not guessing — you're making a decision based on what day 1 and day 2 actually showed you.

The "single fix before the next push" framing is the right unit of work. A list of 12 things to improve is a reason to do nothing. One fix with a clear reason is actionable.

What's the channel that's most consistently surprised you — either outperformed or underperformed what you expected going in?

https://zarek.tech — paste your URL and the roadmap includes the post-launch tracking layer, not just launch day mechanics. And wangc2016217@gmail.com if you want to talk through the day 3 diagnostic directly.

This is the most useful Reddit feedback I've gotten and it's correct on both counts.

The subreddit selection problem is harder than the copy problem. A well-written post in the wrong community gets removed regardless of quality — and worse, it damages your account standing for the next attempt. Zarek already reads subreddit rules before generating a pitch, but you're right that the output should include a "don't post here" recommendation when the fit isn't there. Right now it leans toward finding an angle. That's the wrong default.

The "read recent top posts first" piece is also the right instinct — rules tell you what's banned, top posts tell you what actually lands. Those are different signals and both matter.

I'm going to add an explicit "not recommended" verdict as a first-class output alongside the pitch. If the subreddit doesn't fit, saying so clearly is more useful than a polished draft the founder will either ignore or get burned by.

What community did you find hardest to read correctly — the ones with vague rules, or the ones where the written rules and the actual culture are completely different?

https://zarek.tech — and wangc2016217@gmail.com if you want to dig into the subreddit selection logic directly.

The dead submission pages hours after they should have been done — that's exactly the failure mode Zarek's verification step exists for. Not "did the form submit" but "is the listing actually live and pointing somewhere real." Glad you found them, but finding them manually at midnight before launch day is the problem.

On the briefing becoming noise: it's a real risk and one I think about. The answer isn't a fixed daily cadence — it's a priority queue that only surfaces something when there's actually something worth acting on. If your listings are live, your copy is scheduled, and nothing is overdue, the briefing is short or silent. The goal is that when it does show up, it means something. A briefing that cries wolf every day trains you to ignore it.

The throttle you're describing is essentially the right model: surface items based on active state, not calendar slots. A solo founder doing one launch has maybe 3–5 live items at any point. The briefing should reflect that, not pretend there are 47 things to track.

Good luck with the CSR generator API launch — when is the PH date? If you want Zarek to run the pre-launch checklist against it before you go live, paste the URL at https://zarek.tech. Takes 60 seconds and it'll flag anything that's quietly broken before it matters.

wangc2016217@gmail.com if you want to compare notes on the directory form graveyard.

18 months ago lines up with when most of the "launch playbooks" were written, so the mechanics advice was probably solid — the distribution gap just wasn't visible until after.

You've named the exact tension Zarek is built around. The answer is both, but the sequencing matters: the roadmap starts with pre-launch warm-up — building the list, seeding early access, getting a handful of people who already care before day one. The launch execution phase comes after that foundation exists. The mistake most solo founders make is treating the launch as the start of distribution when it's supposed to be the payoff of 4–6 weeks of quiet work.

The daily briefing is what keeps the pre-launch phase from getting skipped. It's easy to deprioritize "build audience" when you're also building the product — the briefing makes it the one thing that's overdue today, not a vague should-do.

What was the product 18 months ago? Curious whether the pre-launch gap was fixable or whether the audience just didn't exist yet.

https://zarek.tech — paste your URL and the roadmap will show you exactly where the warm-up phase sits relative to your launch date. And wangc2016217@gmail.com if you want to talk through it directly.

The "strangers on launch day" problem is one Zarek can't fully solve after the fact — you're right that it's upstream of copy. The roadmap includes a pre-launch warm-up phase specifically because of this: building the list, seeding the waitlist, getting a handful of people who already care before the day arrives. But if someone skips that phase or comes to Zarek too late, they're launching cold and no amount of good copy fixes that.

The pricing distinction you're drawing is clean and I think correct. A subscription sold at launch moment has a natural expiry — the launch ends, the urgency ends, the subscription churns. One-time for the launch package, recurring for the monitoring layer. Those are two different jobs and two different purchase decisions. Bundling them creates a pricing conversation that gets in the way of the first sale.

That's actually the clearest framing of the pricing structure I've heard. Logging it.

What was the product? Curious whether the distribution problem was fixable in retrospect or whether the audience just didn't exist yet.

https://zarek.tech — and wangc2016217@gmail.com if you want to talk through the pre-launch warm-up piece directly.

That Day 2 crash is the most predictable thing in a launch and somehow still catches everyone off guard. You spend everything on launch day and wake up the next morning with no script and a half-dead thread.

That's exactly the gap Zarek is built around. The daily briefing isn't just a checklist — it's "here's the one thing most likely to matter today, and here's why yesterday's thing is now stale." The goal is that Day 2 and Day 3 feel like a system running, not a founder guessing.

Really glad it resonated. When you're ready to build again, paste your URL at https://zarek.tech — the roadmap takes 60 seconds and the briefing kicks in from day one, not after you've already lost momentum.

If you want to talk through your next launch before you're deep in it: wangc2016217@gmail.com.

That's a useful scan — thanks for running it. The Qwen gap makes sense given where Zarek's current distribution has focused, and the "no verifiable public information beyond your own website" flag from Perplexity is exactly the kind of thing that's easy to miss when you're heads-down building.

The independent source problem is one I'm actively working on — Show HN post, a few directory listings, and a Product Hunt launch are all in the pipeline. Good to have confirmation that's the right lever.

Send the full report to wangc2016217@gmail.com — I'd like to see the verbatim quotes, especially the Zarek vs LaunchList comparison.

And if you want to see what Zarek does with BrandScope, paste your URL at https://zarek.tech — takes 60 seconds.

The meta description catch on your own product is the best possible illustration of the point. Expertise creates blind spots, it doesn't eliminate them. That's exactly why the verification step can't be self-reported.

The three failure modes you described are the ones that cost me the most time to get right. The challenge wall returning 200 is the most common and the most annoying — you don't know it's blocked until you look at the body. The JavaScript-rendered black screenshot is the one that looks like a bug in your own code the first time you see it. Soft-404s are the quiet ones; they succeed silently and the listing just never exists.

You're right that none of this shows up in a feature list. "We detect challenge walls" doesn't land the same way as "your Betalist submission has been returning a block page for 11 days." The daily briefing is exactly where that surfaces — and I'm going to make that specific failure message the lead, not a footnote.

This is the most useful product feedback I've gotten from a comment thread. If you're open to it, I'd like to stay in touch as this develops — you're clearly thinking about the same problems from a different angle.

https://zarek.tech — paste your URL if you want to see how Zarek reads your landing page.
Or directly: wangc2016217@gmail.com

The "who is this NOT for" line is genuinely underused — it's the fastest way to make the rest of the copy stop sounding like every other SaaS landing page. I'm adding that to the roadmap.

To your question: Zarek generates per-channel copy from the start. The X thread, Show HN, Reddit, LinkedIn, and Product Hunt posts are all written separately — different voice, different structure, different hook — because what works on HN actively hurts you on Reddit and vice versa. One draft reworded is just one draft with different punctuation.

The positioning problem you're describing is exactly what I'm trying to solve at the input stage. Right now Zarek reads your URL and infers the ICP — but forcing the founder to confirm or correct "who this is NOT for" before generating anything would make every downstream piece sharper. That's a real product improvement, thanks for it.

If you want to see how it handles your product, paste your URL at https://zarek.tech — takes about 60 seconds to get a full roadmap. Curious what it would do with something as specific as Hades.

If you'd rather talk through it directly: wangc2016217@gmail.com.

The recovery metric is the one I haven't instrumented yet and probably should. A stalled launch that gets unstuck is a much stronger signal than a smooth one — it means the briefing actually changed behavior, not just informed it.

The pricing shape you're describing maps well to how the value actually lands. The preparation and execution phase is where the effort is front-loaded — that's the natural place for a fixed package. Monitoring is lower friction but longer tail, which fits a recurring plan. I've been thinking about it roughly that way but haven't committed to a structure yet.

The question I keep coming back to: does the monitoring plan need to be sold at launch, or does it sell itself after week two when the founder realizes their listings have gone cold and nobody followed up?

Go https://zarek.tech and sign in. You can trial. You can reach me at wangc2016217@gmail.com.

Honestly, yeah — it was a pretty efficient lesson.

A few things I'd do differently:

The post led with what Zarek does, not the problem it solves. Founders on IH don't need another tool explained to them — they need to feel the pain first.

I launched on a Sunday. Not fatal, but not ideal for B2B-adjacent products where the audience is in work mode Monday–Thursday.

And the CTA was too passive. "Check it out" instead of "paste your URL and see your roadmap in 60 seconds." The product has a fast aha moment — I buried it.

The 3 signups came from the comments, not the post itself. Which tells me the conversation is where the trust gets built, not the headline.

Go https://zarek.tech and sign in. You can trial. You can reach me at wangc2016217@gmail.com.

That's the exact reframe I landed on after watching people interact with the roadmap. The checklist gets saved, the daily action gets done. There's something about reducing it to one move that removes the excuse to procrastinate.

The 3 signups from 11 upvotes is actually the number I'm most interested in — that's a 27% conversion from engaged readers, which is higher than I expected. The people who upvote and don't sign up probably weren't the target anyway.

What's your read on the right cadence for that daily signal — is it a push (email, notification) or a pull (they check a dashboard)? You can reach me at wangc2016217@gmail.com.

You've put your finger on exactly the tension I'm still working through. The roadmap is what gets someone to sign up; the daily briefing is what makes them come back. Week-two return rate is the number I care most about right now, and it's early enough that I don't have clean data yet — but that's the hypothesis I'm building around.

On directory verification — agreed. Live listing is table stakes. The real question is referral traffic after 2–3 weeks, and that's what Zarek checks. But you're right that I haven't closed the loop to "did this listing produce a conversation." That's the next thing to wire up.

To your question: the clearest link to a real user outcome so far is the Show HN post. It drives the kind of founder who actually reads the roadmap and replies with something specific. Directory traffic tends to be lower intent. Still early, but that's the pattern I'm watching.

What's your measurement setup for Hades — are you tracking at the lead list level or the campaign level? You can reach me at wangc2016217@gmail.com.

Go https://zarek.tech and sign in.

Exactly three, in order:

1. Reply to every comment, upvote, and mention within 24 hours.
   Not to pitch — to learn. Every person who engaged on launch day is a free user interview. Ask them what problem they were hoping it solved. The answers rewrite your next week's copy better than any tool can.

2. Post one honest update to wherever you launched.
   "Day 3: here's what happened, here's what surprised me, here's what I'm fixing." This keeps the thread alive, brings back people who missed day one, and signals you're a real founder not a drive-by spammer. One paragraph is enough.

3. Submit to three directories — manually, one per day.
   Not thirty. Three. Pick the ones where your actual audience looks for tools (for Zarek: there.is, Futurepedia, AI tool directories). Verify each one went live before moving to the next. Done right, these send a slow trickle of traffic for months.

Everything else — the email sequence, the second Reddit post, the backlink outreach — can wait until week two. These three keep the momentum alive without turning launch week into a second full-time job.

Go https://zarek.tech and sign in.

Go https://zarek.tech and sign in. Maybe you will know about everything.