Hey Product Hunt Community!

What s the single best piece of advice you d give to a new founder or early-stage team?

It could be about product, growth, funding, mindset - anything that made a difference for you or that you wish you knew sooner.

I feel like Im using Youtube more than anything else every single day. I want to learn some "hidden gems" channels, cause I feel I seen it all. Ideally channels around solopreneurship/indiehackers, 0$ marketing strategies, how-to-sell stuff fast, philosophy and economics. Here are my GO-TO channels that I watch almost daily:

• @Raoul Pal the Journey man (Macro investing in crypto)

• @Money ZG (macro investing in crypto)

• @Pursuit of Wonder (interesting concepts around societal psychology & philosophy)

• @Fireship - Tech edgelord (lol)

• @Greg Isenberg (Solopreneurship)

• @Starter Story (Solopreneurship, How to build and market apps)

What are yours?

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'm preparing for my first Product Hunt launch, and I've been trying to understand what actually makes the difference between a launch that gets some attention and one that reaches the top of the leaderboard.

There is a lot of advice online about launching on Product Hunt: building an audience beforehand, getting early supporters, posting at the right time, engaging with the community, getting comments, sharing on social media, etc.

But I'd rather hear from people who have actually done it.

Watched a product go from "hoping to get featured" this morning to #1 by this afternoon, and paid attention to what actually pulled people into the comments instead of just counting upvotes.

The single comment that got the most reaction wasn't a pitch. It was the founder admitting a real gap straight up, saying a part of the product wasn't built well yet. That pulled more replies than any feature announcement in the same thread.

Before launching a SaaS project, I spent a lot of time researching competitors. A few weeks later, product work took over and my notes were already outdated.

I m now trying to understand which changes are genuinely worth tracking. Daily alerts could become noise, while a weekly review might miss something urgent.

For founders who monitor competitors:

• Which changes have affected your pricing, positioning, or roadmap?

• How often do you review them?

• What did you stop tracking because it never helped you make a decision?

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?

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?

Whenever I use coding assistants to flesh out app features the generated screens end up looking mismatched. One page uses a custom table, while the next invents a totally different card wrapper or color shade.

Even when referencing component libraries, the assistant eventually ignores existing UI patterns and builds placeholder elements instead. Going through every route to manually clean up design inconsistencies takes up way too much dev time.

As users, we all want to try a product before committing. As builders, we want to show real value without over-engineering and investing time 'just for show'. Finding that balance is harder than it looks.

I just shipped my demo for Rewo (https://rewo.app), and intentionally went with a live, real demo:

• Fully functional product (same codebase as prod)

• Uses demo data instead of real integrations

• Some interfacing + sync pieces are disabled

• Auto-resets on a schedule so anyone can jump in fresh