An ERP consultant advises on what you need and helps you choose and govern a system; an ERP development company designs and builds software, either extending a package or creating a custom ERP. Between them sits the implementation partner, which configures and deploys one vendor's package. Hire by the problem you have: unclear requirements, a chosen package to deploy, or processes no package fits.
The labels overlap in the market. Some consultancies also implement, some implementation partners write custom code, and some development companies run discovery and selection. So look past the title and ask what the firm actually does, whose products it earns from, and who will own the result. This guide sets out the three roles, their independence, typical engagement models and how to combine them. If you already know your core processes need software built around them, our custom ERP software page explains our approach; for deploying a chosen package, see ERP implementation services.
What is the difference between an ERP consultant, an implementation partner and a developer?
Each role answers a different question. A consultant answers "what do we need and which option fits?", an implementation partner answers "how do we deploy this package?", and a development company answers "how do we build what no package does well?"
| Independent ERP consultant | ERP implementation partner | ERP development company | |
|---|---|---|---|
| Main job | Requirements, selection, business case, project governance | Configure, migrate, train and support one vendor's package | Design and build custom ERP modules, extensions or a full system |
| Typical deliverables | Requirements document, RFP, scorecard, roadmap, steering reports | Configured system, migrated data, trained users | Working software, source code, technical documentation |
| Earns from | Advisory fees | Implementation services, and often licence resale or referral arrangements with the vendor | Development and support services |
| Strength | Independence, broad view across options | Deep knowledge of one product | Fit to processes no package handles well; code and data you control |
| Watch out for | No delivery accountability; advice may stay theoretical | Natural preference for its own product | May favour building when configuration would do |
| Best when | You are unsure what you need or which option fits | You have chosen a package that fits most processes | Core processes are distinctive, or packages need heavy customisation |
How independent is an ERP consultant?
Independence depends on how the consultant is paid, not on what they are called. Ask directly whether the firm receives any commission, referral fee, reseller margin or partner status from the vendors it might recommend. A consultant who is also a reseller of one product can still give good advice, but you should know about the arrangement before taking it.
Questions to ask:
- Do you receive any payment or benefit from software vendors you might recommend?
- Which vendors are you a partner or reseller for?
- Would you recommend a custom build if it were the better fit, and have you done so before?
- Will you be involved in delivery, or does your role end at selection?
When should you hire an ERP consultant?
Hire a consultant when the problem is clarity rather than delivery. Typical triggers: departments disagree on what the system must do, you have never run a selection, the board needs an independent business case, or a project is in trouble and you need an outside review. A consultant can also act as your representative during delivery, checking the supplier's plan, testing and readiness on your behalf.
The trade-off: a consultant adds cost and a layer between you and the delivery team. On a small project with clear requirements, that layer can slow decisions more than it helps.
When should you hire an ERP implementation partner?
Hire an implementation partner once you have chosen a package and most of your processes fit its standard functionality. Vendors of packaged ERP commonly deliver through partner networks, so the partner is often your main route to configuration, migration, training and ongoing support. Choose the partner as carefully as the product: the team's experience in your industry and the quality of its data migration and testing usually matter more than the partner's tier.
When should you hire an ERP development company?
Hire a development company when your core processes are where you compete, when packages would need custom code in most of them, or when you need modules a package lacks alongside one you keep. A development company can build a full custom ERP, add specific ERP modules next to existing systems, or connect systems through integrations. Our comparison of off-the-shelf and bespoke ERP helps decide which direction fits.
Check two things before you sign. First, ownership: who owns the source code and when, and confirm that your data stays yours throughout; our intellectual property ownership page sets out how we handle both. Second, the method: you should see working software early and regularly, not only documents.
What engagement models are common?
The commercial structure shapes behaviour, so match it to the stage of the project.
| Model | How it works | Fits | Risk to manage |
|---|---|---|---|
| Fixed-scope advisory | Defined deliverable, such as a requirements document or selection report | Consultant during selection | Deliverable that is not used afterwards |
| Time and materials | Pay for time spent against a plan | Discovery, evolving scope, support | Needs active oversight of progress |
| Fixed price per phase | Price agreed for a defined phase after discovery | Implementation or build with a stable scope | Change requests must be handled formally |
| Pilot then full project | Small working slice first, then the agreed full scope | Custom development, testing a new supplier | Pilot must cover representative, not trivial, processes |
| Retainer or support agreement | Ongoing capacity for changes and support | After go-live | Clear response targets and priorities |
Whatever the model, agree in writing how out-of-scope requests are assessed, priced and approved before work starts.
What should you ask each type of firm before hiring?
Ask questions that test what the firm will actually deliver and what you will own at the end. The table lists the ones that separate strong firms from weak ones in each role.
| Ask a consultant | Ask an implementation partner | Ask a development company |
|---|---|---|
| Which vendors do you partner with or resell, and how are you paid? | How many projects have you delivered in our industry with this product? | Who owns the source code, and when does it transfer? |
| Can you show a requirements document or RFP you produced (anonymised)? | Who exactly will be on our team, and are they your staff? | How often will we see working software? |
| What does your role look like after selection? | How do you run data migration and how many trial loads do you plan? | How do you handle requirements outside the agreed scope? |
| Have you recommended an option you do not partner with? | What do you build as custom code, and how does it affect upgrades? | Who supports the system after go-live, and on what terms? |
| How do you measure whether your advice worked? | What support do you provide after go-live? | Can we see comparable systems you have built? |
What a good proposal looks like from each
- Consultant: a defined deliverable, a clear end point, and a statement of any vendor relationships
- Implementation partner: a phased plan with assumptions, named team members, a migration and testing approach, and a list of gaps with how each will be handled
- Development company: a solution outline mapped to your requirements, a phased delivery plan with early working software, ownership and support terms, and a change control process
A proposal that is mostly marketing, with no assumptions and no named team, is a warning sign in every role.
Can you combine a consultant with a developer or partner?
Yes, and for larger projects it often works well, as long as roles are clear. A common pattern: the consultant runs requirements and selection, the chosen partner or development company delivers, and the consultant stays on in a light assurance role. The risks are duplicated effort and blurred accountability. Write down who owns requirements, design decisions, delivery, testing sign-off and go-live readiness.
Decision checklist: which do you need first?
- Requirements are unclear or disputed: start with a consultant or a discovery phase
- Requirements are clear and a package fits most processes: go to implementation partners
- Requirements are clear and core processes are distinctive: go to development companies
- A package fits most areas but a few critical processes do not: partner for the package plus a developer for custom modules and integrations
- A project is already in trouble: an independent review first, then decide
Illustrative scenario: one company, three roles
This scenario is illustrative. A UAE-based trading group with three companies needs Arabic and English, intercompany trading and a specialised consignment process. A consultant runs workshops and writes the RFP. Proposals show that a package fits finance and purchasing, but consignment would need extensive custom code. The group chooses a package for finance with an implementation partner, and a development company builds the consignment module and integrates it. The consultant reviews readiness at each go-live. Each firm does what it is best at, and the contract states who owns each part.
When is hiring all three the wrong approach?
For a small company with straightforward needs, three firms means three sets of fees and meetings for a project one capable supplier could run. If requirements are reasonably clear, a single supplier that runs discovery, delivery and support, with a contract that protects your ownership and exit options, is usually simpler. Add an independent reviewer only if the investment or risk justifies it.
How to start: what to prepare before you call anyone
Prepare a short brief: business goals, in-scope processes and entities, current systems, key reports, users and volumes. If you will compare several suppliers, turn it into a structured request using our ERP RFP template, and score responses with the ERP selection criteria checklist.
If your processes point towards custom modules or a custom ERP, discuss the project with us. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project starts, so you can judge us on working software rather than a proposal.