193: Here's how I find what to automate with AI (and what NOT to)

193: Here's how I find what to automate with AI (and what NOT to)

Get AI-Ready with Kyle’s 5-Day Challenge: https://aiwithkyle.com/join Subscribe and turn on notifications to catch the next live stream: https://www.youtube.com/channel/UChlLglbHDASnoGkbjDeHnQg Summary: I've seen too many people rush straight into building AI agents for tasks that don't need them. This is the corrective. Starting from a viral prompt retweeted by Greg Brockman, OpenAI's co-founder, I walk through a proper workflow audit - how to find the tasks in your actual working week that are genuinely worth automating, and how to spot the ones that aren't. The framework is simple: audit your real work first, then match the fix to the job. A reusable prompt in a Word doc beats a managed cloud agent if that's all the task needs. I also show you how to put your AI into interview mode to surface repeating workflows you didn't even know you had. A practical system for getting more done with less friction. —— Time Stamps —— 0:00 The Viral Self-Improvement Prompt (Greg Brockman + Vaibhav) 4:06 Why You Shouldn't Automate for the Sake of It 5:29 How to Audit Your Real Weekly Workflows 7:19 When NOT to Automate: Avoid the Over-Engineering Trap 9:17 Put ChatGPT in Interview Mode (Live Demo) 13:04 The Simplest Tools First: Prompts, Checklists, and Templates 15:01 Stepping Up: Zapier, Make.com, and n8n Automations 16:10 Managed Agents, Sub-Agents, Scripts, and Custom Apps 17:18 Fit The Fix To The Job: Don't Get Blinded by Viral AI 19:10 Wrap Up + Where to Get the Prompt — Useful Resources —— Find everything else at https://aiwithkyle.com/

192: Google I/O: What You Actually Need to Know

Get AI-Ready with Kyle’s 5-Day Challenge: https://aiwithkyle.com/join Subscribe and turn on notifications to catch the next live stream: https://www.youtube.com/channel/UChlLglbHDASnoGkbjDeHnQg Summary: Google I/O is over, the dust has settled, and the takes have mostly been garbage. So here's what actually matters from Google's big conference this week. Hint: it's not the video generator. The story everyone missed is Google's move to embed agentic AI directly into Search. That's where 70% of their revenue comes from, and they're knowingly blowing it up. I walk through why that's a genuinely brave decision, what it means for SaaS businesses, how it compares to the OpenAI approach, and why distribution will always beat product quality. Also: Gemini 3.5 Flash benchmarks, Antigravity 2's messy launch, and why I'm not particularly impressed with any of it,  but still think this was one of the more important AI weeks of the year. —— Time Stamps —— 0:00 Intro: Cutting Through the Google I/O Hype 1:10 Why Google Conferences Look Flashy But Say Nothing 2:13 Distribution Beats Product: The Slack vs Microsoft Teams Lesson 3:53 Google's Confusing AI Product Sprawl (Jules, Opal, Antigravity, Spark...) 5:53 Gemini 3.5 Flash: Benchmarks and Why People Aren't Impressed 9:07 Google's Hidden Edge: Bringing AI Directly to Users 10:17 The Real I/O Story Nobody Covered: AI Inside Google Search 12:16 Why Google Must Cannibalize Their $82 Billion Ad Empire 14:46 How Google Agents Will Demolish Lightweight SaaS Companies 17:07 Project Spark: Google's Jarvis-Style AI Assistant 18:21 Antigravity 2: The Codex Clone That Flopped 20:21 Final Verdict: What Actually Matters from Google I/O — Useful Resources —— Find everything else at https://aiwithkyle.com/

191: AI Destroyed Your Career Ladder (Here's What to Do Now)

Get AI-Ready with Kyle’s 5-Day Challenge: https://aiwithkyle.com/join Subscribe and turn on notifications to catch the next live stream: https://www.youtube.com/channel/UChlLglbHDASnoGkbjDeHnQg Summary: AI isn't taking your job. It's doing something more insidious — it's stopping new ones from being created. Entry-level roles are down 35% since 2023, and the grunt work that used to build careers (research, admin, junior analysis, legal discovery) is gone, absorbed quietly by AI with no fanfare and no replacement. That's the real story behind Eric Schmidt getting booed off a graduation stage, and it's worth sitting with. The old deal — degree, job, ladder, pension — is finished. Wozniak's message that you have "actual intelligence" is a lovely thought, but actual intelligence without opportunity just becomes frustration. So here's what I'd actually recommend: stop waiting for a government fix or a tech exec to have a change of heart, and start carving out something small that you own. A skill, a service, a product. AI makes that more achievable than it has ever been, and right now it might be the only career ladder left worth climbing. —— Time Stamps —— 0:00 Tech CEOs Booed at Graduation Speeches Over AI 0:45 Eric Schmidt Booed at University of Arizona Commencement 2:27 Steve Wozniak's "Actual Intelligence" Counter Speech 3:43 Why Schmidt Is Probably Right About AI & Young People 5:09 Gen Z Isn't Anti-AI - They Distrust the Tech Industry Deal 6:29 How AI Kills Entry-Level Jobs Without Replacing Workers 8:55 Why New AI Roles Won't Save Gen Z From Unemployment 10:28 The Career Ladder Is Dead - Start Your Own Income Now 13:25 Action Steps to Stay Useful in the AI Economy — Useful Resources —— Find everything else at https://aiwithkyle.com/

190: How I'd Build an AI Product and Quit My Job If I Started Today

Get AI-Ready with Kyle’s 5-Day Challenge: https://aiwithkyle.com/join   Subscribe and turn on notifications to catch the next live stream: https://www.youtube.com/channel/UChlLglbHDASnoGkbjDeHnQg   Summary: Building an AI product used to mean months of development, a co-founder who could actually code, and probably a few rounds of VC money you'd eventually regret taking. That's not the deal anymore. In this video, I walk you through how to build your first AI product from scratch, including why people will absolutely pay for something they could technically do themselves in ChatGPT, how to find the one process in your industry worth turning into software, and the exact technical stack I use: Vercel for hosting, Supabase for your database, and Codex to do most of the actual building.   The goal here isn't a billion-dollar startup. It's something smaller, more useful, and genuinely achievable this week. I cover the full customer journey, the logic layer (where all the real value lives), and how to think about stripping down an existing SaaS into something specific enough to actually sell. I'm also giving away the prompt I use to get Codex to scaffold the whole thing, available in the newsletter at [aiwithkyle.com](http://aiwithkyle.com/).   —— Time Stamps ——     0:00 Build Your First AI Product This Afternoon 1:11 Why People Pay for AI Tools They Could Build Themselves 4:20 How to Find a Process Worth Productizing 5:35 Real Example: Productizing My Content System 7:24 Steal Ideas From SaaS Companies (Rocket Money & Vexly) 10:52 Start Small: Don't Try to Out-Build DocuSign 12:05 One Painful Input, One Useful Output (Product Examples) 14:02 Customer Journey vs Builder Journey 15:53 Under the Hood: Vercel, Supabase & The Logic Layer 20:36 The Codex Prompt That Builds Your Product For You 22:31 Be the High-Agency Person Who Actually Ships     — Useful Resources ——   Find everything else at https://aiwithkyle.com/

189: Codex Mobile: You Can Now Vibe Code From Anywhere (Seriously)

Get AI-Ready with Kyle’s 5-Day Challenge: https://aiwithkyle.com/join Subscribe and turn on notifications to catch the next live stream: https://www.youtube.com/channel/UChlLglbHDASnoGkbjDeHnQg Summary: Codex just shipped a mobile app, and it's the last piece I needed to properly untether myself from my desk. In this one, I walk you through how to set up an always-on vibe coding workflow across your desktop, laptop, and phone. Meaning, you can start a session at home, walk out to a cafe, and pick it up on your phone without losing a single thread of context. The key is combining the new Codex mobile release with the "Control Another Device" feature. I also get into why I've quietly shifted from Claude Code to Codex as my main tool. The model quality gap has closed, and the usage limits on Claude just aren't worth the stress anymore. If you're still running one session per machine and wondering why it feels fragmented, this is the setup that fixes it. Full technical checklist and written guide are in the Monday newsletter at [aiwithkyle.com](http://aiwithkyle.com/). —— Time Stamps —— 0:00 Codex Now Has A Mobile App: Vibe Coding Just Changed 0:43 How Codex In ChatGPT Mobile Actually Works 1:18 The Multi-Device Problem Killing Your Coding Flow 2:36 My Old Setup Mess & Why OpenClaw Was So Exciting 3:59 Mobile Controls Desktop: How Native Codex Untethers You 5:30 Hardware Setup: Mac Mini As Your Always-On Vibe Coding Machine 6:42 "Control Another Device" Setting + GitHub Central Repository 8:17 Adding Your Phone & The Real Studio-To-Pool Workflow 9:53 Why I'm Switching From Claude Code To Codex — Useful Resources —— Find everything else at https://aiwithkyle.com/