Most people judge AI models by what they can do today. @rahulgs judges the slope. When we started Ramp, people had tasted better software at home and could no longer tolerate the tools they were handed at work. So we built something better. Same thing is happening now with AI. Our customers use these models every day. They know what speed and intelligence feel like — and anything that makes them repeat themselves or wait for an answer feels broken. Rahul builds for that. Not for the best model today, but for where models will be in 3–6 months. Studying traces. Improving the harness. Cutting CI time. Giving agents real work with real guardrails. He gets into all of it with @bcherny, @Anthropic's Head of Claude Code, and our staff engineer @austospumanto.

Eric and I have worked as a team for the past 12 years. This only makes it formal. Strategy decisions are increasingly technology and systems-design decisions, and we want the company built around that reality. Stepping in as CTO is @rahulgs. Rahul's superpower is being right early. He spots the bet worth making while everyone else is still forming an opinion. A lot of Ramp's best decisions trace back to that instinct, and now it's pointed at the whole technical org. @HamidDadkhah3 is taking on a new role as Head of Engineering. Hamid cares about what the customer actually achieved, not what we shipped, and he moves things over the line without waiting to be asked twice. Engineering orgs are supposed to slow down as they grow. Hamid takes that as a personal challenge. Speed compounds. What used to take a year takes < 1 month now. Glad to have these two running it.