The Headcount Model Most Startup Financial Models Either Miss or Build Incorrectly

A company preparing for a Series A presents a financial model in which the headcount plan shows twelve roles added over twenty-four months. Each role has a salary figure attached. The investor's analyst asks for the fully loaded cost per hire, the employer contribution assumptions, the benefits cost by role, and the equipment allocation per employee. The founding team has no answer, because the headcount plan was built as a list of salaries rather than a headcount model. The salary figures in the financial model understate the true cost of headcount by between fifteen and thirty percent, which means the cash runway calculation is wrong, the gross margin trajectory is wrong, and the use of proceeds allocation to headcount is insufficient for the plan as described.

WHAT A HEADCOUNT MODEL IS

A headcount model is a structured component of the financial model that calculates the fully loaded cost of every planned hire, organized by department, linked to the revenue model, and timed against the milestones defined in the use of proceeds.

Fully loaded cost per role includes the base salary, employer national insurance contributions (or equivalent in the relevant jurisdiction), pension contributions at the applicable employer rate, benefits cost allocated per employee, and an equipment allowance covering the hardware, software subscriptions, and workspace cost attributable to the role. In the United Kingdom, the employer cost above a salary of approximately £45,000 exceeds the base salary figure by fifteen to twenty percent. In the United States, the employer burden including FICA, FUTA, SUTA, and benefits commonly ranges from twenty to thirty percent above base salary.

A headcount model that records only base salaries produces a cost projection that systematically understates the true payroll expense. In a company with a headcount plan of twenty roles at an average salary of £55,000, the fully loaded cost exceeds the salary-only figure by £180,000 to £300,000 annually. That gap is not a rounding error. It is a material misstatement of the company's operating cost base.

THE STRUCTURAL REQUIREMENT

The structural requirement is that the headcount model connects to three other components of the financial model: the cost of goods sold, the operating expense structure organized by department, and the revenue model.

The connection to cost of goods sold is required because some roles — customer support directly attributable to product delivery, implementation engineers for software products — are cost of goods sold, not operating expenses. A headcount model that places all roles in operating expenses overstates gross margin and understates cost of goods sold. An investor who calculates gross margin independently from the income statement will find the correct figure differs from the stated figure, and will trace the discrepancy to the headcount classification.

The connection to operating expenses by department allows the company to report management accounts at a departmental level, showing the cost of sales, marketing, engineering, and operations separately. Without a department-level headcount model, management accounts cannot be produced at the level of granularity that institutional investors expect in board reporting.

The connection to the revenue model means that headcount additions are timed against the revenue milestones that justify them. A company that adds six sales roles in month three of a twenty-four month plan must show in the revenue model that those roles produce revenue from month five or six onward. If the revenue model does not reflect the contribution of those specific hires, the plan is not internally consistent.

WHAT THE INVESTOR EVALUATES

An investor reviewing a financial model with a headcount component will perform two calculations independently. First, they will verify the fully loaded cost per hire by applying standard employer burden rates to the salary figures and checking whether the financial model's payroll line is consistent with the result. If it is not, they will ask why. The answer "we used salary only" reduces confidence in every other cost assumption in the model.

Second, they will check whether the headcount additions in the plan are consistent with the revenue growth projected in the same period. A company projecting 400 percent revenue growth in year two with a headcount addition of two sales roles is internally inconsistent unless its sales model shows that two roles can generate the required revenue. A company projecting 150 percent revenue growth with a headcount addition of fifteen sales roles is internally inconsistent in the opposite direction, and will raise questions about the sales model's efficiency.

Investors at Series A and Series B increasingly build their own version of the headcount model from the salary information provided and check it against the company's projections. A company whose headcount model does not withstand this check will be asked to resubmit corrected projections before the process advances.

COMMON STRUCTURAL PROBLEMS

The most common structural problem is salary-only modeling. A headcount plan that records roles and base salaries without employer contributions, benefits, or equipment understates cost and produces a financial model whose payroll line cannot be reconciled to the actual cost of running the team. This surfaces in due diligence when the investor's analyst applies standard employer burden rates to the salary data and finds the model's cost base is materially lower than the corrected figure.

The second structural problem is the absence of department level organization. A headcount model organized as a flat list of roles rather than a department-structured table cannot produce the departmental reporting that post-Series A board governance requires. This means that a company whose financial model has this structure will need to rebuild the headcount model when it attempts to produce departmental management accounts for the first board meeting after closing.

The third structural problem is timing disconnection. A headcount plan that lists roles and planned hire months without connecting the hire timing to a revenue event or operational milestone is a list, not a model. An investor who asks "why are these four roles being added in month six?" should be able to find the answer in the financial model itself, in the relationship between those roles, the revenue projection, and the use of proceeds milestone they are intended to achieve.

HOW THE FFI STANDARD DEFINES THE REQUIREMENT

The FFI Standard addresses the headcount model in Book 2 (Performance Modeling) and Book 6 (Strategic Financial Planning). At Level 2 investor readiness compliance, the Standard requires a headcount model that calculates the fully loaded cost per role including base salary, employer contributions, benefits, and equipment, organized by department, and linked to the revenue model so that headcount additions are timed against the operational milestones that justify them. The headcount model must be consistent with the use of proceeds allocation to personnel costs and must produce departmental cost projections that can be used for management accounts reporting. Full criteria are at ffistandard.org/glossary/headcount-model/.

THE LAYER ENGAGEMENT

The headcount model is a core deliverable of both the Raise layer and the Operations layer engagements. In the Raise layer, the headcount model is built as a component of the investor-grade financial model, organized by department, calculated at fully loaded cost, and connected to the revenue model and the use of proceeds document. In the Operations layer, the headcount model is embedded in the annual operating plan and becomes the basis for departmental financial planning and management accounts.

For a company that has an existing financial model with a headcount plan but no headcount model, the Investor Readiness Scorecard at theoakworth.com/portal/scorecard/ will assess the current state of the performance modeling domain and identify whether the headcount structure is one of the primary infrastructure gaps requiring attention before the raise process begins.

RELATED INSIGHTS
- The Assumption Layer in a Startup Financial Model Is Not a Tab. It Is a Governance Document.
- How a KPI Framework Connects the Annual Operating Plan to Board-Level Financial Governance
- Cap Table Errors That Surface During Legal Due Diligence and the Infrastructure Required to Resolve Them
- Why a Startup Valuation Without a Documented Methodology Does Not Survive Series A Diligence
- The Headcount Model Most Startup Financial Models Either Miss or Build Incorrectly

Tool: Startup Financial Readiness Scorecard