30
104 Comments

I launched on Product Hunt today with 0 followers, 0 network, and 0 users. Here's what I learned in 12 hours.

Hey IH 👋

I'm Sabahattin, solo founder from Baku, Azerbaijan. Today I
launched MailTest on Product Hunt — my first real launch ever.

Current stats (12 hours in):

  • Position: #83
  • Upvotes: 1
  • Paying users: 0
  • Twitter followers: single digits

Here's what actually happened:

What I built:
MailTest is an email deliverability debugger. Most tools tell
you "DKIM failed ❌". MailTest tells you exactly WHY, and how
to fix it. 11 technical checks, self-hosted, Docker Compose.

Built it over 3 months, solo, between freelance work.

What I expected vs reality:

Expected: Launch on PH → viral on Twitter → hundreds of signups
Reality: Launch on PH → 1 upvote (mine) → friends can't
upvote because same IP triggers spam filter

What I learned in 12 hours:

  1. No network = no launch day traction. PH rewards
    existing audiences. If you don't have one, you're starting
    from scratch on launch day.

  2. Twitter without followers is a void. I posted the
    launch tweet. 8 views in 6 hours. No algorithm boost
    without social proof.

  3. Reddit will eat you alive as a new account. r/SideProject
    removed my post within minutes. Spam filter doesn't care if
    your product is real.

  4. Dev.to is slow but honest. Technical article published,
    25 views in a few hours. No viral moment, but the SEO value
    will compound.

  5. The real win is data. I now have real traffic numbers,
    real feedback loops, and real insights into what converts
    (nothing yet, but that's signal too).

What I'm trying next:

  • Actually engaging in IH (this post) instead of lurking
  • Direct outreach to email marketing communities
  • Building in public on Twitter daily
  • Launching again on HN in a few weeks with a different angle

Honest question for the community:

For those who launched solo with no network — what actually
moved the needle? Not "write great content" or "build in
public" (I know). Specific tactics that worked for YOU in
month 1?

Currently live: https://mailtest.scuton.com
Product Hunt: https://www.producthunt.com/products/mailtest?launch=mailtest

Promo code PRODUCTHUNT → 1 month Pro free.

Appreciate any feedback. Even brutal

posted to Icon for group Show IH
Show IH
on April 20, 2026
  1. 1

    Hey, checked your product — nice concept.
    One thing I noticed is you’re not leveraging SEO content yet.
    A few targeted blog posts could help bring consistent traffic.

    I help SaaS startups and Digital Marketing companies grow with SEO and conversion-focused content that turns traffic into leads.

  2. 1

    Wow first of all I wanted to just give kudos for taking the first step at creating something that's yours. I too am running into a similar wall at the moment, trying to validate if there is a market or users for my idea prior to launch but without the network, going in X, I was thinking of writing in r/sideproject but I may have to pivot now and my facebook ad has no views as well.

    A real welcome to the real world moment but eye opening to see it's not just me going through it!

  3. 1

    This is super real — most people underestimate how hard it is to get first traction

    quick thought:
    when you have 0 audience, your landing page becomes EVERYTHING

    I checked similar tools — most lose users in first 5–10 seconds because value isn’t clear enough

    your product sounds useful, but it might not be instantly obvious why someone should stay

    if you want, I can show you how to improve that (I design AI/SaaS products)

  4. 1

    Welcome to the real world... Not everyone can or knows how to get there; some talk about luck, others about persistence... I'd really love to know if anyone knows of a tool that genuinely helps all entrepreneurs who are in the launch phase, and that truly helps everyone... so does anyone here have any knowledge about this and can help? Thank you...

  5. 1

    position 83 with 1 upvote after 12 hours. most people would have deleted this post. appreciated.

  6. 1

    Sabahattin's solo launch is brutal. Respect for posting the real numbers instead of a highlight reel.

    One thing I'd push back on: you're asking what tactic moves the needle, but I think you're one layer too high. Your launch copy says "email deliverability debugger" and "11 technical checks." That's what it is, not what it does for someone at 11 pm the night before a campaign goes out.

    The devs who need MailTest aren't searching for a debugger. They're staring at a 4% open rate, panicking, and Googling "why are my emails going to spam." Your PH tagline, your tweet, your Dev. to intro, none of them catch that person mid-panic. They describe the tool to someone who already knows they need it.
    Quick rewrite of your own line:

    "Most tools tell you DKIM failed. MailTest tells you why, and how to fix it."

    That's the hook. That should be your headline, your tweet, your PH tagline. Not buried in paragraph 4.
    The tactic people are going to recommend in this thread (post more, DM founders, cold outreach to email communities) — all of that works 10x harder when the first line does the selling for you.
    Happy to rewrite your PH tagline + homepage hero if useful. No strings attached — I do this for solo founders because it's the fastest way to see if the positioning is the bottleneck or the distribution is.
    — Boateng Writes

    1. 1

      this is the comment i'll probably remember from today.

      you're right — i've been describing the tool to people who
      already know they need it, instead of catching the person
      mid-panic at 11pm before a campaign goes out. "email
      deliverability debugger" means nothing to that person.
      "why your emails are going to spam" is their actual search.

      your rewrite line is cleaner than anything i've written
      about the product in 3 months. the fact that it took you
      one read to produce that and it took me 3 months to miss
      it tells me the bottleneck isn't distribution — it's that
      i can't see my own positioning from the inside.

      yes, i'd take you up on the offer. if you want to rewrite
      the PH tagline and homepage hero, i'll ship whatever you
      write and report back honestly on whether it moved
      conversions or not. useful feedback loop for you either way.

      what's the best way to do this — comment thread, DM,
      something else?

  7. 2

    This is painful but valuable, you just learned distribution is a system, not an event.
    Most first launches fail because founders treat launch day as strategy instead of just one channel.

    1. 1

      This just rewired how I was thinking about it. Thank you.

      I definitely treated launch day as THE strategy — not A
      channel. The whole mental model was "if I stack enough
      platforms on one day, something will spark."

      What you're describing sounds more like: each channel has
      its own tempo, its own trust-building cycle, and launch
      day is just the entry point for one of them.

      If you're open to it — when you realized distribution was
      a system, what was the first thing you changed in how you
      spent your time? Did you pick one channel and go deep, or
      rotate across several on different cadences?

      1. 1

        The first shift is usually going from bursts to cadence.
        Instead of trying to be everywhere on launch day, pick one channel where your users already are and show up there consistently until trust compounds.

  8. 2

    Respect for sharing the real numbers that’s rare. From what you described, this might not be a traffic problem yet. If you’re getting views but 0 conversions, it usually points to either unclear value messaging or trust friction on the page.

    Curious are users immediately understanding why they need MailTest within the first few seconds on your homepage?

    1. 1

      Really good point — I've been framing this as "no one saw it"
      when maybe the real issue is "people saw it and didn't connect."

      Honest answer: I don't think the value is clear in 3 seconds.
      The hero says "Fix Email Deliverability In 5 Seconds" which
      sounds like a speed claim, not a pain claim. If someone is
      already frustrated with their emails going to spam, they
      might not even recognize themselves in that headline.

      The actual pain is "SPF/DKIM/DMARC all pass but you're still
      in spam and no one can tell you why." That's the sentence
      that would make a real user stop scrolling — and it's nowhere
      on the page.

      Going to rewrite the hero this week based on this.

      If you're up for a 30-second look: mailtest.scuton.com
      what's the first thing you'd change?

      1. 1

        You’re actually very close already the shift you described is exactly the right direction.The first thing I’d change is making the pain instantly recognizable in the first 3 seconds. Right now it still feels like a tool, not a problem being solved.

        If I landed on the page, I’d want to immediately feel: this is exactly my situation. Something like the line you mentioned (SPF/DKIM/DMARC pass but still in spam…) is much stronger because it calls out a very specific frustration.

        Once that clicks, the rest of the page becomes easier to trust.

  9. 1

    You said it - warm up ur account. Also not just built community but finde ur hunter!
    Dont worry you will get to relaunch :)

    1. 1

      finding a hunter is the one i hadn't thought seriously about
      yet. kept assuming i had to be the hunter for my own product
      because who else would care. but that's the whole point —
      someone else caring is the signal that carries weight PH
      rewards.

      account warm-up makes sense too. this one was 3 days old,
      zero history, jumped straight into a launch. of course the
      algorithm ate it.

      relaunch v2 with a hunter + warm account + better hook (from
      all the feedback in this thread) is starting to feel like
      the actual path, not a consolation prize.

      thanks 🙏

  10. 1

    After launching, I spent weeks sending cold emails every single day — low response rate, but I kept going. I funneled interested people into my Discord, then personally DM'd the engaged ones to dig deeper into how they were actually using the product.

    I even hosted a co-creation session —The turnout was modest, but the insights were real. Still debating whether to run a second one, because honestly, I don't think I have enough feedback yet. You can never have too many early signals.

    That's what brought me Reddit and Indie Hackers. Still in full user-discovery mode.

    Here's where I'm at right now: 7-day free trial, and if you leave feedback, you get bonus credits. No strings attached. (Feel free to check my profile if you're curious )

    I'm also working with a handful of solo founders helping them get their businesses off the ground — including setting up AI agents tailored to their workflow. If that sounds useful, feel free to reach out. I'm genuinely happy to exchange ideas, hear what you're building, and figure out if there's a way I can help.

    No pressure. Just looking for honest conversations/feedback.

    1. 1

      the co-creation session idea is interesting — didn't think
      of putting actual users in a room together before the product
      is dialed in. most of us go feedback → build → feedback, one
      person at a time. group dynamic probably surfaces different
      things.

      how did you recruit for the session? cold email from your
      early list, or something warmer?

      1. 1

        After we launched, we got some initial traffic and collected emails from early visitors. From there, I just reached out directly, inviting them to join a co-creation session, or nudging them toward more active channels where we could keep the conversation going.

        Prep matters a lot. Before the session, we shared what the product could do for them specifically, then opened it up for discussion. That structure helped surface real, honest feedback rather than polite noise.
        The group dynamic is genuinely different from 1-on-1. One person's comment would trigger reactions from others — you could see what actually resonated. Some participants didn't speak up during the session but sent detailed thoughts afterward. Both types were valuable.

        Honestly, I've only run one so far — just 5 users, still figuring it out. Before this, I was doing pure 1-on-1 outreach — slower, but when you pull it all together, the signal is surprisingly rich. The co-creation session just surfaces things faster. Both work. It depends on where you are.

  11. 1

    The "0-0-0" launch is the most honest experience in building, Sabahattin. Moving from "DKIM failed" to a "fix-it" roadmap is the right product direction—now you just need to bridge the gap between technical logic and a visible audience.
    I’m currently running a project in Tokyo (Tokyo Lore) that highlights resilient solo builders just like you. Since you're currently gathering raw data and stress-testing your deliverability debugger, entering this round could be the perfect way to turn your "failed" launch into a high-visibility case study while your odds are at their peak.

  12. 1

    This is a really solid breakdown — especially the “commenting > posting” part.

    Quick question: have you checked how AI engines (Claude, ChatGPT, Perplexity) interpret your site?

    We’re seeing cases where SEO looks fine, but AI still can’t clearly explain what the product does — which might affect discovery more than expected.

    Curious if you’ve looked into that.

    1. 1

      actually yes — ran mailtest through the AEO audit that
      saasoffers built yesterday and got 50/100 (D). the specifics
      were painful:

      • gptbot and claudebot both blocked in robots.txt (wordpress
        plugin default, didn't know)
      • no llms.txt
      • 0/23 headings in question format
      • no faq schema
      • tech foundation was 98/100, so seo "looks fine" like you said

      classic case of what you're describing. google crawls it,
      ranks it for the right keywords. claude and chatgpt literally
      can't read half the page. the gap shows up exactly at the
      moment people stop googling and start asking an AI.

      fixing it this week. robots.txt first, then llms.txt + faq
      schema, then restructuring headings into questions. will
      re-audit and post the before/after.

      what's your tool, if you're working on something in this
      space?

  13. 1

    Respect for the transparency here. Most people only share the wins, not the "1 upvote and it was mine" moments.

    Your takeaway about no network = no launch day traction is spot on. PH is essentially a multiplier — if you start with zero, you multiply zero. The real value of a PH launch with no audience isn't the launch day itself, it's the permanent product page and backlink you get afterward.

    One thing that worked for me: instead of trying to build an audience before launch, I focused on being genuinely helpful in communities like this one first. Commenting on other people's posts, sharing what I've learned, actually engaging. The audience builds slowly but it's real people who actually care about what you're building.

    The SEO play with technical articles is underrated. Those compound over months. Keep writing technical content about email deliverability — that's a long game that pays off.

    Good luck with the next launch attempt on HN. The technical crowd there will appreciate what you've built more than PH's general audience.

    1. 1

      "PH is a multiplier — if you start with zero, you multiply zero"
      — that's the cleanest framing i've read for what happened
      yesterday. going to steal that line.

      the point about permanent product page + backlink being the
      real value is something i kept missing. i was treating launch
      day as the whole transaction when it's actually just the
      deposit — the page itself keeps working for months.

      the "genuinely helpful in communities first" thing is what
      today became, accidentally. showed up in this thread with
      honest numbers instead of a launch pitch, ended up having
      the most useful conversations i've had in 3 months of
      building. not what i planned, but probably what i needed.

      HN relaunch is definitely on the roadmap, but not for a few
      months. want to have real user stories and a tighter hook
      before going to a crowd that doesn't forgive weak openings.
      your point about technical audience appreciating the product
      more is exactly why i'm saving it.

      thanks for taking the time 🙏

  14. 1

    Hey Sabahattin — reading this with ~20 min until my own 12:01 AM PT PH launch, so I can't yet tell you what "worked." But three things I did in the two weeks before launch, specifically because I also have zero network:

    1. Cold emailed a dozen niche-relevant blogs and YouTubers 36 hours out. Not asking for coverage — asking if they'd want a demo code for a post-launch review. One-in-ten accepts is still a better conversion than shouting into an empty Twitter. The "timed to your launch, not asking for anything today" framing is the part that works.
    2. Scheduled Show HN for early US morning on launch day — not midnight. HN rewards posts that land during the morning-peak traffic window, not when PH goes live. For a technical product like MailTest, I'd overweight HN and treat PH-day traction as a bonus. Your audience is there.
    3. Went deep in 2–3 niche subreddit threads the week before. Not posting the product — answering questions adjacent to it with real expertise. r/SideProject will nuke new accounts as you found out, but smaller niche subs are more tolerant if you've been in-thread for a while first.
      One note on the SideProject experience: the removal usually isn't spam detection, it's account age + karma. If you let the account season 30 days with decent comments elsewhere and come back in May, the same post likely sticks.
      Also — "Position #83 at 12 hours in" really isn't the disaster you're framing it as. Very few first-time solo launches with no audience clear the top 20. The data you're collecting now is the actual deliverable from launch day.
      — Josh
    1. 1

      josh — just realized you posted this 4 hours ago so your
      launch is already live. going to find it now and drop a
      real comment, not a "congrats!" one.

      the "36 hours out, ask for post-launch review code not launch
      day coverage" framing is the move i wish i'd known. takes
      all the pressure off both sides and gives the ask a concrete
      shape. saving that.

      on HN morning window vs midnight — i completely whiffed this.
      launched PH at midnight PT and just assumed HN would follow
      the same clock. the fact that the technical crowd shows up
      8 hours later is a detail no one tells you.

      reddit account aging: also lines up with what others in this
      thread said. plan is to spend the next 30 days commenting in
      r/emailmarketing and r/sysadmin with real answers (no product
      links), then come back in may.

      on #83 — appreciate the reframe. was emotionally treating it
      as a failure because the number is small, but you're right
      that the data is the actual deliverable.

      dropping by your launch now 🚀

  15. 1

    Sabahattin, I was in almost this exact position 2 weeks ago.. solo, no network, no audience, posting into the void.

    I may not have all of these yet but I would love to share a few specific tactics that actually worked for me in the first 2 weeks:

    For reddit, what I would do is create posts like "drop your SaaS and I'll give feedback" or "Drop your biggest pre-launch fear". I would always go first then be like it's your turn and days later I amassed hundreds or thousands of viewers and commenters on those posts! If you're looking for where to post I'd definitely try r/SideProject to start. Go first with your own product, genuinely engage with every single reply, and give real feedback on other people's products before pitching yours. The key is making it about the community first and your product second.

    Reply to posts in your niche where you have genuine expertise. Don't just post "check out my tool" replies but instead give actual helpful answers where MailTest would naturally be the solution. Be the helpful person first, then mention the tool when it's genuinely relevant.

    Getting karma at first is rough since most subreddits require it, but it can build up quicker than you think if you're consistent. I went from 0 to 21 karma in under 2 weeks just by genuinely engaging, which obviously isn't a lot yes but progress is progress and as long as you're seeing an upward trend in progress, you'll do just fine.

    MailTest looks genuinely useful by the way, "tells you WHY it failed, not just that it failed" is exactly the right positioning. Most devs have rage-quit DKIM debugging at least once.
    Keep going brother, me and many other comments are rooting for you!

  16. 1

    I can definitely relate. I also launched there today, my first launch ever, and I got #366 position, 1 point, and 1 comment. Honestly, I was kinda lost.

    1. 1

      welcome to the #300s club 😅

      honest question back: what did you build? happy to actually
      check it out and leave a real comment. same-day launchers
      gotta look out for each other.

      and "kinda lost" is exactly where i was 12 hours in. the
      thing that helped me was switching from refreshing PH
      analytics to writing this IH post. moved the needle more
      than anything i did on launch day itself.

  17. 1

    Launching in the same boat today, also on PH with no existing audience. A few things that have actually moved for me in the first few hours: replying fast to every comment (even if there are only 2 of them) seems to signal activity to PH's algorithm, and posting the PH link directly in relevant LinkedIn comments where people are already discussing the problem you solve gets warmer clicks than cold posts.

    The IP spam filter thing is brutal. I had the same issue with friends trying to upvote from the same office network. The workaround I found: ask them to upvote from mobile data, not wifi.

    Honest take on month 1 tactics that I have seen work for others in niche B2B spaces: find 3 to 5 specific communities where your exact user already hangs out and genuinely answer questions there before ever mentioning your product. Takes longer but the conversion rate when you do share is much higher than broadcast posts.

    Good luck today. Product looks solid.

    1. 1

      same day, same boat — good luck today 🙏

      the mobile data workaround is something i wish i'd known
      yesterday. ended up with 2-3 friends trying to upvote from
      the same wifi and watching the count stay flat. makes sense
      in hindsight but the IP thing is nowhere in the "how to
      launch on PH" guides.

      the LinkedIn-comment-in-relevant-threads move is interesting.
      haven't tried that angle yet — been treating LinkedIn as a
      broadcast channel instead of a reply channel. same mistake
      i made with twitter.

      on the "3-5 communities" point — this is the advice i keep
      hearing from different people in different words today. at
      some point you stop treating it as a coincidence and start
      treating it as the actual playbook.

      drop your PH link when it goes live. happy to show up with
      a real comment, not a "congrats!" one.

  18. 1

    Many will agree timing is great. Also let say PH, IH or Reddit. You could launch and join those communities thé same day. However if you were to comment amongst first in a thread for a problem your solution solves. You’d be surprised by visibility you’d get despite your no network or account age.

    1. 1

      this is the exact reframe i needed. i was thinking of
      community participation as a slow 3-4 week pre-launch ritual,
      but you're right — being among the first thoughtful commenters
      on a problem thread is itself a distribution event. doesn't
      require account age or followers.

      harder to scale because you have to actually be there when
      the thread is hot, but that's probably why it works. no one
      else is doing the work.

      going to set up alerts on reddit/twitter/IH for deliverability-
      related keywords and just show up early with real answers.
      thanks for naming it.

  19. 1

    Appreciate this — timing is perfect for us. We're in day 2 of a 2-week sprint and planning a PH launch for next week with similarly zero PH-native network. Curious: did you find quote-tweet chains from early commenters were meaningful drivers, or was that mostly vanity? Our read is that in-thread engagement > raw upvote count for front-page stickiness, but hard to tell from the outside.

    1. 1

      Appreciate this — timing is perfect for us. We're in day 2 of a 2-week sprint and planning a PH launch for next week with similarly zero PH-native network. Curious: did you find quote-tweet chains from early commenters were meaningful drivers, or was that mostly vanity? Our read is that in-thread engagement > raw upvote count for front-page stickiness, but hard to tell from the outside.

  20. 1

    The no-network problem on PH is real, and there's no shortcut around it. What actually moved the needle for me early on was going to where the pain was already being talked about, not posting and waiting, but finding people right in the middle of complaining.

    One specific thing: I searched Twitter for people venting about the exact problem my tool solved, then replied with something useful, not a link, just an answer. Some of them became early users. A few even shared the product on their own later.

    The other thing worth trying is IH "Show" posts like this one. The comment threads can drive surprisingly warm traffic because people are already in the mindset of trying new tools. The folks who reply to your posts are also the ones most likely to actually try what you built.

    The dev.to slow-burn play is smart. That compounds. PH doesn't, tbh.

    1. 1

      "searched twitter for people venting about the exact problem" —
      this is the move. not "build audience," not "content strategy" —
      literally find people already in pain right now and show up with
      an answer.

      going to set this up tomorrow. keywords like "emails going to
      spam," "dkim failed but still spam," "cold email deliverability
      nightmare" — reply with the actual fix, no link unless asked.

      and yeah, your read on PH vs dev.to is brutal but accurate. PH
      is a moment. dev.to is a library. one resets to zero the next
      day, the other compounds forever. i prioritized the wrong one
      yesterday.

      the IH "Show" post insight is interesting too — i assumed these
      posts were self-promotional noise, but the comment traffic here
      has been the warmest of anywhere i've been today. people
      actually click through because they're already in "check out
      what solo devs are doing" mode.

      thanks for taking the time to write this out — this is the
      kind of advice that usually costs money.

  21. 1

    I launched on Product Hunt on a new account and got 1 upvote :-) Total failure.

    1. 1

      ha, welcome to the club 😅

      "total failure" is the wrong frame though — 1 upvote on a
      new account means the platform worked exactly as designed.
      spam filters did their job, algorithm didn't know you,
      nobody had a reason to click. that's not failure, that's
      the baseline for launching without pre-built distribution.

      the actual failure would be if we learned nothing from it.
      what did you take away from yours?

  22. 1

    You know its the hardest thing trying to get started on a new project. I should know I have yet to get a sale :(

    1. 1

      same boat. 3 months of building, zero sales, launched
      yesterday — just me refreshing analytics like a madman.

      what i'm starting to realize (from the other comments on
      this post) is that "no sales" in the first weeks is actually
      the default, not a bug. everyone who made it to $1k MRR
      went through the same silence we're in right now. we just
      don't hear about that part because nobody posts "day 47,
      still zero" on twitter.

      what are you building? genuinely curious, and the more of
      us swap notes the less lonely this phase feels.

  23. 1

    Thanks for sharing, it's a valuable lesson for me too!

    1. 1

      glad it resonated 🙏 good luck with what you're building

  24. 1

    this is the most realest thing i have real all day

    1. 2

      ha, thanks 🙏 figured honesty would either resonate or get
      ignored. glad it landed.

  25. 1

    Thanks For Sharing Looks very Interesting.

    1. 1

      thanks James 🙏 appreciate you checking it out

  26. 1

    Launched on Product Hunt today with zero followers, zero network, and zero users. In just 12 hours, I learned growth comes from persistence, storytelling, and engaging early supporters.

    1. 1

      yeah, storytelling and early supporters showing up is the
      part nobody warns you about upfront. i was expecting numbers
      and got conversations instead — turned out the conversations
      are worth way more.

      what are you building?

  27. 1

    The 'no network = no traction' lesson is the most brutal one in indie hacking. What actually works before launch: be a genuine participant in communities 3-4 weeks early. Not promoting, just commenting thoughtfully on others' posts. By launch day you want people to recognize your name.

    On the Reddit angle — new accounts are almost always caught by spam filters regardless of post quality. The trick is aging the account for 30+ days and building karma in unrelated subs first. Painful but it works.

    One thing that really helped me pre-launch: spending time understanding what competing products got right and wrong when they launched. Analyzing the market before you enter it sounds obvious, but most founders skip it. The 'WHY it failed, not just that it failed' positioning you've chosen for MailTest is smart — that's the gap nobody else is filling.

    Good luck, rooting for you.

    1. 1

      the 3-4 weeks early participation point is what i kept
      hearing in different forms today and kept realizing i had
      the order backwards. build first, community later. should
      have been the other way around.

      the reddit aging tip is useful — i figured out the hard
      way that r/SideProject eats new accounts regardless of
      post quality. going to spend the next month commenting
      in unrelated subs and building karma before trying again.

      the competing products analysis is the one i actually
      did skip entirely. assumed my "WHY not just WHAT" angle
      was obvious — turns out it's obvious to me because i
      built it. the rest of the market either hasn't noticed
      the gap or hasn't articulated it. going to study how
      mail-tester, mxtoolbox, glockapps positioned themselves
      at launch — what they led with, what they missed.

      thanks for the rooting 🙏 means more than the metrics today

  28. 1

    Same boat - solo dev, zero audience, just starting to put my first app out there today. This thread is the most useful thing I've read so far. The "distribution is a system, not an event" reframe changes everything.

    1. 1

      good luck with your launch today 🙌

      and yeah, that line wasn't mine — another commenter (The_Data_Nerd)
      dropped it earlier in this thread. credit where it's due. it
      reframed my whole day too.

      drop your link here when you post — happy to show up in the
      comments. we solo-zero-audience folks gotta stick together.

  29. 1

    This hit a bit too close tbh. I’m in almost the exact same phase right now — building solo, no audience, and realizing launch day is basically invisible without distribution.

    One thing I’m starting to understand: the “launch” itself doesn’t really matter. It’s more like a checkpoint. What actually matters is whether you can consistently get in front of the same type of user over time.

    From what I’ve seen (and testing now), a few things seem to move the needle early:

    • commenting on relevant posts instead of posting your own (way more visibility)
    • reframing the product as a problem discussion instead of a “launch”
    • finding small niche communities instead of big ones (less competition, more signal)

    Also your point about Reddit is painfully accurate. New accounts basically have to earn the right to exist first.

    Curious — have you tried reaching out directly to people already talking about deliverability issues (Twitter/Indie Hackers comments etc)? Feels like that might convert faster than broad posting early on.

    1. 1

      the three things you listed are basically the checklist i wish someone had handed me 3 months ago. commenting > posting, problem discussion > launch, niche > big communities. all three i got wrong in that order.

      to your question: no, i haven't done direct outreach to people already talking about deliverability. been posting broadly instead of replying narrowly. that's backwards.

      going to flip it this week — search "email going to spam" on twitter/reddit/IH, find the people actually asking the question right now, and show up with a real technical
      answer (not a link drop). if mailtest fits the problem, mention it. if not, just help.

      thanks for naming the thing i was avoiding. what are you building btw? curious if you've applied the same approach to your own launch yet.

  30. 1

    Thanks for sharing!

  31. 1

    Thanks for sharing your experience. Just random thoughts on your launch:

    • Reddit and Twitter need to be curated before the launch. Similar to what you do in IH. So if you spend time and add some quality interactions there, it can bring views at some point.
    • If you are confident that your application is working properly, you might want to add some ad campaigns in meta/google/... This can help with the initial push.
    1. 2

      agreed on the first point — reddit and twitter presence needs
      to be built before launch day, not on launch day. that's the
      mistake i made. going to spend the next few weeks just
      showing up in deliverability communities without pitching.

      on ads — holding off for now. at $0 MRR and no conversion
      data, i'd just be paying to confirm a landing page that i
      already know doesn't convert (another commenter pointed out
      the hero says "fix in 5 seconds" when the real pain is
      "spf/dkim/dmarc pass but still spam").

      probably the order is: fix hook → get 5 real conversations →
      then consider paid to scale what works. spending money before
      the hook is tight just scales the leak.

      but appreciate the perspective 🙏

      1. 2

        That’s a really sharp take , scale the leak is exactly what most people miss.

        I’ve seen something similar on the AI tools side , traffic isn’t the problem, it’s mismatch between what the user thinks they’ll get vs what actually happens after click. "Conversion"

        That fix in 5 seconds vs deeper deliverability thing you mentioned is probably the core gap.
        The people searching already know basics, they just don’t know why it’s still failing.

        You may try: instead of optimizing the page, try 5–10 direct conversations with people who recently struggled with deliverability like cold email founders, newsletter operators, etc. and ask what exact moment they felt stuck. That usually gives better hooks than guessing.

        Curious , are most of your early users more technical devs. or non-technical marketers?

        1. 1

          the "5-10 direct conversations" thing is the advice i've now
          heard from three different people in this thread. at some
          point you have to stop ignoring a pattern.

          honest answer on ICP: i built for technical devs — people
          shipping transactional emails from their apps, dealing with
          CI/CD, comfortable with docker compose. but the actual pain
          ("why is this in spam") is way bigger for non-technical
          marketers running cold outreach. they just don't buy
          self-hosted tools.

          so i'm in this weird split: the people i built for can fix
          their own problems most of the time, and the people with
          the loudest pain can't use my current packaging.

          probably means a hosted version + a landing page that speaks
          marketer pain, not developer pain. which is a much bigger
          product decision than i thought i was making today.

          what about you — who are your AI tools actually for vs who
          you thought they were for when you started?

  32. 1

    This is one of the most honest launch writeups I’ve seen here.

    I’m in a similar spot, I launched a GTM validation tool with almost no audience and also treated “launch day” as the strategy instead of just one channel. Your line about distribution being a system, not an event is something that really resonates with me.

    The biggest unlock for me so far has been talking directly to a tiny group of people who very clearly have the problem, instead of trying to broadcast everywhere at once.

    Thanks for sharing the real numbers. Posts like this are way more useful than yet another “$10k MRR in 30 days” story.

    1. 1

      the "distribution is a system, not an event" line wasn't mine
      — another commenter dropped it earlier in this thread and it
      reframed everything for me too. glad it's traveling.

      what you said about talking directly to a tiny group — that's
      the part i keep hearing over and over today and kept
      underestimating. broadcasting feels productive because it
      looks like work. 5 real conversations with people who have
      the actual problem is what moves it.

      what's your GTM validation tool? curious how you're doing
      the validation part yourself — kind of meta but that's
      probably the best demo.

  33. 1

    I'm launching my app on PH today too, same situation. I built it for one real customer before worrying about anyone else which has been the only thing that felt like actual traction.

    I'm curious what direct outreach to email marketing communities looks like for you? that's the part I'm still figuring out too

    1. 1

      "built for one real customer" — that's the part i skipped.
      built for an imaginary user instead. going to be paying for
      that for a while.

      honest answer on the outreach: i haven't actually done it
      yet. today was my first real day trying. what i'm planning
      for this week:

      1. join Email Geeks slack, read for a few days, don't pitch
      2. find 5 specific people posting about deliverability
        issues on twitter/reddit/IH — reply with actual technical
        help, not a link drop
      3. only mention mailtest if it genuinely fits, and only
        after i've been useful first

      no idea if this works. ask me in 2 weeks. and good luck
      on your PH launch today — drop the link when you post,
      happy to show up.

  34. 1

    This is brutally honest post.

    I’ve been seeing something similar while building an AI tools discovery platform — getting impressions is actually easier than getting actual users.

    For me, traffic only started moving when I focused on specific trends instead of generic topics (like covering new AI releases instead of “top tools” pages).

    One thing I’m curious about — have you tried positioning MailTest around very specific use cases like:

    why cold emails go to spam or fix Gmail spam issues

    instead of general deliverability?

    Feels like those might convert better than a general tool page.

    1. 1

      this is the pivot i didn't know i needed.

      "email deliverability debugger" is what i built. but you're
      right — nobody wakes up thinking "i need a deliverability
      debugger." they wake up thinking "why the hell are my cold
      emails going to spam again."

      two different searches, two different landing pages, probably
      two different products from the user's perspective even though
      it's the same tool underneath.

      going to test this — spin up /cold-email-spam-fix and
      /gmail-deliverability-issues as dedicated pages targeting
      the actual pain query instead of the category.

      what's your AI tools platform btw? curious how you're
      applying the trend-specific approach yourself.

  35. 1

    Zero upvotes from a cold launch is more valuable than 50 from your network. Network upvotes tell you people like you. Zero tells you the hook doesn't pull without relationship capital. That's the actual diagnostic. The fix is not more channels. It is a better opening line before you relaunch on HN.

    1. 1

      this reframe just saved me a month.

      i was about to go wider — more subreddits, more slacks,
      another launch post. what you're saying is the channels
      aren't the issue, the hook is. if the opening line doesn't
      pull strangers, more platforms just means more strangers
      not pulling.

      so the actual work this week isn't distribution. it's
      sitting with the hook until it hurts to read it, and
      fixing it. then HN.

      what did your own rewrite process look like — did you
      test versions on people or just sit with it alone?

  36. 1

    That experience is pretty accurate.

    Product Hunt feels like a distribution channel.... it only really works if you bring the audience with you. Without that, it’s mostly just a data point.

    The Dev.to point is interesting as well. Slower, but at least it compounds rather than relying on a single moment.

    What usually moves things early isn’t the launch itself, it’s direct interaction. Finding a small group of people who actually have the problem and talking to them directly tends to work better than trying to broadcast.

    Have you had any conversations yet with people running into deliverability issues, or is it still mostly traffic-level feedback?

    1. 1

      honestly? zero real conversations yet. everything so far has
      been traffic-level — people loading the landing page, maybe
      scrolling, bouncing. no one's typed a message or filled the
      contact form.

      which is probably the actual problem. i built the tool, put
      it online, and assumed people with the problem would find
      their way. they won't. not without me going to where they
      already are and talking first.

      another commenter mentioned Email Geeks Slack. planning to
      join this week and just listen for a while before saying
      anything. if you know other specific communities where
      deliverability pain actually shows up, would genuinely
      appreciate the nudge.

      1. 1

        Yeah that’s a good realisation to have early.

        People don’t usually come looking for a tool first, they’re already in the middle of the problem somewhere else.

        For deliverability, a lot of that conversation tends to happen in places like:

        Email marketing Slack groups (Email Geeks is a good start)
        Cold outreach communities
        Indie makers dealing with SaaS onboarding emails
        Even support threads where people are trying to fix DKIM/SPF issues

        The pattern is usually someone trying to fix something broken, not browsing for a solution.

        Being in those conversations early will probably give you better signal than traffic.

  37. 1

    This is one of the most honest launch writeups I have seen in a while.

    One thing I would try today – post it on https://buildfeed.co as well. No followers needed, no timing pressure. Just drop it and see what happens.

    Not saying it will magically fix everything, but it is one of the few places where starting from zero does not immediately bury you.

    Also your “expected vs reality” section is genuinely strong. I would reuse that everywhere. That is the kind of thing that actually gets traction over time.

    You are not doing anything wrong, you just skipped the “have an audience first” part that nobody talks about.

    1. 1

      buildfeed.co — adding to the list, thanks. the "timing
      pressure" part is exactly what killed me on PH and HN.
      drop it and see what sticks feels way more sustainable.

      and yeah, the "have an audience first" part is the thing
      nobody actually explains upfront. every launch guide assumes
      you already have one. mine started today.

      going to save the expected vs reality framing for the next
      writeup. appreciate you pointing that out — i didn't realize
      it was the strong part.

      1. 1

        That is exactly it. When you are starting from zero, tying everything to one “launch day” just sets you up for silence.

        The continuous approach at least lets things compound a bit over time instead of all or nothing.

        And yes, that “expected vs reality” framing is powerful because it is honest. People relate to that way more than polished launch stories.

        Thanks for trying Buildfeed!

        1. 1

          "all or nothing" — that's exactly the trap. launch day makes
          you feel like the verdict is in, when really you've just
          started running.

          going to drop it on buildfeed this weekend. will report back
          with honest numbers either way.

          thanks again joshua 🙏

          1. 1

            Awesome! Good luck with your project and no worries :)

  38. 1

    congrats on launching! the "0 everything" angle is actually more common than people admit — most successful PH launches come from no-name founders who just execute well on launch day.

    one thing I'd add: the first 2 hours matter way more than the full 24. getting early comments from real users (not just hunter friends) is what triggers the PH algorithm to push you up. I've also found that having a solid GitHub presence or dev community footprint helps — people check your profile before upvoting.

    if you're building dev tools btw, there's a comparison of AI coding agents that's been getting traction in the community — might be worth seeing how similar tools position themselves: https://tokrepo.com/en/resources/59436371-30d6-4a51-9f9b-1b1986873728

    1. 1

      the "first 2 hours matter more than 24" point is something i
      completely underestimated — i was pacing myself for the whole
      day when the algorithm had already decided by noon.

      the GitHub presence angle is interesting too. mailtest isn't
      open source yet (planning to open it after 100 users) so my
      GitHub looks empty to anyone checking. probably costing me
      more than i thought.

      thanks for the insights 🙏

  39. 1

    Respect for the honesty here — this is exactly the kind of raw post that IH needs more of.

    I'm also building a free tool site with zero paid traffic, so I feel this deeply. What's worked for me in the early days: forget launch day entirely and focus on getting indexed. Write one genuinely useful article per tool, answer the question people are already Googling. Slow but compounds.

    For your specific case with MailTest — email deliverability communities on Slack (like Email Geeks) are goldmines. Those people deal with DKIM/SPF issues daily and actively look for debugging tools. No algorithm needed, just show up with something useful.

    The "0 users on launch day" feeling is brutal but honestly means nothing about your product's potential. Keep building.

    1. 1

      Email Geeks — didn't even know that existed. searching
      for it now. that's exactly the kind of community i should
      have been in BEFORE building, not after.

      the "write one genuinely useful article per tool" bit is
      interesting. you're saying tool-first indexing instead of
      brand-first? like a dedicated page answering one specific
      deliverability question instead of a blog archive?

      also — what's your site? curious to see how you're
      applying this yourself

  40. 1

    Being myself in the same boat, I can truly relate to you bro! Good Luck with your release!

    1. 1

      thanks bro, means a lot 🙏 we'll figure it out

      what are you building?

  41. 1

    the IP thing with friends upvoting is an underrated PH landmine - worth flagging for anyone reading this who's planning a launch. PH's spam filter eats shared-household upvotes and coworking space upvotes too.

    on the "what actually moved the needle" question, one thing i'd push back on: the "post and wait" model. the pre-launch period is where the needle moves, not launch day. waitlist building, community participation months before the launch, and posting observational content in communities where your users already hang out (not product communities) is what makes PH day actually land.

    the fact that you're showing up in IH comments and DMing people individually is the right instinct. keep going. the first 10 real conversations matter more than the first 1000 impressions.

    1. 1

      Man, the "pre-launch is where the needle moves" line hit hard.
      i treated launch day as the finish line when it's really just
      a checkpoint.

      and yeah, the community thing — i was in IH and PH all day.
      neither of those are where people actually sending cold emails
      hang out. that's the miss.

      gonna rethink the whole approach this week. thanks for
      writing this out, seriously.

  42. 1

    has anyone has any success on X? like, really? it's all bro bots, "drop your link" for non existent feedback, and getting spammed ime

    1. 1

      Honestly? Same experience so far. Launched today, posted
      the thread, got 8 views in 6 hours. The "drop your link"
      replies feel like two people spamming each other into a void.

      But one thing surprised me: replying to other founders
      asking "what are you building" got me a legit connection.
      Someone invited MailTest to a directory (EverList), no
      pitch, no spam. Just a real person.

      So my working theory is X is useless for broadcasting to
      strangers, but okay-ish for 1-on-1 connection when you
      show up genuinely in someone else's thread.

      Bro bots and engagement farming? Unavoidable. You kind of
      have to accept that 90% is noise to find the 10% that
      isn't. Curious what you've tried that didn't work — might
      save the rest of us the trouble.

  43. 1

    I love your sincerity, I identify with your first 12 hours step by step, I've been trying to get out of that state for a few days now

    1. 1

      That stage is rough, especially when you’re putting in effort and nothing seems to move. Out of curiosity, what have you tried so far more traffic or improving how your page converts?

    2. 1

      Thank you, that really means a lot 🙏

      Honestly, knowing someone else is in the same place makes
      it less lonely. The "0 users, loud silence" phase is
      brutal because everyone online is sharing wins and you're
      sitting there refreshing analytics.

      What are you building? Sometimes just having a stranger
      actually check it out is the 1% that keeps you going.

      We'll both get out of this. One real conversation at a time.

      1. 1

        Yeah that ‘refreshing analytics with no movement’ phase is real 😅 I work mostly on helping founders improve how their websites convert, so I see this stage a lot.

        I’m not building a product myself right now, but if you’ve got something live, I can take a look and give you honest feedback sometimes it’s just small things holding it back.

  44. 1

    Love the 'just do it' energy here. I’m still gathering the courage to post mine (and waiting on my Amadeus production key), but this is a great reminder that done is better than perfect. Congrats!

    1. 1

      That’s exactly the right mindset launching early saves you months of guessing. When you do launch, the biggest surprise for most people is how users actually interact with the site vs what we expect.

      1. 1

        Haha this actually pushed me to finally share triply.now publicly — still waiting on my Amadeus production key, but done is better than perfect! Right?🚀

        1. 1

          Exactly done beats perfect every time. Now the real learning starts 😄 I’ll check out triply. now curious to see how you positioned it for first-time users.

    2. 1

      Thanks so much 🙏 That means a lot, especially on a day when
      the metrics aren't matching the effort.

      Good luck with the Amadeus integration — those production key
      waits are brutal. What's the tool going to do once the key
      lands?

      And seriously — post yours when you're ready. "Done is better
      than perfect" cuts both ways: I posted mine today with 1
      upvote and no paying users, and honestly the comments (like
      yours) are already more valuable than the launch stats.
      You'll get the same here. This community shows up.

      1. 1

        Appreciate the support! It's an AI-powered travel planner that creates custom itineraries in seconds—can't wait to share it here soon! And good luck to you too. :)

        1. 1

          That sounds genuinely useful — travel planning is one of
          those spaces where "in seconds" is actually the whole value
          prop. I'd use it.

          Drop the link here when you post, would love to check it
          out and give honest feedback. And send me the IH post when
          you launch too — happy to show up in the comments.

          We got this 💪

          1. 1

            https:/www.triply.now thank you for that, means a lot for me.

            1. 1

              I just tried triply.now. It's a clean, simple design that
              doesn't cause confusion, but it could be improved. The guides
              could be enhanced with example images. 🙌

              Tag me when you publish it!

              1. 1

                Thank you so much! 🙏 That's exactly the kind of feedback I needed. Adding images to the guides is already on my list — stay tuned! 🚀

                1. 1

                  can't wait to see it live 🚀 ping me when it's up

Trending on Indie Hackers
The most underrated distribution channel in SaaS is hiding in your browser toolbar User Avatar 86 comments My users are making my product better without knowing it. Here's how I designed that. User Avatar 66 comments I gave 7 AI agents $100 each to build a startup. Here's what happened on Day 1. User Avatar 60 comments A simple LinkedIn prospecting trick that improved our lead quality User Avatar 60 comments I changed AIagent2 from dashboard-first to chat-first. Does this feel clearer? User Avatar 39 comments