Data as of Sep 16, 2026 · Based on 379 AI responses from ChatGPT Search and Google AI Mode · See how Parse measures this
Brands AI recommends here
Named in 53% of answers
Named in 46% of answers
Named in 38% of answers
Named in 37% of answers
Source | Citation share |
|---|---|
 How to know if you should hire an ERP consulting firmhttps://tax.thomsonreuters.com/en/insights/white-papers/do-you-need-to-hire-a-consulting-firm-for-erp-implementations | 4.4% |
 The Strategic Advantage of Hiring an ERP Consultanthttps://www.top10erp.org/blog/erp-consultant | 4.2% |
 How to Choose an ERP Consultant: Best Practices & ERP Selection Criteriahttps://kpcteam.com/kpposts/erp-selection-best-practices | 3.7% |
 Choosing the Right ERP Implementation Consultant – Terilliumhttps://terillium.com/erp-implementation-consultant-faq/ | 3.3% |
 Choosing an ERP Consultant: Key Points to Considerhttps://erpsoftwareblog.com/2024/05/choosing-an-erp-consultant/ | 3.1% |
 ERP Implementation: A Guide to Picking the Right consultant for your Oracle ERP - Cox-Little & Companyhttps://coxlittle.com/picking-the-right-consultant-for-your-oracle-erp-implementation/ | 3.1% |
 How to Choose the Best ERP Consultant | Ultra Consultantshttps://ultraconsultants.com/erp-software-blog/the-best-erp-consultants/ | 2.6% |
 5 Criteria for Choosing the Right ERP Consultant - Datixhttps://datixinc.com/blog/5-criteria-for-choosing-the-right-erp-consultant/ | 2.6% |
Finding the Best ERP Consulting Firm - 8 Factors to Considerhttps://terillium.com/erp-consulting-firms/ | 2.6% |
What Does An ERP Consultant Do? | Top 5 Factors for Hiringhttps://ultraconsultants.com/erp-implementation/what-does-an-erp-consultant-do/ | 2.2% |
If you're the CFO, I’d treat the ERP implementation consultant as a **business-transformation partner**, not simply a software specialist. The consultant can materially affect scope, controls, data migration, adoption, and ultimately whether the ERP delivers the business case. A disciplined selection process looks…
If you're the CFO, I’d treat the ERP implementation consultant as a business-transformation partner, not simply a software specialist. The consultant can materially affect scope, controls, data migration, adoption, and ultimately whether the ERP delivers the business case.
A disciplined selection process looks like this:
Before interviewing firms, decide whether you need:
If you haven't selected the ERP yet, I'd strongly consider separating vendor selection from implementation delivery. An independent advisor can reduce the conflict that exists when the same firm recommends the platform and then earns implementation revenue from it.
Don't start with "Who are the biggest ERP consulting firms?"
Start with:
Who has successfully implemented this ERP for companies with our size, industry, finance complexity, integrations and geographic footprint? Look for demonstrated experience with:
Industry and process experience, named consultant experience, methodology, data/integration capability, change management and references are all useful dimensions for evaluating implementation partners.
This is one of the most important things I'd do as CFO.
Ask:
"Who exactly will be our engagement partner, program manager, finance lead, technical lead and data lead?" Then put those names in the proposal/contract.
Ask what percentage of their time each person will actually spend on your project and what happens if they leave. A common problem is buying a senior team during the sales process and receiving a much more junior team after signing. Current ERP-selection guidance specifically recommends evaluating the named consultants who will actually be staffed to the project.
Don't accept "we use Agile" or "we have a proven methodology."
Ask them to walk you through an actual implementation from:
Discovery → process design → configuration → integrations → data migration → testing → training → cutover → go-live → hypercare
For each phase, ask:
A mature methodology should have explicit deliverables and decision points rather than relying on generic project-management language.
These are areas where an attractive ERP implementation proposal can become expensive later.
Ask candidates to explain:
Have them show you a sample reconciliation plan.
As CFO, I'd want explicit evidence that they understand financial data integrity—not just technical migration.
Give each finalist several real scenarios from your business.
For example:
"Show us how you would redesign our month-end close." "We currently have seven entities, three currencies and multiple intercompany transactions. Walk us through your proposed future-state process." "Here's our current revenue-recognition process. What would you challenge?" "Here are our current management reports. Which should be redesigned rather than replicated?" "Here's our chart of accounts. What would you change and why?" You're looking for someone who will challenge bad processes, rather than simply reproduce them in a new system.
That's especially important because modern ERP programs can affect controllership, treasury, reporting and broader finance processes—not merely accounting software.
Don't rely on written case studies.
Ask for at least 3 comparable customers, preferably including:
And don't ask only, "Were you happy?"
Ask:
Independent customer references are particularly valuable because they test the implementation partner's claims against actual experience.
Don't compare proposals based simply on the headline fee.
Require each finalist to provide:
| Commercial item | Require |
|---|---|
| Implementation fee | Detailed by phase |
| Consultant rates | By role |
| Estimated hours | By role/phase |
| Travel | Explicitly defined |
| Third-party costs | Explicit |
| Data migration | Explicit scope |
| Integrations | Number and complexity |
| Testing | Explicit scope |
| Training | Explicit scope |
| Hypercare | Explicit duration |
| Change requests | Defined mechanism |
| Ongoing support | Separate pricing |
Fixed-fee, time-and-materials and milestone-based structures each transfer different levels of risk between you and the consultant.
For a significant ERP program, I'd generally want milestone-based accountability even if parts of the work are ultimately T&M.
Ask each candidate:
"Give me three examples where you had to tell a client that something was out of scope." Then ask:
"How did you resolve it?" You're looking for someone who can distinguish between:
A good contract should establish a clear change-control process rather than allowing every disagreement to become a change order.
I'd have the CFO, CIO/IT leader, controller, operations leader and project sponsor independently evaluate finalists.
For example:
| Criterion | Example weight |
|---|---|
| Relevant ERP experience | 20% |
| Industry/business-process experience | 20% |
| Proposed team | 15% |
| Implementation methodology/governance | 15% |
| Data & integration capability | 10% |
| Change management/training/support | 10% |
| Commercial transparency & references | 10% |
| Total | 100% |
Those categories are consistent with current ERP partner-selection frameworks; the actual weights should reflect your company's risks rather than being treated as universal.
Have each evaluator score independently before the committee discussion. That prevents the most persuasive salesperson—or the loudest executive—from anchoring everyone else.
I'd put these directly into your RFP:
That last question is particularly revealing. The strongest firms should be able to tell you what you need to change—not just what they intend to deliver.
I'd be particularly cautious if a consultant:
A low initial quote can be misleading if scope, staffing or assumptions are incomplete; comparing detailed project plans is more useful than comparing headline prices.
Week 1: Define objectives, scope, requirements and evaluation criteria.
Week 2: Identify 6–8 potential firms; narrow to 3–4.
Week 3: Issue the same RFP and project assumptions to each.
Week 4: Interview teams and conduct scenario-based workshops.
Week 5: Perform reference calls and commercial/contract review.
Week 6: Finalist presents the proposed implementation plan to your executive team.
Then select the firm based on evidence from comparable implementations, the actual people assigned, methodology, risk management and commercial terms—not the quality of the sales presentation.
One other important point: if you haven't selected the ERP yet, don't hire an implementation partner solely on its ability to implement one particular product. Consider using a genuinely independent advisor for selection, then competitively sourcing the implementation. That keeps your software decision and your services decision from becoming unnecessarily intertwined.
If you tell me your company size, industry, number of entities/countries, current ERP, and the ERP platforms you're considering (e.g., SAP, Oracle, Dynamics 365, NetSuite, Infor, Acumatica), I can turn this into a CFO-grade ERP consultant RFP and weighted interview scorecard tailored to your situation.
As a CFO, your primary concern with an ERP implementation is protecting ROI, minimizing operational disruption, and ensuring financial data integrity. Hiring the right ERP implementation consultant—or implementation partner—requires a structured, risk-mitigated approach. The step-by-step framework below outlines how…
As a CFO, your primary concern with an ERP implementation is protecting ROI, minimizing operational disruption, and ensuring financial data integrity. Hiring the right ERP implementation consultant—or implementation partner—requires a structured, risk-mitigated approach.
The step-by-step framework below outlines how to source, evaluate, and contract the ideal partner for your organization, drawing on insights from resources like ERP Research and Symhas.
Before looking at resumes or firms, determine where you are in the journey:
Do not let a consultant define your initial parameters from scratch. Document your requirements internally:
Generic "ERP experience" is a red flag. Drill down into specific proficiencies:
During pitch presentations, evaluate how they manage risk:
When checking references, don't just ask if the client was "happy." Ask pointed questions about budget and timeline realities:
To help tailor this approach, could you share:
To hire the best ERP implementation consultant, you must **prioritize independent, technology-agnostic advisors with deep industry expertise and proven change-management methodologies** over generic software resellers . As a CFO, your goal is to protect capital, mitigate operational risk, and realize a tangible return…
To hire the best ERP implementation consultant, you must prioritize independent, technology-agnostic advisors with deep industry expertise and proven change-management methodologies over generic software resellers . As a CFO, your goal is to protect capital, mitigate operational risk, and realize a tangible return on investment rather than just deploying new software.
Transitioning from strategy to execution requires a structured, multi-step vetting process to ensure your organization selects a partner capable of delivering enterprise-wide transformation.
If you'd like to narrow this down, please share:
For a CFO, I’d treat the ERP implementation consultant as a **business-transformation partner**, not simply an IT contractor. The biggest mistake is hiring based on brand name, ERP certification, or lowest day rate rather than the actual team and methodology you’ll receive. Current Gartner research specifically frames…
For a CFO, I’d treat the ERP implementation consultant as a business-transformation partner, not simply an IT contractor. The biggest mistake is hiring based on brand name, ERP certification, or lowest day rate rather than the actual team and methodology you’ll receive.
Current Gartner research specifically frames systems-integrator selection around matching provider capabilities to the organization's particular ERP use cases, while its 2025 RFP guidance warns that poor integrator selection can contribute to delays, overruns, and unmet objectives.
There are three quite different engagements:
For a significant ERP transformation, I'd seriously consider independent advisory support even if the implementation partner is excellent. You don't want the company recommending a particular implementation approach to also be the party whose revenue depends on selling you that approach.
Don't start by asking, "Who implements SAP/Oracle/Dynamics/etc.?"
Start with:
"Who has successfully transformed a company like ours using this ERP, at our scale, with our complexity?" Gartner's current cloud-ERP research evaluates providers across capabilities such as finance transformation, supply chain, manufacturing, change management, discovery/design, platform-specific expertise, and application management.
Your shortlist should contain a mix of:
Don't automatically assume the largest firm is best suited to you.
I'd use a weighted scorecard roughly like this:
| Criterion | Suggested weight |
|---|---|
| Relevant implementation experience | 20% |
| Quality of proposed team | 20% |
| Implementation methodology | 15% |
| Business-process transformation capability | 10% |
| Data/integration capability | 10% |
| Change management & adoption | 10% |
| Commercial model & cost transparency | 10% |
| References / demonstrated outcomes | 5% |
The important point is not to copy these percentages blindly. Your weights should reflect your risk profile.
For example, a manufacturer with complex supply-chain requirements should weight operational expertise differently from a professional-services company primarily replacing its financial system.
Deloitte's ERP research similarly argues that organizations should evaluate more than functional fit, including technical architecture, extensibility, user experience, vendor ecosystem, regulatory considerations, and total cost of ownership.
This is probably my most important recommendation.
Don't let the partner win you with a brilliant sales team and then discover that the implementation is staffed by people you've never met.
Require:
"The people presenting today are the people who will lead our implementation." Then ask to meet:
Ask each person:
"What percentage of your time will actually be allocated to our project?"
And:
"What other projects are you currently committed to?"
Put named personnel and minimum staffing commitments into the contract.
Give each finalist 2–3 of your hardest business problems.
For example:
"We currently close in 12 business days. We want to reach 5." "We have 17 legal entities and three currencies." "Our order-to-cash process requires six systems." "Our inventory data is unreliable." Then ask:
"Show us exactly how you'd approach this."
Have them walk through:
This reveals vastly more than asking for another generic ERP demonstration.
Deloitte likewise recommends focusing evaluation on a smaller number of distinctive business use cases rather than attempting to evaluate hundreds of generic requirements.
Don't accept three hand-picked references and call it done.
Ask for 5–8 customers, ideally including:
Then speak to the references without the consultant present.
Ask:
"Was the project delivered on the original budget?" "What did the consultant tell you that turned out not to be true?" "What was the biggest surprise?" "Who on their team was exceptional?" "Who would you not hire again?" "How much customization did you end up with?" "What happened to your project timeline?" "Would you hire the same people again?" That last question is particularly revealing.
Ask directly:
Independent ERP advisors themselves recommend asking about reseller/commission relationships and whether consultants can demonstrate situations in which they advised clients not to choose the obvious ERP.
You want the consultant's economic incentives to be reasonably aligned with yours.
I'd avoid evaluating proposals simply on total implementation price.
Break it into:
Then ask:
"What isn't included?"
That question is often more valuable than asking what is included.
Also ask for the assumptions behind every major estimate.
If one consultant estimates 10,000 hours and another estimates 25,000, don't simply pick the cheaper one. Find out why the estimates differ.
I'd strongly consider a commercial structure containing:
Be particularly careful with a pure time-and-materials arrangement where the consultant controls both the scope definition and the number of hours required to complete it.
This is an excellent interview technique.
At the finalist stage, tell each firm:
"Assume you have won. Give our executive team a 30-minute briefing on the five things most likely to cause this implementation to fail." A sophisticated partner should discuss things like:
Then ask:
"Which of these risks do you think we are currently underestimating?"
Their answer tells you a lot about whether you're talking to consultants or salespeople.
Your internal governance should ultimately answer:
Why are we implementing this ERP? Examples might include:
Then make the implementation partner accountable for helping you achieve those outcomes—not merely configuring software.
That's consistent with the broader shift in ERP selection toward business value rather than simply comparing feature lists.
I'd run it approximately like this:
Week 1: Define objectives, scope, constraints and evaluation criteria.
Week 2: Identify 8–10 potential firms.
Week 3: Narrow to 4–6 and issue the same RFP.
Weeks 4–5: Written proposals + structured presentations.
Week 6: Deep-dive finalist workshops using your actual business scenarios.
Week 7: Reference checks, commercial negotiation and proposed-team interviews.
Week 8: Final selection and contract.
Gartner currently provides specific guidance and tools for both identifying ERP implementation providers and structuring RFPs, which is a useful benchmark for this process.
Ask every finalist:
"Tell me about an ERP implementation that you advised the client not to proceed with as originally planned. What did you discover, what did you recommend instead, and what happened?" A consultant who can demonstrate that they have **challenged a client's assumptions and protected the client's interests—even when it reduced their own billable work—is giving you much stronger evidence of independence than a glossy list of certifications.
That's consistent with the broader shift in ERP selection toward business value rather than simply comparing feature lists.
I'd run it approximately like this:
Week 1: Define objectives, scope, constraints and evaluation criteria.
If you’re the CFO, I’d treat the ERP implementation consultant as a **risk-management and business-transformation hire**, not simply an IT contractor. Research consistently points to leadership, project governance, business-process design, change management, communication, data, and implementation capability as major…
If you’re the CFO, I’d treat the ERP implementation consultant as a risk-management and business-transformation hire, not simply an IT contractor. Research consistently points to leadership, project governance, business-process design, change management, communication, data, and implementation capability as major determinants of ERP success.
There are three materially different roles:
For a significant ERP investment, I'd strongly consider having an independent advisor separate from the implementation firm, particularly if you haven't selected the ERP yet. An advisor who recommends a product and then earns implementation revenue from that recommendation has an inherent conflict.
I'd score candidates against something like this:
| Criterion | Weight |
|---|---|
| Comparable ERP implementations | 20% |
| Named team's actual experience | 15% |
| Finance/accounting expertise | 15% |
| Project governance & delivery methodology | 15% |
| Business-process transformation | 10% |
| Data migration & integrations | 10% |
| Change management/adoption | 10% |
| Commercial model/value | 5% |
The key word is comparable.
Don't accept "We've implemented 100 ERPs." Ask:
"Show me the three implementations most similar to ours in industry, size, complexity, number of entities, countries and integrations." Then ask for references from those projects.
This is one of the biggest traps in consulting selection.
The senior partner sells you the engagement; six months later you're dealing with people you've never met.
Require your proposal to identify:
Then interview those people.
Put key-person provisions in the contract: substitution requires your approval, and replacement personnel must have comparable qualifications. This is specifically recommended in independent ERP-consultant selection guidance.
I'd ask every finalist:
"Tell me about an ERP project that went badly. What happened, what did you do, and what would you do differently?"
Then:
"Tell me about a project where you told the CFO/CEO that their preferred approach was wrong."
And:
"What are the three biggest risks you see in our project based on what you've learned so far?"
A good consultant should be willing to challenge management.
Also ask:
Data, testing, stakeholder engagement and change management are recurring implementation risk areas.
Don't accept a glossy PowerPoint saying "Our proven methodology."
Give finalists a hypothetical problem from your business:
"We're a $500M multi-entity company. We have five business units, three ERPs today, significant Excel-based reporting, 200 integrations, and a year-end close that takes 15 business days. Show us how you'd approach the first six months." Have them present:
You'll learn more from this exercise than from another three-hour capabilities presentation.
As CFO, you'll naturally focus on fees. That's appropriate—but consulting fees are tiny relative to the economic consequences of a bad implementation.
Instead, compare:
Total economic exposure = implementation fees + internal labor + software + integration + data migration + change management + contingency + cost of delay + business disruption.
A consultant who is 15% more expensive but materially reduces the probability of a six-month delay can be dramatically cheaper.
I'd also avoid selecting solely on lowest hourly rates. Ask for a commercial structure that creates accountability—e.g. milestone-based payments, defined deliverables, capped portions of T&M work, and explicit assumptions.
Don't just ask for references. Conduct reference calls yourself.
I'd ask each reference:
That last question is probably the highest-signal question on the list.
Also ask for a reference from a project that went wrong, not just their showcase customer.
If you're hiring an independent advisor, ask in writing:
An independent advisor should be comfortable answering these questions.
Don't make the classic mistake of saying:
"We hired a great consultant, so they can run the ERP project." You still need an empowered internal owner.
For a major ERP, I'd establish:
Executive sponsor: CFO/COO ↓ Steering committee: CFO, COO, CIO/IT, business-unit leaders ↓ Internal program leader ↓ Business process owners + IT + data + change leads ↓ Implementation partner
The consultant should augment your organization—not become your organization.
Research on ERP success repeatedly identifies management sponsorship, appropriate team composition, project management and change management as critical factors.
I'd shortlist 4–6 firms, give each exactly the same:
This makes proposals genuinely comparable rather than allowing each consultant to define the project differently.
Before awarding the contract, ask each finalist to give you a one-page answer to this question:
"If you were the CFO, what would you be most worried about in this ERP implementation, and what would you do in the first 90 days to reduce that risk?" The best consultant will probably talk less about software features and more about process ownership, governance, data, people, decision-making, scope, testing and business outcomes.
That's what I'd hire for.
If you tell me your company size, industry, number of entities/countries, current ERP(s), and which ERP platforms you're considering (SAP, Oracle, Dynamics, NetSuite, Infor, etc.), I can also give you a CFO-ready consultant RFP, interview scorecard, reference-check questionnaire, and recommended contract terms tailored to your situation.
That last question is probably the highest-signal question on the list.
Also ask for a reference from a project that went wrong, not just their showcase customer.
If you're hiring an independent advisor, ask in writing:
An independent advisor should be comfortable answering these questions.
Don't make the classic mistake of saying:
"We hired a great consultant, so they can run the ERP project." You still need an empowered internal owner.
For a major ERP, I'd establish:
As a CFO, you know an ERP implementation isn't just an IT project—it’s a massive operational, financial, and cultural shift that impacts your balance sheet, cash flow visibility, and day-to-day controls. Hiring the right implementation consultant (or partner) dictates whether you hit your ROI or become a cautionary…
As a CFO, you know an ERP implementation isn't just an IT project—it’s a massive operational, financial, and cultural shift that impacts your balance sheet, cash flow visibility, and day-to-day controls. Hiring the right implementation consultant (or partner) dictates whether you hit your ROI or become a cautionary budget-overrun statistic.
To secure the best advisor for your organization, use a rigorous, multi-step evaluation framework:
If you'd like to narrow this down, tell me:
I can share targeted questions to grill their technical and financial leadership with.
As a CFO, you should evaluate an ERP implementation consultant less like a software vendor and more like a **business transformation partner**. The ERP platform matters, but the implementation partner often determines whether you achieve the intended ROI, stay on budget, and actually improve finance operations.…
As a CFO, you should evaluate an ERP implementation consultant less like a software vendor and more like a business transformation partner. The ERP platform matters, but the implementation partner often determines whether you achieve the intended ROI, stay on budget, and actually improve finance operations.
A strong selection process looks like this:
First determine whether you need:
For a CFO-led transformation, an independent advisor can be valuable if you are selecting the ERP and implementation firm simultaneously, because they can help avoid vendor-driven decisions.
Avoid choosing based on brand recognition or lowest hourly rate. Score candidates on:
| Criterion | Weight | What to test |
|---|---|---|
| Industry experience | 20% | Have they implemented ERP for companies like yours? |
| Finance expertise | 20% | Do they understand close, consolidation, controls, reporting, FP&A? |
| ERP platform expertise | 15% | How many successful implementations on your chosen ERP? |
| Implementation methodology | 15% | Do they have a repeatable approach and clear deliverables? |
| Team quality | 15% | Who will actually work on your project? |
| References | 10% | Can you speak with comparable CFOs? |
| Commercial model | 5% | Are assumptions, scope, and change controls clear? |
A consultant should be able to explain not just how they configure software, but how they improve business processes and manage organizational change.
Many firms put senior executives in the sales process and then assign a different team after signing. Ask:
A credible partner should commit named resources and explain their availability.
Require:
When speaking with references, ask:
References from companies similar in size, industry, and complexity are much more meaningful than generic case studies.
Because you are the CFO, probe beyond technical implementation:
Ask them:
A consultant who only talks about screens, workflows, and integrations may not understand the finance transformation you are trying to achieve.
Strong firms should have a clear approach covering:
Be cautious if a firm jumps straight into configuration without spending time understanding your processes. Poor requirements definition and weak change management are common causes of ERP problems.
Your contract should define:
Avoid vague statements such as “assist with implementation” without measurable outcomes.
Be cautious if the consultant:
A practical CFO timeline:
Weeks 1–2
Weeks 3–5
Weeks 6–7
Week 8
For a significant ERP investment, selecting the implementation partner deserves as much rigor as selecting the ERP software itself.
A useful final question to ask every finalist:
“Tell me about the ERP implementation you are most proud of—and the one that went badly. What did you learn, and what would you do differently on our project?” The best consultants usually have a thoughtful answer to both.
As a CFO, you know an ERP implementation isn't just an IT project—it's a massive operational and financial transformation. Hiring the right partner dictates whether your project comes in on budget and realizes the forecasted ROI, or turns into an expensive, protracted mess. Here is a structured framework to source,…
As a CFO, you know an ERP implementation isn't just an IT project—it's a massive operational and financial transformation. Hiring the right partner dictates whether your project comes in on budget and realizes the forecasted ROI, or turns into an expensive, protracted mess.
Here is a structured framework to source, vet, and hire the best ERP implementation consultant or partner.
When vetting candidates or system integrators (SIs), evaluate them against these financial and operational benchmarks:
Don't let the sales team-leader pitch you. Demand to interview the actual operational leads:
As the financial gatekeeper, tie their compensation to performance:
Are you currently choosing an ERP software package or have you already selected the platform and need an implementation partner?
As a CFO, your priority in an ERP implementation is mitigating financial risk, controlling the total cost of ownership (TCO), and ensuring ROI without crippling day-to-day operations. Hiring the right ERP consultant—or implementation partner—requires a structured, highly analytical…
As a CFO, your priority in an ERP implementation is mitigating financial risk, controlling the total cost of ownership (TCO), and ensuring ROI without crippling day-to-day operations. Hiring the right ERP consultant—or implementation partner—requires a structured, highly analytical approach.
To help narrow down your strategy, tell me:
If I were advising a CFO, I’d treat the ERP consultant as a **risk-management and governance hire**, not simply a software-services purchase. The best consultant is the one who can protect your company from bad process decisions, scope creep, weak implementation teams, and vendor incentives—not the one with the…
If I were advising a CFO, I’d treat the ERP consultant as a risk-management and governance hire, not simply a software-services purchase. The best consultant is the one who can protect your company from bad process decisions, scope creep, weak implementation teams, and vendor incentives—not the one with the slickest demo.
Current ERP-selection guidance also strongly favors evaluating implementation partners separately from the software itself, using weighted criteria and evidence rather than sales presentations.
There are three materially different roles:
For a significant ERP transformation, I'd seriously consider independent advisory + implementation partner, rather than allowing the company selling you the ERP to also define what you supposedly need. An independent advisor can create requirements and evaluate vendors without having the same financial incentive to sell a particular platform.
Your shortlist should contain perhaps 4–6 firms, with every firm responding to the same scope and questions.
I would require evidence of:
Most importantly, meet the actual people who will implement your ERP. A famous consulting firm's brand is worth little if its A-team sells the project and a junior team delivers it. Current implementation-partner guidance specifically recommends evaluating the named team rather than the firm's brand.
Don't ask, "What's your implementation methodology?"
Ask:
"Walk me through the last ERP project that went badly. What happened, when did you realize it, what did you do, and what did it ultimately cost the client?" Then ask:
A vague methodology, weak testing/UAT plan, or unclear hypercare model should be a significant warning sign.
Don't accept three hand-picked references and ask, "Were you happy?"
Call the CFO, controller, CIO, or equivalent at each reference.
I'd ask:
That last question is particularly revealing. Recent partner-selection guidance recommends probing actual timeline accuracy, scope changes, post-go-live support, and whether the client would hire the team again.
This is particularly important if you're still selecting the ERP.
Ask every consultant, in writing:
If the consultant is paid by the ERP vendor, don't necessarily reject them—but understand the incentive structure and adjust your evaluation accordingly. Independent selection guidance specifically flags reseller/referral relationships as something buyers should investigate.
I'd weight the selection approximately like this:
| Criterion | Weight |
|---|---|
| Comparable ERP implementations | 20% |
| Industry/business-process expertise | 20% |
| Actual proposed team | 15% |
| Implementation methodology & governance | 15% |
| Data migration & integrations | 10% |
| Change management, training & adoption | 10% |
| References & commercial transparency | 10% |
| Total | 100% |
These categories are broadly consistent with current ERP implementation-partner evaluation frameworks.
Score each candidate 1–5 and calculate weighted scores before you get emotionally attached to a particular firm.
The cheapest implementation partner can be spectacularly expensive.
Instead, normalize:
Total implementation cost =
Then ask each finalist:
"What isn't included in your proposal that you believe we are likely to need?" That question often exposes the difference between an honest proposal and a deliberately low bid.
Also scrutinize change-order mechanics. Fixed-price versus time-and-materials isn't inherently good or bad; the critical issue is how scope changes are identified, priced, approved, and governed.
I'd run a paid finalist workshop.
Give the finalists the same hypothetical scenario:
"Our close currently takes 12 business days. We have five legal entities, two currencies, a legacy billing system, 15 years of historical data, and a highly customized revenue process. We need to go live within 12 months." Ask each firm to spend 2–3 hours showing:
That last item is critical.
The best ERP consultant will sometimes tell the CFO "no."
Your SOW should explicitly identify:
Don't accept:
"We reserve the right to substitute personnel of comparable qualifications." I'd want the ability to approve or reject replacement of key project personnel.
I'd become very cautious if a consultant:
For a CFO-led ERP project, I'd run this as a 6–8 week procurement process:
The key principle is: don't hire the consultant who tells you your ERP project will be easy. Hire the consultant who can show you exactly where it will be hard—and has a credible plan for dealing with those difficulties.
If you're at the beginning of the process, I can also build you a CFO-ready ERP implementation consultant RFP, including the evaluation scorecard, 50+ interview questions, reference-check script, and SOW requirements.
The key principle is: don't hire the consultant who tells you your ERP project will be easy. Hire the consultant who can show you exactly where it will be hard—and has a credible plan for dealing with those difficulties.
If you're at the beginning of the process, I can also build you a CFO-ready ERP implementation consultant RFP, including the evaluation scorecard, 50+ interview questions, reference-check script, and SOW requirements.
