Every launch guide says the same thing: go live at 12:01 AM Pacific so you get the full 24-hour window. But I've now watched enough launches to suspect that's a leftover from an older version of the platform, and that the algorithm and the audience have both changed.
What I actually observe: the first few hours are dominated by people in a similar timezone, most upvotes come from a few concentrated windows during the day, and a late-afternoon launch with a strong push can outperform a midnight launch with a weak one.
But I don't have real data I have vibes and a handful of launch pages I've stared at.
So: if you've launched more than once at different times, did the time actually move the outcome, or did the audience and prep dominate everything? And has anyone seen a launch succeed that went live at, say, 9 AM Pacific? I'm looking for counterexamples specifically.
Over the past few days, you may have noticed a new account on Product Hunt called "Curious Kitty" commenting on some launch posts. It was created on 20th December 2025.
First observation: it behaves like a bot. It only asks questions (no opinions, no praise, no criticism) and those comments get visually highlighted, similar to how awarded comments stand out on Reddit. (screenshot attached)
Exciting news, makers, we are hosting our first ever virtual summit this July and I would love to see you there! You can register for free here. Expect to hear from amazing individuals from the Product Hunt network: founders, investors, indie makers and individuals on the rise in their fields: from D2C to no code to blockchain and so much more. I'm in the process of inviting speakers and would love to hear from you - who do you want to hear from at the summit? What topics do you want us to cover?
I see a lot of "raise your prices" advice, and I mostly agree with it, but I think it's hiding a harder question: sometimes raising prices is the right move, and sometimes it's a way of avoiding the fact that your positioning is wrong and churn is telling you so.
The distinction I'm trying to draw: raising prices to capture value you're already delivering is good. Raising prices to fix a conversion or retention problem is rearranging deck chairs.
The tell, I think, is whether your existing customers would pay the new price. If yes, you were underpriced. If no, you have a different problem.
Curious how others have told the difference especially anyone who raised prices and then realized the real issue was something else entirely.
I used to treat headlines as just a quick marketing task something you polish right before launch to make the site look pretty.
But recently, while trying to explain a simple feature on a landing page we realized we couldn't describe the core value in one plain sentence without making it sound vague.
Trying to write a clear headline forced us to admit that our feature wasn't actually solving the problem as simply as we thought. It completely changed what we ended up building next.
Have you ever had a moment where rewriting a single line of text exposed a massive gap in your actual product?
In my field (small B2B software), the common knowledge is "you need a sales team once you pass a certain revenue threshold." Everyone says it like it's physics. But the two most profitable small software companies I know personally have zero salespeople the founders just answer support tickets and the customers upsell themselves. Meanwhile the companies I've watched stall out all hired salespeople too early and then had to feed them deals that weren't ready.
I'm not saying sales teams are useless. I'm saying the threshold gets repeated as a law when it's actually a guess, and a lot of people make expensive hiring decisions based on a guess.
So what's the "everybody knows" thing in your field that you suspect is just inherited folklore? Bonus points if you've actually tested it and been wrong either way I'm more interested in the people who believed the common knowledge, tested it, and found out it was right after all.
I was thinking about how annoying traditional sign-up forms are with all the CAPTCHAs and email verification steps. If an AI assistant is trying to set up a service for its owner our current onboarding flows completely block it. Allowing bots to auto-create accounts sounds like a fraud nightmare but forcing a human to manually type in details feels outdated.
I'm leaning toward letting the AI fill out all the fields while keeping just one single click for the human to approve everything.
How are you handling this in your own apps are you keeping sign-ups strictly human, or opening the door for agents?
I am working for a 20-person startup. @Linear is our product development system, which we really enjoy.
Currently, our operations team receives support requests via their personal email and then publishes requests in the Slack channel, where developers are picking up issues, but we would like to upgrade to a more comprehensive system with a shared inbox. I would like it to have an integration with Linear, and the ticket creation to be automated as much as possible. It would be great to have a help center (documentation), too, as a part of the offering.