There's a version of headcount planning that almost every FP&A person has done. You open a spreadsheet. You list the open roles. You plug in start dates, salaries, and maybe a benefits load. You sum it up. Done. The CFO is happy, HR is happy, and the model ties to the budget.
That approach works fine until it doesn't. The breaking point is somewhere around 200 employees, and when it breaks, it breaks fast.
🗂️ What "Planning" Means Below 200
At smaller companies, headcount planning is really just roster management with a financial layer on top. You know every department head. You've probably talked to each of them this quarter. The hiring plan lives in a single tab, and when something changes, one person updates it. The model is simple because the organization is simple.
This isn't a knock on smaller-company FP&A. Keeping a clean, accurate headcount model at 100 people takes real discipline. The point is that the inputs are manageable. One person can hold the whole picture in their head.
📈 What Changes at Scale
Once you cross into the 200-plus range, the organization has enough complexity that a list of names and start dates stops being sufficient. A few things happen at roughly the same time.
First, departments start having internal structure. Engineering isn't one team anymore — it's four or five teams with different managers, different skill sets, and different cost profiles. A single "Engineering headcount" line in your model becomes meaningless for planning purposes.
Second, span of control starts to matter financially. If your average manager supports six individual contributors today and that drifts to four over the next two years, you've just added a material layer of management cost without anyone making an explicit decision. FP&A's job is to make that drift visible before it shows up in the actuals.
Third, ramp costs become a real budget line. At 50 people, onboarding costs are negligible. At 300 people with a 25% annual turnover, the cost of getting new hires to full productivity — recruiting fees, training time, reduced output during the ramp period — is actually worth modeling. Some companies choose not to. That's a choice, but it should be a deliberate one.
🔑 The Real Shift in FP&A's Role
The bigger change isn't the model complexity. It's who FP&A is talking to and what the conversation is about.
Below 200, you're mostly building the plan and maintaining it. Above 200, you're translating. HR has workforce planning goals (retention, diversity targets, succession planning). Department heads have delivery goals and want headcount to hit those goals. Finance has budget constraints. These groups don't naturally speak the same language, and no one else in the building is going to sit in the middle and make the math hold together.
That translation work — turning a VP of Sales's "I need six more reps by Q3" into a fully-loaded cost forecast with ramp assumptions and a productivity timeline — is where FP&A actually earns its seat at the table. It's not glamorous. It requires a lot of back-and-forth. It also happens to be one of the highest-value things a finance team can do at a growth-stage company.
🛠️ When Does the Spreadsheet Actually Break?
This is the question everyone dances around. The honest answer: spreadsheets don't break at a specific headcount. They break when the number of people maintaining the model exceeds one or two, or when the plan needs to be updated more than once a month at any real speed.
A shared Google Sheet with three department heads editing it simultaneously is a mess at 200 employees. A well-structured Excel model owned by one FP&A analyst can work at 500 if the inputs are clean and the process is disciplined. The tool matters less than the data governance around it.
That said, there are real signals that it's time to look at purpose-built headcount planning tools: version control is becoming a problem, HR and Finance are working off different source-of-truth data, or the model takes more than a day to refresh for a reforecast. When those symptoms show up, the spreadsheet isn't the root cause — it's just the most visible symptom.
The companies that handle the 200-employee inflection point well are the ones where FP&A saw it coming and started building the right habits before the model fell apart. Department-level drivers, documented ramp assumptions, a clear owner for each input. None of it is complicated. It just has to happen before the chaos, not after.