The Efficiency Paradox: Why My Accountant Delayed for 4 Months

My accountant delayed a software migration for four months. He had good reasons each time. Data needed cleaning. Templates were not ready. Month-end was coming. When COVID lockdown cut the workload, I thought we would finally have time. We resumed three months later. Same excuses.

I finally put my foot down. “Fifteen days. Everything is mapped. If something breaks, we fix it during migration. No more delays.” We moved to Zoho Books. Billing dropped from four to five days a month down to two.

Five months later, he told me why he had stalled.

“I was worried that if this system makes everything easier, you might replace me.”

He had built those Excel templates over years — formulas, macros, shortcuts. They were his expertise. Zoho Books made all of it obsolete. His fear was not irrational. It was accurate. I had assumed the benefits were obvious. I had never told him his job was safe.

The same pattern appeared with payroll software. We had 450 employees on monthly payroll. Manual calculation in Excel took seven to nine days. I paid Rs 2.5 lakh upfront for the software. The team knew the money was already spent. Resistance was quieter. But it was still there.

Migration took five weeks instead of three. Once done, payroll dropped to two days. We now have 750+ employees. The same person handles it. Without automation, I would need one extra person for payroll and one for billing — roles I never had to hire for because the system absorbed the growth.

I recently finished The Goal by Eli Goldratt. The part that stayed with me was a quiet essay at the end. He wrote about the people who fix broken systems — the ones who challenge how things are done and make everything better. They are often made redundant by the fix itself. The people who created the efficiency pay the price for it.

I had seen this fear. I just did not know where it came from.

Efficiency, in theory, creates freedom i.e. more capacity, better systems, less grunt work. In practice, it creates anxiety. Everyone has learned that efficiency gains usually mean fewer jobs, not better work. So when you announce automation, people hear: you are about to make yourself redundant.

That is not a performance problem. It is a trust problem.

The people who know the broken processes best are the ones who could fix them fastest. But they will not due to a fear that fixing the system means eliminating their role.

I do not announce automation anymore. I start with a meeting. I ask two questions.

• What work do you find most boring and repetitive — the grunt work you would happily stop doing?
• And what work do you wish you had more time for, but cannot reach because the grunt work fills your day?

They tell me. Then I reframe what the software does. This new system takes care of the billing runs. That frees you to do the financial analysis you never have time for. No one is being let go. When we scale, we will not need to hire more people for this, and you will not drown in more billing runs.

After Zoho Books, my accountant started doing financial analysis and cash flow modelling — work he never had time for when billing consumed a 10+ days every month. After payroll automation, the same person who handled 450 employees now handles 750+. He could likely manage 1,500 to 2,000. No new hire needed.

I am still working out the hard case: Automation that genuinely makes someone redundant, not shifts their work to better tasks but removes the need for the role entirely.

I do not know what I will do when that day comes. For now, I check every automation plan against one test: can I explain to my team why this will not cost them their jobs? If I cannot, I am either lying or I have not thought it through. Usually the latter.

My accountant delayed for four months because I never gave him that trust upfront. I thought the logic was obvious. It was not.