Scenario-Based Workforce Planning for 20-500-Person Companies

Short answer: Build three headcount plans instead of one: a base case, a slower case and a faster case, each tied to a business driver such as revenue or customers. For each role, decide whether to hire, build, borrow or automate, and agree in advance which signal moves the company from one plan to another.

Most growing companies plan headcount as one spreadsheet with one number per team. It works until revenue misses, a large customer arrives early, or AI tools change how much work a team can do. Then the plan is either ignored or rebuilt in a hurry.

Employers expect large shifts: the World Economic Forum's Future of Jobs Report 2025 found employers expect a significant share of workers' core skills to change by 2030 (World Economic Forum). Scenario planning makes those shifts part of the plan instead of a surprise.

A team in a conference room listening to a colleague presenting at the front
Photo: Christina Morillo on Pexels

Three Scenarios, One Driver Each

An example of three scenarios for a 150-person company (illustrative)
ScenarioDriver assumptionNet new rolesTrigger to switch
SlowerRevenue +5%6Two quarters below plan
BaseRevenue +15%18Default
FasterRevenue +30%34Pipeline 25% above plan for a quarter

Tie each team's headcount to a driver it actually depends on: support to customers or tickets, sales to quota capacity, engineering to the product roadmap. Leaders then argue about the driver, which is useful, instead of the number, which is not.

Hire, Build, Borrow or Automate

For each planned role, ask four questions in order:

  1. Automate: can software or AI tools absorb part of the work? Plan for partial gains, not full replacement.
  2. Build: can someone already here grow into it within six months?
  3. Borrow: would a contractor or part-time specialist cover it until the need is proven?
  4. Hire: if none of the above, open the role, and know the skills it needs before you post it.

Building from within is usually cheaper and faster than hiring, and it keeps good people. Organization Viewer shows who reports where, spans and open roles, and its headcount planning view lets you try a reorganization or a hiring plan in a sandbox before committing.

The Inputs That Make the Plan Honest

  • Attrition by team. If a team loses 20% a year, a plan for 10 net new roles means 14 or more hires.
  • Time to fill and time to productivity. A role needed in April may need a February start.
  • Fully loaded cost. Salary plus benefits, taxes, equipment and recruiting.
  • Internal supply. Who is ready to move up or across in the next six to twelve months.

Turnover and hiring data from the U.S. Bureau of Labor Statistics give useful benchmarks for your industry (BLS JOLTS). Insight Studio can bring your HR, finance and recruiting exports into one table so each scenario uses the same numbers.

Plan Fairly When the Plan Shrinks

The slower scenario sometimes means fewer roles. Decide in advance how you would choose: by role and skills needed, not by who is easiest to let go. Check any reduction list by group before acting, the same way you would check a hiring stage; Hiring Fairness has a free four-fifths rule calculator for exactly that.

A Quarterly Rhythm

Keep the plan small enough to maintain. One page per scenario, one row per team, with the driver, the assumption, the net new roles and the cost, is enough for most companies under 500 people. Anything bigger tends to go stale after the first quarter, and a stale plan is worse than none, because leaders stop trusting it and go back to asking for headcount one role at a time.

Review actuals against the base case every quarter, check the trigger signals, and move to another scenario only when a trigger is met. Update the plan once, share it with finance and team leads, and keep the version history so next year's assumptions improve.

If you want help building the first version, our workforce analytics consulting team sets up the drivers and scenarios with you, and the Reorganization Design and Facilitation engagement covers larger structural changes.

Questions

How many scenarios should a small company plan?

Three is enough: slower, base and faster. More scenarios add work without adding much insight at 20-500 people.

How often should a workforce plan be updated?

Review it every quarter against actual results and the trigger signals you agreed on. Rebuild it fully once a year with the budget.

How do I account for AI in headcount planning?

Ask, role by role, which tasks AI tools can take over, and plan for partial productivity gains. Avoid assuming whole roles disappear; most change shape instead.

What is the difference between headcount planning and workforce planning?

Headcount planning sets how many people each team gets. Workforce planning adds which skills are needed, where they come from (hire, build, borrow, automate) and when.

Who should own the workforce plan?

HR and finance together, with each team lead owning their driver assumptions. A plan owned by one function alone rarely survives the first budget review.

Sources

← All hr and people analytics trends