"We had been running our Oracle EBS instance since 2007 and the finance team had worked around its limitations for so long that nobody questioned them anymore. Ahmad Hazwan's health review found four specific areas where the customisations we had accumulated were causing month-end delays. The written note was clear enough that I could put it in front of the board without editing."
Accounts from organisations across Malaysia
"After two inconclusive internal studies on whether to move to SAP S/4HANA, we needed an outside view not coming from SAP's partner network. The modernisation paper was the most useful document produced during the whole exercise. Three scenarios, each with risks and costs laid out. We chose the middle path and it held up under audit committee scrutiny."
"The ERP Selection Workshop was the first structured process we had run for a software procurement. Tan Wei Liang pushed us on requirements we had been vague about and the handbook we left with was used almost verbatim in our RFP. The workshop itself was dense — two days is a lot of work — but we were better prepared for vendor presentations than expected."
"I had expected the health conversation to recommend a replacement. It didn't. Raveena spent real time with the finance team and concluded that the data quality issues we were experiencing were process problems, not system limitations. That finding saved us from embarking on a migration that would not have fixed the underlying problem."
"The modernisation advisory took about six weeks. The scoping call was accurate — the engagement ran to the agreed scope and the fee was what we had been told. The scenarios in the paper were realistic. We had hoped for a clearer single recommendation rather than three options, and said so — Ahmad acknowledged that was fair feedback."
"We used the selection workshop after our procurement policy required a documented evaluation process. The selection handbook became part of our formal procurement file. Three vendors were evaluated against the framework we built in the workshop. The process was defensible and the outcome was one we could explain clearly to our board."
Detailed accounts from three engagements
A 220-person manufacturing company on a heavily modified SAP Business One instance from 2009. Month-end close was taking 12 working days. Finance suspected the ERP but could not identify the specific failure points.
Eight structured sessions over ten working days with finance, warehouse operations and IT. The health note identified three customisation conflicts generating duplicate postings and one interface failure creating reconciliation overhead.
Two of four issues were addressed within six weeks using internal IT resources. Month-end close reduced from 12 to 7 working days. The modernisation decision was deferred by a minimum of three years based on the health note findings.
A regional logistics group running Oracle E-Business Suite R12 since 2011. A pending acquisition required the ERP to absorb a new entity. IT was divided between extending the current system and migrating to a cloud ERP before the integration.
Six-week engagement across two office locations with finance, operations and IT leadership. The modernisation paper presented three scenarios with risk registers and indicative cost ranges for each.
The board selected the phased transition scenario. The modernisation paper was presented to the board unedited. The three-scenario format made the decision discussable at board level rather than arriving as an IT recommendation seeking approval.
A 90-person professional services firm had outgrown its accounting-based system and needed to select a proper ERP for the first time. Leadership had received three unsolicited vendor proposals and found them incomparable.
Two-day workshop with finance, IT and operations representatives. Requirements were identified in vendor-neutral language. An evaluation framework was built and the contractual considerations specific to Malaysian ERP implementations were reviewed.
The selection handbook was used as the basis for a formal RFP. Four vendors responded. The evaluation produced a clear preferred vendor and a documented rationale. The firm's managing director described the process as the most orderly procurement decision the organisation had made.
Reach the Padu Consult team
Damansara Jaya
47400 Petaling Jaya
Sat: 9am–1pm
Recognition and affiliations
PDPA Compliant Practice
All engagement data handled under Malaysia's Personal Data Protection Act 2010, with a written data handling policy reviewed annually.
MIM Corporate Member
Corporate member of the Malaysian Institute of Management since 2020, supporting structured continuing professional development for all advisors.
Written Engagement Record
Every engagement since 2019 has produced a written deliverable. No verbal-only advisory work is accepted. This is a practice standard applied without exception.
Consider whether a scoping call would be useful
The organisations whose accounts appear above each began with a brief conversation about their situation. If the circumstances seem familiar, an initial discussion is straightforward to arrange.
Arrange a Conversation