... your users, not for you. Comment from Adana Marukhyan(@adana): @itzhaydar  In our case with RunEvr, even a small popup window can have many criteria and relations to take into account when designing it. Are you building something right now? Comment from Adana Marukhyan(@adana): @itzhaydar  Agree, of course. I think more about complex products, where involving a designer can actually help the developer ship faster and hit the goal right

... david_martin_suarez  I would love to hear more about that. We might be able to help. Comment from Sabber Ahamed(@sabber_ahamed): @busmark_w_nika   @abdullah_javaid3  the random-id-on-activation trick is the right call. weekly active hides exactly the churn-vs

... even when the value is clear. Comment from Abdullah Javaid(@abdullah_javaid3): @somesh_putatunda  Actually yes. The earliest signal shows up before the third person ever appears: someone asking a question back instead of just reacting. It happened right here with your first reply, and looking back most of the threads that ended up compounding for me started that way, with a real question instead of agreement. Comment from Abdullah Javaid(@abdullah_javaid3): @somesh_putatunda  Yes, ones with ... ... question with a real answer required filters most of the room out before they even start typing. Comment from Abdullah Javaid(@abdullah_javaid3): For me it's not finding users, it's telling early which channel is actually compounding versus

... still not reliably tell time from a clock face. Genius and incompetence living in the same box, and no obvious seam between them. That gap between capability and reliability is the thing most makers are quietly getting wrong right now. The instinct is to open a leaderboard, pick whatever's at the top, wire it in, and ship. The demo is dazzling. Then production happens. Across enterprise deployments this year, teams are seeing roughly a 37% gap between benchmark scores ... ... that should scare you isn't the crash. A crash tells you something broke. The dangerous one is the silent failure the agent that returns a confident, clean, well-formatted answer that happens to be completely wrong, and sails right

... scoped to the thing being acted on, not the thing doing the acting, and that's a harder join given session ids are all you're asserting on the tool-action side right now Comment from Jernej Jan Ko ica(@jernej_jan_kocica): @aadilghani  You are right

... been building Amazon affiliate / review sites for years, and something I keep noticing: we all quietly grind on our own sites and almost never compare notes with each other. So let's fix that. I'll start. Right now most of my time goes into a small review site in the watches niche. A few things I've learned the hard way: - The niche matters more than anything else combined. I've picked good ones and terrible ones ... ... sting every single time. But honestly? I still like it. There's something satisfying about an asset that's genuinely yours and quietly does its job. Curious who else here is in the game: - What niche are you building right

... suddenly lose access to all AI. But what happens if , one day, access to the leading American models is restricted more broadly? We would still have European models, open-source systems we can operate ourselves, and Chinese alternatives. But there is no guarantee that another major power would never make the same decision to protect its own strategic advantage. AI is no longer just another software category. It is becoming infrastructure. It will shape education, healthcare, national security, research ... ... finance, software development, manufacturing, communication, and almost every industry Europe depends on. And right

... marketing a product well has become really hard because competition is extremely high, especially thanks to AI. That s why I think the right time to launch isn t just when the product works, but when you also have at least a basic plan for how to stand out and get in front of the right

... side project we re experimenting with, built almost entirely through AI. I m not a developer. I can t read most of the codebase. But I shipped a feature that three users have already told me feels exactly right. And I cannot explain to my team how it works. Not the user-facing part I designed that. I know what it should do, why it matters, what emotion it should trigger. I wrote the spec as a conversation with ... ... asked me to walk through the implementation, I froze. I couldn t explain the architecture. I didn t know which database calls were happening or why the loading state worked the way it did. I just knew it felt right

... product was built, because I needed to have the idea validated and keep momentum while building it. I do not know whether this way is good, because the product can flop too, or be copied. When is the right time to promote a product when you are a beginner in launching something? Comment from Nika(@busmark_w_nika): @virko_kask  The thing is  how would you promote that waitlist? :D Now, I have only 18 submissions :D Comment ... ... launched yesterday and got like 6 upvotes total. So I need to practice what I preach, I guess, and see if it works next time. Comment from Bill Davis(@billspaced): I m living this from the other side right

... everyone, We just opened up Causo.ai for sales lead gen. We originally built Causo for fundraising: help founders find the right investors, research why they fit, and write proper outreach instead of sending hope this finds you well slop to every VC with a pulse. Then people kept asking us the same thing: Can this work for sales too? So we built it. The basic idea is simple: Most sales tools start with a database. You filter by industry, headcount ... ... hard part of outbound is usually not sending the email. It is knowing who is actually worth emailing and what the hell to say to them. Would love feedback from founders, sales people, agencies, and anyone doing outbound manually right

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

... problem, figured other people probably hit the same wall, but I don't know yet if that's true or if this is the right way to solve it for them. Hardest part right

... even existential (where legal costs can put your personal assets at risk). What was the hardest problem you've faced in business so far? Comment from Nika(@busmark_w_nika): @alihabib_  According to what you have chosen the right people into your team? :) Comment from Nika(@busmark_w_nika): @oshylabs  How can I know which of my ideas I should kill? Comment from Nika(@busmark_w_nika): @aggie_ho  How do you approach marketing ... ... dodging that conversation until it is too late, and I think that avoidance quietly does more damage to a team than almost anything else. The lesson I keep relearning: great tools and great strategy still fall apart without the right

... Ayd n(@hakanwd): my desktop, downloads, documents i mean every single place. Comment from Andrea Sofia(@andreasof): My 'vibe coding' folder, literally a bunch of screenshots and zip files all over the place. Comment from Andrii Krugliak(@theuniverseson): @tony2742  Right, and the trap with the boring-maintenance stuff is that automating it quietly is easy, but trusting it ran correctly is the hard part. A misfiled doc you never notice is worse than a messy folder ... ... easily reach the thousands club. It's a self-cleaning ecosystem... or so I tell myself. Comment from Harini Mukesh(@harini_mukesh): Some people will have the habit of save everything on desktop to access it quickly right

... gate at write time a claim from a weak source doesn't land with the same weight as one anchored to something checkable. So it's not just content sitting in a bag.    Your fact vs conclusion split is the right

... stated the intent and the tool call that's the action. We just don't diff them yet. And the "right thing, wrong file" case is the one worth handing to a machine, because it reads as correct and slips right

... Alfredo, a solo founder from Spain. After years in marketing, sales, and entrepreneurship, I m reinventing myself around AI not as a guru, not as a casual observer, but as someone trying to turn experience into useful products. Right now I m building two things: AllAi1 because the problem is no longer finding AI tools. The problem is knowing which ones are actually worth your time, money, and trust. sologang.io a pocket C-suite for solo founders. You bring ... ... mohamed_afrideen): This resonates, Alfredo. Same path here, marketing background, now building with AI instead of only marketing other people's stuff. AllAi1 especially. I run a small account around exactly that, which AI tools actually earn their place vs

... building VertoX, a real-time AI translation platform that preserves your voice, tone, and emotions across languages. Over the last 2 years, I ve faced a lot of challenges while building it. Finding the right team. Choosing the right

... tell me what they wish existed. I haven't A/B tested "anonymous launch vs. founder-visible launch" but I can tell you that nobody has signed up and handed me their family's allergy data without first seeing that there's a real person behind it. That's been the signal so far. Comment from Ricky Singh, MBA(@xquest): Agree, and I think the right

... 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 ... ... nolan_vu): maybe the price is still quite too expensive for even enterprise to charge for? Comment from Nolan Vu(@nolan_vu): This hits close to home. We went through something similar. Built what we thought was the right

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

... Right to Repair stuff (and 2026 updates) now says electronics need 7-10yr parts + tough e-waste rules. But us consumers? We gotta prove service history, serials, ownership at repair shops without digging thru email/paper mess. Asset tracking apps might be the fix: one GDPR-safe vault for full timelines (bill warranty repairs resale). Thoughts: Repair shops demanding digital proof by 2027? How you building for this? DPP schemas? EU data residency? Right

... incredible at writing code. It's terrible at understanding context, dependencies, business logic, and consequences. It doesn't know what you didn't tell it. It doesn't ask questions when something is ambiguous. It assumes it's right. The best work we got wasn't when Claude coded alone. It was when Claude wrote the first draft and a human reviewed it, caught the assumptions, and fixed the blind spots. The hype is real. So is the mess. What ... ... will need to put in for a desired customer satisfaction, just that in this case we are our own customers, in other words, how many human hours are needed for a 92% confidence that nothing is gona break vs

... Last month, I did something that felt slightly insane. I took our product description, fed it into ChatGPT, and asked it to build a competitor. Not a parody. A real competitor