... tools we simply can t imagine our day without. If I had to pick a few AI tools that have become part of my daily workflow, these would be: ChatGPT + Claude summarising and improving text (and Codex in VS Code for coding) Grammarly AI correcting and improving my English Figma with its AI prompting helps me a lot with improving my graphic design ideas Google Gemini for note-taking from Google Meet, plus AI features in Google Sheets and Docs ... ... that remove a category of attention, not just summarize it afterward. Claude Code is one. Good meeting capture is another, but only when it turns a call into decisions and next steps instead of a long transcript. While building OsmO

... answers here are attacking the evidence axis, so let me push on the other half of your question - what would still stop me enabling it. I build a consumer product where people forward their actual phone calls to it (OsmO), so the ask is arguably more invasive than a keyboard. Two things surprised me running that gauntlet. First: almost nobody verifies. Not "few" - close to zero. We published the evidence and watched the click-through. It is still worth publishing ...

... everyone, I'm the founder of OsmO. Quick story on why I'm here: I kept missing calls that actually mattered (a callback from a clinic, a client trying to reach me) because they were buried under spam and robocalls I'd long stopped answering. The habit of just letting it ring was quietly costing me real things. So we built OsmO

... Comment from Anna Ludwinowski(@anna_ludwinowski): @getosmo  "The receipt IS the scope" - YES, that's a sharper way to collapse messaging and product into the same thing. Most people treat those as two separate problems (what we say vs. what we build) and you just made them the same mechanism. Comment from Anna Ludwinowski(@anna_ludwinowski): @getosmo  That's great - you're further along than many! But that's the hard part too, right? Because the calibration ... ... Zaitzow(@dzaitzow): @anna_ludwinowski I guess if I really think about it - it helps solve the 1 to many problem for lead capture - making every lead get something really unique at the end of the intake survey / quiz funnel VS

... just shift shape. Would love to connect and trade notes on how you're navigating adoption inside your customers' orgs, that's where all the interesting problems are Comment from Nolan Vu(@nolan_vu): @getosmo  Thanks Anuj, the OsmO example is such a perfect illustration of this shift. "As an IC, correct is the scoreboard. As an owner of adoption, behavior change is the scoreboard" should honestly be printed and taped above every engineer's desk before they take ... ... reasons-to-say-no than adding capability is exactly where I ended up too, but nobody warned me it would take a year to internalize that mindset shift. Comment from Anuj(@getosmo): Made a version of this jump building OsmO