top of page
Search

How to Choose an ERP Consulting Firm: 7 Questions to Ask First

●      The right ERP consulting firm should show direct implementation experience in your industry, not just familiarity with the software.

●      Vendor neutrality matters. A firm that only sells its own add-ons has an incentive to recommend them over what your business actually needs.

●      Get post-go-live support terms in writing before you sign, not after the project is underway.

●      Ask who is actually staffed on your project. The team that scopes the work should be the team that delivers it.

●      Fixed-fee models remove the open-ended billing risk that comes with hourly consulting arrangements.


Picking an ERP consulting firm is one of the highest-stakes decisions a growing business makes, and it's usually made with less information than the price tag deserves. Two firms can quote the same software and produce wildly different outcomes, because the software was never really the variable, the firm was. Before you sign anything, there are seven questions worth asking every ERP consulting firm on your shortlist, and a handful of answers that should send you looking elsewhere.


Why the Right ERP Consulting Firm Matters More Than the Software


Most ERP evaluations spend the bulk of their time comparing feature lists and licensing tiers, and very little time evaluating who will actually configure, migrate, and support the system once it's live. That's backwards. An experienced ERP consulting firm will steer you away from over-customization, flag data-migration risks early, and build a rollout plan your team can realistically follow. An inexperienced one will let you find those problems yourself, usually after go-live, when they're far more expensive to fix.


This matters just as much for smaller and mid-sized manufacturers and service businesses as it does for large enterprises, arguably more, since a stalled implementation hits a lean team harder and there's less budget cushion to absorb rework.


7 Questions to Ask Every ERP Consulting Firm Before You Sign


1. Do you have direct experience in my industry?


General ERP familiarity isn't the same as knowing how your industry actually operates. Ask for examples of past projects in your specific vertical, whether thats manufacturing, healthcare, distribution, or otherwise, and ask what industry-specific configuration decisions they made and why.


2. Are you vendor-neutral, or do you only sell your own add-ons?


Some ERP consulting companies are structured to push proprietary add-on modules regardless of whether your business needs them. Ask directly what percentage of their recommendations involve their own products, and whether they'd ever recommend against an add-on they sell.


3. Who exactly will be on my project team, and will they still be there at go-live?


It's common for a senior consultant to lead the sales conversation and then hand the project to a more junior team after the contract is signed. Ask for names, roles, and a commitment on team continuity from kickoff through go-live and into early support.


4. What happens after go-live?


This is where a lot of ERP consulting firm relationships quietly fall apart. Ask exactly what post-go-live support is included, for how long, and what it costs once that window ends. Get this in writing before you sign, not as a verbal assurance.


5. How do you price the engagement, and what's excluded?


Open-ended hourly billing is the norm across much of the ERP consulting company field, and it puts the budget risk almost entirely on you. Ask for a clear breakdown of what's included in the quoted price, what triggers additional charges, and whether a fixed-fee structure is available.


6. Can I talk to a reference in my industry, not just any reference?


A glowing reference from a completely different industry tells you less than you'd think. Ask specifically for a reference whose business and implementation scope resemble yours.


7. What does a realistic timeline actually look like?


Be wary of any ERP consulting firm that gives you an aggressive timeline without first understanding your data, your current systems, and your team's bandwidth. A realistic timeline usually comes with a phased plan, not a single end date.


Not sure what to ask your current ERP consulting firm shortlist?

Book a free discovery call and we'll walk through your specific project scope together.




Red Flags to Watch For


The questions above are useful on their own, but how a firm answers them often tells you more than what they say. These are the patterns worth treating as disqualifying, not just noting and moving on.


Reluctance to name specific past clients or projects in your industry


A firm with genuine industry experience can usually point to two or three real examples without hesitation. Vague references to "clients like you" without names, industries, or specifics is often a sign the experience is thinner than the pitch suggests.


Pressure to sign quickly before you've spoken to a reference


Any ERP consulting firm confident in its track record will give you time to check it. Urgency tactics, including limited-time pricing, "we need an answer this week", are more about closing the deal than getting your project right.


Vague or verbal-only answers about post-go-live support


If support terms aren't in the proposal or contract, they aren't real terms yet. Watch for phrases like "we'll take care of you" that never make it into writing.


A sales team that's noticeably more senior than the delivery team


It's common for the most experienced person at a firm to run the sales process and then largely disappear once the contract is signed. Ask directly whether the people in the room during evaluation will still be involved during implementation.


No willingness to discuss a fixed-fee or capped-cost option


Open-ended hourly billing isn't inherently dishonest, but a firm that won't even discuss a fixed-fee or capped structure is telling you something about how much budget risk it expects you to carry.


Scope that keeps expanding before the contract is even signed


If the proposed scope grows every time you ask a clarifying question during evaluation, that pattern typically continues, and even worsens, once the project is underway and change orders start.


No clear point of accountability if something goes wrong


Ask who owns a problem if data migrates incorrectly or a deadline slips. If the answer is vague or shifts responsibility to "the software" rather than the firm, that's worth pressing on before you sign.


Unwillingness to share a realistic project timeline in writing


A firm that gives only a verbal estimate, or refuses to commit anything to writing beyond a start date, has left itself room to slip the schedule without consequence.


How ABCC Approaches These Questions


ABCC's Guided Self-Implementation model was built directly around the gaps most of these questions are designed to expose. Instead of open-ended hourly billing, engagements are scoped and priced as a fixed fee from the outset, thus you know the cost before the project starts, not after. The same team that scopes your project stays with it through go-live, and support terms are defined up front rather than negotiated later.


If your business is smaller or leaner than a typical enterprise ERP client, it's also worth reading about how a Guided Self-Implementation engagement is scoped for small and mid-sized manufacturers, and what an ERP implementation consultant actually does day to day once a project is underway.


Frequently Asked Questions


Is it worth paying more for an ERP consulting firm with industry-specific experience?

Usually, yes. Industry-specific experience tends to reduce costly rework later, a firm that has already solved your industry's common configuration problems will typically finish faster and with fewer surprises than one learning your industry on your dollar.

It depends heavily on scope, data complexity, and how much customization is involved, but any firm that won't walk you through a phased, realistic timeline before you sign is worth a second look.

An ERP consulting firm is the company you contract with; an ERP implementation consultant is typically the individual (or team) actually doing the hands-on configuration, migration, and training work. Ask who specifically will be staffed on your project, not just which firm you're signing with.

It's possible but costly, since a new firm has to re-learn your configuration and data decisions from scratch. This is exactly why the questions above are worth asking before signing, rather than after a project stalls.


 
 
 

Comments

More Posts

bottom of page