Originally posted on LinkedIn.
If you're building a software factory, here are two steps that are easy to miss. We've been running one at Levelpath since April, and it has increased our development speed by more than 10x without sacrificing quality. Most people focus on whether the agent can write code. That matters, but the two things that held us back were harder to see.
1. Verification. Until you know a change will do what it was asked without breaking something else, the AI skeptics are right: shipping broken code at machine speed is worse than shipping slowly. That's why agentic QA and testing is the most expensive stage of our pipeline. What it buys us is a quality guarantee, the same way a physical factory stands behind what comes off its line. Once you can make that guarantee, you can put your foot on the gas. What that guarantee should cover looks different from the pre-AI bar, but that deserves its own post.
2. Input quality. We started with a ticket quality agent that checked for enough context and clear requirements. That was table stakes. But when we traced back the times we were unhappy with the factory's output, the agent had usually done exactly what it was told. We had told it to do the wrong thing. So the input stage grew. It now runs architectural and product checks, and the agent writes a spec before building, pulling in a human when it needs input.
It sounds simple, but building our software factory came down to two things. First, build a factory that produces something of quality. Then make sure you're telling it the right thing to build.
