Skip to content

Blog

Every company will build its own software factory

The question shifts from which editor a team uses to what its factory looks like. Four stages lead from autocomplete to a factory that improves itself, and no team can buy its factory off the shelf.

Written by

Software Factory

Published: 24 March 2026 Updated: 2 min read

The question used to be “which IDE do you use?” Now it is “what does your factory look like?”

A software factory encodes your architecture decisions, quality standards and delivery patterns into composable skills that agents execute autonomously. Orchestrated, not prompted.

Four stages from autocomplete to compound factory

  1. Artisan. Developer plus autocomplete. Faster typing.
  2. Workshop. A human drives the agent step by step.
  3. Factory. Deterministic orchestration between agent steps, quality gates and feedback loops. It scales with compute, not headcount.
  4. Compound factory. The system improves itself, and knowledge compounds.

Most teams are stuck at stage 1 or 2. The leap to stage 3 is where it gets real.

What a factory is made of

  • Agent steps: skills and context that generate code.
  • Deterministic steps between agents: code, not prompts. This is what separates stage 2 from stage 3.
  • Quality gates: tests, linting, architecture constraints.
  • Feedback loops: agents verify their own output before human review.

A two-year migration that became a factory

One migration from our experience was planned for 20 teams over two years. It became a factory running three steps on repeat, and sprint cycles went from 14 days to 1.

Your yoghurt is not their yoghurt

Every yoghurt producer has its own line. The machines come from suppliers, but the line itself is custom, because a farmhouse yoghurt is a different product than a fruit yoghurt.

Software factories work the same way:

  • You can’t copy someone else’s factory. Domain, codebase, conventions and quality bar are all different.
  • Pre-built factories assume a context that isn’t yours. They are someone else’s yoghurt line.
  • You can’t skip stage 2. Builders must know where agents hallucinate and how to recover.
  • When a new model drops, you rebuild parts of the factory. That’s the job now.

The machines may come from suppliers. The factory floor is yours to design.

Build the factory instead of buying one

First movers gain a structural advantage that compounds. Train for stage 2, build stage 3. The factory isn’t a product you buy. It’s a capability you build.

Are you still optimizing your editor, or building the factory that builds your software?

Further reading

  1. AI modernization works as a delivery problem, not a code translation Translating COBOL to Java one to one reproduces the old debt. Treated as delivery, with architecture decisions, encoded context and a migration factory, AI-driven modernization works. 2 min readShort post
  2. The agent shipped a story while the developer slept In a pilot, an agent implemented a complete user story overnight. When work no longer needs a person awake, sprint planning, team sizing and the developer's job have to be rethought. 2 min readShort post
  3. Compounding engineering makes each feature ease the next one Most teams use AI to code faster. Compounding engineering adds a fourth step, codify, so that every feature makes the next one easier to build. 2 min readShort post

All 23 posts on Software Factory

ClientsClient work

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Software Factory: Advanced Team Training
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check