Framework
People · Planning
Headcount Planning Framework
A seven-step framework to model growth scenarios, align with leadership and finance, and keep a rolling plan you can defend in the boardroom.
How to use this
Use this when you are planning next year’s hires, responding to a funding round, or reconciling ambition with runway. It works for People leaders who own workforce planning with Finance and exec sponsors, not as a finance-only spreadsheet exercise.
Work through the seven steps in order. Each step includes actions for HR and People Ops, plus a short summary you can paste into a board deck or share with Finance.
Summary for leadership
We plan hiring in three scenarios, tie every role to a business objective, model fully loaded cost by quarter, and refresh the forecast when metrics or runway change.
The problem
Headcount plans often arrive too late, too optimistic, or disconnected from how the business actually grows. People teams get caught between hiring managers who want capacity now and leadership who need optionality when the market shifts.
Who is this for?
Startup and scale-up HR and People teams who own workforce planning with Finance. Share relevant sections with your CFO or CEO when you need alignment on scenarios, cost, and timing.
- 1Build a credible headcount plan for the next 4–6 quarters.
- 2Translate revenue, product, and expansion goals into roles and timing.
- 3Partner with Finance on fully loaded cost and runway impact.
- 4Explain trade-offs to leadership and hiring managers without hiding uncertainty.
Step 1
Define growth scenarios
Model Conservative, Moderate, and Aggressive paths so the plan survives uncertainty.
Summary for leadership
We agree three hiring paths up front so the company can slow, hold, or accelerate without rewriting the plan every month.
Agree three scenarios with Finance and the CEO (or equivalent). Each scenario should state revenue or ARR targets, key bets (new market, product launch, efficiency mode), and what changes in hiring appetite. Name them so everyone uses the same language in meetings.
What to do
- Conservative: slower growth, preserve runway, hiring only for critical gaps.
- Moderate: base case aligned to the board plan or operating model.
- Aggressive: capture upside if metrics hit early (often tied to a funding or milestone trigger).
- Document assumptions per scenario (win rate, churn, productivity per FTE).
Done when
- Three scenarios written in one page or slide
- Triggers defined for moving from Conservative toward Moderate or Aggressive
- People and Finance co-own the scenario definitions
Step 2
Identify key business objectives
Tie every hire to outcomes leadership already cares about.
Summary for leadership
Every net-new role maps to a stated company objective; if the objective drops, the role is reviewed before it opens.
Pull objectives from the company OKRs, annual plan, or board deck: revenue, launches, geographic expansion, customer segments, or operational resilience. If objectives conflict, surface that in the planning session rather than in Q3 when roles are half-filled.
What to do
- List 3–5 company objectives for the planning horizon.
- For each objective, note which functions must deliver it (Product, GTM, Ops, People, etc.).
- Mark objectives as must-have vs nice-to-have for the Moderate scenario.
- Confirm exec alignment in one working session (30–60 minutes).
Done when
- Objectives sourced from an approved leadership artefact
- Each objective has an exec owner
- People team can explain how headcount supports each objective
Step 3
Analyse the current workforce
Understand structure, skills, capacity, and gaps before adding roles.
Summary for leadership
We know where the org is overloaded, where we have single points of failure, and what is backfill versus true growth.
Start from an accurate roster: role, level, location, cost centre, and start date. Layer on capacity signals: attrition risk, backfill queue, project overload, and skills you cannot hire quickly (e.g. niche engineering, regulated markets).
What to do
- Map org structure and spans of control for critical teams.
- Identify single points of failure and succession gaps.
- Score teams on capacity (green / amber / red) using manager input, not guesswork.
- Separate backfills from net-new growth in your tracker.
Done when
- Current headcount reconciled with Finance
- Gap list validated with functional leaders
- Backfill vs net-new tagged on every proposed role
Step 4
Determine headcount needs
Build role lists by scenario, with timing that reflects hire and ramp reality.
Summary for leadership
Hiring dates reflect time-to-fill and ramp, not wishful thinking; revenue roles show when capacity actually lands.
For each scenario, list roles by quarter: title, level band, location, and hiring manager. Apply time-to-hire from your own data (or sensible defaults by function). Add onboarding ramp (e.g. sales quota attainment, engineering productivity) so “start date” is not treated as full capacity on day one.
What to do
- Build a role grid: scenario × quarter × function.
- Classify hires as immediate (this quarter), near-term (next two quarters), or contingent (trigger-based).
- Apply time-to-hire and ramp assumptions per function.
- Flag roles that depend on others (e.g. managers before ICs, RevOps before SDR scale).
Done when
- Each proposed role links to an objective from step 2
- Immediate vs future hires are explicit
- Ramp assumptions documented for revenue-critical roles
Step 5
Align with budget
Connect the plan to fully loaded cost and overall budget strategy.
Summary for leadership
People cost by scenario and quarter is aligned with Finance, including what we defer first if we move to Conservative.
Work with Finance on fully loaded cost (base, employer taxes, benefits, equipment, commissions where relevant). Compare scenario totals to runway and revenue per employee benchmarks. If the Moderate plan exceeds budget, negotiate prioritisation rules rather than silently cutting roles later.
What to do
- Model cost by scenario and quarter (not just annual totals).
- Compare people cost as % of revenue or burn to prior year and peers if you have benchmarks.
- Define what gets cut first in Conservative (usually contingent and nice-to-have roles).
- Agree who approves moving a role between scenarios.
Done when
- Finance sign-off on cost model assumptions
- Gap between requested and approved headcount explained
- Contingent roles have clear approval paths
Step 6
Create a flexible plan
Use a rolling quarterly forecast you can scale up or down with performance and market signals.
Summary for leadership
Headcount is a rolling forecast with agreed triggers (runway, ARR vs plan), not a fixed annual list of reqs.
Publish a rolling 4–6 quarter view, updated monthly or quarterly. Pair it with leading indicators (pipeline, product milestones, attrition) that trigger scenario shifts. Avoid locking 12 months of reqs if your business replans every quarter.
What to do
- Maintain one master tracker (sheet or HRIS plan) with scenario tags.
- Set a monthly or quarterly refresh cadence with Finance.
- Define 2–3 metrics that trigger a scenario review (e.g. runway months, ARR vs plan).
- Keep a “parking lot” for roles deferred without losing context.
Done when
- Rolling forecast date and owner assigned
- Scenario triggers documented and shared with leadership
- Deferred roles captured with rationale
Step 7
Communicate and collaborate
Share the why, involve cross-functional partners, and keep alignment as conditions change.
Summary for leadership
Leaders see priorities, trade-offs, and scenario triggers; hiring managers and Talent know what is approved versus contingent.
Hiring managers need to understand priorities, not just req IDs. Finance needs visibility into timing. Execs need a concise narrative: what we are betting on, what we are delaying, and what would change the plan. Repeat the story when scenarios shift.
What to do
- Run a headcount review with functional leaders each planning cycle.
- Share a one-page summary: scenarios, top hires, trade-offs, and triggers.
- Loop in Talent on capacity (recruiters, agencies, employer brand) before opening reqs.
- Document decisions so new leaders inherit context.
Done when
- Hiring managers know their tier (immediate vs contingent)
- Talent capacity matched to approved plan
- Decision log updated when scenarios change
Planning worksheet
Copy this outline into Notion, Google Sheets, or your HRIS planning tool.
Scenario snapshot
- Conservative / Moderate / Aggressive: one-line description each
- Triggers to move between scenarios
- Planning horizon (quarters)
Objectives map
- Objective → functions → critical roles
- Must-have vs nice-to-have for Moderate case
Role line template
- Role title, level, location, hiring manager
- Scenario, target start quarter, backfill vs net-new
- Linked objective, time-to-hire assumption, ramp notes
- Fully loaded cost (Finance field)
Review rhythm
- Monthly: tracker refresh, attrition and backfill
- Quarterly: scenario check with exec + Finance
- Ad hoc: trigger-based scenario switch
Useful resources
Playbooks and open resources that pair with workforce planning.
Org Design Cookbook
Headcount philosophy examples from published companies
Proving ROI on People Initiatives
Business case framing when headcount supports people programmes
How to use data and storytelling to get heard
MembersOpen Org playbook for exec narratives
Open Org Workspace membership required. You will be asked to sign in.
People Metrics
Benchmark people-team ratio and talent metrics
Transformation Playbook
When headcount change sits inside a wider change programme
More open resources
Other free templates and diagnostics from Open Org.
Build a headcount plan with AI
Build a headcount plan with AIBring your scenarios, objectives, and budget constraints. Open Org Workspace AI can help you draft a rolling plan and a one-page summary for leadership.
Headcount Planning Framework by Open Org. Free to use and adapt under the same spirit as our other open resources.