How to Choose an ERP Consultant (Criteria, Questions & Red Flags)

Why the ERP consultant is the biggest risk in your project

Choosing an ERP consultant is, in practice, the most consequential risk-management decision in an ERP project. Gartner reports that 55%–75% of ERP projects fail to meet their objectives, and predicts that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals — with as many as roughly 25% failing catastrophically.

The failures are almost never about the platform. Godlan's analysis of more than 2,400 ERP implementations identifies the same three preventable root causes at the top of the list: inadequate change management (cited in 42% of failures), poor data migration (38%), and inexperienced teams (35%) — all partner-driven variables, not software-driven ones. Percentages overlap because most failed projects suffer from more than one.

Partner-selection research in 2026 reinforces the same pattern: industry analyses of Dynamics implementations estimate that roughly 70% of ERP failures stem from pre-implementation decisions (partner choice, timeline, scope, data migration definition), and that early red-flag detection can avoid 40–60% of later recovery cost. Panorama Consulting's ERP Report found that 42% of respondents selected a vendor that may not have been the optimal fit. In other words, the choice of who advises and delivers your ERP is where most projects are won or lost before configuration even begins.

What an ERP consultant actually does

Before you evaluate firms, scope the role. An ERP consultant's work spans the full project: discovery and business-process mapping, platform or vendor selection, system configuration, customization governance, data migration, training and change management, go-live hypercare, and post-go-live optimization.

Independent advisors draw a clear line between a software vendor (whose primary interest is deploying and licensing a product) and a platform-neutral consultant (whose role is to ensure business-process fit, risk mitigation, and alignment with organizational needs). Many buyers also separate pure selection advisory from implementation: an independent advisor can run requirements and RFP, then a system integrator (SI) delivers the chosen stack—especially useful when you want unbiased shortlisting before any reseller has a commercial stake in the outcome.

Use this scope as the baseline when you compare proposals. If a candidate cannot clearly describe what they will and will not own across discovery, selection, build, and post-go-live, that ambiguity is itself a red flag.

The four core criteria for choosing an ERP consultant

A defensible selection comes down to four criteria. Together they cover how the consultant works, who actually delivers, how well they know your world, and what happens after launch. Capital Edge frames a comparable checklist around five factors: breadth of experience, independence (vendor-neutral advice), the profile of clients managed by your consultant, communication, and value-driven pricing.

Use these four as a structured scorecard before you look at any specific firm — including Flectic. The weighted table below turns opinion into evidence: assign scores only when the partner can produce the artifact, named CV, or reference call listed under 'Evidence to demand'.

Methodology: documented lifecycle, not improvisation

A documented methodology is the first filter. Panorama Consulting recommends choosing a consultant with end-to-end methodology understanding and full project lifecycle support from selection through go-live and optimization. If a firm cannot show you a written, phased approach to discovery, design, build, test, deploy, and support, delivery will default to whatever the assigned team improvises.

Ask to see the methodology document, not a slide. A consultant who can describe their phases, entry and exit criteria, and the artifacts produced at each gate is meaningfully different from one who describes ERP delivery as a series of workshops. RSM's partner-failure guidance is blunt here: if you ask for sample end-user training, standard EDI formats, pre-configured testing logs, or configuration checklists and receive only generic placeholders, you may be funding their first real library of IP on your project.

This criterion is the structural answer to the failure modes above: poor data migration and inadequate change management are both methodology gaps, not platform gaps. Thin or generic discovery deliverables after the 'discovery phase' are a mid-project red flag with the same root cause—treat incomplete process maps and vague requirements as a stop-and-replan signal, not a paperwork inconvenience.

Named senior consultant: stop the bait-and-switch

The most under-covered risk on the SERP is who actually delivers your project. The Chain, a supply-chain industry publication, devotes a full piece to the gap between who sells an ERP project and who delivers it, arguing that senior partners sell the work while junior or offshore consultants end up implementing it — a pattern it calls one of the biggest and least-discussed risks in enterprise technology today.

Tigunia echoes this for the mid-market: large generalist consulting firms regularly win ERP engagements and staff them with junior resources while senior partners sell the work. Top Dynamics Partners' 2026 red-flag guide names the same failure mode as a primary pre-signature disqualifier: proposals that list roles and FTE allocations without named individuals leave the partner free to rotate juniors, reassign staff mid-project, or fill gaps with whoever is bench-available. Named resource turnover is repeatedly cited as a top driver of implementation delay.

The protection is procedural and contractual. Require: (1) named day-to-day delivery lead and core functional/technical roles in the SOW; (2) bios, years of experience, platform certifications, and relevant projects for each named person; (3) your right to interview key team members before signature; (4) a substitution clause—equal or greater experience, client written approval, and a hard replacement window (commonly 10 business days). A consultant who will not commit to named senior resources is reserving the right to staff with whoever is available. Treat that as a disqualifier, not a negotiation point.

Industry experience: references in your size band

Industry experience is not the same as platform experience. A consultant may have completed many implementations on a platform without ever having done so for a business your size, in your sector, with your regulatory and operational profile.

Ask for two or three references that are genuinely comparable — similar revenue band, similar industry, similar platform footprint — and actually call them. RSM's test is practical: if you are a food manufacturer, has the partner been teaching you lot track-and-trace, recipes, co-products, and catch weight—or have you been training them? A consultant who cannot produce references in your size band is, at best, going to learn your context on your budget; at worst, they are misrepresenting their track record.

This is also where platform certifications matter. For Microsoft Dynamics 365 partners, the current bar is the 'Solutions Partner for Business Applications' designation, which requires a minimum Partner Capability Score of 70 out of 100 across skilled certifications, customer success, and performance — replacing the legacy Gold/Silver competencies.

Lifecycle support: hypercare, SLAs, and knowledge transfer

Go-live is the beginning of value, not the end of the engagement. Yet many ERP consultants scope their work to end at cut-over, leaving adoption, optimization, and post-launch fixes unowned. Require explicit post-go-live support: a defined hypercare window, severity-based response-time SLAs, and a named owner for the optimization phase.

Panorama's 2026 hypercare guidance frames hypercare as business stabilization—not a temporary ticket queue. Leaders should set hypercare expectations during evaluation, not only during implementation planning. A usable hypercare plan typically includes daily review cadences, business-led issue prioritization, visible severity metrics, designated decision-makers who can approve fixes without delay, and workstream checklists (finance close, order-to-cash, procure-to-pay, inventory, data/reporting, security/integrations).

Lifecycle support is also where change management and knowledge transfer live. If the consultant's scope ends at launch, training materials, process documentation, and adoption measurement will be left to your team — and weak change management is the single largest root cause of ERP failure in Godlan's dataset (42% of failures). Contract exit criteria for hypercare: super-user readiness, documented runbooks, open P1/P2 backlog below an agreed threshold, and a named internal owner for each critical process. The right consultant treats post-go-live optimization as a contracted phase with deliverables, not an implied favour.

Questions to ask before you hire an ERP consultant

These ten questions, drawn from independent ERP advisory guidance and 2026 partner-failure patterns, are the practical vetting checklist. Ask them in writing, and score answers against the weighted criteria above.

Use the answers as evidence, not theatre. A consultant who answers vaguely on team composition, data migration, AI/Copilot scope, methodology, or post-go-live support is telling you something important.

1. 01
   1. How many implementations have you completed on THIS specific platform?

   Platform-specific delivery experience — Dynamics 365 or Odoo — is different from generic ERP experience. Ask for the count on the exact stack you are buying, and for references from those projects.

2. 02
   2. Who exactly will I work with day-to-day?

   Get the named senior consultant in writing. This is the bait-and-switch filter: if the answer is 'a team' or 'we'll assign closer to start', the senior partner who sold the work is unlikely to be the one delivering it. Interview the named lead before you sign.

3. 03
   3. What is your documented methodology—and can I see the artifacts?

   Ask for the phased lifecycle document, entry and exit criteria for each phase, and sample artifacts (discovery pack, config checklist, test logs, training outline). If the answer is a list of workshop names, the methodology is not documented.

4. 04
   4. How is data migration scoped, validated, and reconciled?

   Demand source systems, entities, record counts, cleansing ownership, validation rules, cutover sequence, and success criteria (matching counts, no orphaned records, required fields complete). 'We'll handle migration in discovery' is a red flag—scope it before signature.

5. 05
   5. How are customizations governed—and what is your fit-gap reflex?

   Customizations multiply long-term cost and upgrade risk. The right answer is process mapping and standard configuration first, customization second—with change control. Ask for a real gap they found and what they did with it; the reflex to customize everything is a red flag on modern cloud ERP.

6. 06
   6. What is in scope for AI, Copilot, or agents—and what is explicitly out?

   AI features are a common 2025–2026 scope-creep vector. Require a written list of licensed AI capabilities, data prerequisites, governance, and success metrics—and what will not be delivered in phase one. Ambiguous 'we'll enable Copilot' language becomes an open change-order channel.

7. 07
   7. How is success measured beyond go-live date?

   Ask how the consultant defines and reports on-time, on-budget delivery, and what business outcomes (not just milestones) they commit to. Vague success criteria let under-delivery hide.

8. 08
   8. What does hypercare look like—window, SLAs, and named owners?

   Get the hypercare duration, P1/P2 response and resolution targets, on-call coverage, daily triage cadence, optimization phase scope, and named owner. If support is left to 'we'll figure it out', adoption risk is on you.

9. 09
   9. How do you push back on unrealistic timelines or scope?

   An experienced partner challenges ambitious dates and thin testing windows with specifics. A partner who agrees to everything is either inexperienced, desperate for the win, or planning change orders when reality arrives. Test this during RFP with a deliberately aggressive timeline ask.

10. 10
    10. Can we speak to comparable references in our size band?

    Two or three references in your size band and sector — on the same platform. Actually call them. Ask what they would change if they started over. A 'no' here is disqualifying.

Red flags that should stop you signing

These are the recurring warning signs across independent ERP advisory guidance and 2026 partner-selection research. Each one has a documented cost — usually a project that meets the failure definition above. Independent practitioners (including Eric Kimberling / Third Stage) also warn that vendors and some 'trusted advisors' oversell optimism and understate risk to executives—so treat polish without artifacts as signal, not reassurance.

If you see two or more of these in the same engagement, treat the proposal as high-risk regardless of brand or price. Where possible, convert the flag into a hard contract clause before you proceed—or walk away.

Fixed-bid vs time-and-materials—and the clauses that actually protect you

Pricing model is not a side detail; it decides who owns scope risk. Fixed-price (fixed-bid) sets a single agreed cost for a tightly defined scope—predictable if requirements are stable, rigid when they are not. Time-and-materials (T&M) bills actual hours and rates—flexible when discovery is still open, riskier for the buyer without controls. Hybrid models (T&M with a not-to-exceed cap, or fixed price for discovery plus T&M for build) are common for ERP for good reason: requirements harden over time.

ERP Research's 2026 consulting overview notes day rates often span roughly $200 to $1,000+ depending on seniority, region, and specialization, with full projects ranging from tens of thousands for smaller single-site work to multi-million for large multi-site programs. Treat published ranges as orientation, not quotes—compare two or three written proposals against the same scope package.

Whichever commercial model you choose, the protective clauses are the same family: named resources; substitution rights; detailed data-migration scope; hypercare SLAs; knowledge-transfer exit criteria; explicit AI/Copilot inclusions and exclusions; change-order process with written approval; and—for T&M—a not-to-exceed (NTE) ceiling plus weekly burn reporting. Fixed bid without crisp scope simply moves the fight into claims and change orders later. T&M without NTE and governance turns the engagement into an open tab.

Platform-neutral ERP consultant vs single-vendor partner

Most 'how to choose an ERP consultant' pages are written by one of two parties: a single-vendor partner with inherent platform bias, or a pure-selection consultant that does not implement. Each has a legitimate use case — the point is to choose the model that matches where you are in the decision. ERP Research's 2026 framing is useful: independent advisors focus on requirements, selection, and RFP; vendor-aligned partners configure and deploy a chosen product. Many larger programs use both in sequence.

Panorama Consulting stays vendor-agnostic on the basis that 'one vendor does not fit all organizations,' and Flevy frames independence structurally: a genuinely independent firm provides advisory without affiliations, partnerships, or financial ties to any single software vendor. The most common red flag, per 2026 directory guidance, is a reseller presenting itself as an independent advisor while only recommending the product it sells.

When single-vendor depth is rational: you have already selected the platform (or regulation, ecosystem, or prior investment locks it in), you need deep vertical IP and templates on that stack, and you want a partner with dense product certifications and a stable delivery bench. When platform-neutral (or dual-platform delivery) is rational: you still need a fit-based choice between stacks (for example Dynamics 365 vs Odoo), you want one accountable owner from discovery through go-live, and you refuse to let a single reseller's P&L decide the architecture. When to hire an independent advisor before an SI: selection is still open, stakeholders disagree on the shortlist, or every bidder is a reseller for a different product—run requirements and scoring with a neutral advisor first, then competitively bid implementation.

This decision is upstream of the platform comparison itself — for the head-to-head between the two platforms, see our Odoo vs Dynamics 365 guide rather than re-litigating it here.

How Flectic approaches ERP consultant selection

Flectic is one of the few partners that is both genuinely dual-platform — implementing Microsoft Dynamics 365 and Odoo — and owns delivery end to end. The platform follows the business, not the other way around.

• →Platform-neutral across Dynamics 365 and Odoo, so the recommendation follows fit rather than what we sell.
• →AI-Accelerated Delivery Framework designed to deliver up to 3x faster — a delivery target supported by reusable templates and agile execution, not an unconditional guarantee.
• →Named senior consultant on every engagement, written into the scope — no sales-time bait-and-switch.
• →Lifecycle support after go-live, with defined hypercare, response-time SLAs, and a contracted optimization phase.

ERP consultant selection checklist

A compact recap for skimmers. Use this as the one-page scorecard when comparing two or three finalists.

• →Methodology: documented, phased lifecycle with entry/exit criteria and sample artifacts.
• →Named senior delivery team: written into the contract, with interview rights and a substitution clause.
• →Industry experience: two to three references in your size band and sector, on the specific platform—call them.
• →Data migration: entity-level scope, cleansing ownership, validation and reconciliation criteria before signature.
• →AI/Copilot: phase-one inclusions, exclusions, data prerequisites, and separate estimates for later AI work.
• →Platform certification: verify the current designation (e.g. Microsoft Solutions Partner for Business Applications, minimum Partner Capability Score of 70/100).
• →Lifecycle support: hypercare window, severity SLAs, knowledge transfer, and a contracted optimization phase.
• →Commercial model: fixed-bid only with crisp scope; T&M only with rate card, NTE, and weekly burn; change-order process in writing.
• →Top red flags to reject: timeline theater, unnamed resources, vague migration, no methodology, no hypercare, single-vendor bias posing as independence.

Book an ERP Readiness Call

If you are evaluating ERP consultants — or recovering from an engagement that went sideways — a 30-minute readiness call will clarify your criteria, vetting questions, and platform fit. We will map your highest-impact workflows first, give you a realistic timeline and a qualified cost range, and tell you whether Dynamics 365 or Odoo fits — then point you at the right model, even if that is not us.

Frequently asked questions