Startups: The Ecosystem and How They're Funded · Part 2 of 19

The Startup Lifecycle: Idea to Exit

Same search, different question at every stage.

A startup moves through distinct stages rather than along one smooth curve from small to big. What defines each stage is the question the company has to answer before it can reach the next one.

flowchart TD
  A[Idea] --> B[Pre-seed]
  B --> C[Seed]
  C --> D[Series A]
  D --> E[Series B]
  E --> F[Series C+]
  F --> G[Growth stage]
  G --> H[IPO / Acquisition]

Stage	Typical size	Main objective	Dominant risk	What investors expect	Common mistake
Idea	Founder(s) only	Confirm the problem is real	Market risk	A specific problem, and why this team is positioned to solve it	Building a solution before confirming anyone has the problem
Pre-seed	1–5	Get first signal a solution resonates	Market & product risk	A working prototype and early, honest user reactions	Polishing the prototype instead of testing it
Seed	5–15	Find product-market fit	Product risk	Usage and retention signals, beyond expressions of interest	Building for a scale nobody has asked for yet
Series A	15–50	Prove the model repeats	Distribution risk	A predictable growth engine, sustained past one good quarter	Hiring ahead of demand that hasn't been proven yet
Series B	50–150	Scale the proven model	Financial & organizational risk	Efficient growth with unit economics that hold at scale	Growing headcount faster than the systems that support it
Series C+	150–500+	Expand market and category position	Organizational & competitive risk	Category leadership and a credible path to profitability	Losing architectural coherence across a fast-growing engineering org
Growth stage	500+	Durable, efficient growth	Regulatory, security & operational risk	Predictable performance, real governance, a path to liquidity	Treating security and compliance as someone else's problem
IPO / Acquisition	Varies widely	Withstand public or acquirer scrutiny	Regulatory, reputational & integration risk	Audited financials and provable operational controls	Discovering technical debt during due diligence

Stage tells you more than headcount does. Two companies can both have 40 engineers and sit at completely different points in this table: one still hunting for product-market fit with a large team it can't yet justify, another already proving a repeatable model with a lean one. When deciding how much architectural maturity a company needs, ask which row it's in.

The “dominant risk” column is the thread that ties business stage to technical decisions. What a startup should build, buy, or leave alone at any given moment follows from which risk dominates right now, rather than which risk might matter someday.

Previous ← What Is a Startup?

Next The Risks Startups Face →