Home/Insights/Business case and ROI
The business case for a new HR system, and the ROI your CFO wants to see
By Zené Olivier / Alexandra Wagener · Zanani People Solutions, Cape Town
6 min read

A CFO does not sign for features. They sign for a clear problem, an honest cost and a believable return.
A strong business case for a new HR system shows four things: the problem today, what it costs, the full cost of fixing it, and how you will know it worked. ROI shows what you get back for every rand you spend. Add up the benefits you can measure. Take away the full cost. Then divide by the full cost. Look at it over three years or more. The part most cases leave out is the people side. A system only pays back when people use it.
In our view, CFOs do not reject HR systems. They reject business cases that look too good to be true.
Why business cases fall short
Many business cases focus on licence prices and features. They forget training, communication, data clean-up and the time your own employees will spend, both working on the project for rollout and training on the new system.
Leaders then approve a budget that is too small. The project runs short of time and money in the middle. That is usually when adoption suffers.
The research shows how common this is. AIHR reports that 88% of transformations fall short of their ambitions (AIHR, 7 HR digital transformation challenges). AIHR also advises counting indirect costs, such as employee time on the project and upskilling, not only the price of the technology.
McKinsey's research on AI adoption makes the same point more sharply. In successful AI transformations, for every dollar spent on the technology, organisations spend three on redesigning processes and five on building skills and adoption (McKinsey, How to close the agentic adoption gap). That research is about AI, but the lesson carries: the technology is the smaller part of the cost.
Step 1: Describe the problem in plain words
Start with today, not with the system.
- What takes too long?
- Where do errors happen?
- What risks worry you?
Use your own numbers. Count how many days a leave request takes, or how many hours month-end payroll checks take. Do not borrow numbers from vendor brochures.
Step 2: Put a rand value on the problem
Where you can, show what the problem costs each year.
- Employee hours spent on manual work.
- Payroll corrections, and the time to fix them.
- Late or wrong reports, and the risk that comes with them.
- Time managers lose chasing answers.
Some benefits are hard to price, like better employee experience. Describe them honestly. Do not invent a number.
Step 3: List the South African requirements
Check that your shortlist can handle:
- Payroll and tax. PAYE, UIF and SDL, monthly EMP201 returns and the EMP501 reconciliation with IRP5 certificates.
- Employment Equity. The data you need for your EE reports, if you are a designated employer.
- Skills development. Training records for your Workplace Skills Plan and Annual Training Report to your SETA.
- POPIA. Where employee data is stored, and who can see it.
- Labour law. Leave rules under the Basic Conditions of Employment Act.
- Integrations. How the system links to your payroll, finance and other systems.
If a system needs extra work to meet these, add that cost.
Step 4: Count the full cost, not only the licence
Over at least three years, include:
- Licences or subscriptions, in rand.
- Setup and implementation fees.
- Data clean-up and migration.
- Links to payroll, finance and other systems.
- Training and user support.
- Employee communication.
- Your own employee time on the project.
- A contingency for surprises.
If a system is priced in dollars or euros, show the exchange-rate risk.
Step 5: Show the ROI your CFO wants to see
Keep the maths simple and visible.
ROI = (measurable benefits − full cost) ÷ full cost
Work it out over three years or more. Year one usually carries most of the setup cost, so a one-year view can look poor.
Show your working. A CFO trusts a modest return with clear sums more than a big number with none.
Agree up front how you will measure it. AIHR advises showing leaders what the return will be, how you will measure it, and how it supports business goals. It also notes a CIPD finding: 60% of HR professionals believed their function made a valued strategic contribution, but only 49% said they could measure it.
"Systems don't change organisations. People do." Zanani People Solutions
Step 6: Plan for adoption, and say so
The return depends on people using the system. So the case should answer:
- Who will lead the change?
- How will employees and managers hear about it?
- How will frontline employees without email be reached?
- How will you measure use after go-live?
This section often wins over a sceptical CFO. It shows you have thought past go-live.
Step 7: Give leaders real options
- Do nothing. What happens if we keep things as they are?
- Fix what we have. Can better use of the current system solve part of the problem?
- Buy new. What a new system would cost and change.
Recommend one option, and say why. Put a one-page summary at the front. Put the detail at the back.
An example
Picture an HR manager at a manufacturer. Her first business case listed licence costs and features. Finance sent it back with one question: "What changes, and how will we know?"
Her second version counted the hours her team spends retyping leave forms, added training and communication costs, and named three things to measure after go-live. It was a smaller promise. It was signed.
Try this on Monday
Time one task this week. Pick leave, overtime or onboarding. Count how many people touch it, and how many minutes each spends. Multiply by how often it happens in a year. That is the first real number in your business case.
How Zanani helps
Zanani is an HR technology adoption partner and HR advisory. We help you build the case before you buy, so leaders sign for something real. Here is what that looks like for you:
- A clear problem. Today's pain is written in plain words, with your own numbers.
- An honest cost. The people side is in the budget, not left out.
- A return you can track. Measures are agreed before go-live.
- A plan for adoption. Leaders can see how people will take it up.
We work directly with organisations, and we also work with HR technology providers. Every organisation is different, so let's talk about how we do it.
FAQ
How do you build a business case for a new HR system?
Describe today's problem, put a rand value on it, list South African requirements, count the full cost, show the return and plan for adoption. Then give leaders clear options.
How do you calculate the ROI of an HR system for the CFO?
Take the measurable benefits, subtract the full cost and divide by the full cost. Work it out over three years or more, and show your working.
What costs do business cases usually miss?
Training, employee communication, data clean-up, links to other systems and your own employee time on the project.
What South African rules should the business case cover?
PAYE, UIF and SDL; EMP201 and EMP501 returns; Employment Equity reporting; skills reporting to your SETA; POPIA; and leave rules under the BCEA.
What if we cannot price every benefit?
Describe it honestly. Leaders trust a case more when it does not invent numbers.
Building the case for a new HR system? Email info@zanani.co.za or see what we do. We would love to talk.
FAQ: How do we support your digital journey?
