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

... Staff" and explain the architecture. It fell flat. What actually landed was naming the specific mess: running a software company, a care home, and a cafe at once, and never being sure which one actually needed me that day versus which one was just being loud. Once people recognized that feeling, the product made sense on its own. So I'd say the demo's job isn't to sell the problem, it's to prove you understood it correctly ... ... 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

... 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 ... ... compliance reviewer all named, builds a strategist record that is actually stronger than the engineer one once you set up the format. happy to walk through if useful. Comment from Anuj(@getosmo): Made a version of this jump building OsmO