Solution
Complete digital transformation
The whole stack, sequenced — brand, web, marketing, CRM, automation, reporting and infrastructure — with benefits measured afterwards rather than projected and forgotten.
Transformation programmes fail at a well-documented rate, 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 technology is rarely the reason.
This engagement is structured against that pattern. Each phase delivers value independently, the sequence follows dependencies rather than enthusiasm, and the benefits register is measured after delivery and reported honestly, including where the projection was wrong.
Why this is sold as one engagement
The case for doing this as one programme rather than six projects is dependency. A CRM configured before the sales process is documented encodes the wrong process. Marketing built before the CRM has nowhere to send leads. Dashboards built before definitions are agreed produce numbers people argue about. Sequence is the value.
The case against is equally real, and we raise it: a large programme concentrates risk, and clients who can absorb one phase at a time frequently should. We would rather scope this as five sequential engagements you can stop after any of them than as one commitment you cannot exit.
The binding constraint is almost never technology. It is that nobody owns a process end to end, or two departments define the same metric differently. Software will not fix either, and installing it first makes both harder to see.
What is included
- Discovery and audit
- Systems, costs, processes and capability inventoried, with time and error baselines recorded.
- Roadmap with benefits register
- Phases with costs, owners, dependencies and projected benefits with assumptions stated.
- Brand and messaging
- Positioning and message house, where the existing one is the constraint.
- Website
- Rebuilt or replaced, fast, accessible, instrumented and connected to the CRM.
- CRM and sales systems
- Configured against the documented process, with consolidated lead capture and routing.
- Process automation
- The manual work identified in the audit, removed in priority order.
- AI where it fits
- Applied only where the process is genuinely a judgement task, with evaluation built in.
- Data and dashboards
- Metric definitions with owners, pipelines that fail loudly, and views built per decision.
- Cloud infrastructure
- Defined as code, monitored, backed up with restores actually tested.
- Training and documentation
- So the organisation can operate what was built without us.
How it runs
Audit and quantify
Interviews across roles including the people doing the work, systems and licence inventory, process time and error baselines. This produces a ranked opportunity list where the top items are frequently not the ones people complained about.
Sequence by dependency and return
Cheap, quick, high-return work first. Starting with the most transformative project means eighteen months before anything demonstrable, by which point sponsorship has usually moved on.
Foundations
CRM, measurement and integration before anything that depends on them. Unglamorous, and the phase that determines whether everything after it works.
Customer-facing
Brand, website and marketing, built on foundations that can now capture and measure what they produce.
Automation and AI
The manual work identified in the audit, removed in priority order, with AI applied only where the task genuinely involves judgement rather than because it is available.
Measure against the register
Benefits compared with what was projected, with shortfalls reported plainly. A benefits process that only ever confirms its own projections is theatre.
What changes
- A ranked plan instead of a debate
- Opportunities quantified and ordered, replacing the recurring argument about priorities.
- Foundations that hold
- CRM, measurement and integration in place before the things that depend on them.
- Manual work measurably reduced
- Against a baseline recorded during the audit rather than estimated afterwards.
- One agreed set of numbers
- Metric definitions with named owners, which ends most cross-departmental disagreement.
- Infrastructure that can be rebuilt
- Defined as code, monitored, with restores tested rather than assumed.
- Benefits that get checked
- A register measured after delivery, including where the projection was wrong.
Who this is for — and who it is not
A good fit if
- Several departments each want a different system and nobody can arbitrate.
- A previous transformation programme stalled and nobody says why.
- You suspect you are paying for overlapping software.
- Your commercial systems have not kept pace with the operation.
- You need an independent view before committing a large budget.
Not a good fit if
- You need one specific problem solved — buy that service instead.
- You cannot commit a decision-maker for the duration.
- You want the AI phase first, which inverts the dependency order.
- Budget only covers the visible customer-facing work and not the foundations.
On price. Quoted per phase against a defined scope, deliberately structured so you can stop after any phase. The audit is a fixed-price piece of work sold separately, and we are willing for it to conclude that little should change.
What we need from you
Transformation programmes are constrained by organisational decisions far more than by delivery capacity.
- An executive sponsor with authority
- Someone who can arbitrate between departments. Programmes stall at cross-functional disagreement more than at any technical obstacle.
- Access to the people doing the work
- Not just managers. The gap between the process as designed and the process as run is where the opportunity sits.
- Willingness to hear that little should change
- The audit sometimes concludes the answer is narrow. We would rather deliver that than manufacture a programme.
- Metric definition authority
- Someone in your business must own what "active customer" means. We can write definitions and cannot be the authority on them.
- Realistic capacity assessment
- Whether your organisation can operate what is proposed. A roadmap assuming skills you do not have will stall at handover.
- Tolerance for unglamorous phases
- Foundations are invisible and determine everything. Programmes that skip to the visible work rebuild them later at higher cost.
Where this gets difficult
The most common failure is sequencing by ambition. The most transformative project usually has the most dependencies and the longest payback, and starting there produces a long period with nothing demonstrable — which is exactly when sponsorship changes and the programme dies.
The second is that the real constraint is organisational. Nobody owning a process end to end, or two departments defining a metric differently, will not be fixed by software, and installing software first obscures both.
The third is business cases nobody revisits. A projected saving that is never checked is a number invented to secure approval. We keep a benefits register and report against it, which occasionally means reporting that we were wrong.
A fourth is the AI-first temptation. Organisations under pressure to have an AI strategy start with the technology and search for applications, which reliably produces pilots that impress and never ship. Starting from an expensive process is less exciting and considerably more valuable.
A fifth is capacity. A roadmap that assumes skills and headcount the organisation does not have will stall at handover, and building operating capability is part of the plan rather than an afterthought.
Sixth, scope discipline. Transformation programmes attract every deferred wish in the organisation, and a phase that grows by forty per cent mid-delivery is a phase that will overrun and damage confidence in everything after it.
Finally, the honest exit. This is structured so you can stop after any phase, and we would rather a client stopped after two phases having got value than continued into a third that was not earning its cost.
A further difficulty is sponsor turnover. Programmes of this length routinely outlast the executive who commissioned them, and a successor inherits a plan they did not choose with benefits they did not project. Phasing helps, and documenting why each sequencing decision was made helps more, because the successor's first instinct is usually to reorder it.
There is also a persistent temptation to run phases in parallel to compress the timeline. It rarely works: the dependencies that made the sequence necessary do not disappear because two teams are available, and parallel phases typically produce rework that exceeds the time saved.
Finally, the audit itself is frequently the most valuable deliverable and the least valued one. A quantified inventory of systems, costs and manual processes changes decisions immediately, and clients who treat it as a preliminary to the real work tend to under-use it.
The services this combines
Digital Transformation Consulting
Working out what to do, in what order, before anyone spends money building it.
Read more →CRM & Sales Systems
The system of record for revenue: where leads land, how they are routed, what happens next, and whether anyone can see the truth of the pipeline.
Read more →Website Design & Development
Sites built to convert and to survive — fast, accessible, integrated with your CRM, and maintainable by someone other than us.
Read more →Business Process Automation
Removing the manual steps between systems — the copying, re-typing, chasing and exporting that consumes hours nobody counts.
Read more →Data Engineering & BI
Getting numbers out of the systems that hold them, into one place, in a state somebody can actually make a decision from.
Read more →Cloud, DevOps & Infrastructure
The layer everything else runs on — deployed reproducibly, monitored properly, backed up in a way that has actually been tested.
Read more →Questions
Is this just a large bundle?
It is a sequence. The value is in the order — foundations before the things that depend on them — and it is deliberately structured so you can stop after any phase rather than committing to the whole thing.
How long does it take?
The audit is four to eight weeks. A full programme typically runs twelve to twenty-four months across phases, which is why each phase is scoped to deliver value independently.
What does it cost?
Quoted per phase after the audit. The audit itself is fixed-price and sold separately, deliberately, so the recommendations are not shaped by what we would like to build afterwards.
What if the audit says we should not do much?
Then that is the report. It has happened, and we would rather deliver that finding than manufacture a programme to justify a fee.
Can we start with the AI phase?
We would advise against it. AI applied before the data, process and integration foundations exist produces a pilot that impresses and does not ship. It is the most common way AI budgets are wasted.
Will you recommend your own services?
Sometimes, and we declare it. We also regularly recommend buying a product, keeping what you have, or hiring internally. If you would prefer an assessment from someone with no delivery capability, that is a legitimate preference.
What happens if a phase overruns?
We report it when it happens rather than at the end. Phases are scoped to deliver independently precisely so an overrun in one does not compromise the value already delivered.
Do we need to replace all our systems?
Almost certainly not. Integration is usually cheaper and less disruptive than replacement, and replacing a working system to reduce tool count is rarely justified.
How do you measure whether it worked?
Against the benefits register, using baselines recorded during the audit. Where no baseline exists we say the benefit is unmeasured rather than estimating one.
How do we know you are the right supplier for this?
You do not, from a page. What you can check is whether we describe the failure modes accurately, whether we tell you when something is not worth doing, and whether the scope we write has an explicit list of exclusions. A discovery call costs nothing and is the fastest way to find out, and a supplier unwilling to say what they will not do is telling you something either way.
Other solutions
Start a conversation
Tell us where you are now. We will tell you whether this is the right shape of engagement — including when a smaller piece of work would serve you better.
Get in touch