IT Directors Need People, Not Software

Somewhere in Manchester right now, an IT Director is staring at a Gantt chart that ended three months ago. The ERP went live. The consultants held a celebratory call, sent a closure report with a tasteful cover page, and moved on to their next implementation. The system works, technically. And yet her ticket queue has tripled, her two-person IT team is drowning, finance is quietly rebuilding their old spreadsheets on the side, and the board is asking why the system they spent eighteen months and a serious budget on feels harder than what it replaced.

Nobody budgeted for this phase. Almost nobody does.

I have spent thirteen years at Brainium watching this exact movie play out across mid-market companies, most of them in the UK. The plot never changes. The implementation gets all the attention, all the money, all the steering committee meetings. Then go-live happens, the implementation partner’s engagement ends, and the company discovers that an ERP is not a project. It is a living system that needs people to keep it alive. And those people were never hired.

The crisis has a name, and it arrives on schedule

Let me answer the question directly, because if you found this post searching for ERP support outsourcing, you deserve a straight answer before the storytelling. ERP support outsourcing means engaging an external team, typically dedicated engineers who work only on your system, to handle the ongoing work an ERP demands after go-live: bug fixes, integrations, user support, report building, customisation, and the steady stream of change requests that a real business generates. For most mid-market companies, it costs a fraction of building the equivalent in-house team, and it starts delivering in weeks rather than the months a hiring cycle takes.

Now back to our IT Director in Manchester, because her situation explains why this model exists.

The first ninety days after go-live are brutal by design. Users who nodded through training sessions discover they retained nothing. Edge cases the implementation team never encountered start appearing daily. That integration with the warehouse system that “worked in testing” chokes on real volumes. Month-end close, the true stress test of any ERP, exposes configuration decisions that seemed sensible in a workshop and are catastrophic in practice.

Industry analysts have been saying for years that a majority of ERP implementations fail to deliver expected value, and in my experience the failure rarely happens during implementation. It happens in the twelve months after, when there is nobody left to adapt the system to the business. The consultants are gone. The internal team knows how to reset passwords, not how to rewrite a posting rule.

The hiring math that never works

The obvious answer is to hire. Every IT Director I speak to has tried, or has done the spreadsheet and given up before trying.

An experienced ERP specialist in the UK, someone who genuinely understands both the platform and the business processes it encodes, commands a serious salary. You need at least two, because one person is a resignation letter away from disaster. Add recruitment costs, benefits, and the six months it takes them to learn your specific configuration. You are now looking at a standing annual commitment that most mid-market budgets simply cannot absorb for what the board sees as “keeping the lights on.”

So companies compromise. They stretch the existing team, which burns people out. They buy a support contract from the ERP vendor, which gets them a ticketing portal and a service level agreement that measures response time, not resolution. Or they call the original implementation partner back at day rates that make the CFO’s eye twitch, for work that is fundamentally unpredictable in volume.

None of these are people. They are all, in different disguises, more software and more paperwork wrapped around the absence of people.

What dedicated hiring actually changes

The model I have watched work, and the one we have built Brainium’s ERP support practice around, is dedicated hiring. Not a helpdesk. Not a pool of anonymous engineers who pick your ticket off a queue. A named engineer, or a small named team, who work exclusively on your system, attend your standups, know that Sandra in finance always means the aged debtors report when she says “the report,” and accumulate the same institutional knowledge an employee would.

The economics work because of geography. A dedicated ERP engineer working from our Kolkata team costs a UK company a fraction of the equivalent local hire, without the compromise on capability that offshore work had a reputation for fifteen years ago. The talent pipeline here for ERP platforms, integrations, and the surrounding stack is deep and getting deeper. What the client buys is not cheap labour. It is the ability to afford continuity, which is the one thing an ERP actually needs and the one thing every alternative model fails to provide.

The difference shows up in the texture of the work. A ticket-based support contract fixes what breaks. A dedicated engineer notices that the same category of thing keeps breaking and fixes the cause. A day-rate consultant answers the question you asked. A dedicated team member answers the question you should have asked, because they were in the room when the problem first surfaced. Over a year, that compounding knowledge is the gap between an ERP that slowly ossifies and one that keeps pace with the business.

The question to ask before you sign anything

If you are an IT Director evaluating ERP support outsourcing, here is the filter I would apply, and I say this knowing it cuts against some of our own competitors’ models. Ask one question: will I know the names of the people working on my system, and will those names be the same in six months?

If the answer is a rota, a queue, or a vague assurance about “our team,” you are buying a service level agreement, not capacity. SLAs are fine for infrastructure. ERPs are not infrastructure. They are the digitised nervous system of your business, and nervous systems need people who know them, not people who can look them up.

The post-go-live crisis is not a sign your implementation failed. It is a sign your ERP is being used, stress-tested by reality, and asked to change. That is exactly what you paid for. The only failure is meeting that moment with a support portal when what the moment demands is people.

Our IT Director in Manchester, by the way, is a composite. But the pattern is drawn from real engagements, and if her Gantt chart looks like yours, the fix is not another module or another licence. It is two or three good engineers who wake up every day thinking about your system. That is what we build at Brainium: dedicated ERP support teams for mid-market companies who need the people their budget could never hire locally. If that gap sounds familiar, let’s talk before month-end close does the talking for you.