Scaling leadership capability after a funding round fails for a simple reason, and I see it in nearly every funded company I meet: capital moves on the investor's clock and capability forms on a human one. A round can double your headcount in two quarters. A first-time manager still needs months of repetitions before the role is theirs, and the round has just paid you to skip them.
I wrote this for CEOs, founders and boards of companies somewhere between fifty and five hundred people, usually within eighteen months of a raise, where headcount has outrun the management bench. It is not about "growing companies" in general. There is a real difference between a business adding twenty per cent a year and one that doubles inside six months of closing a round. The first has time to build leadership capacity alongside demand, layer by layer. The second gets no runway at all, which is why development designed for gradual growth rarely survives contact with a funding surge. If you want the wider argument, I make it in why leadership capability does not scale with company growth.
My diagnostic for this is the Leadership Capability Stack, which separates five layers that a leadership problem can live in: Strategic Intent, Leadership Architecture, Decision Systems, Capability Standards and Culture Output. The model holds at any growth rate. What a funding round changes is the order in which the layers fail, and how fast.
Why scaling leadership capability after a funding round breaks the lower layers first
In a steadily growing company the first crack usually appears near the top of the Stack. Strategic Intent blurs as the market moves, and the fix is a conversation between people who already know each other well. After a raise the crack starts lower, in Decision Systems and Capability Standards, because both depend on people having had enough repetitions in a role to have absorbed how it works. A manager promoted eleven weeks ago has had eleven weeks of repetitions. A professional services firm we advised through a Series C raise started tracking manager tenure-at-decision alongside its standard board metrics, and what it showed was blunt. Every major client escalation in the previous two quarters had involved a manager who had been in the role for under ten weeks. A workshop does not close that gap. Capability accrues at roughly the same rate per person whatever the funding, and a round compresses the calendar in which it is supposed to accrue.
McKinsey makes the same observation in its work on founder-led scale-ups. Its authors write that rapid growth often brings instability and sizeable gaps in leaders' experience, skills and capabilities, and that development has to run "at pace, on purpose" (McKinsey, Ready. Set. Scale., 2024). I would add a structural point. Four things tend to go wrong in a fixed sequence, and a board that knows the sequence can see the damage months before it reaches the numbers it tracks.
- Decision Systems crack first: New managers inherit decisions they have never made, with no internal precedent to learn from, because the company is only months old at this headcount. Escalations climb to the founder by default.
- Capability Standards arrive late: The written definition of good leadership at each level usually gets drafted after the third or fourth difficult promotion, rarely before the first.
- Leadership Architecture is skipped, not designed: Founders promote on trust and tenure because nobody has time to design a structure. The org chart becomes the architecture by accident.
- Culture Output degrades on a lag: Engagement scores and exit interviews trail the real damage by two or three quarters, so the board meets a retention problem long after the leadership gap created it.
The compressed tenure problem
In a normal-growth company a first-time manager spends months, sometimes years, working alongside more senior leaders before leading alone. They absorb the norms by proximity. After a funding surge that proximity shrinks to almost nothing. A manager promoted in the fourth month of a company's life at its new size has watched four months of decisions, made by people who were also new to making them. There is no deep well of practice to draw on because the institution barely has one.
Talent selection makes this worse. Gallup's analysis of manager talent found that about one in ten people has high talent for management, and that companies fail to choose the candidate with the right talent for the job 82 per cent of the time (Gallup, 2015). That holds in slow-growing firms as well. A funded company makes dramatically more of these promotion decisions, much faster, about candidates nobody has been around long enough to assess. Nobody intends that error rate. Volume produces it.
1 in 10: people: have high talent for management, according to Gallup's State of the American Manager analytics (2015).
82%: of the time: companies fail to choose the candidate with the right talent for the manager role, on Gallup's analytics (2015).
Three funding-shaped inflection points
Capability does not fail evenly across a funded company's life. It fails at three seams, and each calls for a different response. The headcount ranges below are my working thresholds from practice, not research findings. Treat them as checkpoints rather than a maturity model; a company can reach the second before it has finished the first.
- Seed to Series A, the first leadership layer (roughly 10 to 40 people): The founder moves from doing the work to directing people who do it, usually for the first time. The first leadership promotions happen here, often made on tenure or trust, neither of which reliably predicts who can lead. Every later layer inherits the mistake, because these managers go on to promote the next cohort.
- Series B to C, the compression event (roughly 40 to 150 people, often inside twelve months): Funding-triggered growth parts company with organic growth. One round can add more heads in two quarters than the company added in its first three years. Middle management, the layer that absorbs the daily reality of that many new people, is built with no time and no precedent.
- Late growth or pre-IPO, stacked funding events (150-plus people): The company has usually handled the first two seams badly and the debt compounds. The executive layer manages leaders who were never developed at the layer below, and every new hire inherits a diluted standard because nobody with a clear one is left to enforce it.
Boards sharpen the problem in a predictable way. An investor that has just written a cheque wants to see headcount and revenue move together, and measures both every quarter. Almost no board deck carries a clean measure of leadership bench strength. So the pressure a funded company feels pushes directly against the thing that would help, which is slowing promotions down long enough to get them right. A CEO in that position needs language for the trade-off, not only conviction about it. The language I suggest is simple: we are protecting the speed of the next four quarters by spending one quarter of hiring pace on the managers who will run them.
The reorganisation problem
Funded companies reorganise constantly, because the structure that fit forty people does not fit ninety, and the one that fit ninety will not fit two hundred. Each reorganisation is defensible. Stacked together they create an environment where structure never holds still long enough for anyone to build real capability inside it. Three mistakes sit behind that pattern.
- Reorganising the structure without redesigning the capability standards beneath it, so people get new titles and new teams but no clarity on what the new level expects of them
- Treating each reorganisation as a one-off event instead of tracking the cumulative effect: a manager who has reported to four different leaders in fourteen months has had no consistent development, however good each of those leaders was
- Promoting fastest under the most pressure, so the weakest leadership decisions land straight after a raise, when the company can least afford them
Picture a manager, and treat this as an illustration rather than a client story. She is the strongest engineer in her department, promoted in the quarter after a raise. Over the next fourteen months her function is reorganised three times, each time to follow wherever revenue landed. On paper every change is sensible. In practice she has three bosses with three sets of priorities and none of them in place long enough to develop her. When she resigns, the exit interview says "lack of growth opportunity", which is accurate and misses the cause. Nobody stayed in position long enough for her to grow.
An operating rhythm that keeps pace with the money
Architecture without rhythm is a document nobody reads after the first month. The standard advice, quarterly leadership forums and an annual capability review, assumes a stability that a funded company does not have. A tighter cadence is the cheaper option. Waiting a full quarter to notice that a new manager is struggling usually means finding out in the same week they resign.
- Monthly capability check-ins, not annual reviews: Every manager promoted in the last twelve months gets a short, structured monthly conversation about the specific decisions they are struggling with. This is deliberately more frequent than a steady-growth company would need.
- A standing new-manager cohort that moves as one group: Everyone promoted in the same surge works through the same standards together, so the organisation is not relying on one overstretched executive to calibrate a dozen new managers one at a time.
- A reorganisation impact check before the structure changes: Before any reorganisation ships, someone asks who is about to lose their third manager in a year, and treats the answer as a real cost of the change.
The clearest published example I can point to is the technology scale-up case study on my work-with-me page. It describes a CEO who was the bottleneck on every decision while the company grew from $8M to $25M. The solution was a decision rights matrix, an execution cadence and a leadership pipeline. The results listed there are a 60 per cent reduction in the CEO's decision load, three internal leaders promoted to VP within twelve months, and revenue reaching $25M without adding executive headcount. Those are my own published figures, not independent research, but they show the shape of what installing architecture rather than adding training looks like.
Boards and founders tend to measure the wrong things here for an understandable reason. Headcount, revenue per employee and burn multiple say nothing about whether leadership is keeping pace. I push clients towards a small set of leading indicators instead, because they show the gap months before revenue or retention feels it.
- Average time in role for a manager at the moment they are asked to run a reorganisation or make a major decision, since someone six weeks in is being asked to do something structurally different from someone with a year behind them
- Decision cycle time at the layer below the executive team, tracked through each growth phase rather than averaged across the year, where the surge disappears
- The ratio of promotions to structured capability conversations in the same quarter, which shows exactly how many people are promoted with nothing behind the promotion
What a board should ask before the next tranche
The table below turns the argument into questions a board can put to a CEO in one meeting. None of the signals appears on a standard deck, which is why they tend to be found late.
| Post-round signal | What it usually means | First move |
|---|---|---|
| Decisions stall one layer below the executive team | New managers lack precedent and are escalating by default | Write down which decisions each level owns and publish it |
| The same basic operational questions return from managers promoted last quarter | Nobody has had the time to onboard them properly | Start a monthly cohort session with a fixed agenda |
| A strong individual contributor resigns within a year of promotion | Promotion happened without a standard or support behind it | Review the last ten promotions against a written definition of the level |
| Three or more reorganisations in twelve months | Structure is changing faster than development can follow | Add an impact check before each change |
The companies that handle this well treat leadership capability as infrastructure they fund at the same moment as the round, not as a repair job funded after the damage shows up in retention. CapabilityAI and the Architecture Accelerator aim to put that infrastructure in place before the next surge. If you are a founder carrying every decision yourself, the Founder Bottleneck Challenge is the quickest way to see where the weight sits. Running the current business while building the next growth engine takes the same discipline, set out in how to run today's business while building tomorrow's growth engine.
What founders and boards should take from this
Headcount scaling is addition. Capability scaling is multiplication. You cannot hire your way out of a leadership shortfall, and after a raise you cannot fund your way out of it either, because a larger round buys more people faster, which is exactly the pressure that opens the gap.
The planning question changes after a raise. Instead of how fast you can hire, ask how much leadership your organisation can absorb in a quarter, and build the growth plan around that number rather than around what the round allows. The distinction I keep returning to with boards is this one: a round raises the speed at which a company can grow, and leadership capability sets the speed at which it can safely grow. The lower of the two is your real growth rate.