Digital Transformation
I help established businesses connect systems that don't talk to each other, automate manual handoffs, and modernize software that has become risky to change — delivered in phases, so operations keep running throughout. 8+ years, 200+ projects across 15+ industries.
No strategy deck, no eighteen-month programme. We start with an assessment, fix the most expensive problem first, and prove it before going further.
30 minutes. You'll leave knowing where your biggest operational cost is hiding.
The problem
Most businesses at this stage don't have a broken system. They have five working systems and no connections between them — so people become the integration layer. Every gap is filled by someone re-typing, exporting, checking or chasing.
Where the cost actually sits
| Symptom | What it's really costing |
|---|---|
| The same data entered into two or three systems | Staff hours, plus errors that surface weeks later |
| Month-end reporting built by hand from exports | Days of senior time, and decisions made on stale numbers |
| Nobody agrees on which system has the correct figure | Reconciliation work, and slow decisions |
| Approvals chased over WhatsApp and email | Delays that customers feel directly |
| A critical process depends on one person's spreadsheet | Genuine business risk when that person leaves |
| Software nobody will touch because it might break | Features you can't add and customers you can't serve |
None of this shows up as a cost line. It shows up as "we're busy", as things taking longer than they used to, and as good people spending their week on admin. That's why it survives for years without anyone deciding to keep it.
Transformation is the wrong word for most of these problems. Usually three or four specific fixes remove most of the cost, and the rest of the systems can be left exactly as they are. I'd rather scope the small version and prove it than sell you a programme.
Recognise your business in this table? The systems review shows where the biggest cost sits.
Book a Free Systems Review →Definition
Digital transformation means changing how work moves through your business by connecting your systems, automating manual handoffs, and replacing processes that depend on someone remembering to do them. It is not buying new software. It is removing the gaps between the software you already have.
What it looks like in practice
What it is not
| Not this | But this |
|---|---|
| A strategy document and a roadmap slide | Working systems, delivered in phases |
| Replacing everything at once | Fixing the most expensive gap first, then reassessing |
| A new platform your team has to learn | Connections between tools they already use |
| An eighteen-month programme | A first phase delivered in 4 to 8 weeks |
| Consultants who hand over and leave | The person who assessed it also builds it |
If that sounds closer to what you need than what you've been quoted elsewhere, let's talk.
Book a Free Systems Review →What I deliver
Most engagements use two or three of these. Very few need all five.
Connecting the tools you already run — CRM, accounting, inventory, ecommerce, HR, project management — so information moves between them automatically instead of through a person.
This is usually the first phase, because it removes the most hours for the least disruption. Nothing is replaced; the gaps are simply closed.
Taking the sequences your team performs by hand — approvals, onboarding, order processing, reporting, renewals — and making them run on their own, with people involved only where judgement is genuinely required.
Dealing with software that still works but has become dangerous to change: no documentation, an original developer who left, a technology nobody in the market uses any more.
The approach is incremental. New capability is built alongside the old system and traffic moves across gradually, rather than switching everything on a single date.
Bringing the numbers scattered across systems into one place so reporting is automatic and everyone is working from the same figure.
Includes the unglamorous part — reconciling records that disagree, and deciding which system is authoritative for each field.
Adding AI to the parts of the process where it genuinely helps: reading documents, classifying and routing requests, drafting responses, surfacing information people currently hunt for.
This comes last deliberately. AI layered on top of disconnected systems and unclear data produces confident nonsense. Fix the plumbing first.
Process
The entry point is deliberately small. You should be able to see whether this works before committing to anything significant.
What systems you run, where work gets stuck, and what it's costing. You'll leave with a view on where the biggest gap is, whether or not you go further.
I map how work actually moves through your business — not how the org chart says it does. I interview the people doing the work, document the handoffs, and identify where hours and errors are concentrated. Deliverable: a written assessment with the problems ranked by cost, the fix for each, an effort estimate, and a recommended sequence. It's yours to keep and act on with anyone.
We fix the single highest-cost problem from the assessment. One phase, fixed price, measurable outcome. This is where you find out whether the estimates hold.
We measure the result against the baseline from the assessment. If it delivered, we scope the next phase. If it didn't, you've spent one phase finding out rather than a programme budget.
Each phase scoped, priced and delivered on its own. You can stop after any of them, and what's been built keeps working.
There is no long-term contract. Each phase stands alone, and you own everything built in it.
Proof
[Intro line — add once the case studies are confirmed]
[NUMBER: hours removed per month, reporting time before vs after, error rate or decision speed]
[NUMBER: hours removed per month, reporting time before vs after, error rate or decision speed]
"[Quote — about the process and the lack of disruption, not the technology]"
How disruption is avoided
The reason most businesses live with bad systems for years isn't cost. It's the fear that fixing them will break something during a week when nothing can afford to break. Here's how that risk is managed.
The old process keeps running while the new one is tested against real data. Nothing is switched off until the replacement has been proven on live work, not on a demo.
Phases are scoped so that only one part of the business changes at once. If something goes wrong, it's contained to that area rather than spreading across the operation.
Each phase can be rolled back. If a change causes problems in week one, we return to the previous state while it's fixed, rather than pushing forward because there's no way back.
The people who do the work are interviewed during the assessment and see each phase before it goes live. Systems fail far more often because staff weren't consulted than because the software was wrong.
Staff are trained while the old process is still running, so nobody is learning a new system under pressure on day one.
Some disruption is unavoidable during a cutover. What's avoidable is unplanned disruption. You'll know before each phase exactly what changes, who is affected, what the fallback is, and which day it happens.
Is disruption your main concern? That's the first thing we cover on the review.
Book a Free Systems Review →FAQ
It depends entirely on scope, which is why the entry point is a fixed-fee assessment from [PRICE] rather than a quote for the whole thing. Individual phases typically run from [PRICE]. You approve each phase separately, so you're never committing to a total figure up front.
The assessment takes 1 to 2 weeks. The first phase is usually 4 to 8 weeks. After that it depends on how many areas you choose to address, and you decide that phase by phase. There is no fixed programme length, because there is no fixed programme.
Often, yes. It's been used to sell strategy documents with no working outcome. Here it means something specific: your systems get connected, your manual handoffs get automated, and you can measure the hours removed. If a deliverable can't be measured, it isn't on the proposal.
Each phase runs in parallel with the existing process until the replacement is proven on real work. Only one area changes at a time, and every phase can be rolled back. You'll know before each go-live exactly what changes, who's affected, and what the fallback is.
Usually not. Most of the value comes from connecting what you already have rather than replacing it. Replacement is only worth discussing when a system is genuinely blocking you or can no longer be safely maintained — and even then, it's done incrementally.
That's a real risk and it's why the assessment involves interviewing the people doing the work. Systems fail more often from being imposed than from being badly built. Staff see each phase before it goes live and are trained while the old process is still running.
No. Businesses with 20 to 50 staff often get the fastest payback, because a single integration can remove work for the whole team. The phased approach scales down as easily as it scales up — the first phase is the same size either way.
A written document mapping how work moves through your business, the bottlenecks ranked by what they cost, a recommended fix and effort estimate for each, and a suggested sequence. It's yours to keep and act on, with me or with anyone else.
Book your systems review
Book a free 30-minute call. Walk me through the systems you run and where work gets stuck, and I'll tell you where the biggest cost is hiding and what fixing it would involve.
What you get from the call