From 20 to 50 — When Founders Need to Manage Managers

Somewhere between a team of 10–30 and a team of 30–50, the company you built stops working.

The thing that worked when the team was small — you in every important conversation, decisions made in Slack, weekly all-hands where everyone genuinely knew everyone — starts breaking. Not dramatically. Quietly. You notice the same problems being raised twice. You notice you're the bottleneck on three different decisions that should be moving without you. You notice good people are slightly less energised than they were three months ago.

This is the leadership-layer transition. It's the most predictable structural challenge a scale-up faces, and the one founders most consistently misjudge — usually by waiting too long to address it.

This guide is about recognising the moment, navigating the transition, and managing managers when you've never had to before.

For most UK scale-ups, somewhere in the 30–50 range something fundamental shifts. The signals are subtle at first — and almost every founder we've spoken with has missed them by 2–4 months.

The early signs you've outgrown a flat structure:

• You're spending most of your week in 1:1s and meetings, with shrinking time for strategic work.
• Decisions you used to make in 10 minutes are now taking days — because four people need to be aligned and you're the only one who can align them.
• New hires take longer to ramp than they should, because there's no clear manager owning their onboarding.
• Information silos are forming. Sales doesn't know what marketing is shipping. Engineering doesn't know what the customer team is hearing.
• Your best performers are quietly getting frustrated. They want clarity on their growth, and "we'll figure it out" no longer cuts it.

Founders often interpret these signals as performance problems. They're not. They're structural problems wearing performance-problem clothing. The talented people who feel stuck don't need more coaching — they need a manager who isn't you. The decisions slipping don't need you to work harder — they need a layer of decision-makers who don't have to come to you.

The most useful mental model: at a team of 10–30, you can run a company on relationships. By 30–50, you have to run it on systems and on managers. The transition is happening between those two zones, and it can't be skipped.

The transition doesn't happen on day one. It happens across about six months. Here's the rough sequence we see in well-run UK scale-ups making the move from a team of 10–30 into the 30–50 range.

One pattern worth flagging: the founders who navigate this transition cleanly almost always go one level deeper than feels comfortable in the first wave of management hires. The instinct is to promote your most senior IC. The right move is often to hire the person who has managed before, even if it means they're more senior than the company has felt up to that point.

For most founders, this is the first time they've managed managers. That's a different job from managing individual contributors, and it doesn't come naturally. Three things change.

Your job changes from doer to multiplier. A founder who keeps "doing" once they have managers ends up second-guessing decisions, bypassing the management layer, and undermining the people they just hired. The company tells you when this is happening: managers stop pushing back, your direct reports start asking you for things they should ask their manager for, and decisions quietly route around the new structure.

You measure differently. At a team of 10–30, you measure shipped work. By 30–50, you measure shipped work through someone else. Did your VP of Engineering ship the right roadmap, hire the right people, and run a healthy team? Those are now the things that matter — not whether the code was good (their team is judging that).

1:1s change shape. An IC 1:1 is about the work. A manager 1:1 is about their 1:1s, their hires, their team's energy. If you find yourself going deep on the work in a manager 1:1, you've slipped back into IC mode and you're making it harder for them to do their job.

One trap to flag: the temptation to skip the management layer entirely. Some founders try to scale from a team of 10–30 into the 30–50 range with no real managers — just senior ICs and themselves. It works for about three months. By month six, the founder is exhausted, the senior ICs are quietly leaving, and the next 12 months become a recovery exercise rather than a growth one.

The single biggest variable in how well a 20-to-50 transition goes is the founder's own willingness to change. Most don't. Most try to do the same job they did at 12, just for more people, and the company quietly suffocates.

Practical things that distinguish the founders who navigate it well:

They make a list of what only they can do — and brutally cut everything else. Pricing decisions, board management, key partnerships, hiring exec roles, defining the next 12 months. Everything else: delegate, even imperfectly. The cost of imperfect delegation is low. The cost of being a bottleneck is enormous.

They write things down. The verbal-tradition company that worked at 12 doesn't work at 30. Write the strategy. Write the hiring bar. Write the values. Write the operating cadence. Boring, slightly painful, and the difference between a company people understand and a company people interpret.

They build a single source of truth on metrics. One dashboard. The same numbers everyone sees. The same numbers in every meeting. This sounds basic. Once you're in the 30–50 range it's the difference between a leadership team that argues productively and one that argues from incompatible reads of reality.

They get peer support. The 20-to-50 transition is the most predictable structural challenge in a scaling company, and the experience of founders 6–12 months ahead of you on it is the most directly transferable kind of advice. Helm Club Forums are full of founders in or just past this exact moment, and the conversations on managing first-time managers, on letting go of the work, and on rebuilding cadence are some of the highest-value sessions our members report.

The patterns we see most often, with the cost where we know it.

Mistake 1: Promoting the strongest IC into management without preparing them. They were great at the work. They're not yet good at managing the work. They're given the title with no support. Six months later, the team is underperforming and the new manager is miserable. The damage: lost time, lost confidence, often the loss of the IC themselves when they realise it isn't for them.

Mistake 2: Hiring a manager who's "two levels up". Founders sometimes hire a VP because they want the gravitas. The VP arrives, finds a tiny team, no real systems, and two months of frustration later resigns. Hire one level above where you are now — not three.

Mistake 3: Maintaining the all-hands as the only forum. At a team of 10–30, the all-hands works. By 30–50, it's a broadcast — not a conversation. You need a small leadership team meeting where real decisions get made, and a different rhythm for whole-company communication.

Mistake 4: Skipping written documentation. The senior hire arrives and asks for the strategy doc, the hiring scorecard, the operating principles, the org chart. None of them exist. You spend the next three weeks writing them. Multiply by every senior hire and that's a quarter of founder time.

Mistake 5: Continuing to be the escalation route for everything. If every difficult conversation, hard decision, and team conflict still routes to you, you don't have managers — you have well-paid coordinators. Push the decisions back. Even imperfect manager decisions are better than founder decisions made in 4-minute slack threads.

If you're navigating this transition right now, the most useful thing you can do is talk to three founders who've just finished it. Their advice will be more concrete, more painful, and more useful than any framework.

The 20-to-50 transition surfaces the same set of questions in Forum sessions almost every month. Worth borrowing the way founders 6–12 months ahead are answering them.

Q: My strongest IC just stepped into a manager role and is struggling. Do I demote them or coach them through?

The most common pattern is wait two more months and decide based on hard signals. Specifically: are they running their team's 1:1s consistently? Are their team's outputs hitting expected quality? Are they handling difficult conversations themselves rather than escalating? If two of three are no after four months, the role is wrong — and the kindest move is an honest conversation about whether the IC role is where they're stronger. Most demotions, done well, retain the person and a meaningful amount of their loyalty.

Q: Should our first VP-level hire be People, Engineering, Sales, or Finance?

Almost always whichever of those is currently being done worst by the founders. There's no universal answer. If hiring is breaking — VP People. If product velocity is broken — VP Engineering. If revenue is breaking — VP Sales. Pick the function where the founder is most clearly the bottleneck, not the function that sounds most prestigious.

Q: How do I shift my time without my team feeling abandoned?

Communicate the change explicitly. "I'm intentionally going to be less involved in [X area] for the next 90 days because [Manager] needs to own it. If something is genuinely stuck, my door is open — but try them first." Founders who go silent without explaining the shift cause the team to interpret distance as disengagement. Naming what you're doing, and why, changes the same behaviour from "the founder has lost interest" to "the founder is deliberately building a layer".

Q: I keep getting pulled into operational decisions even when I try not to. How do I actually let go?

Two structural moves. First, stop showing up at meetings where your manager is now the right decision-maker — your presence forces escalation by default. Second, require your managers to write a one-page proposal before bringing decisions to you. Both make it easier for them to own decisions and harder for you to grab them by reflex. The "writing it down" requirement is the magic — it forces them to sharpen the thinking before reaching you, and most decisions resolve themselves in the writing.

Q: How do I know when I've made the transition properly?

Three signals. First, your calendar has 4–6 hours of strategic, no-meeting blocks each week. Second, your managers run their 1:1s — you don't run them through your manager. Third, when you're on holiday for a week, decisions get made and the company doesn't pile up waiting for you. If all three are true, the transition has happened. If any aren't, you're still mid-flight.

Q: How long should this realistically take?

Four to six months for the structural changes — leadership team, hiring, written rhythms. Twelve months for the founder behaviour change to become natural. The founders who try to compress this into eight weeks usually find themselves repeating the transition twice. The ones who give it a year tend to come out the other side with a company that scales without them being in every conversation.

Q: My co-founder isn't making the transition at the same pace. What now?

One of the more difficult flashpoints, and one we see often. Usually it isn't unwillingness — it's that the two of you have grown into different roles and don't realise it. The most useful move is an explicit, scheduled conversation: where each of you is most useful for the next 12 months, and what that means for who reports to whom. Both founders making the transition together, deliberately, is rare and valuable. Both founders pretending to make it together while one quietly hasn't is corrosive.