The COO needs a headcount plan that’s grounded in what the business actually needs to deliver its commitments. The CFO needs a headcount plan that’s tied to revenue assumptions and financial constraints. The CEO needs a headcount plan that reflects the company’s strategic priorities and growth ambitions.
These three perspectives are often in tension — which is exactly why most headcount plans satisfy none of them.
Start With Demand, Not Org Charts
The most common mistake in headcount planning is starting with the org chart — who do we have, what roles are open, what does the next tier of management look like? That’s supply-side thinking.
Start with demand: what work needs to be done to deliver the company’s strategy, and what skills and capacity does that work require? The gap between required capacity and current capacity defines the hiring need.
Connect Headcount to Deliverables
Every headcount request should be tied to specific deliverables: what will this person enable the company to do that it cannot do now? Generic headcount requests (“we need another engineer”) don’t get funded. Specific ones (“we need a senior backend engineer to deliver the enterprise API by Q3, which unlocks the $2M sales pipeline”) do.
The COO’s job is to ensure that every headcount request in the plan is connected to a specific deliverable and a specific strategic priority.
Model the Timing
Headcount has a long lead time. A senior engineering hire takes 3–4 months from approval to start date. Add ramp-up time — another 1–3 months before the person is fully productive — and a decision made in January might not generate capacity until Q3 or Q4.
Build this lag into the plan. Show not just when hires are planned, but when they’ll be productive — and how that productivity curve affects project delivery timelines.
Build in Scenarios
The CFO will want to know: what if revenue underperforms? What if we raise a round sooner than expected? Build two to three headcount scenarios tied to financial outcomes. Scenario A (base case): full headcount plan. Scenario B (conservative): 70% of headcount plan, priority roles only. Scenario C (accelerated): expanded headcount plan, funded by upside.
Having the scenarios pre-built means leadership can make fast decisions when conditions change, without having to go through a full replanning cycle.
Present It as an Investment, Not a Cost
The framing of headcount as “cost” is both accurate and limiting. The CEO and CFO also respond to “investment” framing when it’s connected to returns: “This hire cohort will cost $X and will enable us to deliver $Y in new revenue / $Z in efficiency savings / the A strategic initiative.”
The COO’s skill is connecting the people investment to the business outcome — making the headcount plan a strategy document, not just a staffing document.
