Join us on Zoom Saturday, July 11, 2026 12:30 ET - 13:30 ET we’re opening the AI for Life + AI Bits and Pieces session to everyone, including people outside the community. Join instructions https://us06web.zoom.us/meetings/81545596982/invitations?signature=NQBPitO7KYhO4f7NHMddMYVn476zmP8rjoEmkdhIvzY Meeting ID: 815 4559 6982 Passcode: 050131 Hosts: - 𝗠𝗶𝗰𝗵𝗮𝗲𝗹 𝗪𝗮𝗰𝗵𝘁 from 𝗔𝗜 𝗕𝗶𝘁𝘀 𝗮𝗻𝗱 𝗣𝗶𝗲𝗰𝗲𝘀 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆. - 𝗠𝗮𝘁𝘁𝗵𝗲𝘄 𝗦𝘂𝘁𝗵𝗲𝗿𝗹𝗮𝗻𝗱 from 𝗔𝗶 𝗳𝗼𝗿 𝗟𝗶𝗳𝗲 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝘆. This will be guided questions plus an open forum for practical discussion around what is happening in AI right now, including: - The explosion of AIOS aka Second Brain - AI hot topics and trends - Design and development - Workflows and automation - Process improvement - Tooling, use cases, and real-world implementation Join us for an open working conversation with people who have been building, testing, learning, and applying AI and automations in practical ways. 𝗦𝘂𝗯𝗺𝗶𝘁 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗽𝗿𝗶𝗼𝗿 𝘁𝗼 𝘁𝗵𝗲 𝗲𝘃𝗲𝗻𝘁 𝗳𝗼𝗿 𝗰𝗼𝗻𝘀𝗶𝗱𝗲𝗿𝗮𝘁𝗶𝗼𝗻. We’ll kick things off with pre-submitted questions. Simply submit your question(s) in the comments below, or direct message me in Skool. ✨ Claude will pick the question order. And of course bring questions, examples, workflows, problems, tools, or ideas you want to discuss during the open forum. Hope to see our friends there: @Ron Nedd @Frank Priboy @Gina Wang @Debbie Ai @Pedro Gomez @Usman Mohammed @Nick Mohler @Mike AI Consultant @Diane McCracken @R S @Collin Thomas @Jacob Brodsky @Bradley Kerman @Md. Abdullah Al Mafi @Michele Wacht @Mark Zayec @John Romano @Josh Frison

🏈 My friend @Herman Moore called me, former NFL wide receiver, Detroit Lions. "I'm speaking tomorrow to 125 small business owners. Want to join me and talk about AI?" One day's notice. I built one slide with five points. My strategy, let the room decide which ones we went deep on based on body language and reaction. No fixed script, just reading the energy and following it. Herman worked that stage right alongside me. Great public speaker, no surprise there given his career. We had an easy back-and-forth in front of the audience. 25 minutes on stage. Plain English, no hype. Here's what those 25 minutes turned into: - 12 post talk conversations - 5 leads - 2 solid appointments Results: 1. The Deal: AI OS. A 50-hour build. Not a prototype, not a pilot. A real system going into a real business. 2. The Opportunity: AI Executive Coaching. One business wants me in the room at the executive level as a fractional CAIO, not as a vendor they call when something breaks. 3. The Second Opportunity: Enterprise AI Enablement. AI opportunity mapping, then AI education for their front office professionals. Now here is the important part. I didn't walk in with just a polished pitch. I walked in with the practical AI knowledge that I get from AI Bits and Pieces, and advanced development knowledge from AIS+, and AI for Life where I learn to build complex and trending AI solutions. This is where I: try new things, explore advanced ideas, learn from other professional builder, sharpen the saw, ...and stay ready for that moment you may not expect. If it sounds like a full time plus job... it is. However, this is what enables me to walk in with one slide, a friend who trusted me enough to hand me a mic, and 125 people willing to listen for 25 minutes.

As conversations get longer in LLM Chats, ChatGPT or Claude may give you several questions, recommendations, choices, or action items in one response. Responding to each one can quickly become confusing, especially when you have to explain which item you are referring to. A simple fix: Ask the AI to number every actionable item. For example: 1. Choose between two options. 2. Review a suggested change. 3. Decide what should happen next. Now you can respond: 1. Choose the second option. 2. Make the change. 3. Handle it tomorrow. No copying and pasting. No long explanations. No confusion about which item you mean. Add this prompt to your Project Instructions: “Number every question, recommendation, decision, task, and action item you present. Use a simple numbered list: 1, 2, 3, and so on. When I respond using a number, interpret my response as applying only to that specific item.” It is a small instruction, but it makes everyday conversations with ChatGPT and Claude much faster and easier to manage.

My Claude Cowork inbox triage reads a fresh task file every run. No memory of yesterday, by design, so the reports never drift. This week, that design had a cost. Two calendar items looked like accidental duplicates. - One was two event registration links landing as separate calendar entries. - The other was two client meetings back to back, one of them titled PLACEHOLDER. I confirmed both, in chat: stating, "all four were real, nothing to merge or delete." The next morning, the same two questions came back. Same wording. As if I'd never answered. The challenge was that if I gave it memory of the chats it would stop the repeat questions, but it would also break the fresh-read design that keeps the reports from drifting in the first place. So the fix was simpler: Write the confirmed exceptions into the task file itself, as a standing list it checks before asking anything. How it works now, step by step: - I confirm something, in chat, once - That confirmation gets written into the task file as a standing exception - Every future run checks that list first, before flagging anything - If it matches, the item is reported as settled, not raised as a question Cowork can: ☑️ Read a fresh task file every run ☑️ Check any exception already written into it ☑️ Skip anything already settled Cowork cannot: ❌ Remember what I told it yesterday ❌ Learn a new exception on its own

I read your story in the course and I know your dad is extremely proud of you! It's such a pleasure to learn from you, and I see a lot of myself in your story. Lastly, I love what your dad told you. "Learn it my way, then do it your way" - Thanks for sharing your story! I am going to apply that principle in all that I do going forward.