... wrote the notification copy. Then we actually talked to the people requesting it. What we found: they didn't want to share what they'd written. They wanted their partner to start journaling too -- separately. The "sharing" they were asking for wasn't about showing their entries. It was about getting their partner to have the same experience they were having. The feature they were requesting and the problem they were solving were completely different things. So instead of building ... ... relationship reflection" prompt that both people answer independently, then get a combined insight. The result? Partner invites converted at 34%. Couples who both journaled had 2.3x the retention of solo users. And not a single person has since asked

... launched Mira on Product Hunt today, and the conversations in the comments have been the most interesting part of the whole day. Researchers asked about probe neutrality whether the follow-up questions an AI asks

... more than the feature list, and honestly it feels less forced and gets better replies too. Comment from Arnold Oshenye(@oshylabs): The salesy feeling is almost always a ratio problem, not a promotion problem. It shows up when you ask before you have given, so the fix is to keep a running credit of useful things you put out with no link and no ask

... small mindset shift has made a big difference for me. Instead of asking: "Is this a good opportunity?" I now ask

... changed. We are building Ranklink. A network of 20,000+ website and blog owners. Not a marketplace. Not a "buy links here" page. A community of people who want their content cited and are willing to cite others. We ask them one question: "What topics are you writing about this quarter?" Then we match them with other owners in the same space. They link to each other. No money changes hands. No "guest post for $200." Just humans helping humans ... ... cited. The backlink industry is stuck in 2018. People still ask

... first year of Murror, we ran surveys, interviews, feature request boards -- the whole playbook. We collected thousands of data points about what people said they wanted. Then we started watching what they actually did. The gap was enormous. Users asked for more customization options. What they actually needed was fewer choices at the right moments. They asked

... When we first built Murror's AI companion, we did what every AI product does -- we made it ask a lot of questions. "How does that make you feel?" "Can you tell me more about that?" "What happened next?" It felt like the right approach. Therapists ask

... agency, I think the questions from clients are going to move faster than the excitement around the output itself. At first they care about speed, cost, and whether the agent can do the job. Very quickly, though, they start asking who is checking the agent, what data it can access, and what happens when it gets something wrong. That is usually where governance comes in. Clients want to know about data privacy, approval workflows, auditability, human-in-the-loop review ... ... this while building @OpenBox . Agencies and internal teams usually need a clear record of what the agent did, what it touched, and where human approval happened. That tends to matter more once the workflow is real and clients start asking

... harder when it's a real request from a real tradesperson asking for it. Curious if you've had to say no to something you personally wanted to build, that's usually where the discipline actually gets tested. Comment from Nolan Vu(@nolan_vu): @samuelcrotti  Real pain point, props for tackling it head on. Ran a small Shopify store for a bit and the ad spend vs

... report saving 5 10 hours per week on manual asset requests. Why Do Designers Waste Hours on Brand Asset Requests? A developer needs the logo in white. A copywriter wants the exact brand blue hex. A new team member asks where to find the current  brand guidelines . A client wants a link to all the logo files. Each request takes time: opening Figma, digging through Drive folders, re-exporting a file, writing an email. Multiply that across ten clients ... ... accurately, and without interrupting your work. You generate an API key from Sinqlo under  Settings API Keys , then paste it into your AI tool's MCP server settings. That's the entire setup. From that point, whenever you ask

... These came from people who tried the SlimSnap screenshot-to-JSON workflow during launch and asked for something specific. Listing in the order they came in. Screenshot capture for scrollable content and open dropdowns. Right now the capture clips to the visible window, so if a dropdown or long list is open, parts get cut. Balpreet S flagged this on LinkedIn. Native Mac app screenshot support (scope verification). Several people asked

... Product Hunt! I'm launching today, and I've been collecting the questions business owners say they wish they could just ask their own business and get a straight answer. The most common ones I keep hearing: "Did I actually make money last month?" "Where did our cash go?" "Am I spending too much on payroll?" "Are Square sales matching QuickBooks?" "Can I afford to hire one more person?" All of these questions feel quite simple, but in reality these ... ... most common ones you need to spend a lot of time on. Log into multiple platforms, stitch the data together or ask

... explains why rubber-stamping feels so useless, it's asking the human to re-confirm things the agent already knew instead of supplying the one thing it didn't. Here's the wrinkle that follows from your own logic, and it's where I think the real engineering lands: if the agent can't compute blast radius, then it also can't reliably decide when to ask

... When we first launched Murror, the number one feature request was always the same: "Can I talk to the AI?" Users wanted a chatbot. Something they could vent to, ask for advice, get instant feedback from. Every competitor

... changed. We are building Ranklink. A network of 20,000+ website and blog owners. Not a marketplace. Not a "buy links here" page. A community of people who want their content cited and are willing to cite others. We ask them one question: "What topics are you writing about this quarter?" Then we match them with other owners in the same space. They link to each other. No money changes hands. No "guest post for $200." Just humans helping humans ... ... cited. The backlink industry is stuck in 2018. People still ask

... Most product teams run surveys. We did too. We'd ask things like "What features would you like to see?" or "How would you rate your experience?" And we'd get perfectly reasonable, perfectly useless answers. The turning point for Murror came when we stopped designing around what people said they wanted and started paying attention to what they were avoiding. Here's what I mean: in our app, users can share stories and reflect on their emotions. We noticed ... ... ones that feel effortless, but the ones that feel meaningful. It's counterintuitive in an industry that worships frictionless experiences. But I think there's a difference between unnecessary friction (bad UX, confusing flows) and necessary friction (moments that ask

... checked off. The team is busy. Meetings happen. Decisions are made. But the code does not move. That is not a roadmap. That is a wishlist. 2. The founder is the only one who can explain the product. You ask anyone else on the team what the product does. They hesitate. They look at you. They wait for the founder to answer. That means the vision is not shared. It is just one person's idea. When that person ... ... added the features. But the same complaints keep coming. That means you fixed the wrong things. Or you fixed the symptoms, not the cause. The users are trying to tell you. You are not listening. 4. The team stops asking

... different reason. Wanted to share what all I learnt while building this solo in 2.5 months from scratch. As you all know, AI capabilities for coding has seen significant improvement since last 6 months, but still just asking it to build you an app doesn t cut it. You can take the vibe coded software only till certain extent, not to production. You still need to have good understanding of software development in order to get it right. Me being ... ... discussion. - Need a well structured audit loop to challenge what AI codes. Some people use codex to audit what claude writes. But, for me even claude s separate agent works well for auditing. - TDD works well. Instead of just asking

... just shipped something new on Product Hunt. Ask Product Hunt AI is a way to explore launches, products, and discussions without digging through pages or trying the perfect search query. You can just ask

... thought we knew We assumed enterprise customers wanted the same things as our small business users, just more of it. More security. More control. More features. We never talked to them. We read blog posts. We looked at competitor pricing pages. We guessed. Here's what we missed: Procurement cycles. Enterprise deals take 6-12 months. We had 30-day sales cycles. We weren't built for that. Security reviews. We needed SOC2. We didn't have it. Customers asked

... most important and challenging experiences you ll have as a founder is fundraising. I pitched VCs across London and San Francisco. Some spent 15 seconds on my deck. Some took the call just to diligence a competitor. One told me to ask

... users. 27 distinct features across 8 modules. We looked at three metrics for each feature: Adoption rate % of users who tried it at least once Retention rate % who used it again after 30 days Request volume how many users asked for it The gap between what people asked

... months, our most requested feature at Murror was a chat function. Users wanted to talk to the AI the way they talk to a friend. It seemed obvious. Every competitor had it. Every feedback form mentioned it. So we built it. And within two weeks, our core metrics started dropping. Session length went down. Return rate went down. The thing users said they wanted was actively making the product worse. Here is what we discovered when we dug into ... ... intentional pacing. It does not let you rush through your own emotions. The result was better than both the old experience and the pure chat. But we never would have gotten there if we had just built what users asked

... trying to protect their pet project. Just the raw plan. The prompt: "Analyze this roadmap. Identify the three most likely failure points. Use first principles reasoning. Assume we will follow your recommendations without ego. If you need more data, ask for it." The results were not symmetrical. Failure point #1: The unvalidated feature. The roadmap had a feature labeled "Priority 1." Estimated build: six weeks. Claude flagged it immediately. "No user research cited. No support ticket volume. No search volume ... ... weeks into development. Failure point #2: The integration with no ROI. Another line item: "Integrate with Platform X." Estimated: eight weeks. Claude's analysis: "What outcome does this drive? No stated goal. No success metric. No evidence customers are asking

... seconds. Then refactored a messy function into something readable. We felt like geniuses. By end of day, it had shipped 3 minor improvements. We started talking about cutting engineering costs. Day 2: The first crack. We asked Claude to add a new filter to our dashboard. It wrote the code. It worked locally. We merged. That night, something else broke. A completely unrelated chart stopped loading. No error logs. No obvious cause. We spent 2 hours tracing it back ... ... refactored a shared utility function that 5 other features relied on. It didn't check dependencies. It just assumed. We rolled back. Lesson one: AI doesn't think about side effects. Day 3: The false confidence trap. We asked