“Digital transformation” has become a phrase that means whatever the vendor selling it needs it to mean. In practice it usually describes a purchase: a new platform, a suite of tools, a migration. The old spreadsheet becomes a new dashboard. The old email thread becomes a new ticketing system. A great deal changes on screen and surprisingly little changes in how the business works.
The reason is that the programme transformed the tools and not the process. The enquiry still waits for someone to notice it. The job still has to be re-entered when it becomes an invoice. The report still has to be assembled by hand from four places. The business is running the same operation it always ran, on more expensive software.
What actually transforms a business
Watch a business that has genuinely changed how it operates and the visible part is small. The customer record is in one place and every tool reads from it. When one stage completes, the next starts without anyone typing. The owner can see the state of the business by looking at the system, rather than asking three people. Nobody keeps a parallel spreadsheet because the official record can be trusted.
None of that comes from a platform. It comes from connecting the processes the business already runs so that information flows between them automatically. That is plumbing: unglamorous, specific to this business, and the entire point.
The tools were never the problem. The gaps between them were.
Why programmes buy tools instead
Tools are easy to buy, easy to demonstrate, and easy to put on a slide. Plumbing is none of those things. It requires understanding how the business actually works, which is slower than reading a feature list. It produces no launch moment. And it is different for every company, which means nobody can sell it in a box.
So programmes default to the purchasable part. A new CRM arrives, and with it a project to move the data, train the staff and configure the fields. Six months later the CRM is live, the old problems have moved into it, and the transformation is declared complete because the budget is spent.
The tell is what people do the week after go-live. If they are still keeping the old spreadsheet “just in case”, still forwarding emails to make sure someone sees them, still assembling the Monday report by hand, nothing has transformed. The tool changed. The operation did not.
The plumbing-first approach
A transformation that starts with plumbing looks different from the first week.
- Map the transitions, not the tools. Where does work change hands? Where is information re-entered? Where does a customer wait while the business talks to itself? Those are the targets.
- Establish the record. One source of truth for the customer, the job and the money. Every tool either reads from it or is retired.
- Connect before replacing. A tool that works but is disconnected can often be wired into the record rather than thrown away. Replacement is the last resort, not the first move.
- Automate the handoffs. Each transition that can happen without a person, happens without a person. The remaining ones land in one queue with everything attached.
- Measure by hours, not by go-lives. The programme has succeeded when the business spends fewer hours moving information and more hours using it.
Where the new tools fit
This is not an argument against modern software. Models that read and draft, services that handle payments and scheduling, and platforms that do one thing well are all worth having. The point is the order. Connected plumbing turns each of those into leverage, because whatever they produce flows into the operation. Disconnected, each is one more place to copy from.
The honest definition
A business has been transformed when its processes run as a system rather than as a set of people remembering things. That can involve new tools. It always involves plumbing. The programmes that skip it end up where they started, with a fresh coat of software over the same leaks, and a budget line that says “transformation” next to a business that still works the way it did.