Connect with the Product Hunt community

There is a clear difference between using tools to condense your own curated notes versus letting a prompt pull and synthesize arbitrary web data. When you control the input sources you avoid hallucinations and surface-level analysis. But when you hand over both search and synthesis to software critical context often gets lost in the process.

What does your actual workflow look like when diving into a completely new topic or industry research?

Spent weeks getting threads turned down because i was trying too hard to sound like an expert with frameworks and polished tips.

The second i dropped the promotional tone and just asked a simple question i was genuinely stuck on, it got approved right away.

Anyone else notice that raw questions pass moderation way easier than structured advice posts?

When I see agents that can talk see things connect to apps and actually take actions it sounds useful but also makes me wonder where the line should be. Giving an agent more abilities can solve more problems but it also means there are more things that can go wrong when it misunderstands the situation. How do you decide which actions an AI agent should be allowed to handle on its own?

Half of what I ship is a crawler, and the failures I dread are the quiet ones. A company moved its careers page to a JS widget last month, our parser kept returning HTTP 200 with an empty list, and from the outside it simply looked like they had stopped hiring. Nothing alerted, because technically nothing had failed.

I ended up alerting on the shape of the data instead of the status code: if a source drops more than half its rows overnight, a human looks at it before anything downstream moves. That threshold is a guess, and it still misses the slow rot, where a site changes one selector and you lose a third of the fields without ever losing the page.

When a paid user cancels, our instinct as builders is to immediately jump into our roadmap and build whatever feature they asked for. But after reading through dozens of exit surveys, we realized a hard truth: lack of features almost never drives people away.

They churn because we made onboarding too complex and didn't help them build a daily habit around our tool. They didn't lose interest in the problem; they just gave up on our setup process.

Do users leave because your app lacks power, or because you made it too hard for them to get their first quick win?

We ran a Lifetime Deal to bring in fast cash flow and early feedback. While it brought quick cash, thousands of one time buyers ended up draining 80% of our support resources for years, slowing down our path to stable monthly recurring revenue (MRR).

Did running an LTD help jumpstart your SaaS or slow down your MRR growth?

I used to look at other founders doing cheap growth hacks and think I'd never run my project like that. Fast forward to today, and I ve cut prices and built messy features I vowed I d never touch, mostly out of fear of slow growth.

Some changes genuinely helped the business, but others just feel like I took the easy way out.

Where do you draw the line between adapting to the market and completely selling out on your core beliefs?

Been thinking about this after going down a research rabbit hole on luxury cigar humidors of all things. Weird category to end up in, but it turned out to be a pretty good case study in a pattern I think shows up everywhere in product design.

At the entry level of that category, almost every product looks and performs about the same. But once you get into the higher tier, the marketing copy across brands starts converging on the same vague language (premium materials, precision engineering, timeless craftsmanship) while the actual functional differences get harder to spot unless you know exactly what to look for. In that specific case it turned out to be things like active vs. passive climate control, which is barely mentioned on most product pages even though it's the single biggest factor in whether the thing actually works a year from now instead of just on day one.

We offered 35% off annual plans to lock in upfront cash. However, cohort analysis showed that forced annual commitments led to low feature adoption and massive non-renewals at month 12. Monthly plans actually gave us higher LTV and better engagement.

Did pushing annual plans improve your cash flow or damage long-term retention?

Sometimes I spend 20 minutes trying to understand a bug before asking an AI tool about it, and sometimes I just paste the error in immediately.

Wondering which approach other developers find more useful. Do you investigate first, or let AI help narrow down the problem from the start?

Hey, I remember there used to be a Coming Soon page where we used to create product teasers and get some hype for the product before launching it. Has PH discontinued that feature?

When an application throws a backend error, I ve started wondering whether it is better to paste the entire stack trace into an AI tool or first narrow down the likely cause myself.

What debugging workflow are other developers using? Does giving the agent the full error and relevant files usually get you to the fix faster, or does it create too much noise?

I went back through my last 133 posts on Threads. The 58 with a link averaged 4 views. The 75 without one averaged 70.

So now the link lives in my profile and the post just has to stand on its own.

Do you still put links in your posts, or have you stopped too?

Hello product hunt family, how did you first go about your marketing and acquiring customers for your B2C SaaS? So far I've been trying the expected suspects - TikTok, Instagram, Facebook, Youtube, App Store Ads and have some traction but I feel like I'm not doing this optimally.
So my question is, what did YOU do that worked for your startup to go from 10 - 100 customers? I'm currently starting testing of ~3-5 second UGC hooks, followed by a 15 second product demo. Lots of threads on reddit talk about volume with this format and someday one hits. Is that a common theme you've seen, or experienced with your own product?

I'm bootstrapped and solo. I don't borrow, so I only do what I can pay for myself.

VCs have asked me about going public a few times. Honestly it did sound attractive, but I kept thinking about what I would lose. Once other people's money is in, you cannot decide things just on how you feel. In 2019 I was spending time in Australia, and I wouldn't have been able to do that with investors watching. Also if my kid gets sick I can drop everything.

I have never hired a full-time employee either, I spent that effort on improving the way I work myself.

Choice, or just how it turned out?

A five minute check for anyone who lets a user name a thing and later offers that thing as a download.

On an invoice, the number is text the user typed. It is a form field, and in the API it is a JSON string with nothing on it but a length cap. That is right for the document: 2026/07-001 is a perfectly good thing to print on an invoice. The trouble is where else the number goes. It becomes part of the file name, and the file name goes into a Content-Disposition header on the download, into the attachment name on the email that reaches the client of the seller, and into a path when a command writes the PDF to disk.

In August a review tried it against real responses. A number containing a double quote closed the filename early, and everything after it was read as further header parameters. A number containing a newline made the header invalid, and the download answered 500 on an invoice that rendered fine everywhere else. A slash or two dots in the same number would have written the PDF outside the directory it names.

The embarrassing part: the free generator already stripped its number, with a comment saying why. The four other places that built a file name did not. Same defect, fixed in one place out of five.

I ve noticed that I keep adding new productivity tools, hoping they ll make my workflow easier. But at some point I started spending more time organizing my tools than actually doing the work.

Now I m trying to keep things simple and use just a few products that I actually need.

Curious what others think: how many apps do you really use every day for work, and have you ever deleted a bunch of them because it became too much?

I noticed if I just ask an app to research a topic from scratch the summary sounds fine but none of the information actually sticks in my head. If I grab 3 or 4 solid links myself first and then ask for a quick breakdown I retain way more of it because I knew what went in. Do you guys dump raw queries into tools right away or do you bookmark and skim source material yourself first?

Lately I ve been catching myself trusting instant AI summaries without looking at where the data came from. The problem is that when someone asks me to explain the logic behind a decision I realize I don't fully understand the underlying sources. Now I try to create a quick folder of verified links before asking for a summary just so I have context. How do you keep yourself from getting lazy with background research when summarizing tools are so fast?

Spent weeks sharing progress pics feature updates and little wins on social media. Sure you get a few nice comments but almost none of those people end up turning into paying customers.

Feels like a lot of founders spend half their day editing posts instead of actually talking to users directly.

Has building in public actually brought you paying users or is it mostly just fluff?

I have a bad habit and I am pretty sure a lot of you can relate to this. I am absolutely terrible at launching stuff.

Every time I get close to shipping an MVP my brain starts making excuses. I tell myself it needs push notifications first or the onboarding flow feels a bit clunky or maybe I should just add dark mode before sharing it with anyone.

Before I even realize it two weeks turn into two months. The initial excitement for the project dies down and the code just sits on my hard drive untouched.

Logically I know an MVP is supposed to be basic and simple. But the developer side of me panics at the thought of putting out something that is not completely polished.

I've been putting off a price increase because I keep telling myself I need more data first. "I should wait until I know my churn rate." "I should wait until I have a cohort that's been on the product for six months."

But the waiting has now lasted longer than I'd like to admit. I'm worried I'm using "need more data" as a cover for just being scared to ask for more money.
For those who've navigated this: did you raise prices early and adjust later, or wait until you felt you had solid retention numbers? And if you raised early, what actually happened?

The common thread in all of these is that they're specific, grounded in a real experience, and end with a question that gives people something concrete to react to. A stated frustration or gap works better than a broad "what do you think?" because it gives people a clear edge to grab onto

Our interactive 10-step product tour had high completion rates, but 30-day retention remained weak. Once we stripped the tour down to just one core setup action, retention jumped.
Showing off everything upfront just overwhelmed users before they got actual value.

Did simplifying your onboarding boost retention or increase confusion?

We offered full access for 14 days, thinking it was the best way to prove value. But conversions stayed flat until we swapped the time limit for feature gates. The open trial gave users too much time to wander without hitting their
Aha! moment. Restricting the scope created immediate momentum.

Did limiting trial access help or hurt your paid conversions?

I decided to do an experiment. For 90 days, I logged every hour of work in a spreadsheet. Not just "worked on product" but exactly what I did. Every task, every meeting, every rabbit hole.

Here's the breakdown:

• Product development: 31% (I thought it was way more)

• Admin/email/ops: 24% (this one hurt to see)

• "Research" (reading Twitter, watching YouTube, "staying informed"): 18%

• Actual customer conversations: 9%

• Marketing/distribution: 7%

• Fixing things I broke: 6%

• Staring at the screen feeling overwhelmed: 5%

The number that gutted me was the 18% I spent on "research." I was consuming content about building instead of actually building. I was reading threads like this one instead of talking to users.