ERP Consultant: What They Do and How to Choose

An ERP project touches finance, inventory, purchasing, production, sales and HR at the same time. Get it right and the business runs on one set of numbers. Get it wrong and you can spend a year paying for software nobody trusts. An ERP consultant helps you avoid the second outcome by mapping your processes, choosing the right system, planning the implementation and guiding the people who have to change how they work. This guide explains what an ERP consultant actually does, the different types you can hire, how to evaluate them, and a worked example of the fit-gap analysis at the heart of a good engagement.

What an ERP consultant does

The role varies by engagement, but the work usually includes:

• Process discovery: documenting how orders, purchasing, stock, production and finance work today, including the workarounds
• Requirements: turning those processes into clear, prioritised requirements
• Selection support: shortlisting systems, running scripted demos and comparing proposals
• Fit-gap analysis: identifying where a system fits as standard and where configuration, customisation or process change is needed
• Implementation planning: phases, data migration, integrations, testing and cut-over
• Change management and training: preparing people for new ways of working
• Post-go-live support: stabilising the system and planning improvements

Types of ERP consultant

TypeTypical focusStrengthsWatch forIndependent selection consultantRequirements and choosing a systemVendor-neutral adviceMay not stay for implementationVendor implementation partnerImplementing one product, such as Odoo or NetSuiteDeep product knowledgeRecommendations naturally favour their productCustom ERP developerBuilding or extending ERP softwareCan fill gaps standard products leaveLong-term maintenance responsibilityFreelance specialistOne module or area, such as inventory or financeExpertise and flexibilityLimited capacity for whole programmes

Many projects combine two: an independent adviser for selection, then an implementation partner or developer for delivery.

When you need an ERP consultant

• You are moving off spreadsheets or several disconnected systems
• Finance spends days each month reconciling numbers from different tools
• Stock levels, costs or margins cannot be trusted
• You are growing into new locations, entities or currencies
• An earlier ERP project stalled or failed and you need to recover it

How to evaluate an ERP consultant

Ask for evidence rather than assurances.

• Industry understanding: have they worked with businesses that make, stock or sell in a way similar to yours?
• Method: how do they run discovery, and what documents do they produce?
• Neutrality: if they are tied to a product, how do they handle requirements it does not meet well?
• People: who will actually do the work, and how much of their time will you get?
• Data migration approach: how do they clean, map and test data before go-live?
• Change management: how do they prepare and train users, not just configure software?
• References: can you speak to clients about what happened after go-live?

Worked example: a fit-gap analysis

A fit-gap analysis compares each requirement with what a candidate system does as standard. The example below uses a hypothetical distributor and generic requirements.

IDRequirementPriorityStandard fitGap handlingEffortR01Multi-warehouse stock with transfersMustFitsNoneLowR02Batch and expiry trackingMustFitsConfigurationLowR03Customer-specific price listsMustFitsConfigurationLowR04Approval for purchase orders above a thresholdMustPartialConfigure approval rulesMediumR05Rebate calculation for key customersShouldGapCustom module or reportHighR06Integration with existing CRMMustPartialAPI integrationMediumR07Legacy report formats exactly as todayCouldGapChange process; use standard reportsLow

Two lessons appear immediately. Most requirements fit with configuration, which is good news for cost and risk. And some gaps, like R07, are better solved by changing the process than by customising software. A good consultant pushes back on low-value customisation, because every customisation adds testing and upgrade effort for years.

The analysis can be kept in a spreadsheet or a simple script that summarises the effort by category:

import csv
from collections import Counter

effort = Counter()
with open("fit_gap.csv", newline="") as f:
    for row in csv.DictReader(f):
        if row["Priority"] in ("Must", "Should"):
            effort[(row["Standard fit"], row["Effort"])] += 1

for (fit, size), count in sorted(effort.items()):
    print(f"{fit:8s} {size:7s} {count}")

Summaries like this make it easy to compare candidate systems on the same requirements.

What a sound ERP engagement produces

• Process maps for current and future states
• A prioritised requirements list with fit-gap results
• A selection recommendation with reasons and trade-offs
• An implementation plan with phases, milestones and responsibilities
• A data migration plan, including cleaning rules and trial loads
• Test scripts based on real business scenarios
• Training plans and materials for each user group

Typical phases and what to expect

Most ERP engagements follow a similar rhythm: discovery and requirements, selection, design, configuration and build, data migration trials, testing, training, go-live and stabilisation. The consultant's involvement is usually heaviest in discovery and design, and again around testing and go-live. Expect to spend real time in workshops early on; the quality of that input shapes every later phase.

Red flags

• A system recommended before discovery has started
• Promises that everything will work as standard without testing
• No plan for data cleaning and migration
• Training treated as a single session at the end
• Customisation proposed for every requested change

Working well with your consultant

Assign an internal project lead with authority to make decisions, and involve the people who do the work in discovery and testing. Agree how changes to scope are approved. Keep a decision log so the reasons behind choices survive staff changes. The consultant brings method and experience; your team brings knowledge of the business, and an ERP project needs both.

Budgeting for the consultant and the project

Ask consultants to separate their fees by phase: discovery and selection, implementation, and post-go-live support. This makes proposals comparable and lets you stop after selection if needed. Remember that consulting fees are only part of the cost; licences, integrations, data migration and your own team's time often add up to more. A consultant who helps you estimate those honestly at the start is worth more than one who quotes the lowest day rate.

Whether to buy a standard ERP or build your own is a decision in itself; see our guide to custom ERP development versus off-the-shelf software. If your ERP must exchange data with other systems, our guide to Odoo API integration with NetSuite and SAP covers connector design.

Frequently Asked Questions

What does an ERP consultant do?

An ERP consultant maps your processes, defines requirements, helps choose a system, plans and guides implementation, and supports training and change management.

Should we hire an independent consultant or a vendor partner?

Independent consultants offer neutral selection advice; vendor partners bring deep product knowledge for implementation. Many businesses use one for selection and the other for delivery.

What is a fit-gap analysis?

It compares each business requirement with what a system does as standard, showing where configuration, customisation or process change is needed.

How can we reduce ERP project risk?

Invest in discovery, limit customisation, clean data early, test with real scenarios and train users well before go-live.

Plan your ERP project with us

We help businesses plan ERP projects, analyse fit and gaps, and build the custom modules and integrations standard systems lack. See our custom app development services, or talk to us about your ERP plans.

About the Author

Manav Sharma is the founder of Insyrge and a CRM solutions architect. He works across Zoho, Salesforce, HubSpot, Odoo and more, designing the CRM setups, integrations and automations that keep sales and operations teams working from the same data.