Why Scaling Is Fundamentally Different From Growing
The distinction between growing and scaling matters for business planning: growing means adding revenue, customers, and sometimes people in proportion to each other. Scaling means adding revenue significantly faster than costs — achieving higher output without proportionally higher inputs. The business that grows from $1M to $2M revenue by doubling its staff has grown; the business that grows from $1M to $2M while adding only 30% to headcount has scaled. The scaling business is improving its economics with size; the growing business is maintaining them.
The phase of growth from 10 to 100 people is where most businesses face their most challenging scaling problems because it’s the phase where the informal systems that worked at 10 people break down, and the formal systems required at 100 people haven’t been built yet. The 10-person company runs on direct communication (everyone knows what everyone else is working on, the founder makes or approves all significant decisions), shared context (everyone was there when the culture was established), and direct accountability (everyone can be observed directly by someone responsible for performance). The 100-person company requires systems — management structures, documented processes, formal communication channels, performance management — that the 10-person company never needed.
The Management Layer Problem
The first major structural challenge in scaling from 10 to 100 people: building a management layer that the company has never needed before. At 10 people, the founder or CEO directly manages most of the team. At 100 people, the CEO can effectively directly manage 6–8 people; there must be a layer of managers between the CEO and the majority of the team. The quality of this management layer determines the quality of the scaling experience more than almost any other factor.
The management layer mistakes that most damage scaling: promoting the best individual contributors into management without training or support (the best engineer who becomes a terrible manager, losing both a great engineer and gaining a bad manager), keeping founder managers in roles beyond their ability to operate at the required scale (the operations manager who was excellent at 20 employees and is overwhelmed at 80), and adding management without defining what the management is responsible for (the manager whose role is ambiguous produces ambiguous results). The management investment that most enables scaling: intentional selection, development, and support of managers who are explicitly evaluated on team development and performance, not just individual output.
Culture Preservation Under Growth Pressure
The culture that made the 10-person company excellent tends to dilute during the 10-to-100 growth phase not because growth is bad for culture but because culture transmission hasn’t been systematised. At 10 people, culture was transmitted through direct observation of the founders and through shared experiences. At 50 people, most employees didn’t join when the company was 10 people and don’t have the direct founder relationship that transmitted the original culture. What isn’t explicitly taught, documented, and demonstrated will be replaced by the default culture each employee brings from previous employers.
The culture preservation practices that work during rapid scaling: an explicit articulation of the culture’s most important elements with specific behavioural examples (not just values statements but descriptions of what the values look like in specific decisions), onboarding that specifically addresses culture and provides employees with the context and stories that transmit it, and leadership behaviour that consistently demonstrates the culture values, particularly in high-visibility moments where pressure might justify cutting corners on values. The culture that’s practised differently under pressure will be quickly identified by new employees as the real culture, which is the only culture that matters.
Process and Systems: Building the Infrastructure for Scale
The processes that the 10-person company handled informally need to become explicit and documented as the company scales. The hiring process that was ‘the founder talks to candidates and decides based on feel’ needs to become a structured process with defined criteria, consistent interview questions, and documented evaluation. The financial reporting that the founder did personally needs to become a finance function with regular reporting cycles and defined ownership. The customer success that the founder handled personally needs to become a team with documented processes for customer engagement, onboarding, and problem resolution.
The documentation discipline that most enables scale: writing down the processes that work before they break. The company that documents its most important processes while they’re running well creates the institutional knowledge that allows new team members to maintain those processes as the organisation grows. The company that tries to document processes after they’ve broken under growth pressure is simultaneously fixing the broken process and trying to learn from it — a significantly harder and more expensive task than proactive documentation.
Founder Transition: From Operator to Leader
The personal transition that the founder must make during the 10-to-100 scaling phase is the most uncomfortable and most important: from being the operator who does the work to the leader who enables others to do the work. The founder who is still writing code, closing deals, or managing customer relationships at 100 employees is taking time away from the organisation-building, strategy-setting, and culture-maintenance that only the founder can do — while doing operational work that others could do instead.
The specific founder transition that most predicts successful scaling: learning to make good hiring decisions (the leverage of bringing in strong leaders is enormous at this stage), building the management accountability systems (enabling delegation without abdication requires systems that provide visibility into performance), and communicating clearly enough that people two or three levels below can make decisions consistent with the founder’s intent without requiring direct input. The founder who can articulate their decision-making framework clearly enough for others to replicate it has built the organisational DNA that scales; the one who makes decisions intuitively can’t transfer that capability to others.