01
Platform chosen on fit
Because the practice implements both SAP Business One and Odoo, the recommendation can follow the client's processes, complexity and budget — including the occasional honest answer that neither is right.
Advise, don't sell.The journey
The platform is a choice. The discipline is the difference.
Waqas Athar leads ERP implementations at KEYOB, covering both SAP Business One and Odoo. That dual capability is deliberate: when a practice can implement two very different platforms, the recommendation can follow the client's processes rather than the partner's catalogue.
His conviction is that most ERP programmes do not struggle on software. They struggle on the parts either side of it — the processes nobody documented, the data quality discovered too late, the integrations left until last, and the support that quietly ended a fortnight after go-live.
So the practice he leads is built around those parts. Fit assessed honestly before anything is bought. Processes mapped before anything is configured. Data treated as its own workstream rather than a task squeezed in near the end. Integration designed into the architecture from day one. And the same team present long after the launch week is over.
01
Assess the fit
Which platform suits the business — or whether neither does.
02
Map the processes
Configure against how the business really operates.
03
Build in short cycles
Validate with real users, never one distant demo.
04
Migrate the data properly
Cleansed, mapped and rehearsed — its own workstream.
05
Land the go-live
Training, cutover and the discipline launch week needs.
06
Stay for the long run
Support and improvement, where value compounds.
A system that is installed is not the same as a system that is adopted. Only one of them was worth the money.