How Padu Consult came to be, and why it is organised the way it is
The name Padu — meaning solid, reliable, consolidated in Malay — was chosen deliberately. The founders had spent years in enterprise technology roles and observed the same pattern repeatedly: organisations that had lived with an ERP for a decade were routinely advised to replace it by parties with a commercial interest in replacement. The advice was rarely wrong, but it was rarely the only option either.
Padu Consult was registered in Selangor in 2019 with a clear operating principle: every engagement begins with no predetermined outcome. A client asking whether their Oracle E-Business Suite can serve another five years receives the same quality of attention as one asking how to evaluate replacement options. The work is shaped by what the evidence shows, not what a particular answer would mean commercially.
The practice is deliberately small. We do not seek to grow into a system integrator or a software reseller. The value of the work depends on the advisors remaining independent and retaining the time to think carefully about each client's situation. That requires keeping the engagement load at a level where the work can be done properly.
The consultants who conduct our engagements
Engagements are conducted by the advisors listed below. We do not hand work to junior staff after the initial meeting.
Fifteen years in enterprise systems across manufacturing and services organisations in Selangor. Led ERP selection processes for three mid-market firms before founding Padu Consult.
Chartered accountant with deep familiarity with finance module configurations in SAP and Oracle environments. Particular focus on month-end close dependencies and data integrity concerns.
Supply chain and operations background with experience spanning FMCG, logistics and construction sectors across the Klang Valley. Focuses on process-ERP fit and customisation debt analysis.
How we conduct our work, and what clients can expect
These are not marketing statements. They are operating standards we apply on every engagement, and we welcome clients who hold us to them.
Conflict-of-Interest Disclosure
Before any engagement commences, we disclose all prior relationships with vendors, integrators and technology partners relevant to the client's environment.
Written Deliverables Standard
Every engagement closes with a written paper the client retains. Observations and recommendations are stated plainly, with the reasoning set out rather than merely the conclusion.
Client Confidentiality
Engagement materials, system information and internal processes disclosed during our work are treated in strict confidence and not referenced in other client work without explicit permission.
Scope Clarity Before Commencement
We hold a scoping call before every engagement. If the situation is more complex than the standard scope accommodates, we say so and agree revised terms before any work begins.
PDPA Compliance (Malaysia)
All personal and organisational data handled during engagements is managed in accordance with Malaysia's Personal Data Protection Act 2010 and our written data handling policy.
Stakeholder Access
We request access to the people who use the system daily — not only management. The practical knowledge held by system operators is often where the most important observations reside.
ERP advisory in the Malaysian context
Malaysia's mid-market organisations occupy a particular position in the ERP landscape. Many implemented their first enterprise system in the early 2000s — often a regional product, a localised SAP Business One, or a Microsoft Dynamics installation customised to suit local accounting standards and SST requirements. These systems have been modified, extended and worked around over fifteen to twenty years. The question of what to do with them is not straightforward, and the people best placed to answer it are rarely those trying to sell the replacement.
Padu Consult's advisory work covers the full range of ERP decision points encountered by Malaysian finance, operations and IT leadership. This includes assessing customisation debt — the accumulated cost and rigidity introduced by years of bespoke modifications — as well as evaluating whether a move to a cloud ERP addresses the organisation's actual operational needs or primarily the aspirations of a technology department. It includes examining the data quality and continuity considerations that are often underweighted in vendor presentations. And it includes the harder conversation about what an ERP modernisation actually demands from an organisation's people, particularly in the months surrounding go-live.
Our work is conducted in English and Bahasa Malaysia, depending on the preference of the working team. We are familiar with the SST reporting requirements, the typical audit trails expected by Malaysian-listed companies, and the common integration points between local payroll systems and ERP modules that affect data completeness. This familiarity allows engagements to proceed without the explanatory overhead that can burden advisory work conducted by practices with no prior exposure to the Malaysian market.
A short conversation clarifies more than a long proposal
If your ERP situation is one you have been meaning to address properly, an initial discussion with Padu Consult typically takes thirty minutes and requires no commitment on either side.
Arrange an Initial Discussion