I've seen client sign-offs get lost in long email chains, where nobody is sure which version was approved or what the last round of feedback was. What helped me most was keeping one place per project where the deliverable, the comments and the final approval all live together. I'm curious how others do it. What tools or process do you use for sign-offs, and how do you stop feedback from dragging on for weeks?
I deleted something last year. Took it out of the product entirely, removed the menu item, wrote a short note explaining why, and braced for the complaints.
They never came. What came instead was a slow trickle of messages from people saying the product finally felt clear.
We learned this the hard way after spending weeks building a complex integration that our most active, non-paying community members kept asking for.
Once it shipped, none of them actually used it while our paying subscribers were quietly dealing with basic bugs we hadn't fixed yet. It's so easy to get distracted by loud voices on forums who want everything for free but at the end of the day paying customers have totally different priorities.
How do you decide whose feedback actually makes it onto your product roadmap?
Curious what the community is running for authentication/authorization in their apps (e.g. Auth0, Supabase Auth, Clerk, Firebase Auth, Cognito, etc.)
A few things I'd love to hear your take on:
What provider are you using and what's your primary stack? (e.g. Next.js + Clerk, Go + Auth0, etc.)
What's the one thing that surprised you , good or bad ?
Would you make the same call today? Especially curious if you've hit scaling pain.
For context: I'm building a B2C application with my own database layer, and currently in the process of evaluating which authentication provider best fits the architecture. Trying to understand how others are handling the auth <> database relationship and what influenced your final decision.
We learned this the hard way after watching people spend hours setting up complex dashboards inviting team members and clicking every single button during their trial only to ghost us on day 14.
Meanwhile, a few quiet users who logged in twice, set up one core thing, and stayed silent ended up converting with zero hesitation. Activity volume doesn't always equal real intent.
If high usage isn't a reliable sign of a buyer what specific milestone or action do you actually look for during a trial?
I m not a professional copywriter. I use AI to draft emails, newsletters, and social media posts in seconds. It s a massive time-saver, but it has one quiet risk: it all starts sounding the same.
A few weeks ago, I sent out a feedback email generated by AI. It read smoothly and looked professional on the first read. A day later, a client replied saying, "Did an algorithm write this? It doesn't sound like you at all." The words were grammatically correct, but the soul and voice were completely missing.
It made me wonder if we are trading our authentic voice for robotic perfection just because the grammar is clean.
How do you check AI-written copy before hitting send? Do you rewrite sections manually, run it through humanizers, or just accept the generic tone? And has an AI-written message ever backfired on you because it lacked a personal touch?
I ve been curious to try an AI notetaking tool that doesn t loudly announce itself when joining a call and only shares the notes afterwards with me.
I guess this is starting to become more commonplace but it still feels (to me) like an intruder in the call, and like I should ask permission (just as when someone records the call - I m honestly not sure there is really any difference).
It's weird having a decent number of active users while having zero clue what your typical customer actually looks like. Some people log in every single day for work while others signed up months ago and completely vanished. Trying to build features for a mixed crowd like that makes roadmaping really tough because you can't please everyone at once.
If you've been through this stage, at what point did you decide to narrow down your target market instead of trying to appeal to everyone?
There's a big difference between a weakness that actively breaks your business and one that just makes you uncomfortable.
If your writing is terrible, that hurts your sales copy so you have to improve it enough to get by. But trying to turn a C-grade skill into an A-grade skill usually takes way too much effort for a tiny payout. I've had much better results doubling down on my core strengths while keeping my weaknesses just non fatal.
Where do you draw the line between a flaw you need to fix and one you can safely live with?
