Headcount Planning Model Prompt
Prompt
Build a headcount plan. Context: [stage, revenue, current team size] Growth target: [revenue or customer target for next 12 months] Current team by function: [roles and headcount] Capacity constraints: [where are you bottlenecked?] Hiring budget: [approximate] Lead time: [how long to hire and ramp?] Please build: 1. Recommended hires by quarter over 12 months 2. Prioritisation: which roles first and why 3. The capacity metric that justifies each hire 4. Cost model: fully loaded cost per planned hire 5. Risk: what if hiring takes 2x longer than expected?
Why it works
Building the headcount model from revenue or customer targets rather than from last year's headcount plus incremental additions connects staffing to business output rather than to historical organisational structure. The capacity constraint identification focuses hiring on the functions that are actually bottlenecking growth rather than distributing headcount additions evenly. The monthly hiring calendar output converts the headcount plan into an operational hiring schedule with specific timing.
Watch out for
Headcount plans must be modelled with realistic hiring assumptions — average time-to-hire and ramp time vary significantly by role type and market conditions, and plans built on optimistic hiring timelines will systematically miss their capacity targets. Build in a 20-30% timeline buffer for senior or specialised roles, and model what happens to business plan delivery if hiring runs 60 days behind plan before committing the business plan to headcount-dependent growth assumptions.
Used by