To justify hiring a project manager, price what the project management work costs when nobody is doing it properly, then show that a dedicated hire recovers more than it consumes. The case rarely wins on the project manager's own output, because the role produces nothing you can point at. It wins on two numbers: the senior time currently being spent on coordination, and the cost of the delays that happen because that coordination is being done badly by people whose real job is something else.
This is a harder case than a business case for a tool or a project, and it fails for a predictable reason. The person making it argues that things are chaotic and that a project manager would bring order. Finance hears a request to add fixed cost to fix a problem nobody has quantified. The version that works looks less like a plea and more like an arithmetic problem, with the do-nothing option priced honestly and put at the top of the page.
Key takeaways
- Lead with the cost of not hiring. Project management work does not disappear when there is no project manager; it gets absorbed by expensive people doing it badly.
- Recovered engineer or specialist time alone usually does not cover the hire. The case is won on avoided delay.
- Present four options, not one: do nothing, spread the duties, contract a project manager, hire full time.
- Use assumptions your reviewer can challenge (hours, loaded rates, delay costs) rather than industry statistics they cannot verify.
- If the answer is no, ask for a contract project manager on one project and come back with measured results instead of estimates.
How do you justify hiring a project manager?
Quantify the coordination work already being done by people paid to do something else, add the cost of delays caused by that work being done part time, and compare the total to the fully loaded cost of a dedicated hire. Present the do-nothing option as a real recurring cost rather than as a free baseline, and recommend one option clearly.
The framing matters more than the numbers. Nobody approves a project manager because a team feels disorganized. They approve one when a recurring cost with a dollar figure attached goes away, or when a revenue date stops slipping. Your job is to move the conversation from the first framing to the second.
Start by pricing the do-nothing option
Every business case has a do-nothing baseline, and in a headcount case it is the entire argument. The mistake is treating "no project manager" as costing zero. It costs whatever the project management work costs when it is distributed across the team, plus what the failures cost.
Sit down and count the hours actually going into coordination work today. Not the hours a project manager would spend, the hours your current team already spends on the same tasks:
- Status meetings, and the preparation and follow-up around them.
- Chasing dependencies across teams, and the waiting that happens when nobody chases.
- Building schedules, then rebuilding them when they drift.
- Reporting upward, usually by a lead who resents doing it.
- Risk and issue tracking, or the absence of it, which shows up later as rework.
- Stakeholder communication, which typically falls on the most senior technical person available.
Multiply those hours by fully loaded cost, not salary. Then add the second category, which is where the real money is: what did the last two slipped launches cost, in delayed revenue, in extended run costs, in a marketing campaign that ran before the product was ready? Those numbers exist in your organization. Most people never go and get them, which is why most of these cases fail.
The four options to put in front of finance
A one-option business case reads like a demand. Four options read like analysis, and they give a nervous approver somewhere to land that is not "no." Each needs an honest cost and an honest weakness.
| Option | Cost | Where it wins | Where it fails |
|---|---|---|---|
| Do nothing | Recurring: absorbed senior time plus the cost of continued delay | No new fixed cost, no hiring process | The cost is real, recurring, and invisible in any budget line |
| Spread the duties across the team | Recurring, and higher per hour than a project manager | Fast, no approval needed, works at very small scale | Coordination gets the leftovers of everyone's week; no single owner; accountability blurs |
| Contract project manager | Higher day rate, no benefits, no long-term commitment | Fast to start, easy to reverse, proves the value with real data | Costs more per day; knowledge leaves with them; less invested in the organization |
| Hire a full-time project manager | Fully loaded salary, recurring | Lowest long-run cost per hour, retains knowledge, owns the process | Slow to hire, hard to reverse, needs enough work to justify the seat |
Presenting the contract option honestly is what makes the whole case credible, because it is the one an approver will reach for, and it happens to be a genuinely reasonable answer. A case that pretends the full-time hire is the only sane option invites the reader to go looking for the option you hid.
A worked example: the business case for one project manager
The arithmetic below is illustrative. The point is the structure and the honesty about where the case is weak. Substitute your own hours, rates, and delay costs, because a reviewer who can challenge an assumption will engage with the case, while one who is handed an industry statistic will simply not believe it.
Situation. Five senior engineers each spend roughly six hours a week on coordination work: status, dependency chasing, scheduling, and reporting. Assume a fully loaded engineering cost of 90 dollars an hour and 46 working weeks a year.
Cost of the do-nothing option, part one. Five people times six hours times 46 weeks is 1,380 hours a year, at 90 dollars an hour, which is 124,200 dollars of senior engineering time going into coordination.
Cost of the do-nothing option, part two. Over the last eighteen months two releases slipped by roughly a quarter each. One carried a revenue expectation of 1.2 million dollars a year, so a three month slip deferred about 300,000 dollars of revenue. Take a conservative view and attribute half of that to coordination failure rather than to engineering complexity: 150,000 dollars, or about 100,000 dollars a year on an eighteen month view.
The recommended option. Hire one full-time project manager at a fully loaded cost of 150,000 dollars a year.
Benefits. Assume the hire recovers 70 percent of the engineering coordination time, which is 86,940 dollars a year. Here is where the case must be honest: that alone does not pay for the hire. The recovered time is 86,940 dollars against a 150,000 dollar cost, and if the case stopped there it should be rejected. The second benefit is what carries it. Avoiding even one of the two slipped releases over the same period is worth roughly 100,000 dollars a year on the conservative attribution above.
The result. Combined benefit of about 186,900 dollars against a 150,000 dollar cost. Payback lands inside the first year, with a benefit-cost ratio near 1.25. That is a positive but not overwhelming case, which is exactly what an honest one usually looks like.
Two things make this credible. Every number traces to an assumption a reviewer can argue with, and the case openly states that the obvious benefit is insufficient on its own. A case that arrives showing a 4x return on a headcount hire is not persuasive, it is suspicious. For the full document this example sits inside, use the section-by-section structure in our guide to the project business case.
Benefits you can defend, and ones you cannot
Reviewers discount benefits at different rates depending on how checkable they are, so it pays to know which of yours will survive.
| Benefit | How it lands |
|---|---|
| Senior time returned to billable or product work | Strong, if you counted the hours rather than estimating them |
| Avoided delay on a dated, revenue-bearing commitment | Strongest available, and the one that usually wins the case |
| Reduced rework from missed dependencies | Credible if you can name two real incidents and what they cost |
| Better forecasting and fewer surprises for leadership | Real but unquantifiable. Include it, do not lead with it |
| Improved team morale and reduced burnout | True, and worth nothing in a funding meeting. One sentence, no more |
| Industry statistics about project failure rates | Weak. Reviewers correctly read these as decoration |
Give every quantified benefit an owner who will still be accountable for it a year from now, because a benefit nobody owns quietly fails to appear. That principle is the whole subject of benefits realization management, and it applies to a headcount case exactly as it does to a capital one.
Where the case fits in the approval process
A headcount case follows the same structure as any other business case: executive summary, problem, options, costs, benefits, financial analysis, risks and assumptions, recommendation. Keep it to three or four pages. The executive summary should carry the recommendation and the two headline numbers on its own, because plenty of approvers will decide from that page.
Time it deliberately. Bringing a headcount case in the middle of a budget cycle asks someone to find money that is already committed. Bring it with the planning cycle, alongside the portfolio decisions it affects, and it competes on the same footing as everything else. If your organization runs a formal stage gate process, the same discipline applies here, and the reviewers will already be used to reading a case in this shape.
What to do when the answer is no
Most first attempts get declined, and the decline is usually a request for evidence rather than a rejection of the idea. The strongest response is to stop arguing and go measure.
Ask for a contract project manager on one project for one quarter. It is cheaper to approve, easy to stop, and it converts your estimates into observations. Before they start, write down what you expect to change: the hours the team currently spends on coordination, the current milestone dates, the current count of missed dependencies. Measure the same things at the end.
Come back with a case built on what happened rather than what you assumed. A second case that says "we measured 1,380 hours of coordination time, the contractor recovered 900 of them, and the release hit its date for the first time in a year" is a different document from the first one. This is also the moment to be honest with yourself: if the contract quarter produced nothing measurable, the finance team was right, and your problem is somewhere other than project management.
Common questions about the business case for a project manager
What is the ROI of hiring a project manager?
It depends entirely on what coordination work costs your organization today. Calculate it as the senior time recovered plus the value of avoided delay, divided by the fully loaded cost of the hire. Recovered time alone rarely covers a project manager's salary. The return usually comes from delivery dates that stop slipping on revenue-bearing commitments.
How do you write a business case for a new hire?
Quantify the work the role would do that is currently being absorbed by others, price it at their fully loaded rates, add the cost of the failures caused by that arrangement, then compare against the loaded cost of the hire. Present four options including doing nothing and contracting, recommend one, and show the assumptions behind every number.
Should we hire a contract project manager or a full-time one?
Contract first when you have one project to prove the value on, when approval for permanent headcount is slow, or when demand may not persist. Hire full time when project volume is steady, when process ownership and institutional knowledge matter, and when the day rate premium over a year exceeds the cost of a permanent seat.
What if leadership says the engineers can manage the projects themselves?
Agree that they can, then show what it costs. Engineers do manage projects, at a fully loaded hourly rate typically higher than a project manager's, in the fragments of a week left after their actual work. The question is not whether the team is capable. It is whether coordination is the best use of the most expensive hours you own.
How many projects can one project manager handle?
There is no universal number, and any source that gives you one is guessing. It depends on project complexity, team size, stakeholder count, and how much governance overhead your organization imposes. Rather than arguing a ratio, measure the coordination hours your current projects actually consume and size the role against that. The method is the same one used for resource and capacity planning across a portfolio.
Make the invisible work visible
The reason this case is hard is that project management is the only role whose success looks like nothing happening. No missed dependency, no scramble the week before launch, no executive discovering in October that a commitment made in March quietly moved. Absence of drama is a difficult thing to put on a slide.
So do not try. Put the cost of the drama you already have on the slide instead, in dollars, sourced from assumptions your reviewer can challenge. Then ask for the smallest commitment that would let you replace those assumptions with measurements. That is a case a finance team can say yes to, and it is the same discipline that makes every other project business case credible: honest options, traceable numbers, and a recommendation you would still defend if the money were yours.