We are not a tech company visiting your business.

I have been on the other side of this problem myself, more than once.

Sometimes it was an ERP that was never built for the business trying to use it. Operations had to bend to fit the software, not the other way around. Staff invented workarounds just to get through the day. Managers kept a second set of numbers on the side, because everyone quietly knew the official system did not reflect what was actually happening on the ground.

Other times there was no ERP at all, just spreadsheets. A new one for every operation, stock in one file, sales in another, debts in a third, none of them linked to each other. Someone would eventually try to connect them, usually only after something had already gone wrong, a shortfall nobody caught in time, or numbers that could not be traced back to where they broke.

Then the consultants would arrive. They would compare the business to a textbook case study and conclude the problem was the people, not the system. The owner had paid for a source of truth and got another voice in the room to argue with instead.

I watched teams work long hours trying to reconcile numbers that never quite matched, not because anyone was careless, but because the process had never been written down properly. Everything ran on what one or two people happened to remember. When they left, the knowledge left with them.

I lived enough of this, on both sides, rigid systems and disconnected spreadsheets, to know the answer is not another template that assumes every business runs the same way. At Veridian, we start by digitising what a business is already doing, not what a manual says it should be doing. From there, we can actually see what works and what does not. A method that runs perfectly at one business can quietly fail at another, and you only find that out by looking at the real operation first.

Timothy Kavuma, Founder