Key Takeaways

  • Ramp uses an internal tool named Inspect with over one million sessions, allowing non-engineers to submit 1,000 pull requests per month.
  • Speeding up raw code generation shifts the operational bottleneck downstream to code review and QA testing.
  • Ramp's Review Buddy automatically processes 93% of pull requests, freeing senior staff to focus on the 7% that contain architectural risk.
  • Testo, an autonomous browser QA agent, runs 100 workflow combinations against production-like data and caught 425 bugs in 30 days.

The Downstream Trap of AI Code Generation

When engineering teams adopt AI coding assistants, they usually celebrate a fast boost in raw code output. Then pull request queues swell, review times double, and staging servers break under untested branches.

Geoff Charles, Chief Product Officer at Ramp, compares an engineering organization to a Formula 1 racing team. Accelerating the engine without upgrading the brakes simply crashes the car into the next turn. When code generation speeds up, code review and QA testing become the new choke points.

Ramp restructured its product development workflow around three internal tools designed to handle this downstream volume: Inspect, Review Buddy, and Testo.

Opening Pull Requests to Non-Engineers with Inspect

Inspect acts as an internal developer platform with sub-5-second deploy previews. It gives product managers, designers, and operations staff the ability to generate production code directly against Ramp's existing design system.

“Inspect has a million sessions,” Charles said. “75% of our PRs is actually built by Inspect and a thousand of those PRs over the last month was submitted by a non-engineer.”

This setup only works because Ramp maintains strict architectural boundaries. Charles noted: “Coding agents are really good when you have a strong architecture and a strong code base. This expands how much of your company can actually use AI.” Without clean base code, opening pull requests to non-engineers creates unusable clutter.

Filtering the Flood with Review Buddy and Testo

Generating thousands of pull requests creates severe review fatigue if senior engineers must inspect every line. To prevent this drag, Ramp built Review Buddy. The tool audits prompt lineage and inspects incoming diffs automatically.

“93% of our PRs are now automatically handled by review buddy,” Charles said. “So that the highest quality engineers are spending time on the 7% of PRs that truly matter that have a lot of questions around are we building this correctly? Are there any risks?”

Once code passes review, testing creates the next barrier. Ramp built Testo, an autonomous browser agent that explores the product like a live customer.

“Testo is a browserbased QA agent,” Charles said. “It spins up the product in a 100 different combinations based on the actual production data that we have access to. and it runs in the product like a user.” In a single 30-day window, Testo caught 425 bugs before users ever saw them.

What to Do With This

Audit your team's pull request queue from the last two weeks. If senior engineers spend more than 20% of their time reviewing copy tweaks, CSS styling, or simple UI logic, write automated CI checks to auto-approve low-risk diffs. Reserve human review exclusively for changes that touch database schemas, authentication flows, and financial logic.