Measuring the Return on Automation in Shillings, Not Buzzwords
Picture the board meeting. A vendor has just finished a presentation full of words like "synergy", "digital agility" and "transformational journey". The chairman, Mzee Kiprop, takes off his glasses and asks one question: "Sawa. How many shillings?" The room goes quiet. If you are thinking about automation, that is exactly the right question, and working out automation ROI for Kenyan businesses is far less mysterious than the slide decks suggest.
Start with what you are spending today
Before you can measure a return, you need a clear picture of the current cost. Pick the process you want to automate and measure it honestly for two to four weeks. Track:
Time. How many hours per week do staff spend on this task?
Who does it. A senior accountant\'s hour costs more than an intern\'s.
Errors. How often do mistakes happen, and what does fixing them involve?
Delays. Does the slow process hold up payments, deliveries or decisions?
Extra costs. Printing, courier trips, overtime, penalties for late filings.
Do not estimate this from a meeting room. Ask the people who actually do the work. They know that the "quick" weekly report actually takes half a day because the data comes from three places and one of them is a WhatsApp group.
Calculating automation ROI for Kenyan businesses
The simplest calculation is time saved multiplied by the cost of that time. Take the hours staff spend on the task each month, multiply by what an hour of their time costs the business (salary plus statutory costs and benefits, divided by working hours), and you have a monthly figure. Use your own real payroll numbers rather than guesses.
Then estimate how much of that time the automation will genuinely remove. Be conservative. Very few processes go from four hours to zero. Four hours to forty minutes is more realistic, because someone still needs to check the results and handle exceptions.
Count the savings that hide
Time is the easy part. Some of the biggest returns are harder to see but just as real:
Fewer mistakes. A payroll error that overpays staff, or a missed statutory deadline, can cost far more than the hours saved.
Faster cash. Automated invoicing and payment reminders can shorten the time between doing the work and getting paid.
Less staff turnover. People leave jobs full of mindless retyping. Keeping a good employee is cheaper than hiring a new one.
Growth without hiring. If automation lets three people handle the workload of five, you can grow without immediately expanding the team.
Better decisions. Up-to-date numbers mean managers stop guessing.
Put a cautious shilling figure on these where you can, and list the rest honestly as benefits you expect but cannot price.
The full cost of automation
Now the other side of the ledger. Include everything, not just the headline price:
Software licences or development costs.
Setup, data clean-up and migration.
Staff training time.
Ongoing support, hosting and updates.
A period of running old and new processes side by side.
Divide the total cost by the monthly savings and you get a payback period, the number of months before the project has paid for itself. Mzee Kiprop will like that number. It is simple, it is in shillings, and it does not contain the word "synergy".
Measure after, not just before
The most common mistake is calculating the return before a project and never checking afterwards. Three months after going live, measure the same things again. Did the time really drop? Did errors fall? Are invoices paid faster? If the results are weaker than expected, find out why. Often it is a training issue or a step that was never fully switched over.
Honest numbers also help you choose your next project. The process with the best measured return is a strong hint about where to automate next.
If you want help putting real numbers on an automation idea, talk to Philsoft. We are happy to sit with your team, look at the process and give you an honest estimate, in shillings. You can also see the systems we build on our services page. No transformational journeys required.