---
id: "claim-headcount-collapse"
type: "claim"
source_timestamps: ["§ 3. Autonomous business functions."]
tags: ["team-structure", "human-resources"]
related: ["entity-org-tactix", "concept-ai-librarian", "concept-zero-latency-iteration", "framework-five-forces"]
confidence: "high"
testable: true
speakers: ["Nikki Monterroso"]
enrichment_verdict: "Directionally supported but numerically anecdotal — valid as a case-study pattern (leaner, more leveraged teams), not a universal law."
sources: ["futures"]
sourceVaultSlug: "hbr-seg-futures"
originDay: 2
articleStem: "hbr-new-24-agentic-ai-supercharges-startups"
sourceUrl: "https://hbr.org/2026/07/how-agentic-ai-supercharges-startups-and-threatens-incumbents"
sourceTitle: "How Agentic AI Supercharges Startups and Threatens Incumbents"
---
# MVP Teams Have Shrunk From 6–8 People to 2 People

**Claim (confidence: high; testable).** A conventional technology product team required **6 to 8** specialized roles (engineers, product manager, UX researcher/designer, business lead) and **6–12 months** to build a minimum viable product (MVP). Today, AI-native startups require a minimum of just **two people**: a *domain expert* who understands the business problem, and a single *AI engineer* leveraging coding tools to perform the work of ten. This fundamentally alters startup operating leverage — the essence of *autonomous business functions* (force #3 of the [[framework-five-forces|Five Forces]]).

The exemplar is [[entity-org-tactix]], whose core product team is exactly two people — a QSR industry expert and an AI engineer (cofounder [[entity-nikki-monterroso]]). It compounds with [[concept-zero-latency-iteration]] and internal-knowledge tools like [[concept-ai-librarian]].

**Enrichment note.** Many early-stage AI startups do report 2–3-person teams shipping functional products, but no large-sample data confirms the exact '6–8 → 2' ratio; McKinsey/MIT Sloan confirm reduced coordination cost without specifying it. *Verdict: Directionally supported but numerically anecdotal.* **Counter-perspective:** moving from prototype to a scalable, enterprise/healthcare-grade product still needs roles for security, compliance, data governance, and support — AI shifts the *mix and timing* of roles rather than eliminating them; many 'two-person' stories describe early prototypes, not organizations at scale.