Justin and Lily reflect on their parallel journeys diving deep into AI throughout 2025. They discuss why most AI content misses the mark for operators and system builders working within corporate constraints, share lessons from building production AI tools, and explore what's next for bringing these capabilities into the enterprise.
Guest: Lily Luo — Systems & Operations Leader, Author of Applied AI for MOps Substack
Read more of Justin's thoughts on AI Builders: The operator's roadmap for AI in 2026
KEY TOPICS
The Gap in AI Content Most resources target researchers or GTM engineers focused on outbound automation. There's little guidance for operators dealing with cloud tools, security, and corporate complexity. That creates an opportunity to define best practices for this underserved audience.
2025 Project Highlights Lily built an "Analysis Dossier" tool that generates full account research reports at the click of a button. Justin replaced a vendor intelligence tool with a custom system using Retool and a conversational agent.
Lessons Learned Start with tightly scoped AI steps in linear workflows for reliability. Pre-process insights asynchronously rather than relying on real-time agent calculations. Match tools to use cases. Failures teach more than successes.
Atlas: Lily's Autonomous Agent Runs on Google Cloud and wakes every 4 hours to research and progress projects. Uses a three-layer memory architecture: identity, temporal journal, and knowledge graph. Can push its own code and interact with other agents.
2026 Outlook Focus on scalability, reduced hallucination, and team enablement. Build infrastructure that unlocks flexible, ad-hoc use cases. Bridge the gap between AI capabilities and enterprise readiness.
The Human Side Working closely with AI changes how you think. Boundaries matter—don't let AI become a crutch.
RESOURCES
- Applied AI for MOps — Lily's Substack
- AI Builders Blog — Justin's Substack
- Tools mentioned: Claude Code, Gemini, ChatGPT, Zapier, Retool, Dust, Azure AI Foundry, Letta, VS Code
ONE TIP FOR GETTING STARTED
Pick a real pain point. Start with low-code tools you already know. Test relentlessly. Expect to fail—and learn from it.
