ERP functional management: in-house or outsource?
The go-live went well. The project team has closed its last incidents. The external consultants have moved on to their next assignment. And then, a few weeks later, someone on the team asks a question nobody prepared for:
“Who actually adjusts the approval workflow when we need a second signature?”
It sounds like a small question. It is a governance question. Because at that moment, most organisations have no clear answer. A key user picks up the task, without a mandate, without a procedure, without any record of what changed. That is how functional ERP management begins in most organisations: not as a plan, but as something that quietly grew.
Functional ERP management is the structured adjustment, documentation and ongoing development of your ERP configuration after go-live, so the system grows with your business processes. It sets itself apart from technical management, which deals with servers, updates and security patches, because it works on the content layer: processes, permission structures, reporting, user support and configuration choices that touch daily operations.
In our experience with 265+ specialists working on ERP projects, the quality of this management decides, to a large degree, the long-term value an organisation gets from its ERP investment. Yet it is the item that receives the least attention during project planning, and lands on the agenda far too late.
Why functional management is structurally overlooked
During an ERP implementation, the agenda is full of concrete milestones: requirements, configuration, test phases, go-live. Management sits at the bottom of that list, as something that “gets sorted once we are live.”
That has two consequences we see time and again.
Key users build up the most knowledge about the system during the project. An organisation that does not secure that knowledge in a management structure watches it drain away the moment the project ends and people return to their regular workload. Two years later the same questions resurface, but the people who could answer them have moved on.
At go-live, a clear structure for handling management requests is missing. Everything runs through informal channels: an email, a quick message, a word with IT in the corridor. No prioritisation, no documentation, no ownership.
In our experience with 265+ specialists who guide ERP projects, three recognisable patterns emerge within twelve months of go-live at organisations without structured functional management:
Key users who act informally as administrators, alongside their primary role, without a mandate and without compensation for that extra load.
A growing backlog of improvement requests that never get prioritised, because nobody owns that decision.
Shadow administrations next to the ERP: spreadsheets that start as a temporary fix and stay for years, because adjusting the system itself is “too much hassle.”
Those patterns are not an implementation problem. They are an ownership problem. And ownership starts with a choice: who manages this system on a structural basis, and how?
What functional ERP management involves in practice
Functional ERP management covers four types of activity that continue after go-live.
User support and training. New employees need to be onboarded. Existing users run into situations the implementation never anticipated. Questions, tickets and training needs arrive continuously, not in a single wave.
Small configuration changes. A new product group in the item structure. An adjusted approval rule. A changed tax code. These changes look trivial, but without documentation and controlled change management, errors creep in quietly and carry larger consequences later.
Proactive system reviews. At least twice a year: do the configurations still match the business processes? Have workarounds emerged that bypass the system? Are there updates or new features that would benefit your organisation?
Strategic development. New modules, extensions, integrations with other systems. This goes beyond daily management and calls for more expertise and planning.
The combination of those four activities decides whether your ERP still grows with your organisation three years from now, or slowly falls behind while operations keep asking new questions. That is the quiet test of whether functional ERP management is working: not whether the system runs today, but whether it still fits the business in three years.
The two routes: in-house or outsourced
The choice between building functional ERP management in-house and outsourcing it is not a matter of principle. It is a pragmatic trade-off, grounded in the situation of your organisation. The right answer for a stable manufacturer differs from the right answer for a fast-growing distributor, and both can be correct. The same organisation can also land on a different answer two years later, once its systems, its people or its growth path have shifted.
What follows is a set of conditions rather than a verdict. Read your own situation against them honestly, and the route tends to reveal itself.
Building in-house: when does it work?
Building in-house works best when your organisation meets at least three of these four conditions.
You have a stable key-user population. Key users who know the system, who do not rotate often and who have enough room in their role to take on management tasks alongside their daily work. At least one per module domain, preferably two to avoid concentrating knowledge in a single person.
Your ERP is configuration-driven, not customisation-heavy. The more your system runs on standard configuration, the smaller the risk that an internal administrator sets something incorrectly with consequences that only surface later. Systems with extensive custom development or complex integrations call for deep technical knowledge that is hard to secure internally.
You have deliberately invested in knowledge development. Training for key users, recorded configuration choices, internally documented process descriptions. Knowledge that does not sit in one person but in the organisation, so the departure or illness of a key individual does not trigger a crisis.
Your organisation changes at a steady pace. Mergers, rapid growth and acquisitions demand external flexibility. Stable organisations with a predictable rate of change can secure in-house management more easily, because the system environment shifts less quickly than in a dynamic business.
Meet three of these four and in-house management is a realistic, durable choice. Meet only one or two, and the load tends to fall back on a handful of people who never signed up for it, which is exactly how the informal patterns described earlier take hold.
Outsourcing: when is it the better route?
Outsourcing works better when you fall outside the conditions above.
Your organisation is growing fast. New business lines, new markets, acquisitions: your ERP management has to move at a pace that is hard to match internally without a heavy investment in in-house knowledge. An external partner scales with you, even when the pace is uneven.
Your system is complex or heavily customised. Deep knowledge of specific modules, custom integrations or platform-specific configurations is difficult to maintain internally in a cost-effective way. With an external party, the investment in training and staying current is spread across several clients.
Your key users are structurally at capacity. When your most experienced people already work at full stretch, loading management onto them puts your daily operation at risk. Management then becomes the work that gets squeezed in around everything else, and its quality suffers for it.
You want proactive development. An external partner brings experience from other projects: which configuration patterns work, which pitfalls others have already hit, which updates deserve your attention before you discover them yourself. That outside view is hard to build internally, because a single organisation only ever sees its own system.
Outsourcing does not remove your responsibility for the system. It changes where the work sits, not who owns the outcome. The strongest outsourced setups still keep a single internal point of contact who knows the business and can judge whether an external recommendation fits.
The hybrid model
In practice, mid-sized organisations with more complex ERP environments often choose a hybrid approach, and that makes sense.
A hybrid management model combines internal process knowledge with external system expertise, so your ERP can handle both daily support and strategic development. The principle is straightforward: an internal functional administrator owns processes, user relationships and daily questions, supported by external specialists for deep module knowledge, complex configuration changes and periodic development.
The internal administrator knows the organisation and the users. The external partner knows the system in breadth and depth. Together they cover the full spectrum.
One split we regularly see working at the organisations our 265+ specialists support: roughly 60 to 70 percent internal responsibility for daily support and smaller adjustments, complemented by 30 to 40 percent external expertise for complex changes, periodic system reviews and module-specific customisation. The exact balance shifts as the organisation does.
Read also how ERP management after go-live structurally determines the value of your system, including five pillars that mark working ERP management and the signals that management is falling short.
Five decision factors
Use this framework to set the management route together with your IT manager and operations lead. None of the factors decides on its own; read them as a balance.
| Factor | Leans toward in-house | Leans toward external |
|---|---|---|
| System complexity | Low, little customisation | High, heavily customised |
| Organisational stability | Stable, predictable pace | Fast-growing, M&A-active |
| Key-user availability | Capacity to spare alongside primary role | Key users are operationally indispensable |
| Internal knowledge level | Strong internal ERP experts in place | Limited in-house depth |
| Rate of change in the ERP | Quarterly or less | Monthly or more often |
Three or more factors pointing toward external? Then outsourcing or a hybrid model is almost always the wiser choice, even if in-house feels “cheaper” at first glance. The invoice is rarely where the real cost of this decision sits.
Governance: who owns it?
The most underestimated risk factor in functional management is not a technical question. It is a governance question.
Who decides which change takes priority? Who approves a configuration adjustment before it goes live? Who watches that the backlog stays manageable and does not grow into an impenetrable list?
Functional management rarely fails for lack of knowledge. It fails for lack of ownership. Without a designated owner, the agenda follows the loudest request rather than the highest business priority.
A working governance structure has three elements.
A named management owner. Someone with the mandate to set priorities and approve changes. This is a business role, not an IT role: the owner understands the processes, knows the users and can judge whether a change serves the organisation.
A structured backlog process. Change requests get logged, weighed on impact and effort, prioritised and scheduled. Requests that arrive through informal channels are logged anyway, so they do not vanish into thin air but get a fair shot at priority.
A periodic system review. At least twice a year: do configurations still match the processes? Have workarounds emerged that bypass the system? Which development deserves priority in the coming six months?
A RACI matrix helps to formalise the roles: who is Responsible (does the work), Accountable (holds the mandate and final responsibility), Consulted (asked for input) and Informed (kept up to date). Without that clarity, responsibilities overlap or slip through the gaps.
What does unstructured management cost?
Functional ERP management is sometimes treated as an avoidable cost. Organisations that take that view pay the bill later, through higher repair costs.
Patterns we see at organisations without structured management, measured over two to three years after go-live, fall into three groups.
Workaround maintenance. Spreadsheet corrections, double entry, manual exports: typically 0.5 to 1.5 hours per user per week. At fifty users that adds up to 25 to 75 hours of lost capacity per week, capacity that appears on no budget yet is felt across the operation.
Repair projects. Accumulated configuration errors, undocumented changes and outdated permission structures eventually demand a larger remediation effort. In our experience with 265+ specialists who guide remediation projects, that repair costs, on average, 15 to 25 percent of the original implementation cost, measured over a two to three year period.
Delayed development. Functional needs that sit on a backlog for quarters cost more through missed efficiency than their delivery ever would have. The organisation works around the system instead of with it.
For comparison: structured functional ERP management, when outsourced, typically costs 12 to 20 percent of the annual software licence cost. That is considerably less than the sum of workaround time and repair projects under a neglected management structure.
ERP Company offers a flexible management model, from structural support to targeted module expertise, sized to the scale and pace of your organisation. As a platform-independent party we work with most common ERP platforms, with no preference for a specific vendor. Because we sell no licences, our advice on what to manage internally and what to outsource carries no hidden commercial weight. For organisations ready to discuss that balance, a short conversation is the fastest way to test it: get in touch with ERP Company.
From ad-hoc to structured management
The step from ad-hoc to structured management is rarely dramatic. Most organisations do not start from zero: there are key users, there is knowledge, there are processes. What is missing is structure.
A workable approach in three steps, the one we advise organisations to take.
Step 1: Make the knowledge visible. Who knows what about your system? Which configuration choices are documented? What lives only in the heads of two or three people? A short knowledge inventory shows the risk you carry if a key person leaves, and lays the basis for a deliberate choice between in-house and external.
Step 2: Set the governance. Name an owner, even if the management team is small. Put a simple backlog process in place. Schedule a first system review. It takes a few hours of work to set up. The structural effect lasts.
Step 3: Decide the staffing. On the basis of the five decision factors: fully in-house, hybrid or outsourced. Record the arrangements in a management agreement or SLA, even when you work entirely in-house, so expectations about response times, prioritisation criteria and escalation routes are clear.
For organisations that want insight into how management cost relates to the total ERP investment, what an ERP implementation really costs gives an overview of every cost item across the project, including the one organisations underestimate most often: management after go-live.
ERP functional management is not a closing entry at the end of an ERP project. It is the structure through which your organisation protects and builds on the value of its system over the years that follow. The choice between in-house and outsourced is not a position of principle but a situational trade-off. For most mid-sized organisations, hybrid is the most robust route: internal ownership secures organisational knowledge, external expertise secures system depth. The right combination depends on the five decision factors, and it changes as your organisation changes.
Frequently asked questions
What is the difference between functional and technical ERP management?
Functional ERP management focuses on processes, configuration and user support: making sure the system does what your organisation needs, day in and day out. Technical management focuses on infrastructure, security, availability and software updates. Both are needed. They call for different roles, different knowledge and different owners within your organisation.
When is outsourcing functional ERP management the better choice?
Outsourcing functional ERP management is wiser when your system is heavily customised, your organisation is growing fast, or your key users lack the capacity alongside their primary role. In those cases, mid-sized organisations more often choose a hybrid model: internal ownership for processes and daily questions, external expertise for module depth and development. Full outsourcing applies more often to smaller organisations or strongly technical systems.
How much FTE does functional ERP management cost in-house?
An internal functional administrator typically spends 0.2 to 0.5 FTE per ERP module domain on management in a stable environment, on top of their regular workload. At fast-growing organisations or with extensive customisation, this rises to 1 FTE or more per domain. A structured backlog process and clear prioritisation criteria keep the time investment manageable, so management does not become an uncontrolled item in your capacity planning.
What does functional ERP management cost when outsourced?
Outsourced functional ERP management typically costs 12 to 20 percent of the annual software licence cost, depending on system complexity and the response times you want. Organisations that budget this percentage structurally avoid the repair projects that follow from a neglected management structure. In our experience, those repair costs run, on average, to 15 to 25 percent of the original implementation cost, measured over two to three years after go-live.
Who manages an ERP system after go-live?
After go-live, an ERP system is managed by a designated functional owner who sets priorities and approves changes, supported by key users for daily questions and, in many cases, external specialists for deep module work. The decisive factor is not who does each task but who holds the mandate. Without a named owner, the backlog follows the loudest voice instead of the highest business priority.
Next step
Functional ERP management decides, quietly and over years, how much value your organisation keeps drawing from its system. The choice between in-house and outsourced is a balance that shifts as you grow, customise or restructure, rather than a verdict you reach once.
We are ERP Company. Independent, platform-independent, with no preference for a specific vendor. With 265+ specialists who have worked across every common ERP platform and now bring that experience to your management setup, whether you build it in-house, outsource it or run a hybrid model.
Want to spar about the management structure that fits your ERP environment? Get in touch for an exploratory conversation. One honest discussion of your situation often gives more direction than a stack of service proposals.