Book a free consultation (opens in a new tab)

ERP Consulting

ERP Consulting and Selection Services

Most failed ERP selections start with a product demo and end with a signature nobody can defend.

  • 6-12 wkSelection and business case
  • 3-5 yrTCO horizon we model
  • 0Licence commission taken
  • 2-4 wkFit-gap workshop series

Why It Matters

You cannot evaluate an ERP until you can state what you need it to do

A demo you have not scripted is a sales presentation

Vendors demo what their product does well. That is their job. If you have not written your own scenarios, you will watch four polished presentations, remember the one with the strongest presenter, and discover the gaps in month four of the build.

  • Requirements captured per department, in their words
  • Each requirement marked essential, important or nice to have
  • Vendors demo your scenarios, not their canned script
  • Committed to SAP by the 2027 ECC deadline? See SAP consulting

The licence is the number you see, not the number you pay

Buyers get caught here more than anywhere else. The licence quote is visible, comparable and reassuringly precise. Everything around it is not.

  • Licence, implementation, migration, integration and training in one model
  • Internal staff days costed, not assumed free
  • Three to five year horizon, because year one flatters nobody equally

Five stages from problem statement to signed business case

  1. Requirements and readiness

    Process interviews per department, a written requirements catalogue, and an honest read on sponsorship, data quality and internal capacity.

  2. Criteria and weights

    The scoring model agreed and signed before any vendor is contacted, so nobody can re-weight the criteria to fit a preferred answer.

  3. Longlist to shortlist

    A longlist filtered on hard constraints, then three shortlisted platforms taken through scripted demos on your scenarios and reference calls we place ourselves.

  4. Fit-gap workshops

    Two to four weeks working each real gap to a decision: change the process, configure, extend, or accept the gap and work around it.

  5. Business case

    Scored recommendation, three to five year total cost of ownership model, implementation estimate and a phasing plan your board can approve or reject on evidence.

Everything the engagement produces

  • Requirements catalogue

    Your processes written down per department, each requirement classed essential, important or nice to have.

  • Weighted scoring model

    Criteria and weights agreed up front, with the evidence behind every score recorded next to it.

  • Scripted demo pack

    Demo scripts built from your own scenarios, issued to every vendor so you compare like against like.

  • Fit-gap register

    Every gap resolved to a decision: change the process, configure, extend, or accept and work around.

  • TCO and business case

    A three to five year cost model, an implementation estimate and the benefits stated in numbers you can audit.

  • Readiness assessment

    A plain report on sponsorship, project ownership, data quality and whether you can absorb this now.

Why teams bring us in before they choose

  • We will tell you not to buy

    A good consultant has to be willing to conclude that you should not replace your ERP this year. We have written that report before.

  • No licence commission

    We take no reseller margin or referral fee from any vendor. You pay for the advice, which is what keeps it honest.

  • We have built on all three

    ERPNext, Odoo and SAP delivery experience, so the trade-offs we describe come from implementations rather than datasheets.

  • Weights agreed before demos

    The scoring model is signed off before a vendor is contacted, so the criteria cannot be bent to fit a favourite.

  • Readiness assessed, not assumed

    Sponsorship, a named project owner with real hours, and data quality. Most selections skip this and pay for it later.

ERP consulting questions

How long does a proper ERP selection take?

A structured selection and business case runs 6 to 12 weeks. Requirements gathering is the longest part, usually 3 to 5 weeks, because it means sitting with finance, operations, sales and the warehouse and writing down what each of them actually does. A fit-gap workshop series against the shortlisted platforms adds another 2 to 4 weeks. Anything faster than 6 weeks is a preference, not an evaluation, and you will pay for the difference during implementation.

Do you resell any of the ERP platforms you recommend?

No. We take no licence commission, no referral fee and no reseller margin from any vendor. You pay us for the advice, which is the only way the advice stays worth having. We do implement ERPNext, Odoo and SAP, and we declare that openly at the start of every engagement. If the selection concludes that another platform or another partner fits you better, that is what the report says.

How do we compare an open source ERP against a licensed one on cost?

Compare total cost of ownership over the same horizon, not licence against licence. Put implementation, data migration, integration, training, hosting, annual support and your own internal staff time into both columns. Open source removes or shrinks the licence line but not the other lines, and it often shifts cost towards configuration and internal capability. A licensed platform front-loads a visible annual number and usually brings more out of the box for statutory and multi-entity work. Over three to five years the gap is far smaller than the licence quote suggests.

Should we run the selection in-house or bring in a consultant?

Run it in-house if you have someone who has done an ERP selection before, has time freed up for it, and can say no to a department head. That is a real option and we will say so. Bring in a consultant when nobody has done this before, when internal politics mean the loudest function will otherwise win, or when you need someone outside the reporting line to tell the board that the timeline is unrealistic. The consultant should be running the method, not making the decision for you.

What if the answer is that our current systems are fine?

Then we tell you that, and we tell you in writing. A good consultant has to be willing to conclude that you should not replace your ERP this year. Sometimes the real problem is three broken integrations, a reporting gap and a process nobody owns, and fixing those costs a fraction of a replacement. We would rather hand you a short remediation plan and be the people you call in two years than sell you a programme your organisation cannot absorb right now.

What are the deliverables at the end of the engagement?

A documented requirements catalogue with each requirement marked essential, important or nice to have. A weighted scoring model with the criteria and weights agreed by your steering group before demos began. A scored shortlist with the evidence behind each score. A fit-gap register naming, per gap, whether you change the process, configure, extend or accept it. A readiness assessment. And a business case with a three to five year total cost of ownership model, an implementation estimate and a recommended sequence.

Related

The other services in this section, and related pages from TCB Infotech.

Get a Straight Answer Before You Commit

No commitment, and no licence commission on any recommendation we make.