
the real "software factory" isn’t everyone using coding agents. that’s the 2x. the 10x is a different thing entirely.
the loop starts closing on its own.
2x = every engineer using agents, ~100% AI-generated code. soon, that’ll be table stakes. you made the same loop faster, but the bottleneck is still human attention at every gate.
10x = the loop self validates. agents stop waiting on you. but it only works if the scaffolding is real: comprehensive CI, evals that actually catch regressions, and end-to-end test environments agents spin up to check their own work.
to be clear, 10x is not "fewer humans." it is humans on the decisions that carry real risk and off the rote gates. we still need to hire exceptional engineers, their judgment is the scarce input now, so you spend it where it actually counts.
but here is what breaks traditional SaaS instincts:
building agents is divergent.
fix one thing and 10 new things need evaluating. converging on that locally is a trap. so ship the 80/20 fast, but through controlled early access: opt-in design partners, clear guardrails, tiered rollout. never unfinished work dumped on people who did not sign up for it.
then close the loop. feedback-loop agents take that signal, implement it, merge it, validate post-deploy, continuously. and because CI/CD is fast, the gap between "customer said X" and "X is live and validated" collapses. coding at the speed of thought.
give agents the same context a human uses to make the call, user feedback, docs, prod monitoring, ephemeral test clusters. encode your review standards as rules the reviewer agent reads. auto-merge the low-risk stuff classified by your reviewer agent. reserve human eyes for billing, auth, the paths where a mistake is expensive.
humans do not disappear, they concentrate.
incidents stay human-led, business impact's too high to hand off, though agents now dig datadog + telemetry + code and hand you impact + root cause + mitigation in minutes. and someone guards the critical paths: as agentic volume climbs you risk losing deep understanding of your own codebase. the fix isn't to slow down — it is to lock down what's expensive to get wrong. Not all code carries equal risk.
at Ramp, this is Inspect, our internal coding agent: deep Ramp context, MCP integrations, CI visibility, and self-validation that boots the UI and tests real workflows. On a recent UI change, it deployed a preview, authenticated as a fixture user, validated desktop and mobile behavior, and attached visual evidence to the PR.
the metric I actually care about: fewest human touches per safely merged PR. not lines, not PR count.
how much can the loop close on its own without breaking the things that matter and do it super fast?
that's the edge.
English






