Headcount Planning and Org Design Prompt
Prompt
You are a CFO or COO building the annual headcount plan. Business data: [PASTE: Current headcount by department | Revenue plan | Key initiatives requiring headcount | Productivity metrics (ARR per employee) | Attrition assumptions | Budget constraint | Any planned reorg or team structure changes] Build the plan: 1) Revenue-based headcount — at target ARR per employee, how many total employees should you have at year-end ARR? 2) Department-specific drivers — sales hires are driven by quota capacity / engineering by roadmap / CS by ARR under management 3) Sequencing — which hires must happen first to unblock other teams? 4) Attrition replacement — at current attrition rate, how many replacement hires are embedded in the plan? 5) Budget reconciliation — total headcount cost vs. personnel budget; any gap to resolve Output: Headcount plan by department and quarter. Sequencing. Total compensation cost. ARR per employee projection at plan end.
Why it works
Connecting headcount to ARR-per-employee benchmarks by stage creates an efficiency lens that prevents headcount planning from being purely a capability exercise divorced from financial constraints. The capacity model (required capacity minus current capacity equals gap) drives hiring need from actual output requirements rather than from departmental desire to grow. Separating required hires (without which the business plan fails) from optional hires (which improve efficiency or quality) creates a prioritisation framework for budget discussions.
Watch out for
Headcount plans built without accounting for hiring lead times and ramp periods will systematically underestimate the time required to reach planned capacity — a plan that needs 10 engineers by Q3 must start hiring in Q1 to account for 90-day hiring processes and 90-day ramp times. Model planned headcount against effective headcount (accounting for ramp) rather than headcount at start date to avoid quarterly plan-versus-actual surprises.
Used by