Twitter/X

Rahul (@rahulgs) designs Ramp's AI tooling to anticipate model progress 3–6…

Brief

Rahul (@rahulgs) argues Ramp should build for the slope of AI progress, not just current best models: he plans 3–6 month-forward engineering (traces, harness improvements, CI time cuts) and agent guardrails so customers—who use models daily and expect instant, intelligent answers—won’t have to repeat or wait. Karim shared the discussion with @bcherny and @austospumanto in a linked video.

Why it matters

Rahul (@rahulgs) designs Ramp's AI tooling to anticipate model progress 3–6 months out, emphasizing study of traces, improving the model harness, reducing CI time, and enabling agents to do real work with concrete guardrails.

Key details

  • Ramp's customers use models daily and demand speed and higher intelligence; any experience that forces repetition or waiting is considered broken and drives product decisions.
  • Karim (@karimatiyeh) highlights a video conversation (piped.video/watch?v=i4odXOmg) featuring Rahul, Ben Cherny (@bcherny, Anthropic's Head of Claude Code), and staff engineer @austospumanto; post created 2026-03-11.
Source evidence

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.

piped.video/watch?v=i4odXOmg…

Video