08/08/2026
Recently, I received this message from one of my former students who has now become a client.
“This is your field and you have a lot of experience.”
It made me smile.
But beyond the compliment, it reminded me of something I have come to understand deeply through accounting software implementation:
Knowing the software is only one part of the job.
You can be very good at QuickBooks, Sage, ERP systems or any other accounting application and still deliver a system that doesn't really solve the client's problem.
Why?
Because implementation is not about the software alone.
It is about the person who will use it.
When implementing an accounting system, I try to put myself in the same situation as the person sitting on the other side of the desk.
I ask:
If I were the accountant using this system every day, would this workflow make sense to me?
If I were the business owner, would the reports actually help me make decisions?
If I were the person entering transactions, would I understand what to do without constantly calling the consultant?
If I were auditing this business six months from now, would the system produce reliable and traceable records?
Those questions change everything.
A good implementation is therefore not simply:
“Here is the software. Let me show you how to use it.”
It is:
“Let me understand how your business works, where your difficulties are, and then configure the system to make your work better.”
This is why I believe anyone involved in accounting system implementation must understand both sides:
Accounting + Technology + Business Process + User Experience.
Because ultimately, we are not implementing software.
We are implementing a system that people must live with every day.
And if the person using the system doesn't understand it, trust it, or find it useful, then the implementation has not truly succeeded.
That message from my student-turned-client was a simple reminder of why experience matters.
Don't just learn the system.
Understand the person who needs the system.