Every Monday, host Claire Vo shares a 30- to 45-minute episode with a new guest demoing a practical, impactful way they’ve learned to use AI in their work or life. No pontificating—just specific and actionable advice.

5 OpenClaw agents run my home, finances, and code | Jesse Genet

Brought to you by: Optimizely—Your AI agent orchestration platform for marketing and digital teams

Jesse Genet is a homeschooling parent and entrepreneur who operates five specialized OpenClaw agents, each on its own Mac Mini, to manage homeschool curriculum, family finances, scheduling, development projects, and household operations. She treats each agent like a new hire: defined role, scoped access, decision log, and progressive trust. In this episode she shares how she photographs curriculum books to auto-generate lesson plans, builds custom apps with zero prior terminal experience, partitions sensitive data across machines, and bridges the digital and physical world by inventorying every toy and supply in her house.

Detailed workflow walkthroughs from this episode:

• How I AI: Jesse Genet’s 5 OpenClaw Agents for Homeschooling, App Building, and Physical Inventories: https://www.chatprd.ai/how-i-ai/jesse-genets-5-openclaw-agents-for-homeschooling-app-building-and-physical-inventories

• Automate Homeschool Lesson Planning and Material Creation with an AI Agent: https://www.chatprd.ai/how-i-ai/workflows/automate-homeschool-lesson-planning-and-material-creation-with-an-ai-agent

• Build a Custom ‘Slop-Free’ Kids’ TV App Without Coding Experience: https://www.chatprd.ai/how-i-ai/workflows/build-a-custom-slop-free-kids-tv-app-without-coding-experience

• Create an AI-Powered Inventory of Your Physical Items: https://www.chatprd.ai/how-i-ai/workflows/create-an-ai-powered-inventory-of-your-physical-items

Biggest takeaways:

1. Treat your AI agent like a new hire, not an extension of yourself. Jesse’s entire agent management philosophy comes from her experience hiring employees. She gives agents their own identities, separate data access, and communication channels—never full access to her email or accounts. Progressive trust is the model: start limited, expand as the agent proves reliable.

2. Physical partitioning is a real security strategy. Running each agent on its own Mac Mini sounds extreme, but it solves a real problem: preventing one agent from accidentally leaking sensitive data through another agent’s communication channel. The finance agent can read bank statements but can’t text anyone. The scheduling agent can text, but has no financial data. This is a practical framework anyone managing multiple agents should think through.

3. Photos are the most underrated input for AI agents. Jesse’s core workflow is shockingly simple: take a photo, send it to the agent, get structured output. She photographs lesson activities, book pages, physical supplies, and curriculum materials. The agent handles all the heavy lifting of logging, categorizing, and connecting that information. No typing, no structured input—just photos.

4. You don’t need to be technical to build real software with a coding agent. Jesse had never opened a terminal before six months ago. With Cole, her coding agent, she built a custom kids’ TV app, iterated over four days, and deployed it to a Google TV Streamer. Her approach: describe what you want, push back when the agent says something isn’t possible, and keep going.

5. Inventory your physical world so AI can reach into it. One of Jesse’s most powerful moves was photographing all her educational supplies and having Sylvie build an inventory. Now when she asks for a lesson plan, the agent can say, “Also, pull out the tracing board from the cupboard.” This bridges the gap between the digital agent and the physical world in a way that’s immediately useful.

6. Use “decision files” to prevent agents from relitigating settled questions. Jesse maintains a decisions file in Obsidian that each agent knows about. When she makes a final call, she flags it, and the agent knows not to revisit it. This is a simple, powerful pattern for anyone dealing with agents that keep second-guessing or re-asking about things you’ve already resolved.

▶️ Listen now on YouTube | Spotify | Apple Podcasts

How Coinbase scaled AI to 1,000+ engineers | Chintan Turakhia

Brought to you by:

• WorkOS—Make your app enterprise-ready today

• Rovo—AI that knows your business

Chintan Turakhia leads engineering at Coinbase, where he’s helped turn a 1,000-plus-person org into an AI-native team. In this episode, Chintan shares how Coinbase got 100 engineers to ship 75 PRs in 15 minutes, cut PR review time from 150 hours to 15, and built internal agents that turn user feedback into shipped features in minutes. Claire and Chintan dive into the “speed run” tactic that broke through skepticism, how to identify and replicate AI power users, and why the best engineering leaders are getting more hands-on with code in the AI era.

Detailed workflow walkthroughs from this episode:

• How I AI: Chintan Turakhia’s Playbook for AI Adoption at Coinbase: https://www.chatprd.ai/how-i-ai/playbook-for-ai-engineering-adoption-at-coinbase

• Use ChatGPT to Become Your Own Personal Wine Sommelier: https://www.chatprd.ai/how-i-ai/workflows/use-chatgpt-to-become-your-own-personal-wine-sommelier

• Build an Automated User Feedback to Pull Request Pipeline: https://www.chatprd.ai/how-i-ai/workflows/build-an-automated-user-feedback-to-pull-request-pipeline

• Create a Data-Driven AI Adoption Playbook Using Cursor: https://www.chatprd.ai/how-i-ai/workflows/create-a-data-driven-ai-adoption-playbook-using-cursor

Biggest takeaways:

1. Organize “speed runs” to kickstart widespread AI adoption. Coinbase gathered 100 engineers for a 15-minute session where everyone used AI tools to push 75 PRs simultaneously. The high success rate of merged PRs proved AI’s effectiveness at scale and transformed the team’s mindset about what they could accomplish.

2. Show, don’t tell, when driving AI adoption in engineering teams. Chintan spent months personally using Cursor daily, discovering use cases and techniques before asking his team to adopt it. By tackling real bugs and showing concrete wins, he built credibility that made adoption natural rather than forced.

3. Focus AI adoption on eliminating “soul-sucking” work first. Rather than tackling complex engineering challenges, Chintan targeted the tedious tasks engineers hate: writing unit tests, fixing linting issues, and managing Git commands. Engineers naturally want to build better things faster, and removing friction from their workflow created immediate buy-in.

4. Create public channels to showcase AI wins. Coinbase established a “Cursor Wins” Slack channel where engineers shared their successes. This visibility created organic FOMO and peer learning as engineers saw colleagues shipping more code with less effort.

5. Measure the entire feedback-to-feature cycle time, not just lines of code. Coinbase reduced PR review times from 150 hours to 15 hours and built systems to capture user feedback and convert it to shipped features in minutes rather than weeks. This end-to-end acceleration creates a virtuous cycle where faster shipping leads to more user feedback and continuous improvement.

6. Engineering leaders should be writing more code, not less. Chintan’s calendar is now nearly empty, as AI has eliminated coordination overhead and meetings. Instead, he spends more time writing code, fixing bugs, and exploring technical approaches.

7. Use AI to analyze AI adoption patterns. Chintan used Cursor itself to analyze Cursor usage data, identifying natural user cohorts from inactive to super-users. This meta-application of AI allowed him to create targeted guidance for each segment, helping engineers progress from light usage to power usage. The analysis revealed that agent-heavy users were 16x more productive with AI than other users, providing concrete data to drive further adoption.

▶️ Listen now on YouTube | Spotify | Apple Podcasts

If you’re enjoying these episodes, reply and let me know what you’d love to learn more about: AI workflows, hiring, growth, product strategy—anything.

Catch you next week,
Lenny

P.S. Want every new episode delivered the moment it drops? Hit “Follow” on your favorite podcast app.