2
7 Comments

ChatGPT wrote my launch copy. I still got no traction. So I built something that actually launches

Last year I launched a side project.

I used ChatGPT for everything — Show HN, Reddit posts, Product Hunt description, directory pitches. The copy was fine. Honestly, pretty good.

Two weeks later: 11 directories still not live (wrong format, never verified), my Show HN buried by noon (posted Friday at 2pm), Reddit post removed by a mod (missed a rule in r/SaaS), and I had no idea what had actually worked.

The copy wasn't the problem. Execution was.

GPT doesn't know that r/SaaS bans direct self-promotion on weekdays. It doesn't submit to directories and verify the listing went live. It doesn't know Show HN peaks Tuesday–Thursday 9am ET. It doesn't follow up tomorrow and tell you three submissions bounced.

That's why I built Zarek.

You paste your product URL. Zarek reads it and executes a full launch:

Writes copy tuned to each venue — HN-voice for HN, Reddit-voice for Reddit, not one generic draft
Finds the right subreddits, newsletters, and influencers — with pitches ready to go
Submits directories automatically and verifies each listing is actually live
Emails you a daily briefing: what's done, what needs your eyes, what's next
Keeps running post-launch — tracks listings, referral trends, distribution cadence — so you don't fall off a cliff at day 30
ChatGPT writes copy. Zarek launches your product.

Pricing: 3-day free trial (card required), then $29/month. Everything included — launch execution and post-launch monitoring in one subscription.

Where I am: V1 live, first beta users running real launches through it now.

If you're launching in the next 60 days — drop a comment or email me at wangc2016217@gmail.com. Happy to run it together.

https://track.zarek.tech/t/XTGwkuA0

on August 20, 2026
  1. 1

    The execution thesis is much more interesting than the copy angle. I’m curious which part of the launch process beta users actually value most once Zarek is doing the work rather than just generating it.

    1. 1

      Not the copy, not the roadmap. The moment they see "this listing is live" or "this submission bounced, here's why" — that's when it clicks. Because every other tool leaves them guessing.

      The copy is table stakes now. ChatGPT handles that. What nobody else does is close the loop — tell you what actually happened after you hit send.

      Which part of launch execution feels most broken in your own experience? Curious whether it's the pre-launch prep, the day-of execution, or the week after when momentum dies.

      1. 1

        That’s a strong distinction. The “closed loop” seems to be where the product becomes meaningfully different from a copy generator.

        Would be good to compare notes sometime — what’s the best email to reach you on?

        1. 1

          wangc2016217@gmail.com — looking forward to it.
          And can you have a conversation on whatsapp or telegram?

  2. 1

    This highlights an important distinction: generating launch copy isn't the same as creating distribution. The copy can be perfectly written and still have zero reason for anyone to see or care about it.

    I’d be curious what actually changed traction-wise after you built the new approach.

    1. 1

      Exactly right. Copy without placement is just a draft.

      What changed: founders stopped losing days to silent failures. Verified listings, flagged removals, one daily briefing instead of 12 open tabs. The biggest lift comes from knowing what actually happened — not guessing.

      What does your current launch process look like?

      1. 1

        Right now it's a mix of manual outreach, communities, and building in public. The biggest challenge isn't creating the product — it's consistently getting it in front of the right people. That's actually why your “distribution as a system” angle caught my attention.