Evolving your role as a founder from startup to scale-up

Executive overview

What got you to 10 people will not get you to 50. As a company grows, the founder's job stops being execution and becomes context-setting — ensuring every team member makes the decisions you'd make when you're not in the room.

The founder's job shifts from doing, to managing doers, to scaling the decision-making system itself.

The two failure modes founders hit

• Founders don't recognise the role has changed and become a liability to their own company.
• Founders recognise change is needed but can't let go — and the whole company feels it.
• The analogy: a parent's role at newborn stage vs. teenager stage is nearly reversed, even though the title stays the same.

The 10-person threshold

• At 10 people, you can no longer have everyone in every meeting or Slack channel.
• Start introducing minimum viable process — structure that supports velocity, not bureaucracy that strangles it.
• Bootstrappers often reject process because they saw it done badly at big companies; the real fix is right-sized process, not zero process.
• Software engineering parallel: a large codebase needs tests and architecture — a growing team needs the same scaffolding.

The 50-person threshold

• Multiple teams now operate semi-autonomously with different roadmaps and processes.
• The founder can no longer hold all context or have every person report directly to them.
• A middle layer of management becomes essential — flat structures collapse in this range.
• The founder's leverage shifts to working through an exec team (leaders who execute your vision).

Scaling yourself as a leader

• Your job becomes ensuring the right decisions get made even in rooms you're not in.
• Tools for context distribution: all-hands meetings, weekly newsletters, one-on-ones with direct reports.
• Five Dysfunctions of a Team (Lencioni): your first team is the leadership team you sit on, not the people who report to you.
• Treat that leadership team as the primary channel for pushing context across the org.
• A strength becoming a liability: the more context you can hold in your head, the later the breakdown — but every founder hits their limit.

Bypassing the management layer

• Going directly to someone below their manager — even once — undermines the manager, confuses the team, and erodes trust.
• Work through managers, not around them; they are your eyes, ears, arms, and legs.

Hiring and firing

• Define the role by the shape of the hole in the org, not a laundry list of credentials.
• No interview process is reliable alone — use contracts, trials, and probation periods to defer the final call.
• Reference checks should be treated as a real interview: probe strengths, weaknesses, and specific situations.
• Almost everyone waits too long to let someone go; by the time you're wondering whether to act, you probably already should have.