Why I Verified AX at a Family Company
Three accounting staff worked overtime every closing season. People were shouldering what the system should have done. This is the story of Astros, the trading company my younger brother runs. Because it was a family company, I wanted to properly verify, for once, the true essence of AX.
Why I Changed Course From Ordinary ERP Automation
It started as ordinary ERP automation. But partway through, I changed course. Rather than a structure where the system does the work, I redesigned it into a structure where employees instruct an LLM in natural language for accounting tasks and verify the results.
The key was letting employees handle MCP (Model Context Protocol) directly. Instead of building a tool, handing it over, and calling it done, I put employees in the seat of giving instructions in natural language and checking the results themselves.
The Change That Mattered More Than 60% Automation
The result was 60% automation of accounting work. But for me, a more important change lay elsewhere. The staff's work shifted from simple data entry to analysis and decision-making, and now employees discover new automations on their own.
Even after the consultant leaves, the system keeps evolving in the employees' hands. That, I believe, is what AX is — not injecting a tool from outside and being done, but an organization beginning to build its own next step.