Post-Funding Org Design

Design backwards from the outcomes the round was raised to achieve, rather than forwards from a template of what a company at your stage is supposed to look like. A funding round is permission to attempt something specific. The structure should follow from that specific thing.

Most post-raise reorganisations do the opposite. They start from what a Series B company generally looks like, produce a chart with the expected functions, and then discover which of those functions had nothing to do.

Start from the thesis, not the template

Write down what the round was raised to prove. Usually it is one or two things: reach a revenue level, enter a segment, ship a platform capability, prove a second acquisition channel.

For each, name the outcomes required and who owns them. Roles that do not connect to one of those outcomes are worth questioning even when they feel obviously necessary, because "obviously necessary" is generally an artefact of what other companies have rather than what this one needs now.

Series A and Series B are different structural problems

The transition between them is where most damage happens, because it is gradual and nobody announces it. A company crosses from one regime to the other somewhere around forty to sixty people, and the structures that worked at Series A quietly stop working without producing a specific event that forces a rethink.

The manager transition nobody names

A Series A manager does the work and manages two or three people alongside it. A Series B manager mostly builds the system that lets other people do the work: hiring into a standard, setting how quality is judged, making decisions repeatable so they do not route through one person.

These are different jobs. Promoting a strong Series A manager into a Series B role without saying so is a reliable way to lose both the output they used to produce and the management you expected to get. The conversation is worth having explicitly, including the possibility that the person prefers the first job, which is a legitimate answer rather than a failure.

Transfer decisions before people

Founders scaling out of a founder-led team usually delegate work first and decisions later. That produces an org chart that looks delegated and operates exactly as before, with an extra approval step.

Invert it. List the decisions you currently make, assign each to a role, and then accept that role making some of them differently from how you would. The tolerance for that is the actual constraint, and it is worth being honest about before adding headcount that depends on it.

A useful test: pick a decision you made this week and ask who would have made it if you had been unreachable. If the answer is "nobody, it would have waited", that decision has not been transferred regardless of what the chart says.

Common questions

What does a healthy org structure look like at Series B?

Clear outcome ownership, a thin management layer, and functions that can ship without negotiating across three other functions first. Health is better judged by where work waits than by the shape of the chart: if most delay sits between teams rather than inside them, the structure is the problem regardless of how sensible it looks.

What should my org chart look like at Series A vs. Series B?

At Series A, most people should be producing and almost nobody should be coordinating full time. At Series B a management layer becomes necessary, and the question shifts to how thin it can be. The failure between the two is adding managers before there is enough work to manage, which creates coordination that then justifies more managers.

What's the difference between a Series A manager and a Series B manager?

A Series A manager still does the work and manages a small number of people alongside it. A Series B manager mostly builds the system that lets other people do the work: hiring, standards, and decision-making that does not route through them. Promoting a strong Series A manager into a Series B role without naming that change is a common way to lose both the manager and the output.

How do I scale from a founder-led team to a structured org?

Transfer decisions before transferring people. Write down which decisions you currently make, assign each to a role, and let that role make them badly a few times. Founders who add structure while retaining the decisions produce an org chart that looks delegated and operates exactly as it did before, only slower.

What does post-funding org design look like?

Design around the outcomes the round was raised to achieve, then work backwards to structure. A funding round is permission to attempt something specific, so the structure should follow from that, not from a generic template of what a company at your stage is supposed to look like.