Took the plunge and deployed it on my own AWS infrastructure. For those who've been curious but haven't pulled the trigger yet - it's real and it works. My setup: - Isolated VPC with private subnet (no public IP) - Access via Telegram only - Zero exposed ports - SSM for admin - Encrypted storage, locked-down permissions First conversation hit and Claude responded through Telegram. Wild feeling having an agent just... waiting for me. Security was my main hesitation. Solved it by putting everything behind NAT with no inbound routes. The agent can reach out (APIs, Telegram) but nothing can reach in. If you're on the fence - the infrastructure side is more approachable than it looks. Happy to compare notes with anyone else who's deployed.

Hey everyone! Quick update on how coaching calls are working going forward. 🔄 WHY THE CHANGE I'm going heads-down on EMS Soap for the next 6 months. We're getting SOC2 and HIPAA compliant, building out the marketing funnel, and a bunch more work. It's a lot, and I need to focus. But I don't want to abandon the community. So Patrick and Paul are stepping up to help lead calls. I'll be on about once every four weeks, and they'll rotate the other weeks. 📞 HOW CALLS WILL WORK These calls can run 2+ hours. I want to make sure we're respecting everyone's time. Especially those of you who actually show up. Here's the new structure: 👉 Reply to this post with your questions before the call 👉 If you submit a question and you're on the call, you go first 👉 We work through questions in the order they came in 👉 Then we open it up for everyone else If you can't make the call but want your question answered, drop it in the comments. We'll get to it. But priority goes to people who are there. The goal is simple: if you're taking the time to show up, you shouldn't have to wait behind questions from people who aren't even on the call. 🔗 NEW ZOOM LINK (save this) https://us06web.zoom.us/j/81995207847?pwd=Xe6u6LmIQOmCP5VTnOwWYjDBfZNKGB.1 📅 WHEN Tuesdays at 6PM ET (same as always) Looking forward to seeing you on the calls!

VIEW RECORDING - 165 mins (No highlights) Key Takeaways - Automated Training Creation: Patrick built a system that generates a full training course (NotebookLM, slides, video) from a single Claude Code project by auto-extracting patterns from the dev conversation. - Advanced RAG Architecture: Scott implemented a 3-layer RAG system in NeuralSpark, using a Recursive Language Model (RLM) to have the LLM intelligently "hunt" for information, solving context rot and improving accuracy. - Enterprise AI Consulting: A new business opportunity was identified: helping companies securely adopt agentic AI (e.g., Claude Code, Cowork) to bypass productivity-crippling internal IT policies. - Agentic Workflow Updates: Brandon is releasing new Shipkit videos and commands (e.g., worktree, task review) to optimize agentic development, enabling parallel feature work. Topics The Future of Work: System Creators vs. Task Doers - Morgan's Workflow: Automated a non-programmer's task (creating product sheets) from days to <10 minutes using skills in the Windsurf IDE. Process: Markdown → HTML (styled) → PDF + meta.json for product pages. - Brandon's Cowork Example: Resolved a complex Excel matching problem (50 parts x 50 centers) in 5 minutes by pasting the problem description and file into Cowork. - Consensus: The future workforce will be system creators and managers, not task doers. People must "level up" to think at a systems level, as AI will automate individual tasks.

Quick workflow I stumbled into that's been surprisingly useful. Instead of manually analyzing a platform or community, I have Claude Code do it: • Navigate to the target site • Screenshot key pages • Analyze content patterns • Report back structured findings Did this for this Skool community yesterday. In about 10 minutes I had: • Community size and activity levels • All the content categories • Which post formats get engagement • Platform-specific formatting quirks (like code blocks not rendering) • Tone patterns from high-performing posts The browser automation caught things I would have missed. Like discovering the platform doesn't render markdown properly — would have built the wrong thing without that insight. The prompt pattern is simple: "Navigate to [URL], analyze the content structure and engagement patterns, tell me what resonates with this audience." Works for competitor analysis, community research, content strategy — anywhere you need to understand what actually works vs what you assume works. Anyone else using Claude's browser tools for research like this?

Hey guys, I wanted to recommend this article from article from Alex Razvant (I mentioned him in the call today). His article has really important resources, specially on deploying AI systems: https://read.theaimerge.com/p/the-smartest-ai-engineers-will-bet?utm_source=post-email-title&publication_id=2799726&post_id=184113282&utm_campaign=email-post-title&isFreemail=true&r=1i4qau&triedRedirect=true&utm_medium=email Check it out!