ERP Management after Go-Live: how to get lasting value from your system
The champagne has been poured, the project team gets a pat on the back, and the steering committee signs off the go-live. But what happens three months later? Across more than 250 ERP projects, we see the same pattern: attention drops off at precisely the moment the system needs it most.
Honestly? This is the phase where most value slips away. Not because the system fails, but because nobody actively maintains it. And that is a waste, because the investment you have made deserves to deliver returns for years to come.
In this article, you will learn why ERP management after go-live matters, what the five pillars of good management look like, and how to take concrete action this quarter.
Why ERP management after go-live is critical
Go-live is not the finish line. It is the starting line. Your organisation has just received a new system, but your people still need to learn how to work with it. Processes that looked right on paper turn out differently in practice. And business does not stand still: new clients, updated regulations, changed workflows.
Good ERP management after go-live ensures your system evolves with your organisation. Without active management, the gap between what the system does and what your business needs grows wider. After 6 to 12 months, that gap is often so large that employees build workarounds in Excel, and the system gradually becomes irrelevant.
Research by Panorama Consulting (2024) shows that 43% of ERP users report within two years of go-live that the system no longer fits their day-to-day work. That is not a software problem. That is a management problem.
The five pillars of effective ERP management
Effective ERP management rests on five pillars. Each of these pillars deserves structural attention, not as an afterthought, but as part of your business operations.
1. Functional management
The functional manager is the translator between business and system. When a department needs a new report or changes a process, the functional manager assesses how this fits within the ERP system.
In many SME organisations with 50 to 500 employees, this role is treated as a side task. That works as long as little changes. The moment your organisation grows or processes shift, a backlog builds up that becomes increasingly difficult to clear.
2. Technical management
Updates, patches, performance monitoring and security. Whether you work with Dynamics 365, SAP, AFAS or another platform: every system requires technical maintenance. With cloud solutions, the vendor handles part of this, but configuring and testing updates remains your responsibility.
A common mistake: postponing updates because “the system is running fine.” After three skipped updates, the gap is so large that the next update becomes a mini-project in itself.
3. User support
Your system is only as good as the people working with it. New employees need to be trained. Existing staff have questions when they perform a process for the first time. Without accessible support, people fall back on what they know: manual processes and parallel spreadsheets.
In our experience, an internal helpdesk or knowledge base is worth the investment many times over. Not as a luxury, but as basic infrastructure.
4. Continuous improvement
Your business changes. Your ERP system needs to change with it. Continuous improvement does not mean running a major project every quarter. It means consistently making small improvements: an additional report here, a process optimisation there, an integration with a new system.
The rule of thumb we apply: allocate 15 to 20% of your original implementation costs per year for management and continuous improvement. Organisations that do this demonstrably get more value from their ERP investment than those that stop investing after go-live.
5. Governance
Who decides which changes get priority? How do you weigh a request from the finance department against a need from operations? Without governance, ERP management becomes an endless list of requests without direction.
Effective ERP governance does not need to be complicated. A monthly meeting with representatives from key departments, a shared priority list and clear ground rules: for most organisations, that is sufficient.
Signs that your ERP management is falling short
Do you recognise one or more of these situations? Then it is time to take a closer look at your management structure.
Employees build Excel workarounds. When departments maintain their own spreadsheets alongside the ERP system, that is a signal the system is not doing what they need.
New colleagues receive no structured training. They learn the system by watching a colleague, including all the bad habits and shortcuts.
Updates are being postponed. “We don’t dare” or “we don’t have time” are common reasons. Both point to insufficient technical management.
Nobody knows who the functional manager is. Or worse: everyone points to someone else.
The original implementation partner has not been in the picture for months. No knowledge transfer, no aftercare, no structural support.
Build in-house or bring in external support?
This is a question we get regularly, and the honest answer is: it depends on your situation.
Building in-house works well when you have enough volume to keep a functional manager occupied full-time, and when you are willing to invest in training and certification. The advantage: short lines of communication, deep knowledge of your specific processes.
Bringing in external support works well when you cannot organise the breadth of expertise internally. An external partner brings experience from dozens of projects, knows the pitfalls and can scale quickly during peak periods. The risk: if knowledge transfer is not properly organised, you remain dependent.
What we recommend to most organisations is a combination. A permanent internal core that manages the system day-to-day, supplemented by an external specialist for complex issues, updates and continuous improvement. This way, you combine proximity with breadth.
The difference is not whether you choose internal or external. The difference is whether you consciously choose a partner whose goal is knowledge transfer, not dependency.
Practical action plan for this quarter
Now is a good moment to evaluate your ERP management. Projects have been launched, teams are at full strength, and there is room for structural improvements.
Step 1: Evaluate your current management structure. Who does what? Has a functional manager been formally appointed? Is there a technical point of contact? Do you have a process for change requests?
Step 2: Take stock of the backlog. Which updates have been postponed? What requests are pending from departments? Where are employees using workarounds?
Step 3: Set priorities. Not everything can happen at once. Distinguish between quick wins (immediate results, minimal effort) and structural improvements (more effort, lasting impact).
Step 4: Allocate budget. If continuous improvement is not in your budget, it will not happen. The rule of thumb of 15 to 20% of implementation costs per year gives you a starting point.
Step 5: Put management on the leadership agenda. ERP management is not an IT topic. It affects financial reporting, operational efficiency and customer satisfaction. It deserves a seat at the table where decisions are made.
Want to know what ERP management, support and continuous improvement look like in practice? We are happy to discuss an approach that fits your organisation.
Frequently asked questions
What does ERP management after go-live cost?
ERP management typically costs 15 to 20% of the original implementation investment per year. This covers functional management, technical maintenance, user support and small-scale continuous improvement. Organisations that structurally allocate this budget report higher user satisfaction and less productivity loss.
When should you start with ERP management after go-live?
Immediately after go-live. The first three to six months are the so-called hypercare period, during which the system is intensively monitored and adjusted. This is when most user questions and process adjustments come to light. Organisations that wait six months before starting management build up a backlog that becomes increasingly difficult to clear.
Can you outsource ERP management?
Yes, ERP management can be partially or fully outsourced to a specialised partner. The most effective approach is a combination of internal functional knowledge and external technical and strategic support. It is important that the partner treats knowledge transfer as a goal, so your organisation does not become fully dependent.
What is the difference between ERP management and continuous improvement?
ERP management focuses on maintaining the system: updates, user support, incident handling and day-to-day functional management. Continuous improvement goes a step further and focuses on enhancing and expanding the system: new reports, process optimisations, integrations with other systems and responding to changing business needs.
ERP Company is an independent consultancy and staffing organisation with 260+ ERP specialists. We are platform-independent and advise on Dynamics 365, SAP, AFAS, Exact and Oracle. Want to know how we can support you with ERP management and continuous improvement? Get in touch for a no-obligation conversation.