Connect with the Product Hunt community

We used to blame our UI or missing integrations every time a paid account downgraded. But after jumping on exit calls, a harsh truth came up: the product worked fine but it forced teams to completely upend their daily routines just to use it.

Throwing more features at a workflow mismatch is just building debt.

For those who've tackled this: how did you redesign onboarding to match your users' natural habits instead of fighting them?

In the early days, every new account felt like a major milestone. But once revenue kicked in, watching an active subscriber downgrade or cancel stings far worse than a visitor bouncing from the landing page.

Digging into exit surveys, churn rarely happens because of bugs or missing features. Users leave simply because the product hasn't become a daily habit.

Does the anxiety around churn ever actually go away, or does the feedback loop just become second nature?

I spent a year trying to get better at things I was bad at. Systems, processes, consistency.

I improved slightly. Not enough to matter. And in that year, the things I was naturally good at got a little rusty because I wasn't using them.

Aura farming is the deliberate curation of one's image to build social capital. A calculated gym video. A well-timed silence. An aesthetic grid. It all counts.

I've been noticing how this plays out in founder culture. The "just shipped this" post with the perfectly messy desk in the background. The "here's what I learned from failing" essay that conveniently skips the part where they had a safety net. The "I work 4 hours a day" humble-brag.

It's not lying exactly. It's just... curated. Strategic. Designed to build a certain perception.

And I catch myself doing it too. Every post I write, I'm thinking about how it'll land. What it says about me. Whether it adds to the aura or subtracts from it.

During the year of our business I answered all the support emails myself. It was hard. I did not like it. Looking back it was the important thing we did and I almost handed it over too soon.

Analytics showed which buttons were pressed. The inbox showed which actions users wanted. These are two types of information. One day a user wrote: "I expected the export button to send the report to my accountant." Our button saved a file. No one would have ever noticed this difference in the funnel chart;. In the next month three other users had the same issue. We added an email button. The problem went away.

Now I keep a spreadsheet with four columns. The words that the person uses the screen they were on what they were hoping for and what actually happened. Patterns start to appear after forty entries. It is important to write down the words since they will become your landing page copy and button labels.

There is a risk. Support emails are more likely to come from customers and less likely from happy quiet ones. That feature no one ever asks about could be the thing that keeps everyone coming which is why I look at the email box along with the retention numbers not instead of them.

Product Hunt newsletters have taken on two different pacing schedules. The Leaderboard is on weekdays, and The Roundup comes on Sundays. I subscribe to both of them, but my reading behavior ended up being something I had not anticipated.

The Leaderboard can be read alongside my cup of coffee on weekdays and I generally remember at least one of those products by the time lunch rolls around. The Roundup is longer and so I just skim through it.

A friend who had never coded anything in their life asked me last week how to begin working with AI tools. I did not seem to have an easy answer to that, so I am trying to come up with one.

I would recommend taking a problem which you have yourself, but making it small enough to solve it within one day. Packing list, plant tracker, or bus schedule page for today only.

When churn started ticking up, our immediate reflex was to poll canceling users and build whatever feature they asked for next. Unsurprisingly, it didn t move the retention needle at all.

They weren't leaving because of a missing button; they a missing button they were leaving the core loop felt like extra homework on top of their existing stack.

How do you separate genuine product gaps from fundamental friction when diagnosing why paid users slip away?

I keep getting feature requests from people who want to use the product in a way I never intended. Not better versions of what it does completely different jobs. They want it to be more configurable, more customizable, more "just give me the building blocks and I'll figure it out."

Part of me wants to say yes to all of it. Flexibility widens the market, makes the product valuable to more people, and means I never have to turn a customer away. The more it can do, the harder it is to outgrow.

I m a product designer, and I m not sure what my job will look like in 3 years.

A couple of years ago, being good at Figma, understanding UX patterns, and building clean interfaces felt like a pretty solid skill set.

Now AI can generate decent-looking screens in minutes. And it s getting better at the things designers used to spend hours doing.

I don t think designers are going to disappear. But I d be lying if I said I wasn t thinking about what makes us valuable anymore.

I've been building a SaaS with Lovable + Supabase that handles pretty sensitive stuff bank data via Open Banking, tax-related info. It's still in beta with very few users, but I want to get security right before opening it up more.

I know the basics (HTTPS, not exposing API keys in the frontend), but I'm not confident I've covered what actually matters for something handling financial/tax data.

For anyone who's dealt with this:

What would you consider the absolute minimum before letting real users connect their bank accounts to something you built solo?

We keep a human in the loop for safety. It s the standard line during demos, and on paper, it makes total sense.

But in practice, human review quickly becomes the bottleneck. If someone has to check every step or approve every small update, the speed advantage vanishes. Worse, alert fatigue sets in people stop reading traces and just start blindly clicking "Approve."

When evaluating HITL setups now, my test is simple: Can someone make a confident decision in under 3 seconds?

If reviewing takes as long as doing the task manually, the agent isn't saving time it s just turning real work into an auditing job.

There is a weird kind of numbness that sets in after you ship a few projects. You get your deployment pipeline dialed in you avoid the major bugs, you get a predictable handful of users and... you just feel completely blank. You stop taking creative risks because playing it safe becomes a comfortable habit. The emotional highs and lows fade away, and suddenly work feels more like ticking boxes on a spreadsheet than creating something cool.

Did you notice your own enthusiasm flatlining as your processes got more organized?

We spend so much energy trying to remove all the stress and uncertainty from launching that we end up killing the fun along with the bugs.

I realized recently that I planned every single detail of our last release so carefully that there was zero room left for surprise or joy. Everything went right, but it felt hollow because there was no skin in the game.

I ve been working on SEO and website optimisation for e-commerce stores, and one thing I keep thinking about is the relationship between getting visitors to a website and helping them find what they actually need.

There are plenty of discussions about rankings, keywords, backlinks, and content. But once someone lands on a store, the experience itself matters too.

For example, a customer might search for a specific product using a term that doesn't match the wording used in the store's categories. If the navigation, filters, or product descriptions aren't clear, that customer may leave even if the website ranks well.

I m interested in how other people approach this problem, particularly on stores with large catalogues or products from multiple categories.

We had a live support widget on our landing page, thinking instant replies would build trust and close more sales. Instead, sales calls were cluttered with basic, repetitive questions.

We removed the live chat widget and invested that effort into a clear, searchable FAQ and interactive demo video.

Qualified leads increased because users actually spent time reading the offer instead of relying on chat support to explain basic details.

It turns out immediate chat support was becoming a crutch that prevented buyers from truly understanding the product.

We spent months setting up a private community, posting daily updates, and hosting discussions to drive organic acquisition. While the community members are super engaged, we looked at our attribution data and realized it brought in almost zero paying customers.

It made me realize there s a big difference between building a loyal audience and building a revenue channel.

How do you measure the actual ROI of community building, or is it mostly a long-term brand play for you?

My Downloads folder has slowly turned into a mix of PDFs screenshots installers and random files I only needed once. I keep meaning to clean it up but doing it manually every few days gets annoying. I d rather not pay for another cleanup app just for this. Are you using any built-in rules shortcuts or simple folder setup to automatically deal with old files?

I used to fall into that exact loop arguing with an LLM for half an hour over a broken function pasting error logs back and forth like it was going to magically figure it out.

Total waste of time. The moment I actually drop a breakpoint or check the browser console I usually spot the stupid typo in two minutes. AI is great for scaffolding code but it's terrible at blind guessing.

The check is: count today s rows for this user, and if the count is under the limit, run the call and insert a row. That works for one request at a time. If a client sends 10 requests at once, all 10 can read count = 2 before any of them insert, so all 10 pass.

On serverless, this gets worse, because an in-memory counter doesn t help. Each request may run in a different instance with its own memory.

The fixes I m weighing, all in the database:

• A unique constraint on (user, day, slot number). Each request claims the next slot, and a duplicate insert fails. It s simple, but I need to handle the retry.

• An atomic counter. One SQL statement increments a per-user-per-day counter and returns the new value, and the request is rejected if it s over the limit. There s no gap between checking and counting.

• An external store like Redis. It s fast, but it s one more service for a small stack.

We launched Nimply (AI agents that draft social media replies and posts; you approve before anything goes out) on 23 Sep. Here is what the 24 hours actually looked like, with numbers, because most launch retros only show the wins.

Numbers

- 31 points, 20 comments, 5 reviews.

My feed was full of "passive income" gurus, so I jumped in. I spent weeks designing logos, tweaking my website, picking colors, and building a fancy brand identity for a new project.

I felt like a real founder. But when I looked at my actual income, 90% of my earnings came from one basic thing: reaching out directly to people, listening to their problems, and offering to help.

The beautiful website didn't make me a dollar. I wasn't building because customers were begging for my product; I was playing business because I wanted to feel productive.

That lesson stuck with me. Now, before I spend a single hour on branding or tech, I ask: "Can I get one paying customer for this idea today using just a simple message?" If I can't, I don't build it.

We promised direct, instant 24/7 founder-led support to every new customer to stand out from larger competitors. At first, customers loved the personal attention, and our retention rates were higher than ever.

But as our user base grew, this turned into a constant stress point. Our team is now overwhelmed by midnight support tickets, resolving minor edge cases, and hand-holding users through basic onboarding. As a result, zero time is left for high-level strategy, product improvements, or scaling our marketing.

It made me realize that over-servicing customers early on builds unsustainable expectations that break the moment you try to grow.

Have you ever over-indexed on manual customer support, and how did you transition to automated or self-serve systems without upsetting your early users?

People talk about churn like it's just a cold spreadsheet number, but every single cancellation email still feels like a personal rejection.

Even when you look at the exit charts and realize they just weren't a good workflow fit it's hard not to take it personally after pouring months of work into the product. You tell yourself you'll get used to it but seeing someone downgrade or leave still stings.

For those of you who have been building for years does that feeling eventually fade, or do you just learn to deal with it quietly?

We spent way too much time tweaking our dashboard metrics and digging through cancellation feedback trying to find the exact reason someone left.

Sometimes users don't even know why they churned they just realized the tool didn't become part of their daily routine. Fixing that habit loop and workflow fit is infinitely harder than writing new code or shipping flashy features.

When someone cancels on you now do you spend hours analyzing their exit reason, or do you just focus on the active users who are actually sticking around?