Consulting & Support
Digital Transformation
Modernise legacy systems and processes
"Digital transformation" is a phrase that has been used to sell a great deal of expensive disappointment, usually in the form of a multi-year programme that produces slide decks for eighteen months before anything reaches an actual employee. We use it here for something more specific: replacing the manual processes and ageing systems your business currently works around, in stages, where each stage delivers something usable on its own.
The test we hold ourselves to is simple. Six weeks in, someone should be doing part of their job differently. If a plan cannot meet that, it is not a transformation plan — it is a procurement exercise.
What's included
The work this usually involves
Process discovery.
How the work actually happens today, documented from the people doing it rather than from the process manual, which is usually years out of date.
System inventory.
What you run, what it costs, what depends on it, who understands it, and what happens if the one person who does leaves.
Prioritisation by value and risk.
What to modernise first, based on cost, fragility and business impact — not on which system is oldest.
Data consolidation.
Establishing which system is the source of truth for each kind of record, and ending the situation where three systems hold three different versions of a customer.
Legacy replacement, in stages.
New capability built alongside the old system, migrated function by function, with both running until the new one has earned the traffic.
Process automation.
The approvals, handoffs, notifications and reports that currently consume people's days.
Integration.
Making existing systems work together instead of replacing them, which is very often the cheaper and better answer.
Self-service.
Moving what customers and staff currently do by email or phone into a portal, which reduces cost and improves the experience at the same time.
Reporting and visibility.
Giving leadership current numbers rather than a monthly reconstruction of what happened last month.
Training and change support
because the technology is rarely the hard part.
Why we do this in stages
The big-bang approach — a two-year programme, one enormous cutover — fails more often than it succeeds, and it fails expensively. Requirements agreed in year one no longer describe the business by year two. Nothing is validated until everything is finished. And the cutover concentrates all the risk into a single weekend.
Staged modernisation costs less in total and de-risks itself as it goes: each phase is funded and justified on its own, each one is proven with real users before the next begins, and you can stop at any point with something that works. It also means the organisation absorbs change at a rate it can actually handle, which is the constraint people consistently underestimate.
Legacy systems deserve respect, not contempt
The old system everyone complains about is usually running the business, and it contains years of accumulated business rules that exist because of a real problem someone hit. The most common cause of a failed replacement is a team that treated the legacy system as stupid and rebuilt it without finding out why it did what it did.
So we read it properly. We document the rules before replacing them, keep the ones that matter, and where a rule genuinely no longer applies, that decision is made and recorded deliberately rather than by omission.
Adoption is the actual deliverable
A new system that people work around is worse than the old one, because now you are running both. Where these programmes fail, it is almost never the technology — it is that nobody made it worth an employee's while to change, or the training was a single session six weeks before launch, or the new system was slower than the spreadsheet for the task someone does forty times a day.
So the people who will use it are involved from discovery onward, we phase rollout rather than switching everyone at once, we keep the old route available during the transition, and we measure adoption as a success criterion rather than assuming it. If adoption is not happening, that is a signal to fix the system, not to send another memo.
On working with Codigoo
The first thing they did was tell us to stop two campaigns we were proud of. That is when I knew they were reading the numbers and not the brief.
Questions we are usually asked
- Where do we start?
With whatever combination of highest cost and highest fragility we find — usually a manual process consuming significant staff time, or a system whose failure would stop the business. Discovery gives you that answer in weeks, with a costed plan, and it is a small fraction of what a programme costs.
- Do we have to replace everything?
Almost certainly not, and any adviser telling you otherwise is selling scope. Plenty of older systems work perfectly well for what they do and simply need to be connected to the rest of your operation. Integration first, replacement only where it is genuinely justified, is usually the correct sequence.
- How do we handle staff resistance?
By taking it seriously as information rather than treating it as an obstacle. Resistance is usually rational: the new system is slower for their actual task, or it removes a workaround they depend on, or nobody explained what happens to their role. Involving them early and fixing the real complaints converts the loudest resisters into the people who make it work — and it is cheaper than any change-management campaign.
- What does this cost?
Phase by phase, so it is a series of decisions rather than one commitment. Discovery produces a costed roadmap with each phase priced and justified on its own value, and you approve them individually.
If your business runs on processes nobody would design today, a consultation is where to find out which one is costing you the most.
Talk to us about Digital Transformation
Thirty minutes with an engineer and a strategist who do this work — not a sales team. You will get an honest answer about whether it is the right thing to buy, and what it would realistically cost.