A company archetype is a recurring pattern in how organizational scale shapes technical decisions. Startup, scale-up, and enterprise are useful patterns, not fixed boxes: a company may sit between them or combine their traits. The practical question is which dynamics matter for the decision at hand. section 3.3.3
Each archetype tends to value a different kind of decision:
- Startup: favor reversible bets and speed while learning whether the product works. Over-engineering for an uncertain future can be a costly mistake. section 3.3.3
- Scale-up: choose foundations that can sustain realistic growth for several years. Some decisions now depend on existing systems and are expensive to revisit. section 3.3.3
- Enterprise: account for an existing platform landscape and choices that must endure team changes or serve multiple teams. Once shipped, a decision becomes part of a larger whole. section 3.3.3
The same option, different context
Suppose two companies want conversational AI for product search, use Google Cloud, and need speed to market. Introducing a customer engagement platform, rebuilding the frontend, or adopting a new database may still be judged differently in a five-person startup and a thousand-person enterprise. Shared product goals and infrastructure do not settle what each organization can afford to change. section 3.3.3
Use the archetypes alongside business priorities, technology strategy, industry norms, and team context. Identify the forces that actually constrain or enable this decision rather than scoring every dimension or assigning the company a permanent label. section 3.5
Table 3.1 Scale patterns comparison
|
Dimension
|
Startup
|
Scale-up
|
Enterprise
|
|
Decisions this stage values
|
Reversible bets where speed matters more than fit
|
Choices that will sustain the realistic scale for several
years
|
Decisions that survive across team changes and
ideally fit multiple teams
|
|
Tolerable uncertainty
|
High – most decisions can be revisited quick
|
Moderate – some foundational decisions are hard to revisit
cheaply
|
Low – once shipped, decisions become a of a much bigger whole
|
|
What the decision can lean on
|
Almost nothing – every choice is greenfield
|
Some existing systems, some genuine greenfield
|
An existing platform landscape that constrains the option
set
|
|
Strategic role of the decision
|
Surviving long enough to learn
|
Building the spine the company growth will run on
|
Leveraging the value of decisions already made and scale
|
|
Most likely failure reason
|
Over-engineering for a future that may never come
|
Picking the wrong scale – oversimplifying or
overengineering
|
Not taking pragmatic decisions at the excuse to be
enterprise-ready
|
The comparison table makes the differences in valued decisions, tolerable uncertainty, and existing constraints easy to scan. section 3.3.3
