软件工厂优化：AI 与人力配比下的组织韧性权衡
Optimizing Software Factories
一篇分析文章提出工程预算的三种未来配比：10% AI/90% 人力、50/50、90% AI/10% 人力，每种配比对应截然不同的组织架构、风险画像与盈利轨迹。
In short : A framework for thinking through three future states of engineering spend: 10% AI / 90% labor, 50/50, and 90% AI / 10% labor. Each ratio implies a radically different org chart, risk profile, and profitability trajectory. The post argues that most startups should not overoptimize toward the 90/10 extreme because the key-person risk and institutional fragility are not yet priced into the model.
What happens when a startup employee leaves on a Monday?
In a twenty-person engineering team, one resignation is a 5% headcount loss. The remaining nineteen absorb the work.
In an AI-pilled three-person team running twenty autonomous agents, one resignation is a 33% headcount loss.
The agents do not resign. They keep generating, reviewing, testing, and deploying. But one-third of the institutional memory that trains, prompts, validates, and debugs the agent fleet walks out the door.
The tradeoff at the heart of AI/labor ratio decisions is not throughput. It is resiliency.
At 10/90 (10% AI, 90% labor), a typical mid-stage startup engineering budget powers ~20 engineers and a layer of Copilot, Cursor, and inference spend. Traditional hierarchy. Human code review as the bottleneck. The org chart looks familiar.
At 50/50, the same budget powers ~12 engineers and a fleet of agents. Engineers become solution architects, problem decomposers, and prompt designers. Manager span of control widens because agents do not need standups.
At 90/10, three engineers sit at the center of a constellation of autonomous agents that generate, review, test, deploy, monitor, and optimize. No managers. No hierarchy. No redundancy.
If we are building software factories, maybe it’s time to study operations research.
In manufacturing, the rule of thumb is simple: run your factory at 70–90% utilization. At 100%, one breakdown cascades into missed deadlines, burned teams, and lost customers. The slack is not waste. It is the feature that keeps the system robust.
Engineering teams are not factories, but the same logic applies. When you concentrate orchestration knowledge in three heads, you are running at 100% utilization.
Most startups should not make that bet yet.
Get the next one in your inbox
The 1-minute read that turns tech data into strategic advantage.
Read by 150k+ founders & operators.
GP at Theory Ventures. Former Google PM. Sharing data-driven insights on AI, web3, & venture capital.
来源：Tomer Tunguz 博客（VC 分析） · tomtunguz.com