As a small team, we need honest, targeted insights, but we haven t even set up a feedback loop yet. How can small teams get actionable feedback from potential customers without getting buried in vague comments?

I m curious:

• Have you found short surveys more effective than quick one-on-one calls or in-app prompts?

• What questions did you ask to cut through generic looks good replies and reveal real pain points?

• When did you first reach out right after signup, post-demo, or on a regular schedule and how often did you check in?

• Finally, what lightweight tools or simple templates made the process easy for your users and team?

Hi PH Community,

I'm currently building a health-focused platform where users are rewarded for taking care of their well-being. The idea is to create a positive feedback loop help people stay healthy while contributing to a larger ecosystem of wellness.

I'm working solo right now handling everything from development to outreach. Before this, I collaborated on a few other projects, but it s tough to find people who share the same level of commitment and vision.

Since most of my target audience is in the West and I m planning to incorporate the company in the US, I m looking for a potential co-founder based there someone who deeply resonates with the mission.

Hey planners, overthinkers, and goal-getters!

How many tabs are open in your brain right now?

(Ever feel like your to-do list is working against you? You re not alone. Between deadlines, shifting priorities, and that ever-growing I ll get to it later pile, staying organized can feel like a part-time job.)

What if you could hand that chaos to an AI that doesn t just spit out robotic schedules, but thinks like you ?

When ChatGPT was at the beginning, I and most of my colleagues used it as an enhancer for our work - mostly code and research - much like a person would use Google but more direct, saving time instead of browsing more websites. We'd have a question about our work and talked to an AI expert (that wasn't that good before) to find out the answer. No more, no less.

Today, I see a LOT of people writing entire apps, writing entire essays, university thesis paragraphs, marketing messages, emails and talking to AI non-stop while working, following it blindly at this point. The worst part: sometimes it takes way longer to repair/edit/debug/update what AI produces than would have taken to even learn to do the thing yourself.

When you can build faster than ever these days with AI, how does it affect your launch plans on PH?

The timescale between features is dropping as building is becoming easier. So I'm curious:

• Are you planning one big launch, or many smaller ones?

• When do you feel it s 'enough' to launch when expectations might be higher?

• Does AI change how you think about launch timing and feature scope?

For example, I've got this site waiting for a launch myself: https://feedbagel.com, but I don't know whether to hold off until adding the next part, or can we have multiple launches on here within a short time frame?

Hi everyone!

Just curious if you could reimagine a weather app from scratch, without following the "typical" designs we see today, what would you want to change or add?

For example:

• Would you want the app to feel more fun or even have a personality?

• Would you prefer faster voice updates instead of reading charts?

• Would it be helpful to get forecast reminders tied to your special events or big days?

Bringing a product to market as an indie hacker is no small feat but AI agents are changing the game. From marketing to operations, automation is making it easier (and faster) to launch and scale. Here are a few AI-powered tools I ve found useful:

Influencer Marketing Aha Ads (https://ads.ahaglobal.io)

Twitter Growth: Synthmind (https://ai.synthmind.app