Most small companies don't have a hiring plan. They have a wish list.

The list lives somewhere between a spreadsheet and the CEO's head. It changes every time a department head asks for something. Roles get opened reactively when someone quits or a problem becomes urgent. Nobody can tell you what the company will look like at 50 employees because nobody's actually planned it. The result: erratic hiring, surprise budget conversations, and the wrong sequence of hires for what the business actually needs.

This article gives you a hiring plan template you can build in 90 minutes. It's not the elaborate workforce planning model used by 5,000-person companies. It's the workable version that holds up against the realities of running a small business: limited budget, changing priorities, and incomplete information.

Why most SMBs don't have a hiring plan

Three reasons, all valid in isolation, all costly in aggregate.

The business changes too fast to plan for. Founders argue that planning a year of hiring at a 30-person company is silly because the next 12 months will look nothing like the last 12. There's some truth here, but it's overstated. The broad shape of the year (revenue targets, key initiatives, capacity gaps) is usually predictable even if the specifics aren't.

Department heads can't agree on priorities. Sales wants more sellers, product wants more engineers, marketing wants more demand gen. Everyone's case is reasonable in isolation. Without a plan, the loudest case wins, which is rarely the most strategic case.

The CFO and CEO don't have a shared view. The CEO has growth ambitions. The CFO has burn constraints. Without a written plan, these collide in real time, usually unproductively. A good hiring plan makes the trade-offs explicit before they become arguments.

A plan doesn't solve these problems entirely. It does turn them from recurring friction into a single decision conversation each quarter.

What a hiring plan should do

Three jobs.

Tie headcount to business outcomes. Every role on the plan should answer the question "what business outcome does this hire unlock?" If you can't answer that, the role probably isn't ready to be approved.

Sequence hires intentionally. Not all roles can be hired at once, even with unlimited budget. Onboarding capacity is real. Some hires depend on other hires. The plan should show what comes first and why.

Create accountability across founders, finance, and hiring managers. Once approved, the plan is the document everyone references. New requests have to be added to the plan, displacing something else. The plan stops the constant ad hoc negotiation.

The template

Here's the structure to use. Keep it to one document, one page per quarter.

1. The top-line summary

A short paragraph at the top, no more than 5 sentences:

• Current headcount and start-of-period headcount

• Target headcount at end of period

• Total compensation budget for new hires

• Key strategic outcomes the hiring plan supports

• Major risks or assumptions

This is the version the CEO and CFO read in 90 seconds.

2. The role-by-role plan

A simple table:

For each role:

• Role: Specific title (e.g., "Senior Backend Engineer," not "Engineering Hire")

• Function: What team they're joining

• Target start date: Realistic, accounting for hiring timeline (typically 8-16 weeks from search start)

• Compensation: Total expected (base + variable + equity, or just total compensation cost)

• Outcome unlocked: What this role enables. Specific. "Improves engineering throughput" doesn't count. "Owns checkout reliability, currently sitting at 92%, target 99.5%" does.

• Confidence: High / Medium / Low. How sure are you this role is needed?

Sort the table by target start date.

3. The sequencing logic

A short paragraph explaining why the roles are sequenced the way they are. This is where you make the trade-offs explicit.

Example:
"We're hiring the Sales Manager before the second AE because the manager needs to be in place to onboard and ramp the AE. We're delaying the second engineer until Q3 because we expect our infrastructure refactor to absorb most of the first engineer's time through Q2."

The sequencing logic is what separates a plan from a list.

4. The contingencies

A short section covering what would change the plan:

• If we miss revenue targets by X%, which roles get cut and in what order?

• If we exceed revenue targets, what roles do we add and in what order?

• Which roles are absolutely committed, and which are conditional?

This is the section that prevents most of the year's stressful conversations. If everyone has aligned on what cuts come first if growth slows, the actual conversation when growth slows is much easier.

5. The risks

A short list of known risks:

• Specific roles likely to be hard to hire (and why)

• Specific roles that compete with major company priorities for attention

• Specific budget assumptions that could change

Listing risks doesn't solve them. It just makes them visible so they don't blow up the plan invisibly.

An example, partially filled

Here's what a real plan section might look like for a 30-person SaaS company hiring for a year.

Hiring Plan: H1 2026 (Q1-Q2)

Summary:
Headcount grows from 30 to 38 in H1. Total comp investment $1.4M annualized for new hires. Plan supports our Q2 product launch and the Series B raise targeted for end of H1. Three roles are conditional on Series B closing.

Sequencing logic:
Product Manager and Senior Engineer in Q1 support the Q2 launch. AE before Sales Manager because we want the AE in seat before adding a manager. CS hire timed to the launch (more accounts, more support needed). Q2 roles all conditional on Series B closing in May.

Contingencies:
If we miss Q1 revenue by more than 10%, we delay the Demand Gen hire and revisit the CS hire. If Series B slips, all Q2 conditional roles delay until close. If we exceed Q1 revenue by more than 20%, we accelerate the second engineering hire by 4-6 weeks.

Risks:
Senior Engineer search likely 14-16 weeks, not 8-10. Sales Manager search is competitive for our comp range. Demand Gen hire requires a specific paid acquisition skillset; backup is contracting through Q2.

How to build your first plan

If you don't have a hiring plan, you can build a workable one in 90 minutes.

Step 1 (15 min): Take stock of where you are. Current headcount, by function. Open searches. Roles being talked about but not yet approved.

Step 2 (20 min): List every role you think you need in the next 6-12 months. Don't filter. Get them all on paper. Include the obvious ones, the maybe ones, and the wishful ones.

Step 3 (15 min): For each role, write the outcome it unlocks. If you can't write one, mark it for further conversation with the requesting manager.

Step 4 (15 min): Sequence the list. What needs to come first? What depends on what? What's blocked by capacity (onboarding, etc.)?

Step 5 (15 min): Sanity check against budget. Add up the comp. Compare to what's actually approved. Cut to fit, or flag what needs more budget approval.

Step 6 (10 min): Write the contingencies and risks. What would change this plan? What are you assuming?

That's the V1. It won't be perfect. Share it with the leadership team, get feedback, iterate. Within two weeks you'll have a workable plan.

How to use the plan once you have it

Three habits.

Quarterly review. Every 90 days, review the plan against reality. Roles hired, roles delayed, new roles requested. Adjust forward.

Single source of truth for new requests. Any new hire request goes through the plan, not around it. New role? It has to displace something or add net new budget.

Forward-look at every leadership meeting. Quick 5-minute view in the leadership team's weekly: who's in process, what's coming next, where are we stuck? Keeps the plan alive between formal reviews.

What separates a great hiring plan from a workable one

Three things.

Outcomes, not roles. Strong plans describe what each hire unlocks for the business. Weak plans list functions and titles.

Explicit sequencing logic. Strong plans explain why the roles are in this order. Weak plans just list them.

Honest contingencies. Strong plans acknowledge what would change the plan and how. Weak plans pretend the future is knowable.

If your plan does these three things, it'll outperform 90% of the hiring plans at other small companies.

A note on hiring plans for hyper-early stage

If you're under 15 people, the plan can be simpler. A list of the next 3-5 hires in priority order, with the outcome each one unlocks, on a single page. The structure above is overkill for that stage. The principles (outcomes, sequencing, contingencies) still apply.

What's important at any stage: writing it down. The plan in someone's head is not a plan. It's an aspiration.

Build it into your hiring process

A plan is only valuable if it shapes what actually happens. Build the plan into:

• Budget approvals (no headcount approved without being on the plan or displacing something on the plan)

• New role requisitions (see What Is a Job Requisition?, which is the document that opens a search against the plan)

• Quarterly business reviews

The plan is the document that everyone references. The requisitions are how individual searches get approved against the plan. The hiring process executes against approved requisitions.

Previously in this series: Hiring Plan Template (For SMB Teams)
Next in this series: Candidate Communication Email Templates (For Every Stage)