
Your new hire is supposed to speed things up before the product launch, while cutting that senior role should bring costs down in time for the next budget review. On paper, these decisions make sense. But will they still look like the right call a few months from now?
Not necessarily. The logic behind both moves can feel so obvious that the calculation stops too soon. The new salary fits the budget. Cutting a role saves $100,000. Decision made. But there’s an earlier step that can show you what those decisions actually mean for your company: headcount planning.
Get it right, and you know what you’re signing up for before you make the call. Skip it, and you may not see the full impact until much later.

Think of headcount planning as working out what your team should look like and what it will take to get there.
Headcount planning is the decision-making process: Which roles do we need? How many people in each? At what cost? When? What changes if we add or remove positions?
Hiring is the execution: Finding candidates, interviewing, making the offer and getting the new hire onboard.
Ultimately, headcount planning covers both expansion and contraction. It looks at who to hire and when, but also which teams to restructure and which roles to eliminate.
It’s easy for a hiring decision to come down to one question: can we afford the salary? But that leaves out three aspects that matter just as much.
Take a hypothetical mid-sized company approving a new operations hire at $75,000 a year. The salary fits the budget. Now add benefits, software and equipment, then factor in six weeks of onboarding support from two senior employees and the time it takes the new hire to reach full productivity. Together, those costs could bring the first-year investment closer to $110,000.
That doesn’t make the hire a bad decision. It means the company is making a $110,000 decision, not a $75,000 one. That’s what headcount planning is there to show.

The salary is the easiest saving to see when a role is cut. The costs that follow are much easier to miss.
Now imagine a company cuts two roles expecting to save $120,000 a year. The termination costs come to $40,000, and the productivity lost while that knowledge is replaced costs another $50,000 over the next 12 months. That leaves a first-year saving of just $30,000, not the $120,000 the company expected. The cut may still make sense. But a $30,000 saving is a very different proposition from a $120,000 one.
The two terms get used interchangeably, but they answer different questions.
Workforce planning is broader. It looks beyond roles, numbers and costs to skills, succession and where the organization needs to be longer term.

For a company with 20 to 250 employees, though, headcount planning can be the more immediate need. If the questions are which roles to add, what they’ll cost or where to restructure, you don’t necessarily need a broader workforce strategy to answer them.
A lot of headcount planning advice assumes there’s an FP&A team somewhere in the background. But what if there isn’t? For founders running lean teams, the process needs to work without a dedicated analyst.
Here is a practical way to approach it:
None of this requires a finance degree or a dedicated FP&A team. With accurate data and the right tools, a COO or Head of People can work through the process in a few hours.
When spreadsheets start making that process harder rather than easier, it may be time to compare headcount planning software rather than adding more tabs to the same file.
Good headcount planning looks very different from a process built around static spreadsheets and salary figures alone.
Keeping org data, costs and scenarios current gets harder when they live across separate spreadsheets. The right tools bring that information together, making it easier to see the full cost of a change and compare different options before choosing one.
They don’t replace judgment, though. A tool can show you what a role costs and help you model what changes if you add or remove it. It can’t decide whether that role matters enough to keep. What it can do is give you a clearer view of the alternatives, rather than leaving you to make the call based on a single plan.
That approach is also reflected in McKinsey's research on workforce planning, which highlights the value of considering multiple scenarios rather than relying on a single forecast. Cortextual combines live org visibility, cost intelligence and a scenario builder for modeling different versions of your org and comparing their impact. The Free plan lets you start with your own org data and see what that looks like in practice.
Headcount planning is the process of deciding which roles your organization needs, how many people you need in each, what they’ll cost and when you’ll need them. It covers both expansion and contraction, including hiring, restructuring and cutting roles.
Headcount planning helps you understand the full impact of adding or removing a role. For a new hire, that means looking beyond salary to benefits, tools and onboarding. For a cut, it means accounting for termination costs, lost productivity and the knowledge that leaves with the person. Without that planning, both decisions can look very different on paper than they do in practice.
Start by mapping your current headcount by role and team, including the fully loaded cost of each employee. Then identify the gaps, model what each one would cost to fill and assess the risk of leaving it open. From there, prioritize based on cost-adjusted risk. With accurate data and the right tools, a COO or Head of People can work through the process in a few hours.
Headcount planning focuses on the roles your organization needs, how many people you need and what they’ll cost. Workforce planning is broader, covering skills, succession and how the workforce needs to evolve over the longer term. For companies with 20 to 250 employees, headcount planning can be the more immediate need.

Your hub for research, frameworks, and practical guidance on workforce transition, organizational knowledge, AI adoption and more.