Research / AI amplified the coordination tax

AI amplified the coordination tax

AI amplified the coordination tax: the 5-person strike team as the structural unit of the AI era

2026-03-14 · agentic-ai organisational-design · medium · source → · wiki →
key claims
  1. The communication-channel formula from Frederick Brooks' *The Mythical Man-Month* (1975) — n(n-1)/2 — establishes that expanding a 5-person team to 6 people increases coordination pathways by 50%, from 10 channels to 15, while adding only one additional contributor
  2. When AI multiplies per-person productive output from approximately $250K/year to $2M/year, the economic cost of each additional coordination channel rises by the same multiple, making the penalty for each hire above the 5-person threshold approximately 5–10x more expensive than in the pre-AI era
  3. Midjourney operated at approximately $4.6M in revenue per employee in 2025 — approximately 107 employees generating $500M in annual revenue — a ratio approximately 35x the private SaaS median revenue per employee of $129,724
  4. ElevenLabs operated at $569K–$825K in ARR per employee as of late 2025 ($330M ARR, 400–580 employees depending on source), representing 4–6x the private SaaS median, achieved by maintaining a small team relative to revenue scale
  5. Shopify CEO Toby Lütke's April 2025 memo requires every team to demonstrate why AI cannot perform a required task before requesting additional headcount, operationalising a substitution-before-hiring mandate at scale for one of the world's largest e-commerce platforms
  6. The Lütke memo does not contain the specific claim that team additions beyond five produce a "10x loss of productivity"; that specific quantification appears in the primary video source and is not independently corroborated in the memo text itself
  7. Peter Steinberger built OpenClaw as a solo developer in November 2025 — an open-source AI agent that reached 196,000 GitHub stars and 2 million visitors in one week — providing a concrete existence proof that a single person with advanced AI fluency can achieve outputs formerly requiring large engineering teams
  8. Management research independently converges on 5–10 as the optimal team size ceiling: J. Richard Hackman's rule of thumb is "no double digits"; Amazon's two-pizza rule caps teams at approximately 6–10; Supercell built its top-grossing games with teams of five and six people; the AI-era argument is that the ceiling tightens toward 5 because coordination channels are now economically more expensive

Research Question

Artificial Intelligence (AI) has increased per-person output by 5–10x. If coordination cost scales with the square of team size (see 2026-03-12-team-size-limits-brooks-dunbar-network-theory.md), what is the correct structural unit for an AI-augmented organisation, and how does the increased per-person output change the economics of every additional hire?

Specifically: does the evidence support the thesis that the penalty for exceeding a 5-person team has risen by the same order of magnitude as per-person productivity — and what does that imply for how organisations should be designed today?

Findings

Executive Summary

AI increased per-person output by 5–10x without reducing coordination overhead per person; this makes the economic penalty for over-staffing above five proportionally larger than in the pre-AI era. The n(n-1)/2 communication-channel formula (Brooks, 1975) is unchanged — a 5-to-6 person expansion adds 50% more channels — but when each channel taxes individuals now worth $2M/year rather than $250K/year, the coordination cost of a single additional hire becomes comparable to that person's marginal output. AI-native companies implicitly validate this by operating at 4–36x the private SaaS median revenue per employee while keeping teams small. The scout (solo) and strike team (5-person) archetypes represent the operationally correct structural units: the scout proves viability; the strike team executes at scale.

Key Findings

  1. The communication-channel formula from Frederick Brooks' The Mythical Man-Month (1975) — n(n-1)/2 — establishes that expanding a 5-person team to 6 people increases coordination pathways by 50%, from 10 channels to 15, while adding only one additional contributor. (high confidence)

  2. When AI multiplies per-person productive output from approximately $250K/year to $2M/year, the economic cost of each additional coordination channel rises by the same multiple, making the penalty for each hire above the 5-person threshold approximately 5–10x more expensive than in the pre-AI era. (medium confidence — inference from the formula; the proportional cost relationship is logically derived and not directly measured)

  3. Midjourney operated at approximately $4.6M in revenue per employee in 2025 — approximately 107 employees generating $500M in annual revenue — a ratio approximately 35x the private SaaS median revenue per employee of $129,724. (high confidence — multiple consistent sources)

  4. ElevenLabs operated at $569K–$825K in ARR per employee as of late 2025 ($330M ARR, 400–580 employees depending on source), representing 4–6x the private SaaS median, achieved by maintaining a small team relative to revenue scale. (medium confidence — headcount is contested across sources)

  5. Shopify CEO Toby Lütke's April 2025 memo requires every team to demonstrate why AI cannot perform a required task before requesting additional headcount, operationalising a substitution-before-hiring mandate at scale for one of the world's largest e-commerce platforms. (high confidence — three independent news sources confirming memo text; X post by Lütke)

  6. The Lütke memo does not contain the specific claim that team additions beyond five produce a "10x loss of productivity"; that specific quantification appears in the primary video source and is not independently corroborated in the memo text itself. (high confidence — the memo text is verified; the "10x" figure is unverified against the primary source)

  7. Peter Steinberger built OpenClaw as a solo developer in November 2025 — an open-source AI agent that reached 196,000 GitHub stars and 2 million visitors in one week — providing a concrete existence proof that a single person with advanced AI fluency can achieve outputs formerly requiring large engineering teams. (high confidence — Fortune; Yahoo Finance; Nate Jones newsletter)

  8. Management research independently converges on 5–10 as the optimal team size ceiling: J. Richard Hackman's rule of thumb is "no double digits"; Amazon's two-pizza rule caps teams at approximately 6–10; Supercell built its top-grossing games with teams of five and six people; the AI-era argument is that the ceiling tightens toward 5 because coordination channels are now economically more expensive. (medium confidence — converging independent sources on the range; the AI-era tightening to specifically 5 is an inference)

  9. Meeting proliferation in oversized organisations is a structural symptom of the n(n-1)/2 coordination pathway count rather than a cultural problem: reducing team size eliminates pathways, while meeting-culture interventions address the symptom without changing the underlying pathway count. (medium confidence — follows from the formula; no direct empirical study of meeting frequency as a function of team size vs culture was found)

  10. The scout/strike team framework maps structurally onto military small-unit doctrine: RAND's 1960s Vietnam-era strike team research and US Army Field Manual 7-85 both identify smallness and specific high-value mission targets as defining characteristics of effective strike units, pre-figuring the AI-era framework. (medium confidence — the parallel is substantiated by primary doctrine sources; the direct applicability to commercial AI-era teams is an inference)

Identified but not consulted:

Assumptions

  1. [assumption] The Nate Jones video primary source makes specific claims about 5-person strike teams and quantified productivity penalties for team expansion. Justification: the GitHub digest summary explicitly describes the video as being about "AI team efficiency and small teams achieving massive revenues," and the item context was authored by someone who watched the video. The specific "10x loss" figure cannot be verified from available sources.

  2. [assumption] Each communication channel in the n(n-1)/2 formula costs each participant a roughly constant fraction of their working time. Justification: this is the standard interpretation of Brooks' model and is the basis for the proportional economic cost argument. If channels become cheaper with AI tools (asynchronous AI-mediated communication), the coordination penalty could be lower than the formula implies — acknowledged in Risks/Gaps.

  3. [assumption] The revenue-per-employee figures for AI-native companies reflect team structural design choices rather than other factors (regulatory environment, market timing, product type). Justification: the consistent pattern across multiple AI-native companies with different products (image generation, voice AI, developer tools) reduces the probability that any single confounding factor explains the pattern.

Analysis

The central thesis — that the coordination penalty for team sizes above 5 has risen proportionally with AI-driven productivity gains — is well-supported at the logical level but not yet directly measured. The supporting evidence is convergent from three independent directions: (1) the mathematical formula (Brooks, 1975) establishes that coordination pathways scale quadratically; (2) AI-native company data shows that small teams achieve 4–36x the revenue efficiency of median SaaS firms; and (3) management research independently confirms 5–10 as the optimal team size ceiling.

The gap in the evidence is that no study has directly measured the economic coordination cost before and after AI productivity gains at the same firm or team. The argument is structural inference, not empirical observation. This should not be read as weakening the thesis — the math is arithmetically sound — but it means the specific claim that the penalty has risen "by the same order of magnitude" as per-person productivity cannot be offered as a measured fact.

The Lütke mandate is the strongest real-world institutional evidence: it operationalises AI substitution before headcount expansion at scale, which is consistent with the thesis that coordination overhead (in the form of unnecessary headcount) is now economically punishing enough to warrant a CEO-level mandate. The memo's absence of the specific "10x" figure is relevant context: Lütke's framing is about AI capability substitution, not specifically about team size as a structural variable.

The Steinberger/OpenClaw case is the strongest existence proof for the scout model but is a single outlier instance. Its generalisability depends on the "Steinberger Threshold" — whether the organisation has people with sufficient AI fluency to direct rather than be directed by AI agents.

Risks, Gaps, and Uncertainties

  1. AI may reduce channel cost. If AI tools enable asynchronous, low-overhead communication (AI-mediated status updates, AI-written summaries, agent-to-agent coordination), the n(n-1)/2 formula may overstate the coordination cost in AI-native environments. This would reduce, but not eliminate, the penalty for team sizes above 5.

  2. The "Steinberger Threshold" is a selection bias risk. The scout model requires someone with the capability to direct AI agents effectively. If most team members cannot yet operate at this level, the scout archetype is not deployable and the strike team threshold effectively rises.

  3. AI-native company data is confounded by product type. Midjourney (image generation) and ElevenLabs (voice AI) operate Application Programming Interface (API)-first, infrastructure-light, zero-sales-force business models. These structures are inherently high revenue-per-employee regardless of AI productivity gains. The comparison to traditional SaaS medians includes companies with enterprise sales teams and professional services — both of which are inherently headcount-intensive.

  4. No direct before/after measurement. No study was found that measured coordination cost at the same organisation before and after AI productivity gains. The thesis relies on cross-sectional comparison (AI-native vs traditional SaaS) and mathematical derivation, not longitudinal measurement.

  5. Primary video source unverifiable. The specific quantitative claims from the Nate Jones video (including the "10x loss" figure) could not be verified from a transcript.

Open Questions

  1. Does AI tooling (AI-mediated communication, agent-to-agent coordination) reduce the per-channel cost in the n(n-1)/2 formula? If yes, this would shift the optimal team ceiling upward. Suitable for a new research item.

  2. What is the empirical distribution of the "Steinberger Threshold" in the current workforce? What fraction of knowledge workers can currently direct AI agents effectively, and how is this changing quarter-over-quarter?

  3. How do the Midjourney/ElevenLabs revenue-per-employee figures decompose when controlling for product type (platform/API-first vs enterprise/services)? The comparison to traditional SaaS medians includes product-type confounds.

  4. Does the 5-person ceiling hold for hardware, manufacturing, or regulated-service businesses? The evidence base is almost entirely software/AI-native. Physical-world coordination constraints may differ.

Output

Type: knowledge
Description: Structured analysis of the economic argument for the 5-person strike team in AI-augmented organisations, grounded in the Brooks coordination formula, AI-native revenue-per-employee data, and the scout/strike team archetype framework.

Three most important sources:

  1. Brooks, F.P. (1975). The Mythical Man-Month. — www.historyofinformation.com (establishes the coordination overhead formula)
  2. ElectroIQ "Midjourney Statistics" (2025) — electroiq.com (primary data on AI-native revenue efficiency)
  3. Shopify CEO Lütke memo, TechCrunch (April 7, 2025) — techcrunch.com (operationalised institutional response)

sources

← newerExploration-synthesis gap
older →Force multiplier, not cost reducer

Connected items

Loading…

View full knowledge graph →