Tutorials › Startups: The Ecosystem and How They're Funded › Startup Stages and Risks

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

Startup Stages and Risks

The stages a funded startup passes through, the question each one has to answer, and the risks that dominate along the way.

Startups typically move through distinct stages with different focuses and risks.

The examples below are illustrative. Key areas of focus and team sizes vary significantly.
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]
  

Idea

A common focus is to confirm the problem is real. The dominant risk is market risk: whether anyone has the problem. Investors expect a specific problem and a reason this team is positioned to solve it. A common mistake is building a solution before confirming anyone has the problem. The team might be the founders alone.

Pre-seed

A common focus is a first signal that a solution resonates, with market and product risk both in play. Investors expect a working prototype and early, honest user reactions. A common mistake is polishing the prototype instead of testing it. The team might be very small (for example, one to four people).

Seed

A common focus is product-market fit. The dominant risk is product risk. Investors expect usage and retention signals, beyond expressions of interest. A common mistake is building for a scale nobody has asked for yet. The team might be small (for example, four to ten people).

Series A

A common focus is proving the model repeats. The dominant risk is distribution risk. Investors expect a predictable growth engine, sustained past one good quarter. A common mistake is hiring ahead of demand that hasn't been proven yet. The team might be growing (for example, ten to thirty people).

Series B

A common focus is scaling the proven model. The dominant risks are financial and organizational. Investors expect efficient growth with unit economics that hold at scale. A common mistake is growing headcount faster than the systems that support it. The team might be mid-sized (for example, thirty to one hundred people).

Series C and later

A common focus is expanding market and category position. The dominant risks are organizational and competitive. Investors expect category leadership and a credible path to profitability. A common mistake is losing architectural coherence across a fast-growing engineering organization. The team might be large (for example, one hundred to five hundred people).

Growth stage

A common focus is durable, efficient growth. The dominant risks are regulatory, security, and operational. Investors expect predictable performance, formal governance, and a path to liquidity. A common mistake is treating security and compliance as someone else's problem. The team might be very large (for example, five hundred or more people).

IPO or acquisition

A common focus is withstanding public or acquirer scrutiny. The dominant risks are regulatory, reputational, and integration. Investors expect audited financials and provable operational controls. A common mistake is discovering technical debt during due diligence. Team size varies widely.

The risks behind the stages

A startup carries several kinds of risk at once, and one usually dominates at any given time. Knowing which one should drive a decision, technical or otherwise, more than a generic instinct to “reduce risk.”

RiskThe question it asks
MarketDoes anyone need this? The problem may not be widespread, urgent, or expensive enough for people to change their behavior over it.
ProductCan this team build something people want? A solution can be technically correct and still too slow, too confusing, or too narrow to get adopted.
Domain expertiseDo the founders understand the industry they're entering as well as the technology they're building?
TechnicalCan the technology work reliably, at a cost the business can sustain?
DistributionCan the startup repeatedly acquire customers beyond the first ten won through founder outreach and personal networks?
Talent attractionCan the company convince the specific people it needs to join this early, before there's much to point to besides a pitch and an equity grant?
FinancialCan the company survive long enough to reach its next milestone?
OrganizationalCan the team keep coordinating and making good decisions as headcount and complexity increase?
IncumbentCan an established competitor block a new entrant before it gets a foothold, whatever the quality of the startup's product?
Regulatory and securityCan the startup legally and safely operate within its target market?
Every category stays live at every stage. A late-stage company still has market risk if a competitor changes the game; an early-stage one can still get a regulatory letter it didn't expect. The stages above show which risk is most likely to be the one that kills the company at each point.

The dominant risk at each stage 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.