Overview
Vercel CTO Malte Ubl shares lessons from building two different AI agents - an internal data agent (d0) and the public-facing Vercel v0. The key insight is that simpler architectures often outperform complex ones when building AI agents, as evidenced by their complete rebuild of d0 from a complex multi-tool system to a 50-line coding-style agent.
Key Takeaways
- Be willing to throw everything away - In the rapidly evolving AI space, what worked in summer 2024 may be obsolete today, so maintain humility and readiness to rebuild from scratch
- Make non-coding tasks look like coding tasks - Since models are heavily trained on coding, framing problems as code generation (like using YAML files for business semantics) yields disproportionately better results
- Simple architectures can be more powerful - Their d0 agent went from complex multi-tool system to just 2 tools (bash + SQL) and became transformational for the business
- Start with minimal teams for new AI products - Today you don’t need large teams to validate product ideas; one person can build a working demo before scaling up
- Embrace optimistic locking over approval processes - Allow anyone to ship but give teams veto power rather than requiring pre-approval, which eliminates bottlenecks while maintaining oversight
Topics Covered
- 0:00 - Introduction to AI Agents at Vercel: Discussion of how the current wave of coding agents feels different and the challenge of building while technology rapidly evolves
- 1:00 - d0 Internal Data Agent - First Approach: Overview of Vercel’s internal text-to-SQL agent that answers Slack questions with access to Snowflake database
- 2:30 - The Complete Rebuild Decision: Why they deleted everything and rebuilt d0 as a coding-style agent instead of traditional multi-tool architecture
- 4:00 - Learning to Be Humble with AI: The importance of accepting that AI best practices change rapidly and being willing to start over
- 5:00 - Making Things Look Like Coding Tasks: Strategy of leveraging models’ coding training by framing business problems as code generation tasks
- 7:30 - Vercel v0 Origins and Evolution: How v0 started as a front-end tool but evolved to serve backend engineers and eventually full-stack applications
- 10:00 - Key Breakthrough Moments: Five major ‘aha moments’ in v0’s development, including the Tailwind CSS discovery that made the product viable
- 13:00 - Vercel’s Position in the AI Ecosystem: How Vercel fits as the deployment and hosting platform regardless of which AI coding tools developers use
- 16:30 - Building Teams in the AI Era: Why new AI products should start with single developers rather than large teams
- 18:30 - Optimistic Locking vs Approval Processes: Vercel’s approach of allowing anyone to ship while giving teams veto power instead of requiring pre-approvals
- 24:00 - Unlimited AI Tokens for Developers: Why Vercel gives developers unlimited access to AI tools and the surprising cost implications
- 26:00 - Future of Tech Organizations: How AI is changing engineering roles to be more management-focused, benefiting senior ICs and junior engineers most
- 28:00 - Company Growth and AI Transformation: Plans to cap Vercel at 1,024 employees while continuing revenue growth through AI-driven productivity gains
- 31:00 - The YouTube Analogy for Software: Comparing the current AI transformation to how YouTube democratized video creation, potentially making us ‘software light’
- 33:00 - Future Predictions and Software Maintenance: The challenge of maintaining free AI-generated software and the role of agents in software maintenance