New role business case template: how to justify a headcount request
On this page
A new role business case is a one- or two-page argument for adding a position that does not exist today. It states the problem, shows evidence, compares hiring with the alternatives, prices the role at its fully loaded cost, estimates what the company gets back and when, names the risks, and ends with a specific request. Approvers are deciding where to spend a limited budget, so the case has to show why this role, now, beats other uses of the same money, including doing nothing.
The business case comes before the job requisition. The requisition records an approved role; the business case is what gets it approved. In organizations with an annual headcount plan, it is also how an unplanned role gets added mid-year.
What approvers look for
| Question in the approver's head | Section that answers it |
|---|---|
| Is this a real problem, or a wish? | Problem and evidence |
| Why a new permanent person, and why not something cheaper? | Options considered |
| What does it really cost, this year and next? | Cost |
| What do we get, and how sure are you? | Return and payback |
| What happens if we say no, or if the hire fails? | Risks |
| How will we know it worked? | Success measures |
| What exactly am I approving? | The ask |
The template
BUSINESS CASE — NEW ROLE: [title, level]
Requested by: [name, team] Approver: [name] Date: [ ]
Decision needed by: [date], because [reason tied to a deadline]
1. THE PROBLEM (3–4 sentences)
[What is not happening, or happening badly, today. Who is affected.
What it costs now, and whether it is growing.]
2. EVIDENCE
- [Metric, trend over the last 3–6 months]
- [Metric]
- [Who is doing this work today, and what they are not doing instead]
3. OPTIONS CONSIDERED
Option Cost Why not / why
Do nothing $0 [consequence]
Redistribute to current team [ ] [capacity check]
Contractor / agency [ ] [duration, knowledge retention]
Tool or process change [ ] [what it would and would not solve]
Hire (recommended) [ ] [why this wins]
4. THE ROLE
Title / level: [ ] Reports to: [ ] Location: [ ]
In the first 6 months this person will: [3 outcomes]
Why this level (not more senior or junior): [ ]
5. COST
Base salary (range midpoint): [ ]
Employer payroll taxes: [ ]
Benefits: [ ]
Equipment, software, training: [ ]
Recruiting cost: [agency fee / job boards / referral bonus]
Fully loaded, year one: [ ] Ongoing annual: [ ]
Cost in this fiscal year (from start date): [ ]
6. RETURN
[Revenue enabled, cost avoided, hours returned × rate, risk reduced]
Assumptions: [list each, and mark estimates as estimates]
Expected payback / break-even: [months after start]
7. RISKS
If we hire: [slow ramp, wrong hire, workload drops]
If we do not: [what breaks, and when]
8. SUCCESS MEASURES
At 90 days: [ ] At 6 months: [ ] At 12 months: [ ]
9. THE ASK
Approve [1] [title, level] at [range], start by [date],
funded from [budget line]. [Or: approve now, open when trigger X is met.]Writing each section well
Problem and evidence
Lead with a measurable symptom, not the solution. "Enterprise onboarding takes 11 weeks against a contract promise of 6" is a problem; "we need an implementation manager" is a proposal. Show a trend, because approvers fund growing problems more readily than stable ones. Name who is covering the work today and what they have stopped doing; the hidden cost of a missing role is usually senior people doing junior work.
Options considered
This is the section that most often decides the outcome, because it shows you have tried to avoid spending money. Give each option an honest line. If a contractor would cover the need for six months while the volume proves itself, say so and propose that instead. A case that recommends a hire after showing why cheaper routes fall short is far stronger than one that never mentions them.
Cost
Use the fully loaded figure, not base salary. In the US that includes the employer's share of Social Security and Medicare tax (6.2 percent up to the annual wage base plus 1.45 percent), federal and state unemployment taxes, benefits, equipment and software, and the cost of recruiting. Show the arithmetic so finance can check it. Also show the cost inside the current fiscal year: a role starting in month ten costs a quarter of its annual figure this year and the full amount next year, and approvers need both numbers.
Return
Match the return to the kind of role:
- Revenue roles: expected bookings after ramp, using your own past ramp times, not a hoped-for first quarter.
- Capacity roles: hours returned to more expensive people, multiplied by what those hours are worth when spent on their real job.
- Risk and compliance roles: the exposure reduced, a commitment kept, or an audit finding closed. Put numbers on it where you can and say where you cannot.
- Customer roles: churn, renewal, response times or contract penalties avoided.
List each assumption. An approver who disagrees with one assumption can adjust it; an approver who cannot see the assumptions distrusts the whole number.
Risks
Include the risks of hiring, not only of not hiring: the role takes longer to fill than planned, the new person takes months to become productive, or demand drops. Say what you would do in each case. It shows judgment, and it answers the objections before the approver raises them.
A filled example
Business case — New role: Implementation Manager (mid-level) (invented)
Problem: new enterprise customers take a median of 11 weeks to go live, against 6 weeks in their contracts. Two customers have asked for credits this quarter.
Evidence: enterprise deals closed per quarter rose from 4 to 9 over the last three quarters. Two solutions engineers spend about 40 percent of their time on onboarding, so pre-sales demos now wait 8 business days on average, up from 3.
Options: Do nothing: credits and slower sales continue. Redistribute: the support team has no spare capacity. Contractor: considered for 6 months, rejected because onboarding knowledge needs to stay in the company and volume is not temporary. Better onboarding templates: already done in Q2; reduced time by about a week, not enough.
Cost: base range $105,000–$120,000, midpoint $112,500. Payroll taxes, benefits and equipment estimated at 28 percent: $31,500. Recruiting via referrals and job boards: $4,000. Year one fully loaded: about $148,000. Ongoing: about $144,000 a year. Starting in month 8 of the fiscal year, this year's cost is about $64,000 (five months of the ongoing cost plus recruiting).
Return: returns about 0.8 of a solutions engineer's time to pre-sales (two people × 40 percent). Credits avoided: $22,000 so far this year. If demo wait times return to 3 days, the sales team estimates one additional enterprise deal per quarter (an estimate, based on two deals lost this quarter where the prospect cited slow follow-up).
Risks: if enterprise volume falls back to 4 a quarter, the role can absorb mid-market onboarding, which support handles today. If the hire takes longer than 8 weeks, the solutions engineers continue as now.
Success measures: 90 days: owns all new enterprise onboardings. 6 months: median go-live under 7 weeks. 12 months: no contract credits for onboarding delays; demo wait under 4 days.
Ask: approve one Implementation Manager at $105,000–$120,000, start by the first week of month 8, funded from the customer success budget's unallocated line.
Common mistakes
| Mistake | How approvers read it | Fix |
|---|---|---|
| Starting with the job title | A request for a person, not a solution to a problem | Open with the measurable problem |
| Base salary only | An understated cost that finance will correct, and distrust | Fully loaded, with the math shown |
| No alternatives | Hiring was the only idea considered | An honest options table |
| Return with no assumptions | A number that cannot be checked | List each assumption, marked as an estimate |
| "Everyone is overloaded" | Every team says this | Specific work, hours and who is doing it today |
| No success measures | No way to judge the hire later | 90-day, 6-month and 12-month measures |
| A vague ask | Nothing specific to approve | Title, level, range, start date and budget line |
After approval
Once approved, the case feeds the requisition: the level, range, start date and budget line should match exactly, or the requisition will bounce. Keep the case with the requisition so the interview panel can see what the role is for; the first-six-months outcomes make a good starting point for the scorecard. The route the approval takes, and how long each step should wait, is covered in hiring approval workflow. If several approved roles then compete for recruiting time, how to prioritize open requisitions gives a way to rank them.
At 6 and 12 months, compare the results with the success measures in the case. It is the only way to learn whether your organization's business cases predict anything, and it makes the next one more credible.
Questions people ask
What should a business case for a new role include?
The problem the role solves, evidence that the problem is real and growing, the options considered besides hiring, the fully loaded cost, what the company gets back and when, the risks of hiring and of not hiring, how success will be measured, and exactly what you are asking the approver to decide.
How long should a headcount business case be?
One to two pages. Approvers read many of these; a short case with specific numbers is more persuasive than a long one with general claims. Put supporting data in an appendix or a linked sheet.
How do I justify a role that does not produce revenue directly?
Show what it protects or frees up: hours of higher-paid people's time returned to their core work, errors or delays avoided, risk reduced, or a commitment to customers kept. Put a number on each where you can, and say plainly which benefits are estimates.
What if the business case is rejected?
Ask what would change the answer: a lower cost, a later start, a trigger such as a revenue level, or stronger evidence. Record the decision and the condition, and bring the case back when the condition is met rather than resubmitting the same document.