In ERP Consulting, the Real Problem Is Never the Software

Picture a mid-sized metal processing company in Konya: 107 employees, roughly 23 million Turkish lira in annual turnover, two factory floors, and an inventory management system running across nine separate Excel files. An ERP consultant arrives, assesses the client profile, puts together a comprehensive proposal, and implementation begins. Fourteen months later the system goes live — but warehouse errors are not declining, and the floor supervisor still has not closed his old spreadsheet. A classic ERP story. The problem was never the software. The problem was that the consultant never asked why those nine Excel files existed in the first place.This moment exposes the central contradiction that ERP consulting has been living with for years. One school of thought holds that the consultant’s job is to complete the technical installation, configure the software, and hand over the system. The opposing view argues that a consultant’s real value lies in questioning the existing process, eliminating unnecessary steps, and only then placing technology on that cleaned-up foundation. Both positions have merit, but which one you treat as primary determines the fate of the entire project.The second approach — which I call the ‘product consulting’ frame — treats technical installation as necessary but not sufficient. A consultant can know every ERP module cold and still configure the software incorrectly if they have not asked who authorises a purchase order, at what step an invoice becomes visible to accounting, or whether a paper signature is still required for a warehouse release. Skipping those questions means automating the chaos rather than the process. The Konya firm had done exactly that: every workflow routed through the system collided with parallel workflows running outside it. ‘This is how we work’ was a habit strong enough to outlast the software rollout.In practice, the product consulting frame starts by asking a different set of questions during the needs analysis phase. Instead of ‘which modules do you want?’ the question becomes ‘who creates this data, who consumes it, and what does the lag between them cost you?’ In a similar engagement with a garment exporter in Gaziantep — 260 employees, mid-market in scale — the needs analysis sessions surfaced the following: every export invoice waited for approval from the logistics manager before entering the accounting module, and when that manager was travelling abroad, the delay averaged three working days. The issue was organisational, not technical. The fix required an operational redesign before any software configuration. Had the project started with the installation, this bottleneck would have been invisible until it caused a month-end crisis.Does this approach have limits? It does, and it would be dishonest not to say so. The product consulting frame works when the client is genuinely open to scrutinising their own processes. In Turkey’s SME reality, the moment the owner says ‘this is how our business works,’ process redesign leaves the room. If you cannot break through that resistance, you are doing assembly work, not consulting. In Konya, we broke through only after six weeks of on-site observation produced a number the owner could not dismiss: generating the monthly stock variance report through the existing Excel method took four full working days; pulling the same report from the configured system took two hours. Numbers speak when arguments do not.Integration points are another area ERP consultants routinely overlook. The accounting module works. The inventory module works. But who is responsible for the connection between them? Which data requires human approval before the system updates, and under what conditions does it update automatically? These questions must be answered on paper before software configuration begins. In many Turkish ERP projects, this step is skipped because it takes time, the client pushes for speed, and the consultant accommodates rather than manages that expectation. Both parties complete the project believing they have made progress, but within a few months the integration gaps turn into operational crises — the kind that senior managers blame on the software when the real failure was in the design phase.Moving from ERP consulting toward a product consulting orientation is not a change of expertise. It is primarily a change in the sequence of questions asked. For anyone deciding to make this shift, a concrete frame for Monday morning: first, before any project kicks off, conduct at least two days of needs analysis with actual users on the floor — not a single meeting with management. Second, document every integration point with a responsibility matrix: who approves which data, and what happens when that person is unavailable. Third, before technical work begins, identify and eliminate at least three redundant steps in the current process, and show the client the cost of those steps in measurable terms. Skipping these three actions does not guarantee project failure, but it does predetermine which phase the crisis will arrive in. The real value in consulting is not making the software run. It is making the client see their own operation more clearly than they did before you arrived.

This article was originally published in Turkish by Gökhan MERCANOĞLU on February 1, 2011. The English edition has been reviewed and edited by the author.


For master data management, the critical question is not which system to use. The real question is which problem will be solved, which data can be trusted, and which action will be accelerated. Without these answers, solutions look modern but only digitize old habits.


Gökhan Mercanoğlu
ERP ve Kurumsal Yazılım