ERP Consultant: What They Do and How to Hire the Right One
An ERP consultant is the person who plans, configures and de-risks your ERP project so it actually fits how your business runs. Hire the right one and you save months of rework, a pile of money, and the kind of go-live weekend nobody wants to relive.
Most people start looking for an ERP consultant at the wrong moment. They’ve already picked the software, signed the licence, and now they need someone to make it work. Better to bring the consultant in before the buying decision, because half their value is stopping you spending money on the wrong thing.
Key Takeaways
- An ERP consultant maps your processes first, then recommends software. If they lead with the software, be careful.
- The best ones tell you what not to do. Endless customisation is where ERP projects go to die.
- A phased approach beats a big-bang build. Get the first 100 days right, then extend.
- Fixed-scope first phase, references in your industry, and a written plan are the three things to insist on.
- Total project value matters more than the day rate. A cheap rate on a bloated scope is not a saving.
- For most mid-market businesses, an implementation partner who owns the build, hosting and support beats a lone adviser.
What an ERP consultant actually does
The job is not “install the software”. Any technical person can do that. The job is to make sure the finance, stock, sales and operations of your business run better after the project than before.
A working ERP consultant does five things. They map how your business runs today and where it hurts. They recommend a system and a configuration that fits, including the honest verdict that your current tools might be fine. They set up the system, migrate your data and connect the pieces that need connecting. They train your team so people actually use it. Then they support the first weeks after go-live, which is when the real problems show up.
The order matters. Process before software. If a consultant opens the first meeting with a product demo, they’re selling, not advising.
When you need an ERP consultant (and when you don’t)
You probably don’t need one if you’re a small team, running a simple cloud tool, with no stock, no manufacturing and no multi-entity finance. Self-implementation is realistic there, and paying for consulting would be overkill.
You do need one once the setup gets awkward. Multiple companies or entities. Inventory and warehousing. Manufacturing or assembly. A legacy ERP you’re desperate to escape. Integrations with a website, a payment provider or a bank feed. At that point the cost of getting it wrong yourself is far higher than the fee.
Here’s the honest test. If you can’t clearly describe how an order flows from quote to cash to reporting without three exceptions and a spreadsheet, you’ll benefit from a consultant. If you can, you might be fine on your own.
What good looks like versus what to avoid
| Signal | Good ERP consultant | One to avoid |
|—|—|—|
| First conversation | Asks about your processes and pain | Demos software immediately |
| Scope | Written, phased, fixed for phase one | Vague, open-ended, “we’ll see” |
| Customisation | Pushes you to use standard features | Says yes to every custom request |
| References | Names clients in your industry | Testimonials with no detail |
| Trade-offs | Tells you what won’t work | Promises everything |
| Data migration | Planned early with sign-off gates | Left to the last week |
| After go-live | Committed support window | Hands over and disappears |
The customisation row is the one that catches people. Every custom change is code someone has to maintain forever. A good consultant defends the standard configuration and makes you justify each deviation. That discipline is what keeps your project on time and your system upgradeable later.
The phased approach that keeps projects alive
Big-bang go-lives, where everything switches on at once, carry the most risk. Panorama Consulting’s annual ERP reports have long documented that budget overruns and timeline slips are common across the industry, and rushed scope is a repeat cause. You can read their published research at panorama-consulting.com if you want the detail.
The alternative is two phases. First 100 days: get finance, core sales and the essential operational flow live and stable. Prove the system works with real data and real users. Then beyond: add the reporting, automation and extra modules once people trust the core. This framing keeps the early scope tight and the wins visible, which is what keeps a project funded and supported inside the business.
An ERP consultant worth hiring will structure the work this way by default. If you see a plan that switches on twelve modules across four departments on one date, ask why.
What to ask before you hire
Cut through the sales talk with a short list of direct questions. Can you show me a written scope for phase one with a fixed fee? Who from your team is on the project, and are they the people I met today or someone junior? What have you deliberately talked a client out of building? How do you handle data migration, and when in the timeline does it start? What does your support look like in the first month after go-live?
Watch how they answer the “talked a client out of” question. A consultant who can’t name a single thing they refused to build has never protected a client from themselves.
You can see our Odoo services for how we structure this in practice, and read client case studies to judge the results against your own situation.
How ERP consulting fees usually work
Fees come in a few shapes. Some consultants charge a day rate. Some price a whole project. Some, the implementation partners, bundle the build with hosting and ongoing support on a monthly basis.
Day rates are easy to compare and easy to mislead you. A low rate on a scope that keeps growing costs more than a higher rate on a tight, fixed phase. Judge the total against what you’re actually getting, not the headline number.
The model that gives most mid-market businesses the cleanest outcome is a fixed-scope first phase, then a defined support arrangement after go-live. You know the cost of proving the system before you commit to the rest. If a consultant won’t fix the scope of an early phase, that tells you they don’t yet understand your business well enough to price it, which is itself useful information.
FAQ
What does an ERP consultant actually do?
They map your processes, recommend a system that fits, configure it, migrate your data, train your team and support go-live. The good ones stop you buying software you don’t need.
How much does an ERP consultant cost?
Day rates vary by seniority and region. What matters more is the total project fee against scope. Ask for a fixed-scope first phase so you can judge value before committing to the full build.
Do I need an ERP consultant or can we implement it ourselves?
Small teams with a simple setup can self-implement a cloud ERP. Once you have multiple entities, stock, manufacturing or tricky integrations, a consultant usually pays for itself by avoiding rework.
How do I know if an ERP consultant is any good?
Ask for references in your industry, a written scope, and a phased plan. Watch how they handle your awkward questions. If they promise everything with no trade-offs, walk away.
What’s the difference between an ERP consultant and an implementation partner?
A consultant advises. An implementation partner advises and does the build, hosting and support. For most mid-market projects you want the partner model so one team owns the outcome.
Talk to us before you buy
If you’re weighing up an ERP project and want a straight answer on whether it makes sense, what it should cost, and how to phase it, that’s the conversation we have every week. We’ll tell you if you don’t need us.
Book a discovery call and bring your awkward questions. Those are the ones worth answering.