Don’t Build a Company of Virtual Employees: Build a Catalog of Work

Most enterprise agent diagrams copy the org chart. The useful unit of design is the job, and every agent boundary should be a decision about control, not a job title.

Disclosure: I use GPT search to collection facts. The entire article is drafted by me.

You’ve seen the diagram. An AI Product Manager hands requirements to an AI Developer. The Developer hands code to an AI QA Engineer. QA hands a build to an AI DevOps agent, and an AI SRE agent catches whatever breaks. It has titles, arrows, and upstream/downstream relationships. It looks like a company.

That resemblance is the problem. Are we redesigning how work gets done, or are we using software to photocopy an org chart? The two lead to very different systems. A company with twelve job titles doesn’t need twelve agents. A single job title often bundles several kinds of work. And a single piece of work, like “release this software safely,” often cuts across four titles and six systems.

If you port the titles and the handoffs into software, you don’t get an AI-native organization. You get a faster bureaucracy with higher coordination costs and quicker failure propagation.

This letter does three things. It explains why the virtual-employee pattern is a structural step backward. It…