Case Study: Ramp Inspect, 30% of PRs without a mandate
About 30% of all pull requests merged to Ramp's frontend and backend repos are written by Inspect, the background coding agent Ramp built in-house, and no policy made that happen: "We didn't force anyone to use Inspect over their own tools." The post, on the Ramp Builders Blog (January 2026), doubles as a build spec. Ramp wants you to copy it: "Paste the link to this post into a coding agent and let it begin building." This is one of eight case studies in the landscape.
Ramp's growth mechanism was visibility, not a memo. This is the adoption pattern argued in Cohorts beat mandates, demonstrated at one company.
Ramp's segregation-of-duties control is one design decision: PRs open on behalf of the requesting user, via that user's GitHub token, never as the app. Ramp explains why the app-authored alternative is disqualifying: it "would allow for any user to approve their own changes. You do not want to knowingly create a vector for unreviewed code to go into the codebase." The same principle, argued generally, is Author, never approver.