Full Tutorial: Use AI Agents for Coding AND Product Management | Eno Reyes (Factory)
Summary
The episode is a deep dive into Factory's AI coding agent, Droid, emphasizing an enterprise-first approach with controls, ROI analytics, and multi-surface integrations. Eno Reyes demos building an app from meeting notes and contrasts 'spec mode' (what to build) with 'plan mode' (how to build it), showing how agents fit into real engineering workflows. The conversation covers model-agnostic strategies (mixing planners like Opus with executors like GPT-5.2), rigorous self-validation (linters, tests, screenshots) to raise output quality, and practical choices about skills, MCPs, and hooks. It also explores organizational implications: hiring 'product engineers' over traditional PMs, autonomy vs manual approval trade-offs, and how a small focused team competes with larger players in the AI coding space.
Key Takeaways
- 1Enterprise-first design matters: Droid prioritizes controls, analytics, and integrations for large orgs.
- 2Use spec mode for 'what' and let agents plan 'how' in plan mode.
- 3Model-agnostic workflows and mid-session model switching improve performance and cost-efficiency.
- 4Rigorous self-validation (QA, linters, tests, screenshots) is crucial to trustworthy agent outputs.
- 5Organizational roles and tooling evolve: product engineers and centralized skills gain prominence.
Notable Quotes
"Our product doesn't stop at the terminal or the IDE or the web or desktop. Of course, we have those surfaces, but we also provide tooling that helps you analyze your entire company's code bases to determine what's stopping agents from being successful."
"Opus will plan and GPT 5.2 will execute. That combo actually outperforms either alone."
"Agents are, you know, fundamentally bottlenecked by the ability to validate their own work."
"We went zero to 10,000 people in like a couple months, basically."