I always thought that the common answer to agent permissions is to let the agent act on anything you can undo and request only for crucial part. Sending a customer a messages usually would count as the thing you can't take back I guess.

I'm not sure that line holds for product decisions. In a past project, an agent just changed something that was easy to revert. But if we hadn't noticed, it could have set off a chain of follow-up actions that caused us big trouble under their own understanding. Another instance, when the AI agent marks a customer request as "planned." instead of Notice. It would be great if we found the issue early on, but if not, we might have missed this request

Meanwhile asking for approval with every changes would make things more secure, but when there are too many requests, I notice that people start approving without reading.

For people using agents around product decisions:

As builders, we often focus on creating features, improving design, and fixing problems.

But before someone uses a product, there is another challenge:

Trust.

People need to understand:

We shipped our product a few weeks ago, and while my co-founders have their maker tags visible next to their profile names my account still looks completely standard.

I've double-checked my team settings and maker status, but nothing updates on the public profile.

Is there a hidden setting or a specific admin approval step I missed to get the badge to appear?

We want to hear from you

It s that time of year we ask for your honest feedback on how we re doing. Positive or negative, your responses matter to us. As a way to say thank you for your time, we will be giving out a $50 gift card to a lucky winner. Click here to take our community survey.

Ads so easy even a caveman could do it.

If you tried to run a self-service ad in the past, you may have felt like you were drowning in a sea of next steps. It s much easier now. Go to producthunt.com/ads/new, select your launch, and your product is back on the leaderboard and other high-traffic areas on our site, extension, and app in a few simple steps. You re like, so self-sufficient now.

When you live inside your own product every single day, you forget what it's like to see it with fresh eyes. Every button, label, and navigation menu feels completely obvious to you.

Then we watched session recordings of our first few real signups. It was painful. Users were getting completely stuck on things we assumed were intuitive, dropping off before they even touched our primary feature.

For builders and indie hackers: what methods or tools finally opened your eyes to your own onboarding blind spots?

I've been delaying a price hike for months out of fear of mass churn. We finally decided to bump our rates by 30% and gave current users a two month grace period before the change kicks in. We sent a simple direct email explaining that our server costs went up and surprisingly not a single person canceled.

But now I'm wondering if giving people a two month window just leaves the door open for them to shop around for alternatives.

When you bumped your pricing how long of a buffer did you give existing clients?

Hi.

On many accounts in forum i can see badge with relation to their product. I would to configure my account in same way. Product was launched moth ago, i am assigned as maker, but still i only see my account name.
How can i change it?

In the beginning, we focused heavily on smoothing out our signup flow, and activation rates looked great. But a few weeks in, we realized users were dropping off right after completing onboarding.

Getting users to see the initial value is one thing, but keeping them coming back to perform managing early retention: what onboarding or product changes made the biggest difference in turning initial activation into a daily or weekly habit?

When a customer who pays your bills asks for a custom feature, saying no feels almost impossible. But we learned the hard way that building every single request turned our app into a bloated mess of half-baked tools. Most requests are just users trying to patch over a workflow problem they don't know how to explain yet. How do you tell high-value clients that their requested feature isn't on the roadmap without completely ruining the relationship?