A business case for an HR system is the document that turns a purchase request into a funded decision: what is broken today, what it costs to leave it alone, what the new system costs, and when the two lines cross.
The Association for Project Management defines a business case as a document that justifies a project by weighing its benefits against its costs and risks. Written well, it shows what’s broken today and what leaving it alone will cost. From there, it puts the new system’s price next to that cost and marks the point where the two lines cross.
This guide gives you the six sections written out, a worked ROI calculation, and the questions IT will ask before HR gets to sign
A business case is a written argument for one specific purchase. Addressed to the people who control the budget, it compares the cost of the new system with the cost of keeping the current one.
However, a business case isn’t a vendor comparison. The business case answers whether you should buy at all, while a comparison answers which product to buy. Mix the two, and the document ends up doing neither job well.
Before any of that, you need a reason the request is happening now. A strong case usually starts from one of four triggers:
With the trigger clear, define the system category you’re asking for. Core HR and payroll solve different problems from applicant tracking or performance management, and each one brings its own cost lines. For this reason, it helps to look at the main types of HRIS systems and set the scope before the business case turns into a vague request for “better HR software.”
Every business case that gets funded answers the same six questions in the same order. The order matters more than it seems, since a finance reader tends to stop at the first section that doesn’t hold up.
Write the executive summary last. After all, it summarizes the five sections below it rather than introducing them.
The proposed-solution section should also name the system category, not just the vendor. For example, performance review software can cover formal evaluations and goals alongside one-on-ones and feedback, all without pulling payroll or benefits replacement into year-one scope.

We built a free excell business case template specifically around HR systems that includes every single section we've mentioned above. You can download it for free right here.
The calculation comes down to two savings lines and one cost line. The first saving is the salary cost of the hours the system automates, and the second is the cost of the people you stop losing. From there, you subtract what the software costs per year.
Both savings lines were chosen for a reason. You can calculate each one from your own organization’s data rather than borrowing an industry average. On top of that, finance already treats labor cost and replacement cost as real budget lines, so neither number needs defending from scratch.
Keep the assumptions visible and keep them conservative. A finance reader who can see your inputs will argue with the inputs, whereas one who can’t see them will simply reject the output.
The replacement cost in this model is deliberately low. Teamflect’s methodology sets it at half of annual salary, which works out to $35,000 for an employee earning $70,000. By comparison, Gallup estimates that replacing an individual employee costs one-half to two times their annual salary, or anywhere from $35,000 to $140,000 at that same salary.
Before the numbers go in front of anyone, swap the illustrative figures for your own headcount and salary data, including your real attrition rate. Once you have them, run the ROI model on your own numbers instead of presenting a generic benchmark as your company’s result.
The license fee is the line everyone looks at, and with per-user pricing, it’s the easiest one to calculate. However, it’s rarely the whole first-year cost. A useful business case also accounts for implementation and the integration work behind it.
Getting people to actually use the tool takes effort as well, and that effort has a cost too. Otherwise, the proposal understates total cost of ownership and hands IT or finance an easy reason to send it back.
If your company already pays for Microsoft 365, the last two lines are where the savings sit. However, they’re also the two lines most business cases forget to include.
A business case usually fails in the room it wasn’t written for. To avoid that, write a version of the argument for each person whose signature it needs.
Each reader tests something different. Finance looks hard at the payback period, while IT focuses on risk and integration. Managers, on the other hand, want to know whether the change adds to their workload, and HR operations needs to see that someone can actually run the new process after launch.
A named customer in your own industry answers more objections than another paragraph of benefits. For instance, Andrew Stratton, General Manager at IRE, described the test his leadership applies every year. “Every time it comes up to the Teamflect renewal, the CEO and I look at the value and return on investment for the cost of the software, and it’s unmatched compared to other expenses,” he said.
At many companies with more than fifty employees, the business case needs two approvals. The second is usually a security questionnaire HR has never seen before. As a result, the fastest way to lose momentum is to submit the commercial case without written answers on identity and data handling, or on access controls and vendor assurance.
The answers in the right-hand column below come from what Teamflect documents for its Enterprise plan. Rather than a standard feature list, treat them as an example of what a complete answer looks like. Teamflect’s Enterprise page still refers to Azure AD, which Microsoft has since renamed Microsoft Entra ID, so expect IT to use the newer name.
Get these answers from the vendor in writing before the case goes up, not after IT sends the questionnaire back. For larger deployments, write enterprise security and audit logging into the proposed scope, along with where your data will be stored, rather than assuming they come standard.
A business case rests on five core elements, starting with the problem and what inaction costs. Next comes the proposed solution and its scope, followed by the quantifiable benefits and ROI. After that, the qualitative benefits make the case for what numbers can’t capture, and the rollout plan with its risks closes it out. The template above adds an executive summary as a sixth section, which you should write last.
Follow the six sections in order, starting with the executive summary and ending with the rollout plan and its risks. Keep every assumption visible, so finance and IT can test the same document the executive sponsor reads. Comparing specific tools is a separate exercise, and one that belongs in a vendor shortlist rather than in the business case itself.
Use your own organization’s inputs rather than an industry benchmark. Calculate the salary cost of the admin hours the system can cut, then add a conservative retention benefit if you can defend the assumption. After subtracting the annual software and implementation costs, divide the annual cost by your monthly savings to estimate break-even.
The cost of doing nothing is what the current process keeps costing you every year. For HR systems, the biggest pieces are usually manual administration and late review cycles. Reporting gaps and audit findings add to the total, as does the manager time lost to spreadsheets and disconnected tools.
A decision document typically runs two to six pages plus appendices, depending on the size of the purchase and your procurement rules. Keep the executive summary to one page and put the calculations in tables. The security questionnaire and vendor proposal belong in the appendices along with the implementation plan, rather than in the main narrative.
IT and security usually need to approve how people sign in and where the data lives before HR can buy. Beyond that, expect questions about encryption and audit logs. Access controls and certifications usually come up next, along with how the system connects to your existing stack. Get written answers from the vendor before the business case goes in, rather than after IT returns a questionnaire.

Create high-performing and engaged teams - even when people are remote - with our easy-to-use toolkit built for Microsoft Teams