Sit across from enough mid-market operators and you learn to brace for one word. A board, a firm, a new CIO has sold them "digital transformation," and it lands the way it always lands: a seven-figure number, a program with no edges, and a quiet dread that nobody can say what they'll actually get for it.
The tell is that no one in the room can define done. Ask what "transformed" looks like and you get adjectives — modern, integrated, data-driven — never numbers. The sharpest operators skip the dread and just call it what it is. They're right. A word you can't measure is a word someone can bill against forever.
The pattern underneath
"Transformation" isn't a strategy. It's a container, deliberately open at the top — because an open container is what a billable program needs. The looser the outcome, the longer the meter runs. I've watched the same sequence for twenty-four years. You buy a word. The word resists measurement. So the work drifts into discovery, workshops, a current-state slide everyone nods at and nobody believes. Months in, the first honest question finally surfaces — what does this system actually do today? — and no one can answer it. The estimate was built on a system nobody mapped. It lands 3x off, and the binder goes on a shelf.
A word you can't measure is a word someone can bill against forever.
Strip the word and the fog clears. Real transformation was never a category you buy. It's two numbers moving in opposite directions: the cost to operate, down — and the multiple at exit, up. Buy low. Sell high. Everything sold to you in the space between those two is the tax.
Buy low is not "buy more software." It's the reverse — consolidate the stack, automate the manual leaks, strip the admin nobody defends, drop the baseline cost of running the place. Sell high is not a prettier dashboard. A clean, consolidated, data-anchored operation is a higher multiple, because a buyer doesn't pay for your workflow. They pay for operational trust — the confidence the numbers survive diligence.
None of it needs a new category. It needs refusing the old one. The work I care about starts where the program-sellers skip: an honest map of what's really running — not the architecture diagram from 2019, the thing in production with the undocumented jobs and the integration built for a customer who churned two years ago. You can't move two numbers on a system you can't see. Read what's there first; then wrap it, rebuild it, or something between becomes a decision instead of a guess.
I don't sell the word. I move the two numbers, and I leave the system running on your team's side. That's the whole category, spelled honestly.
The fastest way in is to point at the leak you feel — at whatmovesit. You'll get the honest read: what it is, whether software actually fixes it, and how far it moves.
Point at your leak