What a Digital Transformation Consultancy Should Actually Do

"Digital transformation consultancy" is a label that four structurally different businesses all use. They arrive with similar slide decks, similar language, and wildly different incentives. As the operator paying the invoice, your job is to see past the deck and read the structure underneath it, because structure predicts behaviour far better than any promise a partner makes in the room. This is a buyer's guide to who you are actually hiring.

The four archetypes you will meet

Almost every provider you shortlist fits one of four shapes. None of them is a villain and none is a hero. Each is optimised for something, and that optimisation is exactly what makes it strong in one situation and dangerous in another.

Hold those four in mind as we go through them one at a time. The pattern to watch is simple: what does each firm have to sell, and what does that force it to recommend?

The global strategy firm

This is the brand your board recognises. They arrive with partners, a proprietary framework, and a target operating model that reads beautifully. They are genuinely excellent at framing the problem, aligning a fractured executive team, benchmarking you against peers, and producing a narrative that unlocks budget. If your transformation is stuck because leadership cannot agree on what "good" looks like, this is where they earn their fee.

Genuinely good at:

• Executive alignment and board-level storytelling
• Operating model design and benchmarking
• Business case and value modelling
• Unlocking budget and political cover

Structurally bad at:

Delivery. The named partner who sold you the vision is rarely the person on site. The work drops to a pyramid of bright generalists who are learning your domain on your budget. The strategy deck is often disconnected from what your systems can actually do, and when it meets a real integration or data-migration problem, that team subcontracts the hard parts anyway. You pay premium rates for the framing and then pay again for someone else to build it.

The system integrator with a licence relationship

The system integrator, or SI, is a delivery business. They hold a formal partner relationship with one or more platform vendors, they carry a large bench of configured consultants, and they can put twenty people on your programme next month. For a genuinely large build, they are often the only realistic option, because nobody else has the capacity. Their integration and delivery muscle is real.

Genuinely good at:

• Scaled delivery across many parallel workstreams
• Deep, certified expertise in their chosen platform
• Repeatable methodology and accelerators
• Absorbing risk on fixed-scope builds

Structurally bad at:

Independence. The SI makes margin on licences, on implementation days, and frequently on partner rebates from the vendor. Ask an SI whose entire practice is built on Platform X whether Platform X is right for you, and you already know the answer. Their recommendation is honest within a boundary, and the boundary is their licence portfolio. Change requests are also where the economics live, so a tightly scoped statement of work can quietly become an expensive one.

The vendor's own professional-services arm

Most serious platform vendors run their own consulting and implementation team. These people know the product better than anyone alive, they have direct access to the engineering roadmap, and they can get a defect escalated in a way no third party can. If you have already, firmly, chosen the platform, the vendor's own team is often the fastest route to a clean deployment.

Genuinely good at:

• Unmatched depth in their own product
• Direct line to engineering and roadmap
• Fast escalation of product defects
• Configuration to leading practice for that platform

Structurally bad at:

Telling you no. This team exists to make their product succeed. They will never advise that the product is a poor fit, that a competitor would serve you better, or that you should buy less of it. Their view of your process is shaped by what the product does well, so your requirements get gently bent toward the software rather than the software toward your requirements. That is fine when the fit is genuinely good and dangerous when it is not.

The independent practitioner

This is my own category, so read the rest of this article with that in mind; there is a fuller disclaimer near the end. The independent practitioner is one senior operator with decades of scar tissue, no product to sell, and no rebate to protect. You hire them for judgement: to challenge the business case, to run a vendor-neutral selection, to sit on your side of the table during negotiation, and to sanity-check what the SI is building. Because there is nothing to upsell, the advice can be genuinely disinterested.

Genuinely good at:

• Vendor-neutral selection and honest fit assessment
• Owner-side assurance over an SI or vendor build
• Continuity: the person who scoped it is the person doing it
• Cutting through vendor and SI sales theatre

Structurally bad at:

Scale. One person cannot staff a twenty-workstream build, cannot be on four sites at once, and represents a single point of failure if they fall ill. An independent is an advisor and a small-team leader, not a delivery factory. Pretending otherwise is the fastest way for the model to fail, which is exactly why I say so plainly below.

Side-by-side comparison

Read across, not down. There is no best column; there is only the column that matches the job in front of you.

The diligence questions that expose the difference

A capabilities deck tells you nothing, because every firm has a good one. What separates them is how they answer a handful of specific, uncomfortable questions. Ask these of every shortlisted provider, and get the answers in writing.

1. Who exactly will be on site, and for how many days? Name the individuals, not the roles. Get the named senior people written into the statement of work with a minimum on-site commitment, so the person who sold the work is contractually the person doing it.
2. What commissions or partner rebates exist on this recommendation? Ask directly what the firm earns from the vendor if you buy the product they are proposing. Silence or vagueness is your answer.
3. What happens to your recommendation if the preferred product loses the selection? A truly neutral advisor is indifferent to which product wins. A tied firm suddenly discovers reasons the process should be reconsidered.
4. Can you show me a deliverable from a comparable engagement? Not a case study slide, an actual redacted target operating model, integration design, or selection scorecard. Firms that build real artefacts can show them; firms that sell decks cannot.
5. Who owns the outcome if the programme misses its business case? Listen for whether the answer is about fixing the outcome or about re-scoping the contract.

When an independent is the wrong choice

I am an independent, and I will still tell you plainly when not to hire one. If you are running a forty-workstream global programme across a dozen countries, with parallel builds, hundreds of configured consultants, and a delivery deadline the board has already announced, a single practitioner cannot supply the bench capacity you need. That is not false modesty; it is arithmetic. One person is one person.

In that situation the honest advice is to engage a system integrator for delivery, and, if you want protection, to retain an independent alongside them in an owner-side assurance role. The independent keeps the SI honest on scope, product fit, and change requests while the SI supplies the hands. Where an independent is genuinely the right primary choice is selection, business case challenge, architecture judgement, and assurance, the moments where a single senior brain is worth more than a large team. Knowing which of those situations you are in is most of the decision.

Engagement shapes and typical fee structures

Buyers get surprised by cost because they compare a fixed-price build to an advisory retainer as if they were the same purchase. They are not. Here are the common engagement shapes and how they are usually priced, so you can budget with your eyes open. Treat every number as indicative and dated: these are ballpark ranges as of mid-2026, they vary widely by region, seniority, and scope, and you should confirm current rates in the market.

One rule cuts across all of them: separate the advice from the build wherever you can afford to. The firm that tells you what to buy should not be the firm that profits from you buying it. That is also the logic behind buying selection help before you buy a platform, whether that is a full ERP or something narrower like procurement software. For definitions of the categories and roles above, the Gartner IT glossary is a reasonable neutral reference.

Conclusion

There is no best archetype, only the right one for the job and the stage. Hire the strategy firm to align the board and frame the case. Hire the system integrator when you need scaled hands to build. Hire the vendor's own team when the platform is firmly chosen and you want product depth. Hire the independent for neutral selection, judgement, and assurance, and to keep everyone else honest. The mistake is not choosing one; it is failing to see which one is pitching you, and paying strategy rates for delivery, or trusting product-tied advice as if it were neutral.