I do go-to-market for a product where the customer is a founder, and I keep running into the same wall.
Founders can smell marketing from a mile away. They've written the same emails, run the same ads, built the same funnels. So the usual playbook lands flat. Anything that sounds like copy gets skipped. Anything that sounds too clever gets skipped faster.
What seems to work better is being specific and slightly boring. Less "transform your fundraise," more "here is the exact thing this does and here is what it doesn't do."
But I'm not sure if that's a real insight or just the one thing that happened to work for us.
I have seen multiple launches here (on PH) providing AI solutions to the student exam preparations (and its really helpful). Students can now find fast and simple solutions to their problems or study plans as AI helps them fast and easily. They can now study anytime, anywhere, with no need for anyone's time (24/7 available).
But everyone has its own +ve & -ve thoughts in an easy way (suggestions/improvements) so what are your thoughts about it?
While building an AI coach, we ran into an interesting problem: memory is useful, but some things shouldn t just be remembered - they should become rules.
If someone says, avoid overhead pressing, asking for a harder workout later shouldn t erase that constraint.
It made me wonder: what information in your AI product should survive every follow-up, no matter what?
Hey Product Hunt! I'm launching today, and I've been collecting the questions business owners say they wish they could just ask their own business and get a straight answer.
I've been wondering how other founders navigate this.
When you're building enterprise software, potential customers may expect security audits, SOC 2 reports, penetration testing, and extensive documentation before they're comfortable using your product.
But for a bootstrapped founder, those things can require significant money before you've earned your first dollar.
It feels like a difficult cycle: you need customers to fund security and compliance, but you need security and compliance to get customers.
Users of a focused tool naturally ask for the next thing next door and often they already have the data in your product to do it. Saying yes feels like listening. Saying yes ten times is how a sharp tool becomes a bloated one that does everything adequately and nothing well.
The tempting version is when the adjacent feature uses the exact data the user already entered, to answer the very next question they were about to ask elsewhere. That feels less like creep and more like finishing the job. But that is also what every scope-creep decision feels like from the inside.
I think having more tools to build with can make it harder to be honest with ourselves about an idea.
When something is difficult to build, the effort itself forces you to think carefully about whether it s worth pursuing. But when changes take minutes instead of days, it s tempting to keep experimenting just because you can.
Not every unfinished project needs another attempt, and not every rough idea needs to become a product.
I m curious whether the real challenge now is less about execution and more about choosing what deserves our attention in the first place.
First post here. Been browsing Product Hunt for a while without an account and finally made one.
Honest question about my own behavior. I upvote things way more than I try them. Something looks interesting, I hit the arrow, feel like I participated, and move on. I couldn't tell you the last thing I upvoted and then actually signed up for.
It's not that upvoting is bad. It's just that it's become this frictionless thing I do while scrolling, and it has almost nothing to do with whether I'd use the product. Which makes me wonder what the upvote even means to me at this point.
Do you upvote things you'd actually use, or do you upvote to signal "this looks cool" and move on? And has anyone here found a product because of the upvote count specifically, or do you ignore the numbers entirely?
