I launched VC Deal Flow Signal on Product Hunt last Sunday. Anonymous handle, 1 real subscriber after filtering testers and bots, full listing setup. Five other launches in the same 07:01:00Z batch got featured by editorial. Mine did not. The featured_at field stayed null. 0 votes, 0 comments at T+8h.
I wrote the post-mortem on Indie Hackers the same evening. Honest numbers, what worked, what didn't, no narrative repair. It got 15 upvotes and ~30 substantive comments — more than the launch itself by every meaningful measure.
Here's what the comments taught me that the launch didn't.
The 3:1 ratio nobody saw coming
Three free MCP installs from a single Discord message. Zero installable conversions from the broad PH push the same day. The MCP angle outperformed the dashboard angle 3:1 on engagement, and I had built MCP as the afterthought.
The IH thread named the reason cleanly: distribution channel and product surface being the same thing is a completely different leverage ratio than driving traffic to a landing page. Cursor and MCP Community Discord users have a terminal open. They run npx @gitdealflow/mcp-signal in 10 minutes. Dashboard users bookmark and return later — or never.
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.
The 2021 playbook trap
The most-shared PH launch guides still reference upvoter mining, hunter-follower counts as the main lever, and batch-with-big-names timing. PH stripped public upvoter lists in 2022. The whole strategy is structurally dead in 2026. Founders are still following 4-year-old playbooks and wondering why nothing works.
One commenter put it best: 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. That's the whole reason I wrote the IH post.
Cross-commenting is the highest-ROI prep move
I drafted 19 comments on other PH launches before mine went live. That alone drove most of the profile clicks I got. Several IH commenters confirmed the same pattern from their own launches: profile recognition compounds, and the comment history you build in the three weeks before launch is worth more than the listing copy on launch day.
Nobody checks your profile when you post. They check it when they're deciding whether to upvote.
The ten-relevant-people-in-a-comment-thread thing is also real. Casual upvotes can't refer, can't act, can't tell someone who will. The compounding is in the reply tree, not the upvote count on the post.
PH as a passive listing, not a binary launch
The healthiest mental model that came out of the thread: stop treating Product Hunt as a binary launch event. Treat it as a passive listing that compounds when content does the lifting.
The spike model is practically dead unless you already have an audience. The page exists. New content (the SSRN methodology paper, the MCP server on npm, a Chrome extension) all point at the existing PH page and let it accrete backlinks. PH is the canonical hub. Everything else is the distribution upstream of it.
This reframes the relist plan entirely. Don't relaunch — accrete.
The B2B trust gap I didn't price in
Anonymous handle, no LinkedIn personal, no IRL conversations about the product. I made all three calls deliberately. Editorial filter for B2B is rational about this: an anonymous handle with zero network history is an accurate signal that the buyer can't yet verify who's curating the data.
The product is a signal-quality product. Signal quality is inseparable from "who's curating it and why should I trust them." A face plus a network does conversion work that copy can't.
The mitigation isn't to stop being anonymous. It's to substitute different trust signals: the SSRN paper for academic credibility, the npm install for technical try, the dashboard as the upgrade path. Buyers de-anonymize in stages — academic credential, technical try, product commitment. The order matters.
Eight days later, the iteration is paying
Eight days after the PH zero, the dataset has gone from 91 venture-backed startup orgs to 109 — an 18-org refresh from the autonomous fetch-github-data run, picked up automatically in the next signal report. The MCP angle that the IH thread named as the highest-ROI surface got two Chrome extensions shipped (an existing Crunchbase + Wellfound badge plus a new GitHub-native hover lookup), both pointing back at the same dataset. A /pricing page got built — six tiers from a free weekly digest to a €4,970/yr Sharp Tier for active funds, application-gated and capped at 8 funds in 2026. A /buyers-guide page got built — eleven evaluation criteria for how to choose a VC deal-flow tool, each with the question to ask the vendor and how this product handles it.
None of those four shipments would have been the obvious priority on PH launch day. They became the obvious priority after the IH thread named which channel was actually working. That's the practical version of the post-mortem advice: the comments named the leverage points, the next eight days reorganised around those points, and the listing-tier expansion (the Sharp Tier had been buried on the apex landing only — surfacing it as a first-class /pricing row roughly tripled its discoverability for the small-fund SERP) got prioritised over running the launch playbook again.
The asymmetry is what makes the post-mortem worth writing. Failed launches are common; failed launches that tell you specifically what to do next are rare. When the comments converge on the same answer from thirty different angles, you don't need a strategy meeting. You need to ship.
The reorder pattern showed up in the data shape too. The free MCP server kept being the most-installed surface across the eight days, while the dashboard kept being the most-bookmarked-and-not-returned surface. Treating the MCP as the front door instead of the upgrade path meant putting the install command above the email signup on three of the four landing surfaces and adding a /buyers-guide cross-link on every page where someone might be evaluating the tool against alternatives like Harmonic.ai, Dealroom, Crunchbase, Forager.ai, or Tracxn. None of that work was scheduled before the IH thread happened.
What I'd do differently
Build the credibility anchors (SSRN paper, MCP server on npm, Chrome extension) before the PH attempt, not as parallel bets. Spend 14 days cross-commenting on PH before the launch. Profile recognition compounds — even 30 days isn't too much.
And never run the full playbook on the retry. Doing less, not more, is the move. The first launch revealed which channel actually worked. Doubling down on that one thing instead of running the full playbook again is how you compound the signal instead of diluting it.
The numbers, again
- PH: 0 votes, 0 comments, not featured, 1 real subscriber after filtering testers/bots
- Discord MCP angle: 3 confirmed installs from one message, ~3:1 vs dashboard
- Reddit pre-launch BIP threads: 740 combined views, 10 substantive comments
- IH post-mortem: 15 upvotes, ~30 commenters, the most useful distribution data I've gotten in 11 days of building
The willingness to publish zeros is rarer than it should be. It's also the thing that turns a failed launch into a credibility asset.
If you want the raw thread that produced these lessons, it lives at indiehackers.com — search for "What worked and what didn't — Sunday PH launch with zero email list."
The product is at signals.gitdealflow.com. The MCP server is npx @gitdealflow/mcp-signal. The methodology paper is at ssrn.com/abstract=6606558. All free.
The launch was one bet of seven I'm running this week. The post-mortem turned into the eighth.
Top comments (0)