Business · Finance

A CFO's guide to costing an automation project

Labour is getting more expensive and software is getting cheaper. How to build an honest business case for automating a process: what to count, what to leave out, and when the numbers say no.

Pikabyte Engineering 4 min read

RM1,700

monthly minimum wage, in force for all employers since 1 August 2025

Two lines on a Malaysian income statement have moved in opposite directions.

Labour costs have risen. The minimum wage went from RM1,500 to RM1,700 on 1 February 2025, and applied to every employer, including those with fewer than five staff, from 1 August 2025. From 1 October 2025, employers and non-Malaysian employees each contribute 2% of wages to the Employees Provident Fund.

The cost of software that does routine work has fallen. Reading a document, filling a template, moving data between systems: tasks that needed a custom project and a large budget a few years ago are now modest ones.

That makes more processes worth automating than before. It does not make every one worth automating. Here is how to tell.

Step 1: Count the real cost of the manual process

Start with hours, then be honest about the rate.

Hours per week. Ask the people doing the work, and watch for an afternoon. The figure is usually higher than managers believe, because nobody counts the interruptions and the rework.

Loaded cost per hour. Salary is the start. Add EPF, SOCSO, EIS, leave, medical, allowances, workspace and the share of a supervisor’s time. A loaded cost of 1.3 to 1.5 times base salary is a reasonable planning range.

Error cost. How often does it go wrong, and what does a mistake cost? A wrong invoice, a missed deadline, a re-issued certificate. Estimate frequency times average cost. Be conservative, but do not leave it at zero.

Delay cost. If invoices go out a week late because of a backlog, that is working capital. If quotes take three days, some orders are lost.

Annual cost = (hours × loaded rate × 50 weeks) + errors + delay.

Step 2: Count the full cost of the solution

Vendors quote the build. You need five numbers.

  1. Build. Most of our custom projects fall between RM30,000 and RM150,000 depending on scope.
  2. Running cost. Hosting, AI usage if any, licences, per month.
  3. Support and maintenance. Fixes, security updates, small changes.
  4. Your own people’s time. Requirements, testing, training. Real, and almost always left out.
  5. Change. A period of running old and new in parallel, at lower productivity.

Ask how running cost scales with volume. Consumption-priced services grow with usage.

Step 3: Calculate payback, conservatively

Do not assume the manual hours fall to zero. A person still reviews the output and handles exceptions. Assume 60% to 80% of the hours are recovered, and test the case at the lower figure.

Payback period = total first-year cost ÷ annual saving.

In our experience clients commonly recover ten to twenty hours a week from a single workflow, and most projects pay back within six to eighteen months. If yours shows payback under three months, check the assumptions. If it shows more than three years, it is probably not the right project.

Step 4: Be clear about what the saving is

A recovered hour is only a saving if something happens with it. Decide in advance which it will be:

  • Capacity. The same team handles more volume. Often the most realistic outcome for a growing business.
  • Avoided hire. A planned position is not needed.
  • Redeployment. People move to work that earns more.
  • Headcount reduction. The rarest in practice, and the one business cases most often assume.

Write the choice into the business case. “Efficiency” without a destination tends to evaporate.

Step 5: Price the risk

Delivery risk. Will it work? Reduced by seeing a working demo before committing. We build one before we send a quotation, for exactly this reason: it turns the largest uncertainty into something you can look at.

Adoption risk. Will staff use it? Reduced by involving them in testing.

Dependency risk. What if the supplier disappears? Reduced by owning the source code, the data and the cloud account.

Security risk. New systems hold data and credentials. Ask how access is controlled. A leaked cloud credential can produce a bill larger than the project.

When the answer is no

Say no when the process is rare, when it changes every month, when an off-the-shelf product already fits, or when the volume is too low to repay the build. A spreadsheet and a careful person is sometimes the right system.

The value of doing the arithmetic is that it gives you a reason for either answer.

Our free automation readiness assessment includes a worksheet for these calculations.

Sources

This article is general information and is not financial or tax advice.

Written by

Pikabyte Engineering

Pikabyte builds custom business systems, applied AI and secure cloud infrastructure from Malaysia. Talk to us.

Start a conversation

Want this applied to your business?

Tell us what is slowing the business down. You will talk to an engineer, not a salesperson, and get a straight answer on whether software is the right fix.