How Intercom 2X'd engineering velocity with Claude Code | Brian Scanlan
Brian Scanlan from Intercom reveals how the company doubled engineering throughput in nine months by systematically adopting Claude Code across its entire R&D organization, not just as a coding tool but as a platform that requires intentional skill design, telemetry instrumentation, and cultural permission-granting from leadership. The episode demonstrates a replicable playbook for ambitious engineering teams: treat your internal AI setup like a product, measure everything, build guardrails that enforce quality rather than slow velocity, and bet on the premise that imagination—not typing speed—is the real bottleneck in software delivery.
Key takeaways
- • Measure AI adoption rigorously by tracking pull request throughput per R&D head and correlating it with quality metrics (code review time, incident rates, customer-facing feature velocity) rather than assuming velocity gains come with quality losses.
- • Build a centralized skills repository distributed via IT infrastructure (not just plugin managers) to reliably deliver organization-wide guardrails—Intercom uses hooks to enforce high-quality PR descriptions and prevent agents from bypassing established systems like feature flags.
- • Instrument all internal Claude Code sessions with telemetry (session data to S3, skill invocations to Honeycomb) and build internal dashboards that give engineers actionable feedback on their AI usage patterns, adoption gaps, and areas for improvement.
- • Create high-impact agent skills using the "and then" workflow—define a clear goal (e.g., fix all flaky tests), let the agent execute, capture learnings, apply them to similar problems, then expand to adjacent codebases—this transforms intern-level work into distinguished-engineer-level output at scale.
- • Make your product agent-accessible by building CLIs, ephemeral APIs, and multi-step workflows that hint to agents how to traverse signup, verification, and configuration flows; the conversion rate drop-off point is now the escape key when an agent gives up, not a human clicking back.
- • Grant explicit permission and accountability from senior leaders—tell your team "you can do this, and if it breaks, blame me"—rather than requiring endless risk assessments; this cultural shift unlocked Intercom's velocity gains as much as the tooling itself did.
Recommendations (8)
"I'm going to do a fairly trivial change in our majestic Ruby on Rails monolith"
Brian Scanlan · ▶ 21:46
"We've been largely going all in on Claude Code and really pushing out enablement and giving people freedom to explore and start to build skills"
Brian Scanlan · ▶ 6:00
Mentioned (2)
More from these creators
Claude Cowork tutorial for non-engineers | JJ Englert (Tenex)
I built a custom Slack inbox. It was easier than you think. | Yash Tekriwal (Clay)
Claude Code + 15 repos: how a non-engineer answers every customer question | Al Chen
Claude Code for personal productivity: a step-by-step tutorial | Hilary Gridley
How Stripe deploys 1,300 AI-written PRs per week
How Microsoft's AI VP automates everything with Warp | Marco Casalaina