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:
-
No network = no launch day traction. PH rewards
existing audiences. If you don't have one, you're starting
from scratch on launch day. -
Twitter without followers is a void. I posted the
launch tweet. 8 views in 6 hours. No algorithm boost
without social proof. -
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. -
Dev.to is slow but honest. Technical article published,
25 views in a few hours. No viral moment, but the SEO value
will compound. -
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
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.
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.
keep going!
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.
I launched on Product Hunt on a new account and got 1 upvote :-) Total failure.
You know its the hardest thing trying to get started on a new project. I should know I have yet to get a sale :(
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.
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?
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?
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?
Thanks for sharing, it's a valuable lesson for me too!
this is the most realest thing i have real all day
Thanks For Sharing Looks very Interesting.
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.
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?
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.
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
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.
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.
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.
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.
Thanks for sharing!
anytime 🙏
Thanks for sharing your experience. Just random thoughts on your launch:
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 🙏
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?
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?
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.
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.
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
"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:
issues on twitter/reddit/IH — reply with actual technical
help, not a link drop
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.
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.
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.
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.
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?
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?
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.
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.
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.
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!
"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 🙏
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
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 🙏
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.
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
Being myself in the same boat, I can truly relate to you bro! Good Luck with your release!
thanks bro, means a lot 🙏 we'll figure it out
what are you building?
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.
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.
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
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.
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
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?
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.
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!
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.
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.
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. :)
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 💪
https:/www.triply.now thank you for that, means a lot for me.
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!