Launch Diary · Published 2026-05-02
A Sunday launch with no email list. Anonymous handle. Editorial did not feature it. Five other products in the same 07:01:00Z batch were featured. This one was not. What follows is the honest version of what happened and what the comments on the Indie Hackers post-mortem taught me about distribution.
The two journeys
External journey: I went from a developer who occasionally wrote angel checks and kept losing deals to better-networked investors, to running a read-only data tool that any developer-investor can use to spot the same patterns weeks before AngelList does. The tool exists because I wrote it for myself first and stayed disciplined about not turning it into a startup-pitch dashboard.
Internal journey: I stopped trying to network my way into deals and started reading commit graphs the way quant funds read SEC filings. The shift wasn’t learning a new skill — it was accepting that the edge I was looking for was already public, already free, already updating every fifteen minutes, and that nobody else was watching it because nobody had bothered to package it for an investor audience. The product is a side-effect of that internal shift. Most of the work on this site is me trying to share the shift, not the tool.
If the internal journey lands for you — if you read commit graphs and feel like the consensus deal-flow tools are reading the wrong column — the rest of this site (the Perfect Webinar, the avatar quiz, the six tiers) is the operational version of this paragraph.
Product Hunt: 0 votes, 0 comments at T+8h. Not featured.
Email list at launch: 1 real subscriber after filtering testers and verified-disposable bots.
Telegram channel at launch: 1 subscriber. Skipped any send activity.
Discord, MCP angle: 3 confirmed installs from one message across Cursor, MCP Community, and Vercel forum servers. Roughly 3:1 vs the dashboard push.
Reddit pre-launch build-in-public threads: 9 + 1 substantive comments and 564 + 176 views by Sunday evening.
Indie Hackers post-mortem the same evening: 15 upvotes, ~30 substantive commenters. The most useful distribution data of the entire week.
The free MCP server converted at roughly 3:1 against the broad PH push. 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 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.”
— ReleaseLog, on the Indie Hackers post-mortem
Product Hunt stripped public upvoter lists in 2022. The most-shared launch guides still reference upvoter mining, hunter-follower counts as the main lever, and batch-with-big-names timing. The tactics look reasonable until you check when the post was written.
“The half-life of bad advice on these platforms is approximately forever. Nobody retracts a 2021 tweet when the algorithm changes in 2022. Post-mortems beat playbooks for exactly that reason.”
— epopteia, on the Indie Hackers post-mortem
Nineteen substantive comments on other Product Hunt launches in the two weeks before mine drove most of the profile clicks the launch generated. Nobody checks your profile when you post. They check it when they are deciding whether to upvote.
“'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. The listing got people to click; the history got them to trust.”
— HarborPointPress, on the Indie Hackers post-mortem
The healthiest reframe of the entire thread. The spike model is dead unless you already have an audience. The page exists. New content all points at the existing PH page and lets it accrete backlinks. Distribution is upstream of the launch and sustained over months, not concentrated on one day.
“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. The better play: leave the page alone, point all new content at it as the canonical hub, and let it accrete backlinks.”
— davidamoroso, on the Indie Hackers post-mortem
Anonymous handle, no LinkedIn personal, no IRL conversations about the product. All deliberate calls. Editorial filter for B2B is rational about this: an anonymous handle with zero network history is an accurate signal that the buyer cannot yet verify who is curating the data.
“PH editorial didn't just reject a product. It rejected a B2B product without B2B trust signals. The same product with a named founder, a LinkedIn with 500+ connections, or a single reference customer would have passed a different filter even with identical completeness. This reframes the relist strategy: the SSRN paper isn't just a new hook, it's a trust signal that compensates for the anonymity gap.”
— aegiswizard, on the Indie Hackers post-mortem
Friday relist held. The original PH page is the canonical hub. Re-listing without resolving the editorial issue would just produce a second silence. Every new content surface (this story, the SSRN paper, the MCP server) points at the existing page.
MCP angle is now the lead. Show HN with the free MCP install as the lead next week. The dashboard becomes the upgrade path, not the hook.
Methodology paper as the credibility anchor. Lead with the paper, follow with the technical install, list the product last. Buyers de-anonymize in stages: academic credential, technical try, product commitment. The order matters.
Post-mortems are the distribution. The willingness to publish zeros turned a failed launch into a credibility asset that the polished launch could not have produced. This page exists because of that.
Methodology →
The full signal definition and the 47-day median lead-time analysis. SSRN paper linked from here.
Research →
Thirty research findings cited from the SSRN paper. Read them free, no sign-up.
Install (MCP) →
npx @gitdealflow/mcp-signal. Five free tools, runs in Cursor or Claude Desktop. Ten minutes from install to first signal.
Predict →
The forward-looking prediction game. Call whether a startup raises a Series A in six months. Public leaderboard.
Receipts →
The backwards-looking version. Paste your GitHub username, see which unicorns you starred early.
Citations →
Cross-graph map of every external citation, dataset mirror, and academic index this product appears in.
The launch was one bet of seven this week. The post-mortem turned into the eighth. The next surfaces are the dev.to long-form, the Show HN with the MCP angle as the lead, and the Reddit follow-ups in the same subreddits where the build-in-public threads already live.
None of these will produce a featured Product Hunt placement. None of them need to. The distribution that actually works for this product is sustained over months and lives upstream of any single launch day.
The MCP install was the conversion the launch could not produce. Ten minutes from install to first signal. Free. No sign-up. Works in Cursor, Claude Desktop, or any MCP-compatible client.
npx @gitdealflow/mcp-signalInstall instructions →