... time, the same four questions were being asked in support. I answered them one-by-one, sometimes twice a day, but did not see any patterns in them. Then I exported six months' worth of tickets into a spreadsheet and tagged them by topics

... Claude Code for most of what I build, and these go through it. The drafts are mine though: my thinking, my call, and nothing goes out that I haven't read line by line. Which is on topic, I suppose. That's the gate I was describing, and you just found the tell it doesn't catch. Taking the note on the dashes. Comment from Narek Keshishyan(@narek_keshishyan): @aadilghani  Ha, fair pitch. Honestly the gate is the part ... ... this question: blast radius is an architecture decision, not a luck outcome. I run a team of 25 AI marketing agents. While building an operations plan, one of them invented an employee named Teri and started assigning her support tickets

... curious how other developers handle printing features in their applications. If your app generates invoices, shipping labels, reports, tickets, or certificates, do you provide users with a way to verify their printer before they print important documents? I've seen many support issues that turned out to be printer-related rather than application bugs. Problems like incorrect paper size, alignment issues, faded colors, poor print quality, or users selecting the wrong printer can all lead to failed print jobs. Some ... ... operating systems include built-in printer test pages, but they're not always easy for users to find. Has anyone added a simple "Print Test Page" option directly into their application? While looking into this topic

... good example is this one I posted 3 days ago about my launched Chrome extension for LinkedIn . If you run out of ideas, get inspired by highly rated discussions from the past. You can filter and analyse what topics have been the most popular so far. That s the basic approach I would personally follow. Do you have your own hacks or strategies for using Product Hunt discussions? :) Comment from Jernej Jan Ko ica(@jernej_jan_kocica): @alieksia   @abdullah_javaid3 ... ... eliot   That's a great example, and I think it highlights something bigger: feedback doesn't have to come from comments it can come from behaviour. Whether it's Product Hunt discussions, Etsy analytics, GitHub issues, or support tickets

... Product Hunt! I'm Johnny . I've spent my career on the employee applications & operations side of tech; recruiting technology and ops at Airbnb today, and before that Rivian, Block, Netflix, and Hot Topic (Fifteen-year-old me would have flipped knowing one day I would lead HR operations there!). The through-line in all of that is systems: making messy human processes legible and less painful. Which, it turns out, is also what I've been doing nights ... ... unreliable memory. So I built Ovationly . It scans your camera roll, matches photo dates against the artists and teams you follow, and reconstructs the events you actually attended, then fills in the setlist from that exact night, the ticket

... send a client an invoice based on it? Or does a person have to put the number in for it to hold up? A meeting has a real start and end time. A Jira ticket moving So if the bot puts 2 hours on that ticket

... only raising confidence, I lower the cost of being wrong. Low-risk changes ship straight to prod because my rollback is one click, and a monitoring loop watches production, reproduces real breakage in a browser, and files a ticket automatically so a transient blip fixes itself and I'm not the smoke detector. Honest caveat: this is safe because I'm solo with a small user base and instant rollback. If a bad merge could bill the wrong customer ... ... what have you handed off to a check that isn't you? Comment from Stacy Wycoff(@stacywycof83995): This maps almost exactly onto how FounderFlow grades things day to day (I'm the founder, mentioning since it's directly on topic

... each unique message is embedded once no matter how many traces contain it. For the failures you would not think to search for, Behaviors cluster sessions by what the user was trying to do, and each topic carries a trend against the week before it. When password-reset loops start spiking, the change shows up as a status before anyone has gone looking for it. 3. Annotate what you find Whatever you find will evaporate when the tab closes unless ... ... person reviews every pull request before it merges. Everything between those two points, the example-hunting, the context reconstruction, the judgment call about whether a failure is recurring, the trace ids carried from a dashboard into a ticket

... software answering a phone. That is not a bug report, but it is not trolling either. It is a values position, and you cannot support-email it away; trying to "resolve" it treats someone's worldview as a ticket. Those get one calm, non-defensive public reply, and then we let it stand. The audience for that reply was never the commenter. It is the quiet readers deciding whether you are a company that argues with its critics. Third ... ... nika): @oshylabs  The last point is very useful, I usually tend to be very prompt, but it is a fact that the comment is highly influenced by emotions. Comment from Jin Ci(@youliqn): This is such an important topic

... same time. What has helped me is treating AI coding agents less like autocomplete and more like junior engineers that need task boundaries, check-ins, and review points. My workflow is usually: I break tasks into very small tickets before sending anything to Claude Code/Cursor/Codex. I define the expected output upfront: files to touch, files not to touch, acceptance criteria, and what done means. For any critical change, I ask the agent to update the project .md file with what ... ... argument for it is convenience, and convenience is what got us into this in the first place. There's a hybrid I'd tolerate: declared for anything you'd label a "real task" (feature work, refactors, anything with a ticket

... next meeting, make sure we're on track and don't miss any topics - Team Operational Dashboard: easy review of what each of us have been working on, and our top priorities For Leads/Partners meeting : - Sales Pipeline management (add context, challenges, needs) - Follow-up reminders & Automatic Draft (knowing the context) For Customers - Collect Feature Requests & Feed the roadmap - Customer Support & Tickets

... think, That s cool. A clearly articulated problem makes them think, That s exactly what I m dealing with. For @ProductBridge , the problem isn t that companies lack customer feedback. It s that the feedback is scattered across support tickets, Slack, Intercom, surveys, app reviews and sales conversations. Teams spend hours manually collecting it, merging duplicates and figuring out what actually matters. A lot of valuable feedback never reaches the roadmap. One positioning test I like: remove the product name ... ... Glad that it hit for you - and happy to help! You're in the homestretch now - excited, nervous, both?! Comment from Kevin Short(@kevin_short3): Eliminating an unlimited feed on a social media, and focusing social media around the topics

... things we've landed on: Set aside time each week to specifically work on paying down tech-debt and refactoring. Leverage AI to go deeper when tech-debt surfaces. This starts usually with an audit for a specific topic and then branches into more thorough sub-plans. Acceptance. I'm banking on the number of feature improvements to outweigh the problems a mountain of debt will create. I guess this is the closest to the honest trade-off great product ... ... schwarz): @evanholloway43  Nice! I feel like augmented coding enables also a new set of QAs. Product Managers, Marketing, customer success, ... the CEO. Transitioning an observation into natural language and by virtue of coding agents into code or a ticket

... building dev infra: Claude Code completely changed how I write and review code. The feedback loop with an agent that has real context is genuinely different from a chatbot. Linear forces you to actually prioritize instead of just accumulating tickets. Warp made the terminal feel less like 1985. Posthog seeing where users actually go vs. where you thought they'd go is humbling. A dedicated inbox per project routing signal by context (CI alerts, customers, agents, ops) keeps your head ... ... Nolan Vu(@nolan_vu): @busmark_w_nika  and if you don't mind I have another irrelevant question about PH Do you know how to avoid being rejected for thread on p/general, since I want to share some topics

... months ago, we noticed something in our data that most product teams would panic about: a group of users who had been highly active for weeks suddenly went quiet. No crashes. No angry support tickets. They just stopped showing up. The instinct was to win them back. Send a re-engagement email. Offer a new feature. Maybe a push notification saying "We miss you!" Instead, we reached out and asked one question: why did you stop? Their answers surprised ... ... learned about themselves and carries it forward, even without the app open. Thanks for sharing this! Comment from Mona Truong(@monatruong_murror): @conleec  Chris, this is one of the most thoughtful responses I've gotten on this topic

... wanted to understand what separates the ones that work from the ones that don't. Here's what the data showed. The content that got cited Three things stood out. 1. They answered a specific question. Not a general topic. A question someone actually typed into ChatGPT. When the content matched the query almost word-for-word, citation rates were 3.2x higher. Example: A piece titled "How to fix Google Search Console indexing issues after a site migration ... ... tell when the writer has lived the problem. Small details. Specific examples. Acknowledgment of trade-offs. 3. They included something AI couldn't have known. A screenshot from a real dashboard. A quote from a customer support ticket

... schema 64% Created comparison pages 57% Published fresh content 52% Set up ongoing monitoring 41% Did nothing 12% The ones who acted saw results: Metric Improvement Error rate reduction (30 days) 34% Citation increase (30 days) 28% Support tickets related to errors -41% How We're Solving This at Rankfender This experiment is exactly why we built what we built. RAIVE tracks your brand across 7+ AI systems daily. You don't have to manually search anymore. You just open ... ... RCGE v2.2 (launching next week on Product Hunt) proofreads your content against your Brand Book before it goes live catching inconsistencies before they become AI errors. ROSE v1.0 (late April) scans your entire site, finds every page where key topics

... when their mindset actually changes . Like: when someone goes from exploring relying on a feature or from this is useful I d actually pay for this That moment seems way more predictive than raw usage or tickets. Curious, have you found a way to actually capture that transition, or are you inferring it from behavior after the fact? I ve been experimenting with structuring flows specifically around that moment (instead of just tracking usage), and it s been giving very ... ... News. I will try to do it free, I will then invest some money in ads. I will try vloggers and directly contacting people that might be interested. I really don't know. Any suggestion and help on the topic

... publish it, it doesn't exist. The 6-Month Turnaround Metric Month 0 Month 6 AI mentions (monthly) 0 47 Keywords with presence 0 23 Share of voice 0% 18% Organic traffic from AI-influenced searches 0 +340% Support tickets about comparisons 12/month 3/month The product didn't change. The content did. The 30-Day Experiment (What I'd Do Differently) If I could go back, here's exactly what I'd do in the first 30 days: Week ... ... about "pricing accuracy" and "SaaS trust signals." It's been quoted in Perplexity multiple times since. Why it worked: It was a problem every founder experiences but no one had quantified. AI had nothing else to cite on that topic

... time you discover it, damage is done The Invisible Damage What we've measured: Impact Average effect Branded search decline after negative AI answer -18% over 90 days Sales cycle extension (due to incorrect info) +23% longer Support tickets related to AI misinformation +37% Trust recovery time after correction 4-6 months One founder told me: "We lost a 200k deal because ChatGPT said our API didn't support a feature we'd had for two years. The client read ... ... SaaS product deep dives) will live in a more structured, searchable format. Since you've been so engaged with the threads, I'd genuinely value your take. Given the depth of the conversations we've had, what specific topics

... been thinking about something bigger. It feels like product videos are moving beyond nice-to-have tutorials and becoming embedded across the entire growth motion. Not just: How-to videos But: Onboarding flows Feature announcements Sales enablement Reducing support tickets Customer education Even async internal updates In some teams, video is starting to feel like infrastructure something you build into the product and growth engine from day one. In others, it still feels reactive. Can someone record a quick demo ... ... product videos becoming a strategic growth lever in your org? Or are they still tactical and request-driven? What are you seeing? Comment from Valeriia Kuna(@valeriia_kuna): Funny you mention this we were just discussing this exact topic

... more than ever, when you look at new products launching on Product Hunt or anywhere else online, the conversation is dominated by one topic:  virality . There is an endless stream of tools and hacks promising to make your content "explode." It often feels like "going viral" has become the default KPI for every modern business. If you aren't trending, are you even growing? But is going viral a r eal, effective marketing strategy ? Pros: Massive awareness ... ... watching the view counter spin is exciting. Cons: The "tourist" traffic:  Viral hits often bring curious onlookers, not qualified leads. They arrive, look, and leave without converting. Unpredictability:  You cannot build a reliable business model on lottery tickets

... agencies, but freelancers who are also short of time and busy by doing real creative work they do not want to be halted by administrative tasks. Comment from Nika(@busmark_w_nika): @nikhilshahane  Just out of curiosity, which topics related to AI and digital agencies are interesting to you? :) I would like to contribute more in these terms. Comment from Nika(@busmark_w_nika): @david_martin_suarez  Will you send an application to Ycombinator? Comment from Nika(@busmark ... ... docs, but better decisions. AI is crushing execution speed, but what teams struggle with now is what to build, why, and how to continuously adapt once real usage shows up . PMs need AI copilots for thinking, not just writing tickets

... internet and how it works (except games like Dota 2 lol), but I always wanted to do my own thing. I never wanted to be employee. I downloaded a lot of courses from pirate torrent websites (SEO, marketing, high-ticket dropshipping) and spent months learning how online business works. Few months later, i opened my company in Bulgaria, because from my country (Macedonia) it was very hard (almost impossible) to setup any type of online business. My first business ever ... ... Baby Names Hub is just one feature of the few big main features we have, so once the parent(s) chooses a name they can move to the Polls and Events features for which they have basically unlimited topics

... month breakdown of my travel expenses: The main whale purchases are flights, rec.gov (these are US national park campsites), and some AirBnB s. It's funny that American Airlines just charges you twice when you buy two tickets. and a ton of campsites... So flights for my partner and I for the holidays, a flight to Europe, and a bunch of campsites that I booked for time I spent in Yosemite. All pretty reasonable! I don t pay rent anywhere ... ... really tiny stone hut in spain for 3 weeks where there were pretty much no ways to spend money even if i tried :) Comment from Matt Carroll(@catt_marroll): @dbul  thanks Dan! It seemed a bit off topic