Early on, we treated every user request like an urgent priority, only to realize later that custom features didn't even stop those users from churning. Building what people ask for instead of solving their actual root problem destroyed our focus and wasted months of dev time. If you run a small product team, what framework do you use to filter out isolated demands and keep your core vision intact?

In our early days, we built every single feature requested by our first 50 vocal users. We thought we were being super responsive and customer centric.

Turns out, we built a Franken app. Those exact users ended up leaving anyway because the core workflow got cluttered with niche requests that nobody else cared about.

How do you filter out the noise of loud feature requests without ignoring genuine product gaps?

Not a slow realization, an actual moment. Mine was a weekend away with no laptop, and by Monday there were three things that only I knew how to answer, a pricing question, a scheduling conflict, and a client who wanted to know why nobody had followed up. None of it was an emergency on its own. All of it together made me realize the business was running on what was in my head, not on anything anyone else could pick up. Curious if there was a specific day that did it for you, or if it built up slowly until you just could not ignore it anymore.

My friend launched his tool a few weeks back and texted me at like 7am saying he was already awake refreshing the page. I checked in around noon and he hadn't eaten, hadn't left his desk, just kept switching between the upvote count, the comments, and Twitter mentions on repeat.

At one point the ranking dropped two spots and he called me convinced something had gone wrong, even though the actual upvote count was still going up. I tried telling him the number going down for a second didn't mean much, but it didn't really land in the moment.

What got me was that he barely replied to half the comments people left, because he was too busy watching the count instead of talking to the people leaving it. Told me afterward that the conversations he did have were the part that actually mattered, way more than where he landed on the board, but he only realized that after the day was basically over.

I haven't launched anything myself yet, so I don't know if this is just how day one always goes or if he made it harder on himself than it needed to be.
For people who've actually done this, is the refreshing and spiraling pretty universal, or is there something you did differently that kept you sane?
And for anyone else who hasn't launched yet either, does hearing this make you more nervous about your own launch day, or does knowing it happens to almost everyone take some of the pressure off?

We used to let people use the core function without an account at all. Turn up, get a result, leave. This week we put a free account in front of it. Same allowance, same features, no card but you sign up before you get anything. The reasons were boring and real: we couldn't attribute anything to anyone couldn't tell a returning person from a new one, and an anonymous endpoint that costs money per call was an abuse problem we'd have to solve eventually. What we didn't think through is what to say about it. The people affected are almost by definition people we can't contact. They never gave us an email. That was the whole point of the thing we removed. Every draft announcement reads either defensive or like we're dressing it up as a feature. How do you communicate a change that is genuinely worse for some users without it sounding like spin?

Someone used our product for about five minutes and wrote a short, calm message explaining what they were trying to do and why our approach didn't fit. No feature request, no complaint, no suggestion. Just a clear "not a match." It did more for our direction than a year of "looks cool" and "nice idea." It made us realize we'd been sanding the product down to accommodate people who were never going to stay, while the people who actually needed it got a diluted version. The rejection was honest, and honesty is rarer than praise. How do you tell the difference between a user who's wrong for the product and a user who's telling you the product is wrong?

I use AI every day as a Product and UX/UI Designer, and it saves me hours every week. But sometimes I spend 20 minutes trying to get AI to do something I could finish manually in 5. I am sure every profession has tasks like this.

What is that one task in your workflow where AI is still slower than doing it yourself?

We simplified a setup flow that used to take about ten minutes of configuration. Fewer options, fewer decisions, faster to the first result. A group of experienced users pushed back hard. They said the product now felt like it didn't trust them that the old settings were how they'd made it fit their actual job and that "simple" meant "generic." We'd optimized for the person starting and accidentally made the product worse for the person staying. The simplification was real but so was their loss. How do you decide when to simplify for new users without stripping away the control that keeps the experienced ones around?

Dragging a dead project along for months just because you've already put so much time into it is a terrible feeling. I've been there you know deep down after month two that the idea has no traction but you keep writing code every night just to avoid admitting it failed.

Deleting that repository hits hard because it feels like throwing away all those late nights.

Looking back what was the exact sign that made you finally kill your project instead of pushing through?

There is a massive trap when you first start vibe coding where you end up overbuilding features just because the AI makes it ridiculously fast to spin them up.

You spend days adding things nobody asked for only to realize the real bottleneck is maintenance API costs and actually getting people to care.

Shipping the app to the App Store turned out to be the easy part compared to distribution. If you ve built something using AI tools recently what is one thing you wish someone had warned you about before you started?