Building for CA Firms: Websites, Tally Tools and the Hours Automation Gives Back

Building for CA Firms: Websites, Tally Tools and the Hours Automation Gives Back

Chartered accountancy firms have been part of my work since my own software business began in 2001. A commerce degree meant I already spoke their language, and that turned out to matter more than any programming language I knew.

The work came in many shapes: websites, Excel and VBA tools, tools around Tally, systems for collecting client documents, and plain automation of office work. Later I spent two years inside a firm of chartered accountants as a senior audit manager on SAP systems, which showed me the same work from the other side of the desk.

How the work found me

Mostly through people: friends and relatives, contacts from my own accounting work, my college network from St. Xavier's, and one CA recommending me to another.

Referrals between CAs make sense once you see how the profession works. Accountancy runs on trust. A firm that hands someone access to its systems, and through them to its clients' numbers, wants a name it has heard from a colleague, not a name it found on a flyer. Every job done well was the advertisement for the next one, and every job done badly would have been too.

What a CA firm's website has to do

A CA firm's website has a narrower job than most business sites, and a harder one. The firms I built for wanted it to:

  • Look attractive and trustworthy. A profession that deals in other people's money cannot look careless online.
  • Show what the firm really knows. Not a slogan, but a complete picture of the tax and audit work it does, so a visitor can tell straight away whether the firm handles their kind of problem.
  • List the services and make contact easy. Who to call, where the office is, what to send.
  • Carry tax dates and updates. Clients come back to a site that tells them what is due and when.
  • Cost little and need little looking after. A firm's time is its product; nobody wants to spend it updating a website.

There is a balance in there. Chartered accountants work under professional rules about how they present themselves, so the site has to inform rather than sell. The way through is substance: show the work clearly and completely, and let a visitor reach the conclusion themselves.

The tools behind the website

The website is only the part clients see. Behind it is the work every firm repeats, season after season, close to a deadline: pulling figures out of Tally, reshaping them in Excel, chasing clients for the same documents every year, typing the same numbers into the next form.

That is where Excel and VBA tools, Tally-related tools and document systems came in. The useful ones are rarely large. Each takes a task somebody does by hand, the same way every time, and makes it happen with a click, checked and consistent. A document system means clients send what is needed to one place instead of to five inboxes. A VBA tool means a report builds itself from the export instead of from an afternoon of copying.

Automation is not about replacing people. It is about giving the hours back to the work only people can do.

Why automation pays

This is the lesson I would most like a business owner to take from those years. In a CA firm, time is the product. An hour spent re-typing figures is an hour that cannot be spent on advice, on reviewing a file properly, or on another client. Automating that hour saves its cost twice: once in the wages, and once in the work that can now be done instead.

Saved time becomes saved cost, and saved cost becomes profit, with a smaller chance of a typing error reaching a client along the way. That arithmetic is the same for any business that repeats work, and it is why automation has stayed at the centre of everything I build.

Know the business first

The tools worked because I understood what they were for. I knew what a trial balance was before I wrote code that touched one, and I knew why a particular report mattered in a particular month. A programmer who did not know accounting could have built software that ran perfectly and still did the wrong thing.

That is still how I work. The code is the easy part to change. Understanding the business is the part you cannot skip, and the reason a small, useful tool beats a large impressive one is that it was built by someone who knew exactly what the work was. If your firm repeats the same task every month, that is a conversation worth having: tell me about it.