The four startup stages didn't change — the bottleneck at each one did

[xg-gh-25]

---

AI 时代创业的四阶段，和传统创业长得一样——但每个阶段的退出条件完全不同了。

The Old Startup Stages vs The New Ones

Traditional startups move through Idea → MVP → Launch → Scale by adding people, money, and skills at each transition.

AI-native startups can stay at 1-3 people through ALL four stages. The bottleneck shifted: from "can we build it?" (always yes, now) to "do we understand the problem well enough to direct the AI correctly?"

TRADITIONAL:                    AI-NATIVE:
Idea:   1-2 people              Idea:   1 person + AI research
MVP:    5-10 people             MVP:    1-2 people + AI coding
Launch: 20-50 people            Launch: 2-5 people + AI ops
Scale:  100+ people             Scale:  5-15 people + AI systems

The constraint moved from EXECUTION to JUDGMENT.

The Four Stages — Redefined

Stage 1: Idea → Problem-Solution Fit

Old exit condition: "We have a team that can build this."
New exit condition: "We have evidence the problem is real — NOT just a prototype that works."

The most dangerous AI-era anti-pattern: building a prototype to validate an idea. Prototypes are near-free now. You can build 5 MVPs in a weekend. That's not validation — that's motion disguised as progress.

Validation is still conversations, not code. AI makes the conversations faster (research, competitor analysis, user interview synthesis) — but it cannot replace them.

Stage 2: MVP → Product-Market Fit

Old exit condition: "Users are paying and retention is stable."
New exit condition: Same — but with a new failure mode: agentic tech debt.

Without persistent context (architecture decisions, conventions, non-goals), every AI coding session starts from scratch. Session N doesn't know what session N-1 decided. Result: drift. The codebase works but contradicts itself.

This is showing up across the industry:

• Cursor users report "the AI keeps suggesting patterns I explicitly rejected last week" (r/cursor — recurring complaint pattern)
• Devin had to add "session knowledge" specifically because autonomous runs drifted from initial requirements
• Replit Agent users find projects become unmaintainable after ~20 agent sessions without any persistent context mechanism

The fix isn't "write more docs." It's structural: decision context must persist in a format the AI reads automatically. The specific mechanism (CLAUDE.md, .cursorrules, spec files, context directories) matters less than the principle: every session must inherit the judgment of prior sessions without the human re-explaining.

The projects that skip this hit a wall around month 3: every new feature takes longer because the AI keeps making decisions that contradict prior decisions nobody recorded.

Stage 3: Launch → Operational Independence

Old exit condition: "Growth is repeatable and the founder isn't the bottleneck."
New exit condition: Same — but "bottleneck" is redefined.

In traditional startups, you remove the founder bottleneck by hiring. In AI-native startups, you remove it by systematizing judgment:

• Which decisions are mechanical (auto-approve)?
• Which are taste (batch, review weekly)?
• Which are genuine judgment (block, require human)?

If you can classify your decisions, you can delegate the mechanical and taste ones to AI systems permanently. The founder only touches judgment calls — which is what founders should be doing anyway.

Stage 4: Scale → Moat Through Accumulation

Old exit condition: "Sustainable profitability or exit-ready."
New exit condition: Same — but the moat question changed.

Old moats: network effects, switching costs, brand, patents.
New moats: accumulated context that makes the product better for THIS user over time.

Day 1:   Generic AI tool (same as competitor)
Day 30:  Knows your preferences (slightly better)
Day 100: Knows your domain, your failures, your judgment patterns
Day 300: Irreplaceable — switching cost isn't contractual, it's experiential

Three layers, hardest to copy at top:

1. Domain expertise embedded in product (methodology → code, open-sourceable)
2. Integration depth (user built workflows on top — weeks to recreate elsewhere)
3. Behavioral fingerprint flywheel (corrections + patterns + evolution = irreversible)

The Meta-Insight

The four stages didn't change. The bottleneck at each stage changed:

Stage	Old Bottleneck	New Bottleneck
Idea	Can't build prototype fast enough to test	Can't distinguish "built it" from "validated it"
MVP	Can't ship fast enough	Can't maintain coherence across AI sessions
Launch	Can't hire fast enough	Can't systematize judgment classification
Scale	Can't serve enough users	Can't accumulate context faster than competitors

Every bottleneck shifted from execution (doing) to cognition (understanding). AI solved "can we build it?" permanently. It didn't solve "should we build it?" or "are we building the right thing?"

Questions

• Which stage transition is hardest in AI-native companies? (My bet: MVP→Launch. "Judgment classification" is a skill nobody teaches.)
• Is the "agentic tech debt" problem (Stage 2) solvable by better tooling, or is it fundamentally a discipline problem?
• Can accumulated context (Stage 4 moat) be commoditized? If every tool offers "memory," does the moat evaporate?
• Is the "1-3 person through all stages" claim real, or survivorship bias from the first wave of AI-native builders?

---

Currently at the Launch→Scale boundary: 11 context files, 68 skills, 300+ sessions of accumulated judgment, 25 structural corrections. The tech is Scale-ready. The GTM is still Launch-stage. SwarmAI. Related: Flat vs Compound value curves