Inside Zapier's Codex rollout: What enterprise engineering teams are actually building
Wednesday, April 29
1 PM ET
Zapier's engineering org doesn't pick tools for their engineers. Engineers pick their own.
That means every coding assistant has been in the running — Cursor, Claude Code, Codex, and everything in between. No mandates. No top-down rollouts. Just engineers choosing what actually makes them better at their jobs.
Codex wins for a lot of the department.
When enough of your best engineers are gravitating toward the same tool, you start paying attention to what they're actually building with it.
On April 29, Zapier's Ryan Fitzgerald and OpenAI's Derrick Choi are opening up a private room with 50 engineering leaders to share exactly what this looks like in practice at Zapier. And when Codexis combined with Zapier's new SDK, Ryan will show some magical workflows that bring developer productivity to a whole new level:
Automated code review agent:Identifies pending reviews and delivers Slack summaries
Jira ticket generation: Higher-quality tickets generated from full codebase context
SDK vs. MCP in practice: How Zapier's engineers are using each, and the decision framework that guides it
50 seats. Invite only. Recording not shared publicly.
We're prioritizing real shop talk and live demos. We'll go deep on:
– Why Zapier's engineers, given total freedom to choose, landed on Codex
– What they're building with it that they couldn't do as well before
– Governance and rollout patterns for teams that want structure without bureaucracy
– SDK vs. MCP: a practical decision framework for enterprise teams
Can’t attend live?
Register today, and we'll send you a recording after the webinar ends.
Register now