What worked and what didn't — Sunday PH launch with zero email list (0 votes, not featured)
Yesterday I launched VC Deal Flow Signal on Product Hunt. No email list (1 real subscriber after filtering testers and bots), anonymous handle, Sunday launch (lower competition, fewer competitors).
Final result: NOT featured by editorial. The featured_at field stayed null. 0 votes, 0 comments at the T+8h window.
Here's what I tried, what worked, what didn't, all numbers honest.
WHAT I EXPECTED (and was wrong about)
PH editorial would feature the listing because it checked every box: maker present, hunter follower, full description, image, gallery, comments enabled, paid tiers wired. 5 other Sunday launches in the same 07:01:00Z batch DID get featured. Mine did not. PH support email sent, no reply yet.
WHAT WORKED (despite the no-feature)
- Cross-PH commenting on other launches: drafted 19 comments on other products before mine went live. Drove most of the profile clicks I got. Highest-ROI prep move.
- Two pre-launch Reddit threads (r/IndieHackers + r/SideProject build-in-public posts from Apr 19) had 9 + 1 comments and 564 + 176 views by Sunday evening. Substantive replies, not noise.
- Discord blitz across Cursor + MCP Community + Vercel forum delivered the technical audience. The MCP angle (free npx @gitdealflow/mcp-signal) outperformed the dashboard angle 3 to 1 on engagement.
WHAT DID NOT WORK
- Telegram channel: 1 subscriber. Skip until you have an audience to send to.
- Email blast: 1 real subscriber after filtering. Same logic.
- Show HN today: deferred (25 karma + Sunday flag risk too high). Pushing to next week.
- The "upvoter mining" PH tactic from old playbooks: PH stripped public upvoter lists in 2022. The whole strategy is structurally dead in 2026.
WHAT I'D DO DIFFERENTLY
- Build the credibility anchor (SSRN paper, MCP server on npm, Chrome extension) BEFORE the PH attempt, not as parallel bets.
- Spend 14 days cross-commenting on PH BEFORE my own launch. Profile recognition compounds.
- Stop treating PH as a binary launch event. Treat it as a passive listing that compounds when content does the lifting.
WHAT'S NEXT
Re-list Friday with the methodology paper as the lead asset (ssrn.com/abstract=6606558). Different hook, same product. Daily Reddit comments compound. Wiki submissions persist forever. The launch was one bet of seven I am running this week.
Numbers behind every claim are in the threads if anyone wants to dig. Solo, anonymous, 11 days into building distribution.
Site: gitdealflow.com.
Quick update for the watchers. PH editorial support hasn't replied to the Apr 26 not-featured ticket yet, so the Friday re-list is held. Re-listing without resolving the original issue would just produce a second silence, and davidamoroso's framing in this thread (PH treats relaunch as downranked) sealed it for me. Doing the inverse instead: leaving the existing PH page as the canonical hub, pointing the SSRN paper, the MCP server, and new content at it, and running Show HN with the MCP angle as the lead next week. Will report numbers either way.
It’s almost exactly the same as what happened with my launch two days ago. Same time slot on Sunday, same silence.
Personally, in your case, the point about cross-promotion is the one I’d focus on the most. I didn’t do enough of it myself before the launch: this is the real groundwork that nobody talks about—or at least not in depth. Essentially, it’s about making yourself known within a community before asking its members to take an interest in your project. Put yourself on the other side—what would you do?
One thing I’d add: thinking of “PH as a passive list” is probably the healthiest way to approach it in the long run. The spike model is practically dead or nearly so, unless you already have an audience—which isn’t your case—unless someone helps you with a boost. The distribution has to come from somewhere else first.
Relaunching on Friday with the article as the main resource is an interesting move that I hope proves you right. A different hook changes everything on PH.
Sunday silence is apparently a shared rite of passage. The "passive list not a spike" reframe is the one that took me longest to accept - whole launch culture is built around the spike model so it feels like failure when it doesn't happen. Good luck with yours, curious what channel you're betting on next.
You’ve hit the nail on the head. I did the opposite of what I was advised to do, not because I want to be different, but simply to understand why the market, media professionals, and many others chose that particular peak.
Now, while I publish in a purely human way, at a time when it seems that AI will be the one and only means of driving us forward, I will make my own choices after reading the research—which I will certainly analyze using new technologies, but which I will manage at my own pace.
Thank you for your kind words.
To your channel question: betting on long-form research distribution next. dev.to plus a couple of newsletter circuits where data-first readers already gather. It compounds through citations instead of needing a spike, so Sunday silence stings less. Good luck with the Friday relaunch, curious whether the new hook flips it.
Thank you for the explanation and for your kind words.
One thing this post is doing that is underappreciated: the post-mortem itself is distribution.
The founders who will eventually pay for a VC deal flow signal are the same founders reading an honest account of a failed launch. You are not just recovering from a bad launch -- you are building a track record of intellectual honesty, which is the exact signal that makes B2B buyers trust your analysis product.
The Discord MCP installs outperforming everything else is telling you where your early adopters live and how they prefer to try tools. That 3:1 ratio versus dashboard clicks is worth running hard at before re-listing anywhere.
I am building WhatCarCanIAfford.com and had a similar realization after launch: the channel that feels too small (a niche Discord, a specific subreddit) often converts better than a broad platform launch, because the audience already self-selected for the exact problem. The broadcast approach gets traffic; the community approach gets users.
Good write-up. The willingness to publish zeros is rarer than it should be.
The B2B trust angle is something I didn't consciously plan but you're right that it works. If I'm selling signal analysis, publishing zeros is the most honest demo of what the analysis looks like. The Discord number is the one I keep coming back to. Three installs from a single message in one dev tools server. Zero from a broad PH push the same day. Niche self-selection does the conversion work before the product even loads. WhatCarCanIAfford - the constraint framing is smart. "Can I afford" is already the question someone is asking. Most tools make you discover what they answer first.
This is helpful. I think a lot of founders underestimate how much launch prep matters before Product Hunt.
I’m learning that even if the product is useful, you still need the messaging, audience, and support lined up before launch day or the traffic may not convert.
The thing I'd add: "audience lined up" isn't a list of warm contacts you email the morning of. It's the comment history you built in the three weeks before. Nobody checks your profile when you post - they check it when they're deciding whether to upvote. Four days of seeding Reddit and IH pre-launch was worth more than the listing copy. The listing got people to click; the history got them to trust.
Running 19 cross-comments on other PH launches before your own went live is the most underrated prep move in this whole post most people spend that time tweaking their own listing copy instead. The upvoter mining being structurally dead since 2022 is something I wish more launch post mortems said explicitly. Founders are still following 4-year-old playbooks and wondering why nothing works. The 3 confirmed MCP installs from Discord outperforming everything else is actually the most interesting data point here distribution channel and product surface being the same thing is a completely different leverage ratio than driving traffic to a landing page. Good luck on the Friday re-list.
The upvoter mining point is the one I wish I'd read two weeks earlier. Every 2022-era playbook has a section on it. None of them mention that PH changed the notification model. Following outdated launch advice is its own trap - the tactics look reasonable until you check when the post was written. The distribution-channel-equals-product-surface thing is the real unlock. A landing page is a billboard. An MCP install is already inside the workflow. The trust gap between those two things is enormous - you never have to sell again after someone integrates the tool. Friday is the retry. Doing less this time, not more. One channel, same Discord angle.
Doing less on the retry is counterintuitive but probably right. The first launch revealed which channel actually worked, discord MCP angle at 3:1 over everything else. Doubling down on that one thing instead of running the full playbook again is how you compound the signal instead of diluting it. The billboard versus already inside the workflow gap is the thing most founders never close because they keep optimizing the billboard. The MCP install is a solved trust problem. The landing page is a trust problem you have to solve every single visit. Those are fundamentally different economics and most acquisition advice is written for the billboard world. Friday should be interesting. One channel, full focus, actual data on whether the first result was signal or noise.
That last line is the real test. Three installs from one channel could be signal or sample noise - Friday gives you a second data point. If Discord MCP angle repeats at any ratio above chance, you have your channel and everything else is just overhead. Most people never isolate enough to find out.
Friday is the cleanest experiment you’ll run. Same product, same channel, isolated variable. If the ratio holds you don’t have a launch problem you have a distribution answer most founders spend months not finding because they run everything at once and can’t read what worked.
The overhead point is underrated too. Every channel you’re not running on Friday isn’t laziness, it’s control. You’re protecting the data.
What’s your threshold how many installs from Discord on Friday makes it signal rather than noise to you?
Most founders never set a threshold in advance, so any result gets rationalized after the fact. The pre-commit on what counts as signal is half the experiment. Whatever number you land on, install-to-active ratio at day 7 is probably the cleaner read than raw install count.
This Indie Hackers post gives a very honest takeaway: Product Hunt is not a guaranteed growth channel, especially with zero email list, zero votes, and no feature placement. The biggest lesson from the launch was that distribution matters more than just launching cross-community engagement on Reddit, Discord, and niche forums drove more visibility than the PH listing itself.
The B2B credibility filter framing is exactly right and I hadn't articulated it that cleanly. Anonymous handle + no network history is a rational editorial filter, not an unfair one. On the SSRN sequencing: that's the current bet. Paper first, MCP install second, dashboard third. The order signals "rigorous → practical → paid" which is how a developer-investor de-risks a new tool. Discord MCP question: 3 confirmed installs from that thread. One sent unprompted output screenshots. That's the conversion that actually matters - you're right.
Thank you for the honest breakdown. This thread has already covered the distribution gap and cross-commenting compounding better than I could, so I'll add one angle I haven't seen yet:
PH editorial didn't just reject a product. It rejected a B2B product without B2B trust signals.
The checklist you optimized — images, tiers, comments, maker present — is designed for consumer tools where the product demo sells itself. But VC Deal Flow Signal is a B2B credibility product. The buyer is making a judgment about signal quality, and signal quality is inseparable from "who's curating it and why should I trust them."
An anonymous handle with zero network history is a rational filter-out for B2B editorial. Not unfair — accurate. The same product with a named founder, a LinkedIn with 500+ connections in the space, or a single reference customer would have passed a different filter even with identical completeness.
This reframes the Friday relist strategy. The SSRN paper isn't just a new hook — it's a trust signal that compensates for the anonymity gap. Lead with the paper, follow with the MCP install, list the dashboard last. The order matters because B2B buyers de-anonymize in stages: academic credential → technical try → product commitment.
The real question: has anyone in your Discord MCP thread actually installed it and given feedback? That's the conversion that matters more than PH votes — one developer who ran npx @gitdealflow/mcp-signal and told you what the output looked like is worth more editorial signal than 50 upvotes from founders who'll never be users.
Thanks for the framework - funnel infra is already in place (landing page, 5 free MCP tools live, email flow active). The gap isn't the funnel, it's the distribution reach upstream of it. That's the thing the cross-commenting is meant to fix.
Why not try creating a waitlist to see if people are interested. If you can get people to join your waitlist, then you won't struggle getting users. Here are what you should focus in:
Are you ready to implement these suggestions?
Thanks. The relaunch isn't really a second chance at PH - it's using the time to earn a better first word in (SSRN paper as B2B trust signal before the product pitch). Will report back either way.
I appreciate you sharing this! I love how you’re focusing on building traction before the launch. Looking forward to seeing how the relaunch goes with the new angle.
The separate-audience pages exist already - /mcp for the developer install flow, /dashboard for the VC angle, /methodology for the paper anchor. The mistake was that the launch post pointed to one generic URL instead of the right one per audience. Good reminder to fix the link routing.
Well this is a smart adjustment! Directing traffic to the right pages should definitely boost engagement. Good luck with the relaunch
Thanks! The routing fix sounds obvious in hindsight - sending a developer to a VC-pitch landing page and expecting them to convert is just friction. Will report back on whether it moves the needle.
The useful signal here is that three different audiences clicked for three different reasons: Product Hunt makers, Reddit founders, and MCP or terminal users. I’d turn those into separate pages immediately instead of sending future traffic to one generic launch page.
One page for the deal-flow use case, one for the MCP workflow, one for the dashboard angle, and one for the founder post-mortem itself. When the next click lands on the exact angle that earned attention, conversion usually gets a lot cleaner.
For context, I'm building Clustra which does this automatically and happy to generate a free example for your product if useful: clustra[dot]nanocorp[dot]app
The separate-audience pages exist already - /mcp for the developer install flow, /dashboard for the VC angle, /methodology for the paper anchor. The mistake was that the launch post pointed to one generic URL instead of the right one per audience. Good reminder to fix the link routing.
The cross-commenting takeaway is correct and underweighted. The re-list-on-Friday plan is the one I'd push back on.
PH treats a relaunch as a downranked listing. The signal that matters internally is first-launch velocity, and once that's spent the page just sits as a passive SEO asset. Re-listing in five days dilutes the URL you already have without giving you another shot at editorial. The better play with the same effort: leave the page alone, point all new content (the SSRN paper, the Chrome extension, the MCP server) at the existing PH page as the canonical hub, and let it accrete backlinks.
The MCP angle outperforming dashboard 3:1 in Discord is the thing to actually run with. That's not a PH lesson, it's a positioning lesson. "Free MCP server" is a developer-distribution hook and it deserves its own Show HN attempt once karma allows, with the dashboard listed as the upgrade path. The audience for the MCP and the audience for the dashboard are different people and PH was a poor venue for either.
How many of the Discord engagements turned into MCP installs you can measure? That conversion number is the one that decides whether to lead with MCP next round.
Right call to stop. One thing that compounded faster than expected: genuine replies in subreddits your target user already lives in - not launch posts, just comments on live threads. One week of that built more profile recognition than a week of PH prep would have. Good luck with Triply.
Thank you for sharing this! I was literally about to launch my project (Triply) with zero followers and no email list, thinking the product would speak for itself. You just saved me from a major disaster.
It’s a huge wake-up call to see that even a 'perfect' technical setup gets ignored if you don't have that initial 'social credit' on the platform. I’m definitely going to stop and spend a few weeks building a presence first.
Good luck with the re-launch on Friday! I'll be cheering for you.
The compounding on profile recognition is real and it accelerates with one adjustment: reply to the top commenter in a thread, not the OP. Their upvotes pull you up with them, and they're more likely to engage back. You're on the right track.
Wow, that is a pro-tip! I never thought about it that way—hacking the 'gravity' of the top comment. It makes total sense for someone like me who has limited time to be online.
I’m going to start testing this 'piggybacking' strategy right away. It’s exactly the kind of efficiency I need while balancing my shifts and dev time. Thank you so much for sharing that shortcut and for the encouragement. It really helps to feel like I'm moving in the right direction!
Good luck with Triply. The top-commenter move is underrated - most people default to OP out of habit. Testing it on a few threads before launch is low cost and the feedback is fast.
Exactly! I noticed that most people just shout into the void of the main thread, but the real gems are in the sub-conversations.
Doing these 'low-cost tests' is my favorite way to iterate right now—it saves me time and energy before the big launch. Thanks for the encouragement, it feels good to know I'm not just overthinking the strategy!
What to track on the test is reply rate, not just views. Top-commenter replies that the OP also engages with are the ones that compound. Silent views mean the gravity didn't catch. Good luck with Triply on Friday.
That makes perfect sense. I’ll stop chasing 'vanity metrics' and start focusing on the gravity of the conversation. High reply rates are definitely the goal to make the Triply name stick.
About Friday—I’m currently in the middle of the 'Production Key' battle with Amadeus to get everything live. It’s the classic pre-launch hurdle, but I’m pushing through.
Thanks for the masterclass on engagement. I’m going to make sure my replies are worth responding to!
The Production Key game is its own pre-launch hurdle that doesn't get talked about enough - bureaucratic, opaque, on their timeline not yours. The accidental gift is the runway: API approval queues are the highest-leverage distribution-building window you'll ever have, because there's no live product yet to split your attention. Most founders treat the wait as dead time. It's actually the only window where every test is cheap and every reply that compounds becomes a name people already recognize when the key clears. Sequential, not parallel. Good luck with Amadeus. Curious to see Triply when it's live.
The "distribution gap that existed before it" line is the real takeaway. I'm in the same position - Chrome extension, zero list, building distribution through daily Reddit and LinkedIn comments. Your cross-commenting insight confirms what I'm seeing: profile recognition from genuine replies compounds way faster than any launch post. Bookmarking this for when I plan my own PH attempt. Thanks for the honest numbers.
You nailed it. I built the three entry points specifically for that split - devs want the MCP install (/mcp), investors want the signal dashboard (/dashboard), researchers want the methodology and paper (/methodology). The launch post lazily funneled everyone into the homepage and let them self-sort. Fixing the CTAs now. Also thinking about a smarter top-of-page CTA block that asks "I'm a…" and routes accordingly.
The I'm a… routing idea is smart. I deal with the same problem — my extension serves freelancers, gamers, and remote teams, but they all care about different features. Right now everyone lands on the same page and has to figure it out themselves. Definitely stealing that approach for my own landing page. Let me know how the re-list goes on friday.
Freelancers, gamers, and remote teams is actually a harder routing problem than mine — those three use completely different language, care about different outcomes, and might not even recognize themselves as the same kind of user. A single headline can't hold all three. The "I'm a…" block works because it converts a misread into a routing signal. Instead of guessing who landed, you let them self-identify and then show them the version of the product that's actually for them. The conversion lift isn't from better copy - it's from reducing the cognitive load of "does this apply to me." Friday re-list is in motion. PH editorial flagged the first attempt; working through their support channel. Will post an update here when it's live either way.
The anonymous handle is the thing that stands out to me as the highest-cost decision for a B2B product specifically. For VC Deal Flow Signal, the buyer is a professional making a decision about signal quality — and trust in the signal comes partly from trust in who's curating it. An anonymous handle short-circuits that before they've even evaluated the product.
We launched SiteBirds with a real face and real company behind it (Dutch, EU-based, very clear about who we are) and found that for B2B, that visibility does a lot of the conversion work that copy can't. The product page might be great but if there's no person behind it, skepticism stays high.
The cross-commenting insight is exactly right though. We found the same thing: the accounts that get traction on PH are the ones that have been consistently visible in the community for weeks before. PH is much more a credibility harvest than a discovery engine at this point — you're surfacing to people who've already seen your name somewhere.
The point is valid and I accepted it as a known cost upfront. Anonymous identity removes the person-behind-the-product trust signal that B2B conversion depends on. The bet I made is that the signal itself - GitHub activity data, methodology, the SSRN paper - would carry that credibility instead of a face. It is a harder path and whether it works is still an open question.
fair on isolation. but 0 cold votes don't tell you about the product - just confirms the network gap. still no read on whether the thing has legs.
Right - zero PH votes measures network depth, not product quality. The reads I actually trust: paid conversions from cold organic arrivals with no prior context, and MCP installs from devs who found it through search or the npm listing. Still thin, but those don't have the network confound baked in. PH was always the wrong instrument for this one.
The cross-commenting point is real and seriously underrated. We're launching our affiliate/partner program on PH next week (not the main SaaS product — the product is 18 months live, launching a new program on top of it). Spent the last few days commenting on other PH launches not because I expected traffic back, but because your name needs to feel familiar to the people who'll see your launch.
Your insight about treating PH as a passive listing that compounds when content does the lifting matches what I've seen in B2B. The launch day is almost theatre — the real value is the persistent page that gets found later via Google.
One thing I'd add: launching a specific thing (feature, program, price change) that's new gets editorial attention more reliably than re-launching an existing product under a new name. The product is what you have to position. Good luck with the Friday relaunch.
The "launch a specific new thing" note is exactly what the Friday relist is built around. The methodology paper is the new thing, not a rebadge of the same listing under a different hook. That framing clarifies what I was doing intuitively. Good luck with the affiliate program launch next week.
The cross-commenting point is real. I'm doing the same
thing right now. Launched my open source project today
across dev to, Hacker News, and Twitter with zero
audience. The comments I left on other people's posts
over the past few days drove more profile clicks than
any of the direct posts did.
Your point about treating launches as passive listings
instead of binary events is something I wish I'd read
a week ago. I was thinking about it as "launch day"
when really it's just the first day of distribution.
The honesty about the numbers is refreshing too. Most
launch recaps only share what worked. The Telegram
channel with 1 subscriber and the email list with 1
real subscriber after filtering is the kind of data
that actually helps other founders calibrate
expectations.
Good luck with the Friday re-list.
The fact that your pre-launch comments are already outperforming your direct posts is the experiment confirming itself in real time. That data point from your own launch is more useful than anything I could add. Good luck with the open source project - following to see how it compounds.
Thanks, appreciate that. Will keep posting updates as
the distribution side develops. Your breakdown of the
PH mechanics was genuinely useful for calibrating
expectations. Good luck with the Friday re-list.
Mutual - I'll be watching your updates. The part I don't have data on yet is whether the cross-commenting effect compounds or flattens. Your launch is a live experiment for that question.
The "distribution gap that existed before it" line is the real takeaway here. I'm learning this the hard way. Built an AI support tool for DeFi protocols, 77K lines of code, 46 chains, everything works. Spent months shipping features thinking the product would carry itself. Then tried cold outreach: 80+ DMs, 40+ emails, zero replies. Not one.
Your cross-commenting strategy is exactly what I've started doing on Twitter. Replying to trending crypto security threads with genuine analysis, not pitching. One reply got 1,764 views from a 13-follower account. That single reply did more for visibility than every cold DM combined.
The lesson I keep relearning: distribution compounds slowly through repeated presence, not through one launch event. Your PH experience confirms it. I was planning a PH launch soon but reading this, I'm going to spend the next month building profile recognition across communities first. Appreciate the honest numbers.
1,764 views from one reply on a 13-follower account is the number worth sitting with. That is not a fluke. It is what happens when the reply does real analytical work inside a thread where attention is already concentrated. Cold DMs start at zero context. Replies inherit the thread's existing engagement. Completely different starting conditions. One month of community presence before PH is the right sequencing.
Yeah I really hope that wasn't a fluke, I genuinely believe this method works though. You're right that a reply with built-in credibility is a completely different game to a cold DM from zero from a random nobody. 1,764 views from 13 followers only happened because the reply did real work inside a thread people were already paying attention to. My 80 cold DMs had zero context, zero trust, zero reason for anyone to care. Same person, same product, completely different outcome just because of where the message landed. Hoping the momentum keeps building. Appreciate the honest breakdown, this whole thread has been more useful than months of outreach.
It wasn't a fluke - the variable that made it work is repeatable. Find threads where attention is already concentrated, do the real analytical work, land it there. The 13 followers is irrelevant; what you borrowed was the thread's existing engagement. Do that consistently and you're building presence through compounding, not hoping for lightning to strike twice.
That's reassuring. The variable being repeatable is the key insight. Going to keep doing exactly that, find where attention already exists and add real analysis. Appreciate the encouragement.
Exactly this. "Find concentrated attention, do real work there" is an actual system, not a tactic. Going to run it deliberately now instead of hoping the next good reply lands by accident.
That's the shift. Once you treat it as a system instead of hoping for lucky replies, you can actually measure what's working. Let me know how the deliberate run goes, curious whether your conversion looks different when you're targeting specific communities vs broad posting.
The calibration's the part I'm still figuring out. Different communities have different thresholds before a reply earns attention. Some land on one sharp observation, others need full analysis or you get scrolled past. That nuance is half the system right there.
Exactly right. A one-liner that works in a crypto Discord gets scrolled past on Indie Hackers. A full analysis that works here gets ignored on Twitter. I've been adjusting per channel for weeks now and the hit rate is noticeably different once you stop copy-pasting the same voice everywhere.
"Weak signal in warm network" → "favor-yes" is the same upgrade as "PMF issues" → "people don't actually want this." The polite version protects the ego for a quarter and burns the runway for a year. Most founders need permission to say it plainly; very few find the permission alone. The reshape you mentioned is the real ROI. Posts get archived, upvotes decay, but the change in who you're building for compounds. That's what BIP measurement misses - it scores reach instead of recalibration. One forward thought, since you mentioned reshaping who you're building for: pain-yeses usually come from people already running a hacked-together half-solution. Spreadsheet workarounds, in-tool feature requests on a competitor product, search behavior on niche queries. They're already paying time to solve it, just badly. That's the population to find next. Good thread. Genuinely.
without seed votes from a real network, the day of week doesn't move the needle. PH editorial follows traction, not the other way around - the checklist matters less than who shows up on day one.
That is the correct diagnosis. Day of week is marginal variance. Network is the variable that matters. I accepted the cold-start cost deliberately because it keeps the experiment clean. You cannot isolate what the product does on its own if warm contacts inflate day-one traction. The tradeoff is real, I just wanted the honest baseline.
The cross-PH commenting thing is something I hadn't considered before - treating profile recognition as a compounding asset before you even launch is smart. I've been doing the equivalent on Reddit (genuine participation before posting about my own thing) but never thought to apply the same logic to PH
The passive listing point resonates too. I'm about to do my first post here on IH before touching PH - partly because I want real user feedback before putting it in front of a launch audience. Your experience reinforces that call
Curious about the Discord results - was the MCP angle outperforming because it was more technically novel, or because Discord audiences tend to skew toward people actually building things rather than just evaluating them?
And for the Friday relist, are you changing the product description entirely or just leading with the MCP angle? Wondering whether PH flags it as a duplicate if the core URL is the same
On MCP vs dashboard: audience behavior, not novelty. Cursor and Vercel Discord users have a terminal open. They run npx in 10 minutes. Dashboard users bookmark and return later, or never. Different behavior, different conversion rate. On the Friday relist: leading with the MCP install line, SSRN paper as the third paragraph credibility layer, not the hook. On PH duplicate flag: same URL does not trigger it. PH flags by product name and similarity score. Different angle on the same underlying product is standard practice.
The line that hit me: "treat PH as a passive listing that compounds when content does the lifting." That's a much healthier mental model than the binary launch-day-success thing most of us trap ourselves in.
A few reactions to your retro:
The MCP angle outperforming the dashboard 3:1 is the actual signal in this post. That's your wedge — npx-installable, technical audience, zero onboarding friction. I'd lead Friday's relist with that, not the SSRN paper. The paper is the credibility anchor, not the hook.
The cross-commenting prep move is underrated and you nailed why — profile recognition compounds. 14 days is right; I'd say even 30 if you can stomach it.
Also — not getting featured on Sunday while 5 others in the same batch did is genuinely weird. Worth a polite nudge to PH support with the batch comparison, not just a generic email.
I'm Shirley from ZooClaw, also deep in user-discovery mode and running my own daily-comments-compound experiment. If you ever want to compare notes on what's actually moving the needle, ping me. Friday relist — rooting for it.
MCP as wedge, paper as anchor is cleaner framing than I had it. That is exactly how Friday is structured. On the batch comparison - email to PH support sent April 26, no reply yet. The specific ask is narrow: five other 07:01:00Z batch launches were featured that morning, mine was not, with comparable completeness signals. If they respond with anything useful I will post it here. Good luck with ZooClaw.
Really appreciate the honesty here. The cross-commenting on other PH launches before your own is such a underrated move — most people only think about launch day, not the days before. The MCP angle outperforming the dashboard 3:1 is a useful signal too. Good luck with the Friday re-list!
Thanks. The 3:1 ratio was the most useful data from the whole day. Sometimes the version of the product you built for your own convenience ends up being the version the actual user wants. The MCP was an afterthought. It outperformed everything else. Good luck with your launch.
Currently planning my own PH launch with a similar setup, no real list. Two questions if you don't mind: was there any traffic source besides the PH page itself that actually moved the needle? And in hindsight, would you have launched at a different time of week or just kept Sunday?
Traffic that moved the needle: two build-in-public Reddit threads from the week before launch. 740 combined views and 10 comments before April 26. Discord (Cursor + MCP Community + Vercel forum) was second. The PH page itself generated profile clicks but nothing convertible without the feature placement.
On timing: I would keep Sunday. Lower daily velocity means fewer products competing for front-page slots, and if you miss the feature cut anyway, you have two quiet days before the algorithm resets to build organic thread traction. The problem was not the day. It was the distribution gap that existed before it.
Super useful, thanks. The "distribution gap that existed before it" line is the actual lesson here. I've been treating PH like a one-day thing when you're describing it as the visible peak of stuff you started two weeks before.
Quick follow-up: those build-in-public Reddit threads, did you frame them around specific milestones (shipped V1, here's what worked, that kind of thing) or were they more discussion / question-asking? Most BIP posts get crickets so curious what made yours land.
Both posts were milestone-framed, not question-asking. Specific numbers in the title (day count, user count, a metric that moved) plus one honest confession that most builders skip. The r/SideProject post was "11 days, 0 paying users, here is what the data actually shows." The question at the end was one sentence, narrow, answerable in two lines. Generic "feedback welcome" posts die. Specific confessions with a tight question survive.
This is the part I'll actually take with me. "Specific confessions with a tight question survive" vs generic "feedback welcome" posts die. Pinning that one.
Also the "one honest confession that most builders skip" line is the part most people will fail at, because being specific about what didn't work feels expensive in the moment. Easier to generic-post and protect ego. Worth the discomfort apparently.
Going to write my first BIP post next week with this structure. Will probably overshare and figure out what lands. Thanks for the genuine playbook, this thread's been more useful than the post that started it.
"Probably overshare" is the right call for the first one. You learn faster what to cut than what to add. Drop the link when it goes up - genuinely curious what the confession ends up being.
link's here: reddit.com/r/SaaS/comments/1sxyp2t/
the confession ended up being that all 5 of my yeses were probably favor-yeses from my linkedin network, not pain-yeses from people actually struggling with planners. one commenter called it pretty cleanly and the followup convo has been more useful than the post itself, which i think is exactly what you meant about specific confessions surviving.
Favor-yes vs pain-yes is a clean distinction and the commenter who named it gave you more than the upvotes would have. That's the whole point of the confession structure - it attracts the one person willing to be honest back. Thanks for pushing me to post it.
the "pushing me to post it" cuts both ways honestly. your framework was the thing that gave me permission to write the favor-yes confession plainly instead of dressing it up. before reading your post i had been calling it weak signal in my warm network, which is just a polite version of the same thing.
that followup convo has genuinely reshaped how i think about who i'm building for now. most useful single thread i've had in 17 days of being in market.
@The_Data_Nerd "PMF issues → people don't actually want this" — yes, that upgrade stings the right way. the euphemism feels like progress because you're doing something with it (talking about it, building on it),
but you're optimising for the version that lets you keep going, not
the version that breaks the loop.
honest answer on the link: the messaging shift hasn't shipped yet.
current site still talks to the favor-yes ICP because that's who's
been opening the app. next iteration reframes around
execution-rate-as-honesty for people who've already given up on
planners — should be live in the next 7-10 days. i'll drop it here
when it's up, rather than send you to a thing that doesn't reflect
the convo we just had.
current link if you want the warts-and-all version:
planner.axtrastudios.com
The "weak signal in my warm network" line is the part I'm taking with me. It's the same euphemism upgrade as "PMF issues" → "people don't actually want this" — polite version protects the ego for a quarter and burns the runway for a year. The reshape you mentioned is the real ROI; posts decay, but the change in who you're building for compounds. Good thread, genuinely. Drop a link if the next iteration with the new ICP goes up.
This is one of the more honest PH breakdowns I’ve seen.
I’ve tried launching with almost no audience too, and the “PH will carry it if everything is set up right” assumption just doesn’t hold. If distribution isn’t there before, it doesn’t magically appear on launch day.
+1 on cross-commenting. That’s been the only thing that consistently gives visibility early.
One thing I’ve noticed: early traction (even small) seems to matter more than completeness. A slightly rough product with a few real interactions often does better than a fully polished one with zero signal.
Curious to see how the re-launch plays out with a stronger credibility anchor. That part feels like the real lever here.
The completeness vs. early traction observation is correct, and it probably runs deeper than PH. Completeness is a solo metric - you can verify it in isolation. Traction requires other people, which means editors treat it as real signal. I optimized the wrong thing in the final 48 hours.
Curious to see how the Friday re-list goes too. The credibility anchor framing changes what the listing is for, even if the product does not change.
Experiment is good
That is the frame. One variable at a time, honest readout. The not-featured result is data, not a verdict. Already running the next iteration.
You ran a clean experiment and read the data without ego. That’s rarer than a featured launch.
The real find here: PH stripped upvoter lists in 2022 but most founders still plan like it’s 2021. You noticed. Most won’t.
Cross-commenting before launch is the quiet work that actually compounds. Everything else is just hoping for an editor’s mood.
The 2021 playbook thing is worth naming directly. The most-shared PH launch guides still reference upvoter lists, hunter follower counts as the main lever, and batch-with-big-names timing. All three worked differently once PH changed the algorithm and stripped public upvoter data. The quiet compound work doesn't make for a good tweet. So the outdated advice keeps circulating.
The outdated advice keeps circulating because it's easy to tweet. The quiet work, cross-commenting, building relationships before launch day, doesn't screenshot well. So founders keep optimizing for the 2021 playbook because it feels productive. But chasing old levers isn't strategy. It's nostalgia with a launch date. The data changed. Most people just didn't notice because they stopped measuring.
The half-life of bad advice on these platforms is approximately forever. Nobody retracts a 2021 tweet when the algorithm changes in 2022 - no incentive to. Which means the only person with current numbers is whoever ran the experiment last week. Post-mortems beat playbooks for exactly that reason.
Launching to crickets on PH is brutal, but this transparent breakdown is exactly why I love this community. You're spot on that distribution needs to precede the launch. To help pinpoint the exact high-intent subreddits and niches for your next bet, we actually built an AI agent that handles that entire audience validation process for you. Good luck on the Friday re-list!
Thanks for the kind words. The audience validation piece is real - knowing which communities have the right intent before you show up matters a lot. Appreciate you stopping by.
Our team also launched a project called "Business GPT" on Product Hunt about 20 days ago, but honestly, the result was a disaster with only 8 upvotes and 30 followers. It’s upsetting. We worked hard, but we couldn't achieve good results on the second launch either, so it seems we have a similar experience.
So, we are looking for which channels would be the best fit for promoting our project.
8 upvotes from a cold start with no list is actually close to honest signal. The inflated counts from friends and founders do not convert to anything useful downstream.
On channels: depends entirely on what Business GPT does specifically. General AI assistant space is saturated at every level. If there is a specific vertical - legal, HR, finance, operations - the niche forums and professional subreddits will outperform PH by a large margin for your actual target user. The pattern that has been working for me: find the threads where your user asks "how do I do X" in their professional context, not startup or launch subs. Answer the technical question first, mention the product only if it is directly relevant. That is the channel. The platform is wherever those threads live.
Thanks for the reply. We need to produce a small result (proof that the client is interested in our project) within two weeks. Would it be better to do this on Product Hunt or Indie Hackers? I am a UI/UX designer and a member who launched the project together. I know my questions were too varied, but meeting someone who shares the same concerns makes me feel like I have so many questions.
For a two-week proof-of-interest sprint, IH is more useful than PH. A Show IH post gets you comments and direct questions, which is a usable artifact for a client conversation. PH gives you a vote count, which is founder signal, not client signal. But the faster path to proof: find two or three Reddit threads or Slack communities where your target client role already discusses the pain you are solving. One real conversation there outweighs 50 upvotes from founders who will never buy. What vertical does Business GPT serve? That changes the answer significantly.
really?i got it! Reddit and Slack are absolutely the real goldmines for genuine client signals over just vanity metrics! To answer your question, Business GPT is tailored for founders and product teams, automating the heavy lifting like business logic, competitor mapping, and PRD generation. Since the whole goal is helping builders skip the boring setup to ship faster, getting that raw feedback directly from those specific communities is definitely the smartest play!
Do you happen to have any Slack communities you would recommend?
For that vertical: Lenny's Newsletter Slack is the highest-density product community that's actually active - PMs and founders who care about process, exactly the Business GPT use case. Product School's Slack skews slightly earlier-career but high volume. For the founder/PRD angle, the Build in Public community on Twitter/X has migrated a lot to Discord and the signal-to-noise is better than most Slacks right now. One thing that matters more than which community: search before you post. Find the thread where someone already asked "how do you handle PRDs at your team" or "what's your competitor research process" - answer that specifically, then mention the tool only if it fits the question directly. That conversation already has intent. A fresh intro post doesn't.
Thank you for your reply. It seems Slack and Discord are the main platforms. I have mainly been active in Product Hunt and Indie Hackers so far, and this is my first time using Slack and Discord. Could you share a link to the Build in Public community on Discord? For Slack, would Product School be a good choice? Since our goal is to promote our product as soon as possible, I would prefer a community where users who are interested in AI agents gather.
Thank you so much for your advice. It was very helpful.
For Build in Public, search "Build in Public" on Twitter/X - the Discord invite links surface there regularly and rotate so I won't link a stale one. Product School Slack is straightforward: productschool.com/slack. For AI agent specifically, the Latent Space Discord is worth joining - that's where practitioners hang out, not just enthusiasts. Same rule applies: search existing threads before posting anything about your product.
Respect for sharing the real numbers. A lot of launch posts only show the win, but the useful lessons usually come from transparent misses like this. It also reinforces that distribution is rarely one event, it’s usually accumulated trust, visibility, and repeated touchpoints.
Niche fit first, always. Vote count is mostly a proxy for general traffic, not your audience. High vote count + zero niche fit = profile clicks that don't convert to anything. The pattern you described - "how do I solve X" technical threads - is exactly right. The compounding is in the reply tree, not the upvote count on the post.
Exactly. A lot of makers chase visible metrics because they’re easier to measure, but targeted attention usually compounds harder than broad attention. Ten relevant people in a comment thread can be worth more than a hundred casual upvotes.
The ten relevant people point is the one worth keeping. They have the context to act on it, refer it, or tell someone who will. Casual upvotes can't do any of that.
Exactly. Relevant attention carries context, which is what makes it valuable.
Enjoyed the back-and-forth on this thread.
Right. Context is the multiplier. Someone who understands the problem can do something with it - use it, share it with the right person, come back later. A passive upvote just dissipates.
The line about cross-PH commenting being your highest-ROI prep move matches what I've been seeing exactly. I'm shipping a tiny Captio-style memo app for iOS in a couple of weeks — one-tap-to-email, no menus — and my best week of profile clicks came from leaving 12 thoughtful replies in three indie subreddits, not from any post of my own. The compound on your "profile recognition compounds" point is wild — most of my early DMs name a comment I left a week earlier, not my build-in-public thread. One add: the replies that converted weren't on launch posts, they were on "how do I solve X" technical threads where I had a real answer. Curious — when you pick which PH launches to comment on during the 14-day pre-launch sprint, are you optimizing for niche fit or for vote count?
Honest answer on the editorial filter: I don't know. It's a black box and I stopped trying to model it. My read is the three anchors don't change the featured decision - they change what happens after: Friday re-list credibility, search visibility, referral traffic that doesn't depend on PH. On PH vs Reddit for pre-launch: PH comments stay visible under the product tab indefinitely. Reddit threads age out in 48h. The ROI difference is there.
Launching Tuesday with similar setup (no list, fresh handle, three apps not one). Your "stop treating PH as a binary launch event" is the line I needed. The cross-PH commenting being the highest-ROI prep move is the data point I didn't have, was leaning toward Reddit-only. One question: of the three credibility anchors you'd build first next time (paper, MCP server, Chrome ext), which do you think actually triggered the editorial filter? The rest read like distribution wins (substantive, compounding) but the "featured" decision feels orthogonal to all of them. Also bookmarking the gitdealflow MCP angle, that 3:1 ratio vs dashboard is the data I expected to see going the other way.
The 3:1 ratio made sense once I saw who was sharing it. MCP gets found by developers who already know how to wire tools together - they try it in 10 minutes. Dashboard gets bookmarked by analysts who want to see output but won't run a CLI. Different behavior, different conversion. On the editorial filter: account age and early-hour velocity seem to matter, but that's speculation. Nobody outside PH knows for certain.
Thank you so much!! This post has really useful information! (I'm currently building a product myself and have zero experience launching)
Thank you so much, that means a lot. I wanted to write the kind of post I wish I had found before launching: honest numbers, what actually worked, and what turned out to be outdated advice. If you’re building your first product, my biggest takeaway is that distribution starts before launch day. Wishing you lots of momentum with your build.
I'm thinking of a few questions for you
You're using accounts under the pseudonym "The Data Nerd" instead of your real name. Did this impact you when promoting your product? (Especially since platforms like Product Hunt explicitly mention in their community guidelines they only want profiles of real people with their real first name and last name)
I see gitdealflow has a LinkedIn company page. Do you also have a LinkedIn account under pseudonym or did you need to use your real LinkedIn account (with real name) to create the page?
Did you talk about your product with people you know in real life?
If you needed to use your LinkedIn account with real name, did gitdealflow page got displayed to your network automatically?
Good questions, all of them practical.
On the pseudonym and PH policy: yes, there is tension there. PH guidelines reference real names but enforcement appears inconsistent - anonymous and handle-based builders are common on the platform. My read is the editorial risk is real but unquantifiable. I accepted it as a known tradeoff.
On LinkedIn: company page only, no personal profile tied to this product. The page exists for legitimacy - for anyone who Googles "GitDealFlow" and wants to see a real entity behind it. It is not an active distribution surface, which also means there is no personal network to bleed into.
On IRL conversations: zero. Distribution has been entirely digital. Nobody in my physical or professional network knows this exists. That is intentional. It also removes an obvious early-upvote pool, which is a real cost.
On the network display question: no personal profile means no network bleed. That is the tradeoff I made at the start.
About LinkedIn my question more: is your personal account admin of gitdealflow LinkedIn page? Because I tried to create a LinkedIn page without using a personal account but failed
Yes, LinkedIn requires a personal account to create and admin a company page. There is no workaround for that. The anonymity holds because being an admin is a backend relationship - your name does not appear on the page, you do not show up as an employee unless you add it, and you do not post from personal unless you explicitly switch accounts.
Thanks a lot for all your answers!
Anytime. The LinkedIn admin route is one of those quiet anonymity tools that rarely makes it into launch playbooks. Good luck with your build.
This comment was deleted 8 days ago.
This comment was deleted 8 days ago.