PH Radar BI is now live.

by

What started as a Product Hunt companion has become a BI layer for launches.

Custom dashboards, momentum, opportunity radar, hunter analytics, repeat launches, race replay, maker responsiveness — and more.

Special thanks to and everyone in this forum whose feedback shaped a lot of this — repeat launches and the responsiveness signal came straight out of conversations here. (The responsiveness metric even caught a question I'd missed on my own launch.)

What's still missing? If you could add one metric to Product Hunt itself, what would it be?

25 views

Add a comment

Replies

Best

@m_m_carvalho Congrats on shipping it, and the thanks runs both ways. That back and forth sharpened how I think about what a launch actually signals.

One metric PH itself is missing: survival. Does the product still have a live site and a shipped update ninety days after launch day? Most launches are dead links within months, but the leaderboard treats day one as the whole story. A simple still alive at 90 days marker would tell people which launches became real products and which were launch day theatre. It is the one number that separates a milestone from a tombstone, and PH already holds the data to compute it.

  Oshenye

You nailed it. That's exactly the gap—PH celebrates day 1, but the real metric is day 90.

We're adding this to PH Radar PRO: Product Longevity

How it works:

- Automatic crawler checks if the product's site is still live

- Detects recent updates (changelog, blog, public commits, social activity)

- Badges: "Still Active", "90-day Survivor", "Recently Updated"

- Historical view: track which launches became real products vs which were theater

The insight you pointed out sharpens everything. Launch signals don't mean much

without the follow-through metric. A product that ships updates 90 days later

tells a different story than the rank ever could.

Thanks for the back-and-forth—it pushed us to build something that actually

separates signal from noise.

Launching in the next release.

Live on Chrome + Firefox — free to explore. Link: Happy to break down how any metric is computed.

This is the right build, and the badges are clean. One trap to design around before it ships: absence of a detected update is not evidence of death.

Plenty of real products sit on a static marketing page with no blog, no changelog and no public commits, yet ship constantly behind a login. If the crawler reads silence as decay, your most heads down builders get punished for not performing in public. I would keep site is live as the hard binary and treat recent updates as a positive signal that adds confidence, never a negative one that revokes it. A live site with no visible changelog is unknown, not dead.

Two edge cases worth handling early. A domain or brand change reads as a dead link but is often a pivot that worked, so a rename is not a death. And a parked or expired domain should score differently from a 200 that still serves the product. Get those right and the 90 day survivor badge becomes a number people actually trust. Good to see it going in.