... Vineeth Nair(@vineeth_n1): I finally launched my product today. Do have a look and let me know your feedback. https://www.producthunt.com/prod... Comment from Michele Furgeri(@michele_furgeri): I'm launching today, so this is live rather than hindsight. The mistake I would undo: I spent two weeks on the page and almost no time on the people. With your three days, write down actual names. Not a follower count. People who will open a message from you. Then ...

... archived. 27 were marked "Act now." The classifier had no concept of an item resolving itself. Two things I took from it: A default value that doubles as a real signal is indistinguishable from that signal downstream. Obvious in hindsight, invisible in the spec. And "matches the specification" and "works" are separate claims. Our tests confirmed the code did what we wrote down. They couldn't tell us that what we wrote down was wrong. Curious whether others have ...

... Sending those eight emails gives me eight chances to be ignored, and no way to tell if I did it well or badly. Building always feels like progress. Selling only feels like progress in hindsight. So I hope it's not laziness. What was yours this week?  And if you've beaten this, I'd really like to know how. Comment from Shivangi Tripathi(@roguetink): Mine was an open-source blog CMS for non-technical teams. I built ...

... became obvious after actually launching. Comment from Maxwell(@maxwell_wx): Honestly, the biggest surprise was how little the launch itself mattered. Most of my early users came from search before launch day, not the 24h spike. The leaderboard, in hindsight, was mostly vanity. Comment from Hudson Reid(@hudson_reid): The search thing caught me off guard. Never really thought about getting users before the PH launch. Comment from Albert Nelson(@albert_nelson1): Nothing prepare you for refreshing the PH leaderboard ...

... love to hear from this community: What due diligence do you do before trusting a new factory/supplier you've never worked with? Have you ever gotten burned by a supplier, and what red flags did you miss in hindsight? Do you prefer working through platforms (Alibaba, trade shows) or building direct relationships? I've seen this from the supplier side, so I'm interested in the buyer's perspective what actually builds trust for you when sourcing internationally? Comment from ...

... thing apart and rebuilding it instead of just patching the parts people complained about. That decision is what I'm actually curious about. A handful of comments pushed us into a full rebuild rather than a few tweaks. In hindsight it was the right call, but at the time it wasn't obvious it easily could've been one loud opinion instead of a real signal. For other makers here: how do you tell the difference? Do you wait ...

... same broken assumption in our data model, and neither knew the other had done it. The obvious answer was a rewrite. We didn't do it not immediately. We spent a month arguing about it instead, which in hindsight was the most useful month we spent that year, because it forced us to name the actual problem: it wasn't the codebase. It was one early decision about how we modeled user accounts that everything else had been built ... ... know if that was the right call. A full rewrite might have cleared out debt we're still paying for. Or it might have killed us the graveyard of startups that spent a year rebuilding while a competitor

... From a relationship standpoint, I think we made the right decision. For the business, I m less sure. A VC is incentivised to get you to the next round and bring their VC network. A potentially pivotal decision in hindsight. June I went full-time. a16z decided not to invest. They thought we had underestimated the technical complexity. I already knew we needed an exceptional technical co-founder. Through the YC ecosystem, I met Mariana: an applied maths genius ... ... market: I speak Portuguese, Mariana is Portuguese and my wife is Brazilian. We ran a test in Portuguese. We recruited 100s of Brazilian users in three weeks, mainly thanks to Ting on WhatsApp. IYKYK . December Based on competitors

... looking back, the "simple tool" idea and the finished thing are pretty different. For those who've built something similar: did your project scope creep in a similar way? At what point did you decide "okay, this is done" vs. keep adding? And with hindsight

... contribute) every time :) It is worth to build a product page throughout the year. Comment from Farrukh Ahmed(@farrukh_ahmed8877): Launched just once, a few weeks ago, to near silence. Hardly any footprint on PH beforehand. The error, in hindsight, wasn t the launch itself. It was arriving as an unknown on that day. So your advice about maintaining the page year-round hits home default neglect made it obvious. Going forward, I ll engage in discussions like this between ... ... repeated efforts, or has it always been worthwhile? Comment from Nika(@busmark_w_nika): @farrukh_ahmed8877  To be honest, each other's launch seemed to me less successfulessful, but I think it was because of very big competitors

... hard to negotiate fairly when you dont have any reference point. Comment from Alina Sprengele(@alina_sprengele): @kassandra_ripley  Exactly. The combination of a meaningful retainer and 10% equity was what made it feel so off in hindsight. I also like your point about advisors proving value before formalizing anything. A small amount of equity tied to clear scope, vesting, and actual contribution feels very different from handing over a co-founder-sized stake upfront. Comment from Alina Sprengele ...

... time thing. A number that drifts slightly off for a few weeks in a row. A task that keeps getting rescheduled instead of finished. None of those look urgent on the day they happen. They only look obvious in hindsight, once they have already turned into something bigger. Curious what your early warning sign looks like, the thing that in hindsight

... into a much pricier tier than you expected. Curious to hear from other makers and users here: What's a pricing structure that seemed reasonable at signup but turned out to be a bad deal in practice? In hindsight, what pricing-page signal should you have caught before paying? As a maker, how do you think about pricing transparency for your own product to avoid this exact reaction from users? Would love this to turn into a useful reference ... ... both users evaluating tools and founders designing their own pricing pages. Comment from Rittwika Roy Choudhury(@rittwika_roy_choudhury): @alieksia  The "$1.99 vs

... every week. By the time someone actually complains, the real damage happened weeks earlier and everyone just called it a busy season. I am curious what the earliest tell has been for other founders, the one signal that in hindsight always shows up before the complaint does. What is yours, and did you catch it in time or only see it afterward ...

... proofread myself. It just kind of quietly stopped needing to be. I honestly don't know if my writing improved or if I just stopped being the one to review it, which is a strange thing to notice in hindsight. They seem to be very different things but from the outside they probably look the same. I m curious what that has been like for other people who write a lot for work has it changed how carefully you actually ...

... canvas, it generates clean Bootstrap HTML, and you can push it to a live URL from inside the same app where you already have the client's brief, budget, and contact info. No Figma export, no copy-pasting into VS Code, no separate hosting step. That full path, from blank canvas to a URL you can text your client, is something I haven't seen in Bonsai, HoneyBook, or Dubsado. They don't attempt it. The CSS tools and color ... ... pickers are honestly the weakest wedge in hindsight

... what their actual evaluation criteria are. three weeks of follow-up emails later I found out procurement had a competing tool already shortlisted and my "yes" was really just "this doesn't look bad." the tell in hindsight was that they never asked about pricing tiers - genuinely interested buyers usually poke at that pretty fast ...

... flag to quote the draft verbatim before we'd trust it if the quote doesn't match character-for-character, we drop the flag and log it as a reviewer error instead. Felt like a dumb-simple fix in hindsight, but we didn't think of it until we caught the reviewer doing exactly that in production. Anyone else running multi-agent review setups hit this? Curious if there's a more elegant way to handle it than string-matching ...

... from Sabber Ahamed(@sabber_ahamed): @nolan_vu  makes sense, that's basically our rule too. do you have a gut check for the ones that look like a one-file tweak but aren't, or is it always hindsight? Comment from Sabber Ahamed(@sabber_ahamed): @galdayan   @nolan_vu  that reframe is right, it's a review habit gap not a model limitation. curious if the "show thinking early" step stays sticky once you trust an agent more ... ... hoping it works out throw a vague prompt and pray. Kind of a tell on its own honestly, no need to even see the output yet. Comment from Nolan Vu(@nolan_vu): @sabber_ahamed  Honestly it's mostly hindsight

... market fit. Hoping to leave this session with a clearer idea of which habits I should keep strengthening early on. Comment from Ashir Murtaza(@ashir_murtaza1): I have always wondered whether great founders are identified through patterns or if hindsight makes it seem obvious. looking forward to hearing Alice's perspective on separating genuine signals from luck. Comment from Ghost Kitty(@ghost-kitty-9993672): Comment Deleted Comment from Ghost Kitty(@ghost-kitty-9993577): Comment Deleted Comment from sandeep kumar ... ... signal has proven most reliable over time, and whether that signal evolves as markets and founder journeys change. Comment from Joseph Parker(@joseph_parker3): I like the premise, although I wonder how much of founder evaluation is actually measurable versus

... every product creator asks themselves. For me, I jumped in on day one after launching and never looked back. You have to believe in yourself before expecting others to believe in you. 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 ... ... garg9): For me it ended up being the opposite of what I originally planned I built most of Naxely quietly first, then started talking about it right around when I had something people could actually try, not before. In hindsight

... found it by getting bitten myself. I was dogfooding a scan on my own inbox and noticed an annual app subscription I knew I had wasn't showing up. Digging into the logs, the reason was obvious in hindsight: yearly subscriptions only send one receipt a year, and our scan window only looked back 90 days so their single receipt was almost always outside it. The fix was to extend the look-back window to a full year specifically ...

... heavy in tech, but imagine the rest of population. 85% of people do not have any clue what is happening :) Comment from Moeez(@moeez1): I think the cost debate misses the real shift, it s less about AI vs humans and more about where trust breaks in the workflow. In outbound, we built Dialbotix as an AI Voice SDR to handle the first layer of outreach and qualification. What we noticed wasn t cost savings, but that teams stopped caring ... ... technical problem, that's a communication one and no model can fix it. Comment from Erika (@erika_th): I learned this the hard way. I spent over $170 in API costs while building an automated reporting script. In hindsight

... user___1702026e6f946759d1d798a): This is also one of the first things investors look for. A polished demo can attract attention, but if someone cannot quickly understand who has the problem, how painful it is, and why the current alternatives are inadequate, the conversation hits a dead end. Based on my own experience and a friend who works at 1752vc, the strongest pitches often make the problem feel inevitable before they spend much time explaining the product. Comment from Martin Tanner ... ... that's a very important distinction. That could also explain why you're attracting more men, who are looking for a real solution vs

... like the point about understanding why an account was suggested that turns the list into learning, not just more leads. Comment from Elias(@elias_motionfy): Lookalike-from-existing-customers is one of those things that's so obvious in hindsight that it's embarrassing how many teams skip it. Most outbound campaigns get built from ICP guesses instead of paying customer reality. I'm running cold email to ~160 manually sourced DTC beauty leads right now, and the only reason ... ... like. The piece that's hard isn't finding lookalikes. It's defining the "alike" axis correctly. Two brands with identical Shopify revenue, traffic, and ad spend can be completely different customers if their creative cycle is 1 week vs