... noticed a pattern in my own product work: When I'm deciding what to build next, it's very easy to make a feature list. "Add this." "Improve that." "Users might need this." So I tried changing the question. Instead of asking: "What feature should we build next?" I ask: "What assumption are we still uncertain about?" For example: If we think users will pay for a product, the uncertainty isn't "should we add Stripe?" It's: "Will someone ... ... build nothing and investigate the assumption first. I've found this especially useful while working on AI products, because AI makes it so cheap to turn an idea into something that looks finished. The harder part is deciding

... leadership." Copy, paste, post. Zero lived experience, zero original thought. It's just AI slop in a blazer. AI-written emails to people who matter. Your client can tell. Not because the grammar's off because the warmth is. VS GOOD AI JUDGEMENT Using AI to actually look at what a candidate did. Not keyword-matching a CV pulling apart their portfolio, cross-referencing their claims. You still decide

... than building an agent on top of it. 2. Pay yourself properly. There is already so much going wrong every day as a founder. You re earning far less than you did before, with none of the stability. I decided to pay myself the least on the team so we could put as much money as possible into the product and the people building it. That sounds honourable. In reality, you re adding more pressure to your life at exactly ... ... hear back about a $1 million investment. Imagine how crazy that felt. May We planned a three-week fundraising window and filled 75% of the round. Then a major UK VC offered to take the whole thing. We decided

... whatever tool can do it. Your product isn't the destination anymore. It's a capability the agent picks up mid-task, uses, and puts down. Nobody onboards. Nobody sees your landing page. The agent reads your tool definitions, decides if you're the right instrument for the step it's on, and calls you or doesn't. That reframes a bunch of maker questions at once. Your tool descriptions are now your marketing copy, and the audience ... ... model deciding

... book but not pay. somewhere, someone made that call. but how? was it intuition? a security review? a near miss? a customer asking a very uncomfortable question? because here's what i keep noticing: most teams haven't actually decided what their agent is not allowed to do. they've just decided

... start to lose my understanding of what it actually does. More features make sense only when the product is already established and wants to serve the needs of different types of users [cover a bigger market]. How do you decide how many features your product should have? (Are you a maximalist or a minimalist?) What helps you decide

... exact action and context each time, and can the user see why it decided to approve or steer something? Comment from Flavio Riper(@flavio_riper): I agree that reach is an important part of risk, but I do not think it tells the whole story. With Navlio, I see blast radius as a mix of reach, context, permissions, and evidence. The agent should not decide

... building a product around relationship-driven outreach, and one workflow keeps coming up: When someone has a goal like hiring, sales, fundraising, partnerships, or career exploration, the hard part is often not writing the message. It is deciding who is actually worth reaching first, why now, and what the smallest good ask should be. I am curious how other makers and operators handle this today. When you are trying to reach someone through your network: 1. Do you start with ... ... testing is: goal -> who to reach -> why now -> warm path -> first message If you work on sales, partnerships, hiring, fundraising, or career outreach, I would value your read on whether this matches how you actually decide

... goal: if you want raw eyeballs go Tue-Thu, but for a badge/ranking with a modest following a weekend can punch above its weight. Comment from Sabber Ahamed(@sabber_ahamed): @busmark_w_nika   @abdullah_javaid3  the invitation vs favor framing is the most useful line in this whole thread. i caught myself drafting DMs that were basically upvote asks in a nicer outfit. what actually worked was showing up in threads like this one for weeks with nothing ... ... most important thing is to launch as soon as you can and keep iterating to improve, and keep launching Especially with how fast everything is moving with AI, waiting for a perfect time to launch will just let competitors

... businesses at once, and the hard part was never information, it's attention. Everything has a dashboard, but nothing tells you which fire is actually worth putting out today versus which one will burn itself out on its own. Curious how other multi-business folks decide

... worker. For UI testing, a remote headed browser is not just a convenience. It changes the debugging loop. Instead of asking "what did the script think happened?", you can ask "what did the user actually see?" ### Harness Code vs Local Agent Harness Another important decision is where the agent capability should come from. One option is to build the entire reasoning layer yourself: call an LLM API directly, manage prompts, retries, tool calls, screenshots, JSON parsing, and safety rules. That ... ... gives maximum control, but it also means the test harness becomes an AI platform project. The alternative

... Been thinking about this after a few good conversations here lately: there's a real tension between building something that flags "this looks off" for you automatically, versus just surfacing the raw signal and trusting the human to interpret it. Too much automation and you risk false confidence, the tool says everything's fine, so nobody looks closer. Too little, and you're back to relying entirely on someone's attention, which doesn't scale past a certain team size ... ... context. But I'm genuinely unsure that's the right call long-term. Curious what this community thinks: Do you prefer tools that flag problems for you, or ones that just show you the data and let you decide

... tarot better when it's human-led, not AI? Try a free card of the day and decide for yourself. Try it here: https://your-tarot.site I've been reading tarot for 15+ years. Most "tarot" sites today use AI-generated scripts that sound generic and hollow. That's not tarot. It's just text. So I built Mysticum a place where you get a real, human-led tarot reading. But I know not everyone trusts tarot (or even knows ...

... keeps the review focused and reduces the risk of introducing subtle regressions just for cleaner code. Comment from Jason Scott(@jason_scott8): I have seen the same pattern where agents always suggest cleaning tested code. How do you decide when the readability gain is worth another careful review cycle? Comment from Esat Turan(@esatturan): My rule ended up almost identical to yours: never a standalone cleanup pass, only when I'm already in that file for a real reason. What ...

... been before? Comment from Ghost Kitty(@ghost-kitty-9930853): Comment Deleted Comment from King Joshua Marcos(@moddy): Honestly just trial and error early on. Let it fully own something low stakes, watched what broke, adjusted from there. The billing/auth vs UI split came out of getting burned once on something billing-adjacent, not from planning it ahead of time Comment from King Joshua Marcos(@moddy): @donna_gerrard  Would probably help me a lot, I don't have one written ... ... that quietly conflicts with something else in the app, and it all still compiles fine. Small tasks that's rare. Big features, way more surface area for that to happen unnoticed. Comment from Megan Scott(@meganscottjb0): how did you decide

... launching Hello Inbox on PH as a B2B email deliverability SaaS. But, there's a back story I wanted to share with the community on how I validated the idea, and scaled to $12K MRR before deciding to build and launch a SaaS solution for my clients. I think this could be useful for startup founders who are trying to validate their business models. Because let's be honest, time is the most valuable resource. Sometimes the biggest lever ... ... deciding

... realizing I had spent the last 8 hours glued to back-to-back meetings without standing up, stretching, or drinking a single glass of water, it hit me: our calendars have become bullies. So, I decided to stop planning and start shipping. I built BreakMode . Think if Sunsama, Motion, and a Pomodoro timer having a baby. Except this baby doesn't force a complex workflow on you, and it doesn't charge you $30/month just to protect your right ...

... asking the question that decides whether any of this works.   @rabnoor_s   Direct answer first: yes, it stores where it came from. Every memory carries an author and an author role, and the role feeds the 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

... thing I keep noticing is that almost everything can feel important when you are building. Posting content, talking to users, improving the product, replying to comments, checking analytics, fixing small bugs, testing new channels, networking, reading advice, watching competitors. All of it can be useful. But not all of it moves the business forward at the same stage. I m curious how other founders think about this. How do you decide

... they ask for. Focus on one thing, but keep testing channels. Build in public, but don t become distracted by content. I m curious how other founders filter this. When you hear advice that sounds reasonable, how do you decide whether it actually applies to your product or stage? Comment from Farrukh Butt(@farrukh_butt1): @kicksaascopy  This is a really good way to look at it. I like the idea that most advice is a reaction to a specific ... ... matching their one experience into a rule. Comment from Sherice Jacob(@kicksaascopy): The contradictions are real but most of it's because the advice is collapsed by stages, so people are compressing "What worked for me in the beginning" vs

... useful. Recently, I ve really liked concepts like @ProblemHunt and @404tomb , where people can validate an idea before building, whether there s actual demand for it, or whether that idea has already failed in the past. How do you decide if something is worth building? And how much time do you usually give an MVP before moving on? Comment from Nika(@busmark_w_nika): @willatsharpread  I had a look at the Problem Hunt because its maker is pretty active ... ... properly because I haven't been building any product. Everybody lack something and we need to learn on our own failures :D Comment from Nika(@busmark_w_nika): @susanne_ertl  Okay, so how many ideas usually have vs

... 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 ... ... review before they'll talk pricing. If they ask, you're in enterprise territory. If they don't, you're not. Comment from Imed Radhouani(@imed_radhouani): @miles_anthony2  Exactly. You don't declare yourself ready. The buyer decides

... this guide isn't just a quick summary. We're going to go deep. We'll explain exactly what Snaply is, how it works, why privacy matters so much for dictation tools, how it stacks up against every major alternative, who it's best for, and how to get the most out of it. Whether you're a solo professional, part of a team, or evaluating dictation software for an enterprise deployment, this is the most complete breakdown ... ... find. Table of Contents Why AI Dictation Matters in 2026 What Makes a Truly Great Dictation App What Is Snaply? Snaply's Core Features: In Depth Why Privacy Is Non-Negotiable for Dictation Snaply 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

... what are the most porpular ones. Several months after, when I had enough active users, I decided to make me extension freemium and I already knew what features I should charge for. Comment from yurukusa(@yurukusa): @Nika Yes the biggest one was when we audited our own product and realized the free version had MORE features than the paid version. 10 hooks free vs