How to build the business case for replacing HR software

A business case for new HR software has one job: to let a sponsor say yes or no with confidence. It does not need to be long. It needs honest numbers, a small set of options, and a clear recommendation. This is a way to build one in an afternoon once you have the inputs.

Step 1: add up what you pay today

Start with the yearly cost of how things work now. It is easy to count the subscription and stop. The fuller list has four lines:

• Subscriptions. The current HR system, the payroll provider, and any modules billed separately.
• Manual admin time. Hours spent re-keying data, chasing approvals and reconciling spreadsheets. Estimate hours per month, multiply by twelve, and multiply by a loaded hourly cost that Finance agrees with.
• Error corrections. Off-cycle payroll runs, corrections and the time spent on them.
• Side tools. Spreadsheets, form builders and add-ons that exist to cover gaps in the main system.

Be conservative with the time estimate. A sponsor will test the softest number first. If it holds, they trust the rest.

Step 2: describe two or three options

For each option you need two numbers:

• One-time cost. Implementation fees, data migration, integration work, training, and any overlap period where you pay for both systems.
• Cost per year. The subscription at your headcount, plus support and any modules you will need.

Include a "stay as we are" option in your thinking even if it is not on the page. It is what every other option is measured against.

Step 3: work out the three figures

The arithmetic is short.

• Saving per year = cost today − the option's cost per year
• Payback in months = one-time cost ÷ (saving per year ÷ 12)
• Three-year net = 3 × saving per year − one-time cost

If an option costs more per year than you pay today, it has no payback on cost alone. Say so plainly. It may still be the right choice for other reasons, and step 5 is where you make that argument.

A worked example

These figures are made up to show the method. A small company adds up its current yearly cost:

Cost today	Per year
HRIS and payroll subscriptions	$27,600
Manual HR admin time	$21,800
Payroll error corrections	$4,000
Spreadsheets and add-on tools	$2,400
Total	$55,800

It compares two options:

	Option A	Option B
One-time cost	$15,000	$28,000
Cost per year	$34,000	$31,000
Saving per year	$21,800	$24,800
Payback	About 8 months	About 14 months
Three-year net	$50,400	$46,400

Option B saves more each year. Option A pays back sooner and is ahead after three years, because B's higher setup cost takes time to earn back. Over five years B would pull ahead. A sponsor can decide with that in view, and it took three lines of arithmetic to get there.

Step 4: show your assumptions

List the assumptions under the numbers. Headcount, hourly cost, how much manual time you expect to remove, and how long both systems will overlap. Then show what happens if the main one is wrong. If you expect to remove 80% of the manual admin time and only remove half, does the option still pay back inside three years? A case that survives that test is one a Finance lead will support.

Use vendor quotes for the one-time and yearly costs, and check what the quote leaves out. Integration work, extra environments and training are the usual gaps.

Step 5: make the case beyond cost

Cost is rarely the whole reason. The other reasons are stronger when they are specific and countable.

• Pain points. Map your current processes and count the steps that involve re-keying, manual checks or waiting on an inbox. "Eleven steps across five processes depend on someone copying data by hand" is evidence. "The system is clunky" is a complaint.
• Risk. Where does compliance depend on one person's memory? Where does payroll depend on a spreadsheet only one person understands?
• Experience. What do new hires, managers and employees have to do today that they should not have to do?
• Growth. What breaks at the next fifty hires, the next state or the next country?

Keep this section to half a page. One counted fact per point is enough.

Step 6: recommend, and ask for a decision

End with one recommendation and one request. Name the option, the cost, the payback and the date you need an answer. Then get the decision recorded as approved or not approved, with the sponsor's name. A project that starts on a verbal "sounds good" has no answer when someone asks who agreed to the budget.

Mistakes that sink a business case

• Counting every saved hour as cash. Saved time is real, but it only becomes money if the time is used for something of value. Say what the team will do with it.
• Leaving out the overlap period. You will probably pay for two systems for a while.
• Using list prices. Use the quote you have, for the headcount you have.
• Too many options. Two or three is enough. Six looks like you have not decided what you think.
• No date for the decision. Without one, the case sits in an inbox.

Where HRjects fits

Every HRjects project has a business case workspace. You enter the yearly cost lines for today and one or more options with a one-time cost and a cost per year. It works out saving per year, payback in months and three-year net for each option, counts the pain points you flagged on your process maps, and records the sponsor's decision as Pending, Approved or Not approved. It does the arithmetic above and nothing fancier. The steps are in the business case help article, and you can try it for free.