Most payroll business cases fail for one reason: the number is soft. The cost of the new system is precise and the benefit is vague, so the proposal reads as an expense with a hopeful upside. Reverse that by making the cost of doing nothing as concrete as the cost of change.
The do-nothing option is not free
A new system is never compared against an empty page – it is compared against the status quo. Most cases leave that number out, because it sits across salaries, rework and lost time rather than on an invoice. Making it visible is what turns "a nice-to-have upgrade" into "a cost we are already paying, quietly, every fortnight".
Cost your current system honestly
The licence fee is only part of it. The larger cost is the manual effort, rework and risk around the system – the work people do to make an imperfect system produce a correct pay run. Those hidden costs are where the case is won, because they are exactly what a new system removes.
Manual effort and time
Re-keying between systems, checking every run by hand, and the month-end and year-end load.
Compliance and accuracy
Interpreting awards by hand, correcting underpayments, and staying across STP, payday super, KiwiSaver and Holidays Act obligations.
Integration and data
Reconciling re-keyed data, and fixing interfaces that drift or break.
Reporting and visibility
Spreadsheet rebuilds to answer questions the system can't, and decisions delayed for want of a real-time view of labour cost.
Employee and manager experience
Payroll time absorbed by queries that self-service would handle, and the productivity cost elsewhere.
Resourcing and risk
Key-person dependency, overtime to absorb peaks, and the cost of onboarding into new entities or regions.
Some costs are exposure rather than a bill – a remediation, a penalty, a key person leaving. Price each as cost multiplied by likelihood, so it reads as a defensible expected value rather than a scare number.
Separate the benefits a CFO can bank from the ones they can't
Every hidden cost you remove is a benefit – but keep two kinds apart, because mixing them weakens both.
Quantifiable benefits carry the case: time recovered at a loaded rate, rework avoided, risk reduced, capacity released to absorb growth without adding headcount.
Qualitative benefits are real and worth stating – better experience, faster insight, less key-person risk – but put a dollar value on them and the whole case looks inflated. State them alongside the financial return, not inside it.
The three numbers a CFO looks for
Payback period
How long until benefits cover the cost of change. The most intuitive measure, and often the most persuasive.
Return on investment
Net benefit as a percentage of the investment, across the horizon.
Net present value
The net benefit discounted to today's dollars, so a multi-year case is stated in terms finance trusts.
The cost & benefit model calculates all three from your inputs. Run it at conservative assumptions as well as expected ones – stating the range yourself builds more trust than defending a single optimistic number.
Be honest about the effort, and where the team lands
A board will ask what the change demands, and a case that skips this reads as naïve. Account for project-team time, parallel running and adoption explicitly – as a cost line and a demand on capacity – whether you run payroll in-house or under a supported delivery model.
Be careful how you state the steady state. The gain is usually capacity returned – the same team absorbing growth, skilled people moved off re-keying onto work that needs judgement – rather than roles removed. That framing is both more accurate and easier to approve.
What the free guide covers
A short, practical walkthrough you can work through with your team:
- Start with the cost of standing still
- Cost your current system honestly – the visible and the hidden
- Define the future state and what the change is worth
- Model the investment, one-off and ongoing
- Get to the bottom line – payback, ROI and NPV
- Account for resourcing and change impact
- Package it for the board, with a readiness checklist
Once the business case is approved, the next step is choosing a payroll system or provider.
Prefer to talk it through?
If you'd rather work the case through with someone – costing the current state, testing the benefit assumptions, or reviewing the numbers before they go to your board – we're happy to help.
Get in Touch