When Does a Software Factory Make Sense?

Zach Lloyd says a software factory starts to make sense around five to 10 engineers. For a team of only a few people, the setup is overkill: use a Claude Code subscription or a Codex subscription and go faster. A larger team eventually needs a platform built to accelerate the work.

The need runs up to very large companies, and the bigger the company, the more implementation work it takes. Standing the system up inside a company's own infrastructure is not purely plug and play, because the internal developer setup grows more complex with size. He does not know how much of that work Cursor takes on. For a fast-growing startup of 10 to 100 engineers, the fit is often self-serve. On what he calls the happy stack of Slack, Linear, and Jira, a team can plug the factory in and get value without much setup.

Slack and Linear are natively multiplayer, so a central record does more than the chat or the tracker. A Slack integration can take a server-crash channel and a user-feedback channel and feed them into the factory, which can loop in the people who know the right part of the codebase. A small team should still skip it. The factory makes the most sense for a company that wants infrastructure to build on as models and agents keep changing.