
An ERP implementation team needs someone to keep the work moving between meetings. Gene Hammons, a business consultant specialising in ERP acquisition and deployment, tells Joanna England why internal ownership matters, how accessible support removes everyday blockers and why taking on more implementation work does not always reduce the cost for a business.
This interview has been edited and condensed for clarity.
Key takeaways
- The successful clients Gene Hammons studied spoke to other customers, brought in expertise to support their internal team, started training early and followed the project plan.
- An internal project manager keeps the ERP implementation team moving between consultant visits by finding out what is blocking colleagues and arranging help.
- Accessible system administrator support stops a small question holding up someone’s work for a week.
- Taking more work in-house only reduces cost if your ERP implementation team has the experience and capacity to do it.
What did successful ERP clients do differently?
Gene: I looked back at clients who had used the same software and consulting teams but achieved very different results. The successful businesses had several habits in common. They spoke to other customers, brought in expertise to support their internal team and started training early.
They also followed the project plan. When an issue came up, they asked who would resolve it and when. At the next meeting, they checked whether it had been done. They did not assume that discussing a task meant somebody would complete it. They kept following through.
Why does an ERP implementation team need an internal project manager?
Gene: External consultants can explain what needs doing, but someone inside the business needs to follow up. People already have jobs. Between meetings, project tasks can be delayed, forgotten or pushed aside by something urgent.
An internal project manager can speak to colleagues, find out what is blocking them and arrange help. That might mean contacting the system administrator or showing someone how to complete a simple step. The aim is to have the work ready when the consultant returns, rather than spending the next meeting discussing the same unfinished tasks.
[Insert in-body image: erp-implementation-team-roles.jpg. Alt text: “Diagram of ERP implementation team roles: internal project manager, system administrator and technical consultants”]
Can an existing employee manage implementation alongside their normal job?
Gene: You cannot simply assume they can. I often describe the problem as expecting Bob to handle the project in his spare time, even though Bob already has a full-time job and has never done this before.
The business needs to understand the work involved and allocate resources to it. That starts with understanding the value it expects from the project. If you have not established that value, it is harder to justify giving people the time and support they need to deliver it.
Where does a system administrator help the ERP implementation team?
Gene: Sometimes a person stops because they do not know where to click or how to make something work. If they wait until the consultant visits again, a small question can hold up their work for a week.
Having someone available to call or meet online makes a difference. They can help with the immediate problem so the employee can continue. During implementation, you are also developing the people who will eventually run the system. They need training, but they also need access to help while they put that training into practice.
How can an ordinary approval become a serious delay?
Gene: The chart of accounts is one example. A team may ask its accountant to approve the design before that accountant understands how reporting works in the new system. They are being asked to advise on something they may need to learn first.
Meanwhile, other work may depend on that decision. The answer is to recognise the dependency early and help the people involved get the understanding they need. Otherwise, the project can spend weeks waiting for an approval that everyone assumed would be straightforward.
Does taking more work in-house always reduce the cost?
Gene: A supplier may offer a lower price if the client takes on more tasks. But the client needs to understand what those tasks are and whether its people can do them.
I work on the business side and bring in technical consultants for the technical work. When internal project managers and administrators handle the work they are equipped to do, external specialists can concentrate on their part. That division can work well. Simply accepting more responsibility without the experience or capacity to deliver it can create delays instead. The important thing is to match the work to the right people and keep ownership clear.
Early training helps with that preparation. If employees use the period before consultants arrive to learn the software, they can have a more useful discussion when configuration begins. Instead of spending the meeting discovering the basic features, they can explain their requirements. That helps the consultant understand what matters and helps the client make decisions.
ERP implementation team: frequently asked questions
In Gene Hammons’ view, an effective ERP implementation team pairs external consultants with an internal counterpart: a project manager inside the business who follows up between meetings, supported by a system administrator people can call for help. Technical consultants then concentrate on the technical work.
Gene warns against assuming they can. The business needs to understand the work involved, establish the value it expects from the project and give people the time and support to deliver it.
Some approvals depend on knowledge people do not have yet. Gene’s example is an accountant asked to approve a chart of accounts design before understanding reporting in the new system. Spotting the dependency early and helping people learn avoids weeks of waiting.
Not always. Gene says a lower price for taking on more tasks only helps if your people can do those tasks. Otherwise it can create delays. Match the work to the right people and keep ownership clear.
Related reading
- ERP implementation checklist
- ERP steering committee representation
- Outsourced NetSuite admin support
- Before the ERP demo: the questions Gene Hammons wants answered
- Choosing an ERP implementation partner: why industry experience matters
- APM: what does a project manager do?
About
Gene Hammons is an experienced ERP leader with over 400 projects. He helps CEOs, CFOs and COOs turn complex software investments into measurable strategic value. Bridging finance, operations and enterprise tech, he provides the proven methodology midsize companies need to bypass implementation pitfalls and build scalable systems that drive long-term control and profitability.
Author

Joanna England is Marketing & Growth Operations Lead at Suite Generation and an award-winning tech and business journalist with more than 25 years' experience. A former Editor-in-Chief of Insurtech Insights, Fintech Magazine and Insurtech Digital, she was named one of MPVR's Top 30 Journalists in Fintech & Insurtech in 2023.
Follow us on LinkedIn
New NetSuite field notes, UK pricing guidance and implementation practice, as we publish them.
