... 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

... threads daily has done more for actual visibility than follower count ever has 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 launches ... ... worth to build a product page throughout the year. 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

... does he want to invest his time in "shit" project? 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 KASSANDRA EMARD(@kassandra ...

... 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 Nolan Vu(@nolan_vu): @galdayan  This is so real, the plan review step is the first thing that gets skipped when you're in a rush, and it's exactly when you need it most. Watched ... ... 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

... ceciliatran): Great topic, and it maps almost exactly onto a problem I live in on the talent side: how do you evaluate a person before there is a track record to point to? A few people here raised execution versus potential, and I would add one thing. The most reliable early signals tend to be the messy ones nobody bothers to measure: how someone talks about a problem they have not solved yet, what they build when ... ... asking, how fast they update when they turn out to be wrong. Those do not fit neatly on a scorecard, which is exactly why they get missed. Really curious what Alice says about separating real signal from hindsight

... 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 I think I left feedback on the table by not talking earlier, same as what you're describing. But there's a real tradeoff on the other side too: if you promote before you have anything working, you're asking ... ... honest experience is: PH gives you the venue, but the traffic has to come from somewhere, and "somewhere" is the audience you built (or didnt) in the months before. that said, i dont think "before the product" vs

... 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 ...

... drastically change in 5 years. Nevertheless we need to be involved to be relevant. 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, hiring someone for that specific task probably would've cost less. AI is amazing, but it's definitely not always the cheaper option especially when you're iterating a lot or letting agents run freely. Comment from Deepanshu Garg(@deepanshu ... ... garg9): @busmark_w_nika  Ha, fair. Guess the real AI disruption is teaching companies to read their own spending reports. Comment from Moeez(@moeez1): I think the cost debate misses the real shift, it s less about AI vs

... more than any UI polish did. So yeah, I d say naming the problem is the actual unlock. The demo just has to not get in the way of it. Comment from Viraj Parab(@viraj_parab): StartupHQ to organize competitor research, validate ideas, and keep my roadmap focused. It removed a lot of the "what should I do next?" moments. Now the challenge is exactly what you mentioned: getting distribution right. Comment from Mincheol kim(@mincheol_kim): @anna_ludwinowski ... ... Kozlo(@wvitalik): I look for the problem/need first. However, note that some products are solving the problem of a bad existing UX and user interface (think about the goal "to manage virtual private servers" and solutions via the terminal VS

... just display layer. Comment from Sudipta Biswas(@sudipta_biswas4): @ritesh2503  The crazy part is most people ignore it. 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

... example, launching halfway through the day instead of right at the start of a new day). And many more. For me personally, it was relying too much on my follower count. It didn't guarantee visibility, and in hindsight, I would have invested more time in personally reaching out to LinkedIn and Twitter friends to ask for support. What was the most surprising lesson or realisation from your own launch? Comment from Jens Thenakara(@jens_thena): @oshylabs   Thank ... ... axis, and I optimized the wrong one. I had a launch that got attention but didn't convert, and my instinct was "the launch mechanics were off, pick a better day, line up more support." The actual finding, in hindsight

... Usually, when you start something, you don't have the experience you have now, and you would have done things 100 times better with hindsight. It's not much different in business. What did you think was a good idea before, but now, in your career as a founder, do you regret it? So I'll start with a few examples: When I started yoga business/classes, I didn't really promote it, I just practised in my room and thought ... ... have to talk about it and I learned that way too late Comment from Nika(@busmark_w_nika): @daniel_nwankwo  but even that freedom is limited :D Comment from Rivra(@rivra_dev): Great question, Nika. Hindsight

... value. Comment from Ghost Kitty(@ghost-kitty-9559276): Comment Deleted Comment from Mickael Chiron(@hivin): Good point, personal brand helps early traction, but it can also bias feedback and hide product flaws. Maybe the real question is less brand vs product and more how to get honest users early without distortion. Have you seen cases where strong founder visibility actually blocked real feedback? Comment from Ghost Kitty(@ghost-kitty-9554895): Comment Deleted Comment from Faysal Fateh(@faysal_fateh): @evelyn_chen6 ... ... doesn t need a savior complex Comment from B ra eker(@busra_seker1): @tonyspiro  Attention can bring the first users but the product still has to earn trust after that. Comment from Sourav Mahapatra(@sourav_mahapatra1): The framing 'before vs

... think this will help in the long run. Comment from Maliik(@maliikb): I'm in the middle of this right now, so I can share what's working and what isn't in real time rather than in hindsight. I've been building a recall alert app solo for months. 13 countries, 41 data pipelines, 991 tests, 14 languages. The app is live, users are using it, but the "big launch" hasn't happened ...

... 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 ... ... promotion feels wrong. But you still have to tell people you exist. What's the first thing you'll do differently with your marketing this time? Comment from Miles Anthony(@miles_anthony2): @imed_radhouani  The idea of "ready vs

... months ago, we ran an experiment with our own data. At Rankfender, we tracked 5 of our own competitors across 8 AI systems. We log their share of voice, citation velocity, content gaps, platform variance. Months of raw numbers sitting in a dashboard. I pulled 6 months of data and fed it into Claude. One question: "Based on this, who is most likely to overtake us in the next 6 months? Show your work. Use the data. Don't summarize ... ... Give me the numbers." The answer changed how I think about competition. The dataset: 5 competitors