Digital transformation consulting

Digital transformation is a phrase that has been used to sell a great deal of expensive nothing. What it should mean is narrow and useful: an honest assessment of how a business currently works, where technology would genuinely change the economics, and a sequenced plan that starts with the cheapest high-return work rather than the most impressive.

We do this as a paid engagement with a written deliverable, and we are willing to conclude that the right answer is to change very little. That is a real outcome and we have delivered it.

Why this is worth doing properly

The failure rate of large transformation programmes is high, and the pattern is consistent: too much at once, sequenced by ambition rather than dependency, with benefits claimed in a business case nobody revisits. The programmes that succeed are the ones broken into pieces that each deliver value independently.

The current pressure is AI, and it is producing a specific distortion — organisations starting from the technology and looking for somewhere to apply it. That is backwards, and it reliably produces pilots that impress and never ship. Starting from an expensive process and asking what would fix it usually leads somewhere less exciting and considerably more valuable.

The other consistent finding is that the binding constraint is rarely technology. It is more often that nobody owns a process end to end, or that two departments have incompatible definitions of the same thing. Software will not fix either, and installing it first makes both harder to see.

Where this work usually goes wrong

Starting with the technology

Deciding to adopt a technology and then searching for use cases inverts the analysis. Start with the processes that are expensive, slow or error-prone, and let those select the tool.

Sequencing by ambition

The most transformative project is usually the one with the most dependencies and the longest payback. Starting there means eighteen months before anything demonstrable, by which point sponsorship has moved on.

Business cases nobody revisits

A projected saving that is never checked against outcomes is a number invented to secure approval. Benefits should be measured after delivery and reported honestly, including when they fell short.

Ignoring who will operate it

A roadmap that assumes capacity and skills the organisation does not have will stall at the point of handover. Operating capability is part of the plan, not an afterthought.

Consultancy that produces only a document

A strategy nobody can execute is an expensive artefact. A roadmap should name the first three things, what they cost, and who does them.

What this covers

Business technology audits

What systems exist, what they cost, what they do and where they overlap or leave gaps.

Marketing audits

Channels, spend, measurement quality and the honest attribution position.

Workflow and operations audits

Manual processes with time and error costs recorded, ranked by what removing them would be worth.

AI opportunity assessment

Which processes are genuine candidates, which are not, and what would have to be true to proceed.

Automation roadmaps

A sequence starting with the cheapest high-return work, with dependencies made explicit.

Digital transformation strategy

The overall direction, scoped so each phase delivers value independently of the next.

Technology selection

Structured evaluation against your requirements, with total cost of ownership rather than licence price.

Software architecture consulting

Independent review of proposed or existing architecture, including build-versus-buy.

Marketing-technology stack development

The tools marketing needs, connected, without duplicated capability nobody noticed paying for.

CRM selection and implementation planning

Requirements, shortlist, evaluation and a migration plan before commitment.

Data and integration strategy

Where data lives, which system owns which record, and how they connect.

Security and data-privacy planning

Obligations that apply, current gaps, and a proportionate plan to close them.

Phased implementation plans

Named phases with deliverables, costs and success measures for each.

Team training and documentation

Building the capability to operate what gets built, which is where handover usually fails.

Ongoing strategic support

A standing advisory relationship for the decisions that come up between projects.

How the work runs

1. Interview widely, including the people doing the work

   Leadership describes the process as designed; the people running it describe it as it is. The gap between those two accounts is usually where the opportunity sits.

2. Quantify before recommending

   Time spent, error rates, licence costs, cycle times. A recommendation without a number attached is an opinion, and it will be treated as one.

3. Rank by return and dependency

   What is cheap, quick and valuable goes first. This builds the credibility that the larger work later depends on.

4. Assess capability honestly

   Whether the organisation can operate what is proposed, and what has to change if it cannot. This is the question that determines whether a roadmap survives contact with delivery.

5. Write a plan somebody can act on

   Named phases, costs, owners, dependencies and success measures. The first phase should be specific enough to start on Monday.

6. Review against outcomes

   Benefits measured after delivery and compared against what was projected, with shortfalls reported rather than reframed.

What you receive

• Systems, cost and capability inventory
• Process audit with time and error baselines
• Quantified opportunity list, ranked
• AI and automation feasibility assessment
• Technology evaluation with weighted scoring
• Total cost of ownership models
• Phased roadmap with costs, owners and measures
• Benefits register with stated assumptions

You probably need this if

• You are being asked for an AI strategy and do not have one.
• Every department wants a different system and nobody can arbitrate.
• You suspect you are paying for overlapping software.
• A previous transformation programme stalled and nobody says why.
• You need an independent view before committing a large budget.

What we build and work with

The deliverable is analysis, so the tooling is about making findings comparable and traceable rather than impressive.

Structured interview protocol

A written script across roles, so findings are comparable rather than a collection of anecdotes.

Process time and error baselines

Measured where possible and estimated with the method stated where not, so later benefit claims can be checked.

Systems and cost inventory

Every tool, its licence cost, its owner and its overlap with others — which usually finds duplicated spend.

Weighted requirement scoring

Technology selection scored against weighted requirements agreed in advance, so the decision is not retrofitted to a preference.

Total cost of ownership model

Licence, implementation, integration and operating cost over several years, rather than the headline subscription price.

Phased roadmap with dependencies

A plan expressed as dated phases with owners, costs and success measures attached to each.

Benefits register

Projected benefits recorded with their assumptions, then measured after delivery and reported as measured or missed.

What changes once this is in place

A ranked list instead of a debate

Opportunities quantified and ordered, which replaces the recurring argument about priorities with a sequence.

Duplicate spend surfaced

A full systems and licence inventory typically finds overlapping tools nobody had compared.

Realistic sequencing

Cheap high-return work first, so the programme demonstrates value before it asks for a larger commitment.

Decisions you can defend

Technology selected against weighted requirements agreed in advance, with the scoring recorded.

Benefits that get checked

A benefits register measured after delivery, including where the projection was wrong.

How this differs by market

The work is the same craft everywhere. What changes is the law, the language and the buying culture — and those change enough to matter.

European Union

Any roadmap touching personal data has to account for GDPR obligations by design, and AI initiatives need classifying against the EU AI Act risk tiers early — a use case that turns out to be high-risk carries documentation and oversight requirements that materially change its cost. NIS2 has also widened cybersecurity obligations across many sectors.

Nordics

High baseline digital maturity means the opportunities are usually in integration and data quality rather than in first-time digitisation. Works council consultation is a real planning input in several countries where changes affect how employees work, and it belongs in the timeline rather than as a surprise.

United States and Canada

Sector compliance frequently sets the constraints — SOC 2 for enterprise sales, HIPAA for health, PCI for payments. Canadian planning has to account for provincial variation, with Quebec’s Law 25 imposing assessment obligations that affect where systems can be hosted.

United Arab Emirates

An unusually supportive policy environment for adoption, with national AI and digital government strategies. The practical planning questions are which regime applies — federal PDPL, DIFC or ADGM — and how bilingual Arabic and English operation is handled, since retrofitting it is expensive.

Not legal advice. Regulatory summaries on this site describe how we scope and build, and are current to our latest review. Verify the operative text with qualified counsel in the relevant jurisdiction before relying on it.

How we know it worked

The deliverable is measured by whether the first phase actually starts. A roadmap that is admired and not acted on has failed regardless of its analysis, so we scope the first phase to be startable immediately.

Afterwards, benefits are measured against the register — the projected saving, its stated assumptions, and what was actually observed. We report shortfalls plainly, because a benefits process that only ever confirms its own projections is theatre.

We do not present projected savings as achieved results anywhere, on this site or in a client report. A projection is labelled as a projection with its assumptions attached, every time.

Estimates are labelled as estimates. Any figure on this site that describes a range is a planning estimate with its assumptions stated, not a measured client outcome. We do not publish client results without the client's permission and a date.

Related services

Sectors where this is usually the lead engagement

These are the industries where this discipline is typically the first thing a client buys rather than something added later. The link goes to a page written for that sector specifically, with a paragraph on this service and on every other one.

• Manufacturing & Industrial — Excellent products, world-class production, and commercial systems that have not been touched in a decade. That gap is the opportunity.
• Construction & Engineering — The fastest-accelerating sector for AI adoption, running on drawings, variations and payment applications that arrive as PDFs.
• Energy & Utilities — Enormous operational data volumes, heavy regulatory reporting, and customer systems that were built for a market that no longer exists.
• Wholesale & Distribution — Thin margins, enormous SKU counts and customer-specific pricing that lives in a system nobody wants to touch.
• Public Sector — Where accessibility is law, procurement is formal, and the service has to work for everyone rather than for a target segment.

It appears on all thirty sector pages, because every one of them carries a paragraph on all twenty-two services. This list names only the sectors where it tends to lead.

Where we deliver this

This service is delivered across the European Union, the Nordic countries, North America and the United Arab Emirates. The craft does not change; the law, the language and the buying culture do. Consent regimes, invoicing mandates and payment conventions differ enough between markets that a campaign or a system built for one frequently cannot be used unchanged in another.

Each country page sets out what actually differs there and what it means for scope — all 32 countries and 10 cities are listed here. A few of the markets we work in most:

• Germany
• Netherlands
• France
• Sweden
• United States
• United Arab Emirates