... personalize the experience, and understand who's using the product. And some tools need a bit of setup before they can show useful results. Personally, I like the idea of letting someone try one small part of the product first, then asking them to create an account when they want to save their work or go further. But I'm not sure that approach makes sense for every type of SaaS. Comment from Ghais Dahdouh(@ghaisdahdouh): Try first

... Makers I m Mohit. For 10+ years I ve worked on M&A and capital raises, sitting with 750+ founders on one side of the table and 2,500+ investors on the other. One thing keeps standing out. First-time founders usually need fundraising guidance the most, but they re the least likely to get it. Most advisors only work with later-stage companies. So founders figure out SAFEs, dilution and term sheets alone, often after they ve already ... ... building a simple system to fix that. It explains how fundraising really works, step by step, from someone who s seen both sides. Before I build more, I d love your honest input: What confused you most the first

... make usebravery, so this is partly about my own product. Better to say that first. Before there was a product there was a watch comparison site I'd made for my own use, BraveryWatch. Its first

... instrumented the first minute of 400 new signups and compared it to our onboarding flow. What we designed them to do: watch a 90-second product tour, then complete a setup wizard. What they actually did: 71% skipped the tour within 4 seconds. 58% went straight to search. 34% typed a question into search instead of clicking anything. 12% closed the tab entirely. The single most common first

... Vitals is live on Product Hunt today. It's an Activity Monitor alternative for Mac that shows you 60 apps instead of 1,000 processes, and in its first

... been building BYEOL , a small universe where people can leave stories on stars and create constellations with their friends. Tomorrow, I'm launching it on Product Hunt for the first time. I honestly don't know what will happen. Maybe a lot of people will check it out. Maybe almost nobody will. And that's okay. For me, simply getting to the point where I can put something I made out into the world already feels meaningful. I've spent ... ... time building things quietly, and I'm starting to realize that shipping, sharing, listening to people, and trying again are just as important as building. So I'm treating tomorrow as a first

... Published My First App on Google Play! Today is a special milestone in my developer journey I ve published my first

... moving fast, you've shipped login, it works, users are in. and then an enterprise prospect shows up and the first thing they ask is 'do you support SSO?' and suddenly the thing you built in a weekend is blocking a six-figure deal. but SSO is usually just the first

... Yesterday, Naseem finished its first day on Product Hunt: #21 Product of the Day 76 upvotes 57 followers And today, Naseem got its first

... send details if you want. any feedback on product and/or rebranding would be nice. Comment from David Kaaungwa(@davemadeit): Imo a half-baked AI-generated UI can hurt startups more than people realize. The interface is often the first signal of how much thought and care went into the product. If it feels generic or inconsistent, users can subconsciously question the product's credibility and quality. And trust is harder to rebuild after a poor first

... everyone! First time posting here, so go easy on me I'm a solo dev, and I just shipped Dating Counselor , an iOS app that acts like a brutally honest friend for your dating life. The idea: we all ignore red flags in the moment and only see them clearly weeks later. So the app walks you through a short "audit" of a match, before or after a date, and gives you a Red Flag Score (0 100) , a breakdown ... ... what's concerning, and a straight-talking counselor's analysis. It even has a Ghost Meter that estimates how likely someone is to ghost you based on how the date actually went. A few things I care about: Privacy first

... them. Over the last few weeks, I joined a hackathon and somehow went from asking could we build something around this research idea? to actually having a product that people can use We re now getting ready for our first Product Hunt launch and I'm discovering that launching something is a completely different learning experience. So I'd love to hear from people who have done this before: What is one thing you wish you had known before your ... ... first

... When you're a first-time founder/maker, and you're the only person using your own product, you probably overlook important things. That's why you need to test the product with as many people as possible. The problem is that time is limited. You have to decide not only how many people will test it, but also who those people should be. Yesterday, I launched my Chrome extension for the first

... active here, and English isn t my first language. It s actually interesting that the whole global community of builders, makers, and founders has basically one common language: English. And sometimes I wonder: how good does your English actually need to be? I definitely overthink it sometimes: Is this sentence natural? Is my grammar okay? Will people understand what I mean? Maybe it doesn t matter that much if you have something worth sharing. So, if English isn t your ... ... first

... hardest parts of building a marketplace isn t building the product. It s deciding which side needs to exist first. I m working on a marketplace where one group has unused capacity and another group is looking for access to it. The obvious answer is: get supply first

... Most products lose people in the first 60 seconds, here's where I'm a UX designer who lives in the first

... click apps on the first screen. It felt like the whole point of the thing, everything in one place, look how much you get. People opened it, scrolled, and left. Not confused. Just done deciding before they'd made a single one. We cut the first

... deliver. But not launching it and waiting for a moment like let me build traction first, let me build campaign first

... third thing. Which is also why my two open questions turn out to be one. Add a second escalation hop and first click wins stops being a policy and becomes a race. You cannot escalate to a second person if you cannot tell them apart from the first

... true. Since my product is not ready, people only talk about how brilliant the idea is. Maybe when I launch it, and others will test it, they will hate it :D hahaha Comment from Arnold Oshenye(@oshylabs): The doer versus yapper worry has a clean fix: you are not promising anything if you only ever talk about the problem and the question. A promise is a dated claim about a feature. A problem is just an observation about the world ... ... when they can pay is signal. So my honest answer to when: start promoting the day you can state the problem in one sentence, and start selling the day a stranger takes a small action without being asked. The first

... rewrite it. A small real example: today, the only new follower I could directly trace came from a contextual X reply with no DeepPane pitch or link. The person liked it, replied, then followed. Meanwhile, product-first posts mostly sat quietly. So I don't think the answer is hiding the product. It is earning the right to mention it: lead with the sharp observation, the frustrating moment, or the useful experiment; let the product appear only when it completes ... ... sources full of useful data, but turning that into clean CSV/Excel/JSON is slow, unclear, and often too technical. Same with website scraping risk audits the interesting problem is not buy an audit, it s: Do you know what bots, competitors

... buyers need to see their own pain reflected back at them first. if they don't recognize the problem immediately, the demo doesn't matter. Comment from Shabnam Katoch (@better_shab): Problem-first

... them, named the failure patterns, rebuilt the emails, and published everything publicly. 59 teardowns. Every single one open at strategicflow.tech/teardowns.html . Here's what the data shows. The 3 structural failures that appear in almost every SaaS email Feature-First Bias 83% of emails The email leads with what the product does instead of what changes for the reader. " We're excited to share our new real-time collaboration feature " is Feature-First

... part right now: not the AI, the first ten minutes. Every early user tells me the same thing: they want it, then stall at "where do I start?" Getting someone from empty account to their first

... everything. A plain notes file where every decision and gotcha lives, so I never re-solve the same thing twice. The first two genuinely changed how much one person can ship. Comment from Eliot Ferstl(@eaferstl): Claude Code(duh) GitHub - how did people handle version control before git?! Proton - best business suite in my opinion. Security first