Connect with the Product Hunt community

Early on, I thought if users loved the product and gave great feedback, retention would take care of itself. But after sending our first renewal notices, the reality hit differently.

The hardest part was realizing that the end-user loving the product isn't enough. People are canceling not because they dislike the app, but because they can't quantitatively prove its ROI when budgets get tight.

For founders managing paid tiers: how do you adjust your product or messaging to help users clearly demonstrate value to their decision makers?

I've been thinking about a frustrating problem in agent development: when a run goes wrong, reproducing the failure isn't always straightforward.

You can save the conversation, but that doesn't necessarily preserve the tool responses, external state, or exact context that shaped each decision. Replay the run later, and the agent may take a completely different path.

Launched on PH today, yay! And I noticed my inbox got filled up with a lot of inbounds, all following the same script: "Congrats on the launch! Love what you've built. Have you considered also launching on [other platforms]?"

I appreciate being noticed, but it's not great to feel like they're empty compliments that end in a pitch.

I keep noticing that good ideas (or just things I don t want to forget) show up at the worst times walking, in the middle of something else, right before bed. I ve tried a few note apps and quick capture tools that show up here, but half the time I still end up dumping stuff in a random notes app or even texting myself.
Curious what the rest of you actually use when something pops into your head and you just need to get it down fast. Do you stick with one simple tool, or do you have a little system that actually works without becoming another thing to manage?

Connecting third-party MCP servers makes desktop AI assistants way more capable but it opens up serious security risks if those servers aren't tightly scoped.

A tool meant for simple data lookups often carries dangerous write or delete permissions in the background. When those tools sit directly in the context window bad data or malicious prompts can lead to unintended actions without explicit approval.

If you're building or using custom MCP tools daily how are you validating actions before execution to keep your system safe?

Building new features always feels like progress, but it was actually masking our biggest retention problem.

Every time a user canceled, we rushed to build what they asked for. Six months later, we had a bloated product with complex navigation, and users were still leaving for simpler alternatives.

For founders managing mature products: how do you decide when to freeze feature development and spend an entire sprint strictly stripping away complexity?

Noticed our dev speed was fast at first but lately we end up redoing work because everyone interpreted the spec slightly differently.

On zoom people just log off as soon as the meeting ends. You lose those quick 30-second casual chats where small confusions usually get cleared up.

Does anyone have a virtual setup that fixes this, or do you just deal with the extra rework?

One thing I find tricky when designing AI products is deciding when the product should just act and when it should ask the user first.

Asking for confirmation feels safer, especially when AI is making decisions or changing something for the user.

But if every action needs confirmation, the experience quickly becomes annoying. At some point, the user is basically supervising the AI instead of benefiting from it.

I don t think the answer is simply confirm important actions, because what counts as important can depend on the user, the context, and whether the action can be reversed.

We moved ours last week, a few days before the date.
The product worked. The payments didn't fully work yet, and it moves real money for the people using it. A checkout that only works in test mode felt like a demo, not a launch.
It stung for a day. It still felt like the right call.
What made you move yours, or what did you ship anyway and wish you hadn't?

For 365 days straight, I posted every single day. No exceptions. Weekends, holidays, sick days I pushed content out just to keep the streak alive. I was terrified that if I missed a day, the algorithm would banish me to shadow-realm.

Then I hit a wall of absolute creative bankruptcy. I had nothing left to say, so I wrote generic, empty fluff just to hit publish.

One day, I just couldn't do it. I skipped a day. Then two. Then a week.

I waited for my reach to plummet to zero. It didn't. In fact, when I came back with a post written out of genuine inspiration rather than algorithmic panic, it performed better than anything I had written in months.

Hey community! I thought to share this because it really changed my week, and I think more people should build their own tools, even if they are not perfect, regardless of their technical background.

For context: I built a tool that pulls my weekly calls from Granola, and turns them into a podcast-style audio every friday using @GranolaMCP, @Claude by Anthropic, and @Cursor.

When I launched I just picked a price below a couple of competitors without really looking at long term math. Six months in between hosting costs and hours spent answering tickets I'm essentially working for free.

Grandfathering old users or adding higher tiers makes sense on paper but actually communicating the change to people who signed up early feels extremely awkward.

If you had to fix underpriced software after launch what made writing that announcement email easier?

When I started building automated content pipelines I kept running into problems. Every time someone pasted an article the AI would mess up. It would. Skip the final instructions. The context window got too full. Everything fell apart.

The key fix was changing how I structured the prompt. Of writing one long block of instructions I started using XML-style tags to separate different parts. I now put the formatting rules at the end right after the input data. That way the model sees the content first then gets the rules right after. It pays a lot attention when the instructions come after the data.

I rewrote 40 different workflow prompts this way. The error rate dropped from 15% to than 2%. That s a difference. It shows that where you place your instructions matters more, than how warnings you add.

So what method do you use to keep language models focused on your formatting rules? Do you use tags? Do you put rules at the end?. Do you try something else?

I ve noticed how easy it is to abandon a project when the only person who knows about it is you. There s no deadline, no follow-up, and no awkward conversation when you stop.

Sometimes telling one person what you re working on creates just enough accountability to keep going not because they re pressuring you, but because the project becomes real outside your own head.

Do you share projects while they re still unfinished, or prefer to work privately until they re ready?

I used to explain my product. Long paragraphs about what it does, why it matters, how it fits into a workflow. I was proud of those explanations and nobody read them.

Then I started showing it. One screen, one action, one result. No preamble. And people understood it in three seconds in a way that four paragraphs had never managed.

I was talking about my goals with someone and they asked a simple question. Where did that goal come from?

I did not have an answer. I had been chasing a number I had never chosen, in a shape I had never questioned.

There's a thing I built, shipped, and then felt nothing about. It worked. People used it. I got the messages I'd been waiting for. And about three days after launch I realized I had no interest in maintaining it.

I kept it alive for a while out of obligation. Answered the emails, fixed the small bugs, pretended I was still invested.

Almost every cancellation feedback form says the price is too high.

Naturally you start thinking about discounts or making a cheaper plan.

But after talking to a few lost users turned out they were spending way more on competing apps because those tools actually solved a daily pain point.

How do you figure out if your pricing is actually wrong or if people just don't see the point of using your product enough?

The car did a graceful fall more so than full-flight, and that too with the correct height, speed, friction of the ramp, pressure, etc/ all calculated meticulously to make it happen with multiple thrusters. Even if they are able to build this fully within the next 20 years, would such a vehicle be safe to have on the road?

Is there a way to edit a post that was added? I did not see any settings on the posted thread not could I find a setting for "Your Posts."

I've always worked remotely, always in small teams. For years I struggled with the same things:

• staying productive

• staying consistent

• doing the right tasks instead of the ones I enjoy

• getting my habits back after travel or a messy month

I thought I was alone in this, so I kept hacking my way to solutions. Here's what has actually worked so far.

Whenever I share something I m working on, the feedback comes in all directions. One person says it needs more features, another says it s already too complicated, and a third wants a completely different design.

Last month I changed a small feature because three people asked for it in the same week. After the update, nobody used it, and the people who had asked never came back to try it. I realized I had counted requests instead of asking who really needed it.

It made me wonder if I m too quick to act on feedback just because it s loud or repeated.

How do you decide which feedback is worth acting on? Have you ever built something because people asked, only to find they didn t use it?

In the early days, it s tempting to keep driving top-of-funnel traffic to see sign-up numbers grow. But if only 10% of those sign ups actually activate and get value pouring more traffic into the funnel feels like pouring water into a leaky bucket.

On the flip side, pausing marketing to fix activation with a small user sample size makes it hard to gather enough statistical data.

How do you balance top of funnel growth with product activation during the first few months after launch?

When looking at our user session replays, we noticed a trend: users who didn't experience the main benefit of the product within the first 3 minutes almost never returned. We tried adding guided walkthrough tours, but most users just clicked Skip as fast as possible.

It made us realize that users don't want to be taught how to use a tool they tool just want to get to the result immediately.

How did you streamline your onboarding to get users to their Aha moment faster? Did you strip away setup entirely or show dummy/pre populated data first?

During a recent round of feedback calls, our power users requested a workflow feature that would fundamentally change how our product operates. On paper, it solves a big problem for them but it moves our app away from the simple, focused solution we set out to build.

Balancing listening to your customers with sticking to your core vision is much harder in practice than in theory.

How do you handle conflicting user feedback? Do you adapt your roadmap to high value requests or stay firm on your original vision?