“Not now” is too vague for product decisions
I ve started treating not now as three different decisions:
The evidence is too weak.
The problem matters, but the timing is wrong.
The idea conflicts with a choice already made.
They look identical in a backlog, but they deserve different revisits. The first needs research, the second a trigger date, and the third a deliberate re-open of the earlier trade-off.
How do you record deferred product decisions so future you can tell whether to investigate, schedule, or leave them closed?
How do you come up with names for your products?
How do you all come up with a name when you're launching something new?
For me naming is always the hardest part. I've named around 30 products so far and this is roughly my flow:
- One sentence on what the product actually does, not the feature list. Most of my names come out of that sentence
- Then names from anywhere. One of my apps basically stands in for you, so it became Kagemusha, a Japanese word for a double. Short, and no AI or Pro stuck on the end
Do you let your agent touch your database directly, or is that a hard no for you?
Been going back and forth on this. Right now my setup lets Claude Code run migrations and seed scripts directly against a local dev database, but I've kept it firewalled off from ever touching staging or prod, even read-only. Everything that reaches prod goes through a PR I review manually.
Saw a comment in another thread here about a subagent going off-script and targeting its own orchestrator, which made me second-guess even the local access I've been giving it.
Where does everyone else draw this line?
Is read-only prod access ever okay in your setup, or is that a line nobody here crosses?
And for the people who do give agents broader database access, what made you comfortable enough to do that?
What’s a feature users asked for that you ended up regretting?
I feel like a lot of product bloat starts with a request that seems totally reasonable in the moment.
Then it ships, and months later you realize it added more complexity than value more support, more exceptions, more maintenance, and one more thing the product has to carry forever.
Would love to hear examples from other builders. What s one request you wish you had handled differently?
What hiring mistakes do you wish you never made?
Have you ever regretted a hiring decision? How did you know they were a "bad" hire? Maybe you brought someone on full-time, part-time, or freelance, and things just didn t work out. That happened to me in a non-technical role. I believed hiring someone for marketing and public relations would boost sales, help grow the team, and build our brand. Instead, I ended up with someone who seemed perfect on paper but couldn t execute, which cost me more in both wages and lost revenue.
What I learned is that you need different questions to really understand someone s skills and experience. When I switched from asking traditional or situational questions to using behavioral interview questions, I made better hires.
Most founders have had someone on their team who didn t work out. What was yours? And how did you course correct?
Making a promo code redeem without kicking you out of the app
Small ship this week, but I sat on the why longer than the code.
I build an app people open in the hard ten minutes with a kid a tantrum, a bedtime that came apart. Whoever's using it is, by definition, not in a state to go spelunking through Settings. So Apple's standard path for redeeming a code always bugged me: copy it, leave the app, App Store tap your face Redeem Gift Card or Code, paste, switch back, hope it took. Fine for a productivity tool. For someone at the end of their rope, that's where you lose them.
Your 12-character password could take hours or years to crack — and you'll never know which
Most people know the rules: use a unique password for every service, make it long, don't reuse it anywhere. And yet almost nobody actually does this consistently not because they don't understand the risk, but because humans are fundamentally lazy and comfortable when it comes to security. It's not stupidity, it's just how we're wired: the effort of managing 40 different passwords feels real and immediate, while the risk of a breach feels abstract and distant.
There's also a quiet assumption a lot of people carry around without saying it out loud: "that happens to other people, not to me." Data breaches happen to companies, celebrities get hacked, someone else's crypto wallet gets drained never mind that statistically, reused or weak passwords are involved in the vast majority of account compromises. The moment it's framed as "yeah but that won't happen to me," all the rational advice about password hygiene just quietly gets ignored.
How are you using AI agents in your work or daily life?
I am curious to hear how people are using AI agents outside of programming. Are they helping you with personal tasks, productivity, research, or other areas? What tools or services are you using, or have you created your own? How have they impacted your day-to-day life? I would love to learn from your experiences and see the creative ways people are putting AI agents to work.
What I learned launching my solo SaaS on PH last week
Hey PH.
Launched Briefance here last week. Solo founder, Istanbul, no team, no investors. Wanted to share what actually happened instead of the usual "thank you so much" post.
Quick context: Briefance turns chaotic client emails into structured briefs. Freelancer target. Paste the mess, get scope, timeline, budget, and follow up questions in ten seconds. Free tier has 3 briefs, no card needed.
Here's what the launch week taught me.
Ready to launch, but what should I do first/next?
Hi everyone
I m new to Product Hunt and preparing for my first launch.
My product is ready to use, and I have prepared the website, screenshots, video, and other launch materials. However, I do not yet have an established audience or any users for the app as yet.
For makers who have launched here before, what would you recommend doing before choosing a launch date?