I have seen a lot of people post on here purely for engagement, likes and followers. Is that actually necessary to get legitimate feedback on a release, or am I just feeding the algorithm what it wants?

Hi everyone,

I recently launched my first SaaS and I'm trying to learn the best way to collect meaningful user feedback during the first few weeks.

I'm curious:

• What channels have worked best for you?

• How do you prioritize feature requests?

• What mistakes should first-time founders avoid after launch?

I'd love to hear your experiences. Thanks!

Isme tum apne product ka naam zarurat padne par discussion ke context me mention kar sakte ho, lekin focus question par hona chahiye, promotion par nahi.

I've been working on ReadymadeUI for the past 3 years. It has organic traffic, an established developer audience, and premium templates.

Lately I haven't had enough time to maintain it, so I'm thinking about selling it to someone who can keep growing it.

If you've been through this before, where did you find buyers? Any advice would be really helpful.

I run three businesses and for a long time I assumed the big decisions were the risky ones. The one that actually cost me was small, a supplier invoice I meant to double check and kept pushing to tomorrow, and by the time I noticed the error it had already gone through two billing cycles. Nothing about it looked urgent in the moment. No fire, no message marked important, just quiet until it was expensive.

Curious what your version of that was, the small thing nobody in the moment would have called risky, and whether you changed anything afterward or just started worrying about the next quiet one.

While building an AI-powered product, I quickly realized that adding an AI feature isn't just a question of whether it works-

that's also the question of whether it makes sense to run it every time.

some AI features can genuinely improve the experience, but using AI too frequently can make the product unnecessarily expensive, especially when you're still building and don't have predictable usage.

For other makers building AI products, how have you balanced useful AI functionality with API costs?

I work closely with product and growth teams, and one challenge I keep running into is explaining user drop-offs to people who aren t deep into analytics.

The data usually shows where users leave, but turning that into a clear, confident explanation without overloading dashboards or making assumptions can be tough. Especially when the audience is leadership or business stakeholders.

I m curious how others handle this in practice:

Most mornings I open my laptop and go straight to whichever inbox feels loudest, a client email, a staffing text, an alert from whichever business had a problem yesterday. It is rarely the thing that actually matters most that day, it is just the thing that shouted first.

I started keeping a note of what I checked first for two weeks. Out of ten mornings, the first thing I looked at was the actual priority only three times. The other seven were just noise wearing a priority's clothes.

I found one this morning, a reply I owed a client since last Tuesday, sitting three notifications deep between two things that felt louder. Nothing about it looked urgent when it arrived. It just sat there while everything else took the seat marked urgent first. Curious what yours is, the one you know about, have not done, and keep telling yourself you will get to today.

Been working on launches for a while now and noticed people underestimate this angle.

A few things that actually work:

Investors browse PH. More than founders realize. A strong launch = visibility in rooms.

Top launch page = pitch deck material. It's third-party proof that real people showed up and cared, commneted and reviewed + team worked well. That belongs in a deck.