Doubling Is the Expensive Plan

Many founders build their annual plan by taking the organization they have and adding the people needed to double. It sounds prudent. But companies don't get more efficient one hire at a time, and a company built to double is often more expensive to run than one built to grow tenfold.

Organizations have efficient sizes. Between them are configurations that carry the costs of the next stage without its benefits. Three salespeople reporting to a founder can be efficient. So can eight salespeople with a dedicated manager. The expensive version is three reps supporting a manager who can neither fully manage nor fully sell.

At a 1:3 manager-to-AE ratio, each rep carries a third of a manager's cost. At 1:8, an eighth. At three reps, the manager usually has to carry a bag, becoming a player-coach who is inevitably better at one job than the other. Either the number suffers or the coaching does.

The larger cost is learning. Three AEs generate fewer first calls, demos, and losses than eight, and the manager struggles to distinguish a weak pitch from a weak territory from a weak rep. Every conclusion takes longer to reach and rests on fewer observations. With eight AEs, the manager sees patterns sooner, rewrites the talk track, and knows within the next cycle whether the change worked. Speed of learning is an overlooked return on scale.

The wider span also changes who you can hire. A role managing three AEs is a player-coach position. A role managing eight attracts someone who has already built teams, developed reps, and run a repeatable sales process. It also changes the economics of systems. A team of three can be managed from memory. A team of ten cannot. It needs defined metrics, a review cadence, and a pipeline view that both the manager and CEO trust. Those systems cost time and money to build, and the investment pays off across more people. The metrics make performance visible, people accountable, and the organization easier to improve.

The same pattern shows up in SDRs, customer success, and deployment. Each has a range where the team is too large to manage informally but too small to justify dedicated management and specialized processes. Sometimes a company has to get bigger just to become efficient again.

This is where annual planning goes wrong. Founders start with a revenue target, estimate the headcount required, and build an organization around that number. That sequence ignores the economics of organizational design. The alternative is to identify the next efficient organization, determine the revenue and investment required to support it, and build the growth plan from there. Sometimes that means staying small. For an early-stage company with a repeatable sales motion and a large market, it can mean growing substantially faster than the founders intended. The reason isn't that growth is inherently good. It's that reaching the next efficient configuration improves management leverage, learning speed, and operating economics at once.

A plan to grow 10x doesn't deliver 10x economics on its own. Demand has to support the added capacity, the sales motion has to work, and the company needs the capital to finance the transition. Hiring ahead of demand can be ruinously expensive. So can growing incrementally, adding management and infrastructure a little at a time, and never reaching the scale at which those investments pay for themselves.

As companies get larger, the argument changes. Once an organization can support professional management, specialization, and operating systems, the question becomes one of marginal economics: what does the next dollar of investment produce? At earlier stages the decisions are structural. You're not deciding whether to add another rep. You're deciding which organization to build.

Don't design an organization to support your growth plan. Design a growth plan that gets you to an efficient organization.