quality_assurance · saas · workflow
Ramp builds Inspect: an internal background coding agent that writes ~30% of merged pull requests
Ramp needed a coding agent that not only writes code but also closes the loop on verifying its own work with the full context and tools available to a human engineer, rather than being limited by missing context.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · User submits prompt
A builder submits a prompt via Slack, Chrome extension, web interface, or on the pull request.
Tools used
ModalVitePostgresTemporalSentry · partnerDatadog · partnerLaunchDarkly · partnerBraintrust · partnerGitHub · partnerSlack · partnerBuildkite · partnerOpenCodeDurable ObjectsAgents SDKGPT 5.2
Outcome
Inspect now writes approximately 30% of all pull requests merged to Ramp's frontend and backend repos, reaching that level of adoption within a couple of months without forcing anyone to use it.
Results
Time saveda couple months
Volume~30%
Grounding & classification
Source type: technical build writeup
33 fields verified against source quotes, 1 dropped as unverifiable.
agent assistagentic workflowcode generationcode diff prhuman review describedmetric backednamed customerproduction runtime claimedtools describedworkflow describedsoftwareautomation rateemployee productivitytechnical build writeupquality assuranceagentic task executionai draft human approval