Hey Academy, Join the AI Architects for support or to learn how to build your own agentic software. Most AI agents are a pain to set up—and that keeps people from actually using them. So I built an easier system you can use for free. In this video I’ll show you the Popebot in action by creating an email assistant that monitors my Gmail every 30 minutes, kills the spam, sends me Telegram DMs about urgent emails, and can even reply on my behalf. All built just by describing what I want. You’ll also see powerful features no other agent has: multi-user support with smart message routing, scoped agents that stay focused, seamless switching between chat mode and Claude Code CLI, voice-to-text, and a built-in scheduler. By the end, you’ll know exactly how to install it and start building agents to run your own life 24/7.

I run a UK digital agency and one of my clients is a builder who sends me raw build project videos via WhatsApp. We turn these into branded shorts and reels for YouTube, Instagram, Facebook, and Nextdoor. Current setup ($100/month): My VA in Nigeria handles the whole pipeline manually: • Downloads videos from WhatsApp • Runs them through Descript (adds voiceover when client’s ops manager hasn’t recorded one) • Polishes clips in Opus Clip Pro • Adds logo and branding • Writes captions • Schedules to YouTube, Insta, Facebook • Manually posts to Nextdoor via GHL workspace He’s reliable, the quality is OK, and at $100/month it’s hard to beat on cost. The AI-automated alternative I scoped: Make.com + Claude API + Creatomate (branding) + ElevenLabs (voice clone) + Opus Clip Pro API + GHL scheduling. Roughly £60-75/month in tooling, plus probably 20-30 hours of build time on my end. The build would handle: WhatsApp ingestion, Claude analysing each video and writing platform-specific captions, voiceover generation when needed, automated clipping, branding overlay, scheduled posting across all platforms, with one approval gate before publishing. Where I’m stuck: On paper the AI route looks cheaper long-term, but when I actually compare: 1. My VA costs $100/month flat, no build time, no API surprises, deals with edge cases naturally 2. The AI stack is ~£60/month in tools but needs my time to build and maintain, and breaks when APIs change or videos are unusual 3. Nextdoor still needs a human click either way (no API) 4. Voice cloning needs careful setup and consent 5. The VA can also handle other ad-hoc tasks the AI can’t My questions for the group: • Has anyone built something similar and found the maintenance cost was higher than expected? • Is there a hybrid worth considering — AI for the captions and Claude analysis, VA for the video editing and posting? • Am I overcomplicating this when a good VA with the right SOPs is genuinely the more cost-effective answer?

Hey Academy, For support join the AI Architects. The $200 subscriptions and API fees make it hard to get started with AI coding—so I built a solution that runs Claude Code 100% free on your computer using local models. In this video I'll walk you through a live demo of the full setup: free local models through Ollama, budget-friendly alternatives like DeepSeek and MiniMax, and a flexible interface that supports multiple coding agents including Claude Code, Gemini CLI, and OpenAI Codex. You'll see how to switch between chat mode and interactive mode, configure any LLM provider you want, and use the complete development environment with a built-in editor and shell. I'll also walk through the entire installation step by step so you can get up and running today—whether you're a complete beginner or an experienced developer looking to cut costs.

I woke up this morning to 10 fresh podcast episodes. Fully researched. Scripted. Narrated. Visuals timed to every beat. Published to YouTube, RSS, and my own website. I didn't make any of them. A machine on my desk did. While I slept. I launched these channels at the end of February. It hasn't been a month yet. Some channels are pulling 1,000+ views and gaining subscribers - with zero ads, zero promotion, zero outreach. But here's what I need you to understand: this is not a prompt. When people hear "automated content," they picture someone typing a topic into a chatbox and hitting publish. That's not what this is. That's not even close. What I built is a multi-stage production pipeline. Not a single generation step - a sequence of independent systems, each with its own job, its own rules, and its own quality bar. Every stage has to pass before the next one starts. If something isn't good enough, it gets caught, flagged, and redone automatically. Here's what that actually means in practice: Every episode starts with real research. Not "summarise this topic." Actual source-finding, fact-checking, angle evaluation. The kind of editorial groundwork a good producer would do before writing a single word. Most automated content skips this entirely. Mine can't - the pipeline won't let it move forward without it. Then there's the writing. And this is where I spent most of my 45 days. I didn't just generate scripts - I built an entire set of rules around how spoken language works differently from written language. How rhythm changes when someone is listening instead of reading. How a pause lands. How a transition should feel. Early versions sounded like a textbook. Now they sound like someone talking to you. After the writing comes the part most people don't think about: quality control. Every script gets evaluated across multiple dimensions before it moves on. There's a hard pass/fail threshold. I've watched the system reject its own output dozens of times and come back with something genuinely better. Nothing mediocre gets through. That's not a nice-to-have - it's the reason the content performs.

Hey Academy! To get support join the AI Architects! I built a free AI coding platform that lets you spin up a 20-person dev team in under 60 seconds—and manage everything from your phone. In this video I'll walk you through the PopeBot's new cluster mode, where you can create teams of AI agents that work together automatically. You'll see how to define roles like CTO, security expert, UI/UX designer, and developer—each with their own system prompts, triggers, and concurrency settings. Connect it to GitHub and your agents will pick up issues, create technical plans, review code, and submit pull requests without you lifting a finger. I'll also demo the new Claude Code interactive and headless modes, show you full mobile support for coding on the go, and walk through the complete setup process so you can launch your own cluster for free.