Zach Lloyd on the software factory you define in code
Warp's CEO reframes agentic coding as an engineering discipline: define your software factory in code, store and measure every agent run, and tune it like any other system — the payoff is a self-improving pipeline, and a new job called factory engineering.
A Factory You Define in Code
A software factory is not “we use agents a lot” — it is a concrete system defined in code, one per product surface, that you can orchestrate, measure, and tune.
you should actually think of a software factory as a very specific thing like you should define your factory in code
The Factory Stack
Treat the factory as a stack of pluggable layers — a declarative definition at the foundation, then data, compute, inference, an improvement layer, an orchestrator, and access points on top.
the analogy is like terraform here. You get the same benefits but actually more.
The Factory That Rewrites Itself
Because the factory is defined in code, coding agents can grade their own past runs and open pull requests against the factory definition to make it better.
because you have your whole factory defined as code and these are coding agents they can essentially make a pull request against the factory definition to try to improve the factory itself
$80 a PR Became $15
Tuning the factory cut Warp's cost per merged PR from about $80 to roughly $15 to $20, while throughput rose about 40% and the revert rate stayed flat.
when we first started using the factory approach it was costing us about $80 per PR because we were using like opus where we shouldn't have
Your Own SWE-Bench
Replaying your own agent runs across a matrix of models and harnesses gives you SWE-bench-style results on your real codebase, which you feed straight into routing.
a result that looks very similar to like the published results for SWE or Terminal Bench, but on your company's own real runs
You Can't Build on Tokens
Subscriptions can be far cheaper than paying by API — five to 50 times, by one estimate in the interview — so a coding agent built on raw API tokens can't compete, which is why Warp sells optimization, not tokens.
you can't build a competitive coding agent on top of a thing that costs so much more money
Factory Engineering Is the Job
The job splits in two: product engineers ship features through the factory, and factory engineers build and tune the system that builds the software.
How do you as an engineer build the right skills so that you're engineering the system that builds the software and not just building the software directly?