Gone by Thursday: The Consultant Who Saved Your Tech Strategy and Couldn't Find You on LinkedIn Afterwards

The engagement began, as these things always do, with enormous promise. They had a methodology. They had case studies — anonymised, naturally, but clearly impressive. They had a two-by-two matrix that explained your entire competitive situation in a way that seemed, in the room, to be genuinely illuminating. They wore the kind of trainers that suggested they understood startups but could also be trusted in a boardroom.

Three months and an invoice that required two signatories later, they were gone. The strategy document lives in a shared drive folder called "Consultancy 2023 — FINAL v3 ACTUAL FINAL." It has been opened twice: once during the handover call, and once by a new joiner who thought it might explain why the authentication system works the way it does. (It does not explain this.)

Welcome to the British tech consultancy experience.

The Parachute Drop

There is a recognisable rhythm to the external tech consultancy engagement, and once you've seen it, you cannot unsee it.

Week one is discovery. This involves a great many meetings in which the consultant asks questions that your team could have answered in a single email, but which feel important because they're being asked by someone external. There is a workshop. There are Post-it notes. Someone draws a customer journey on a whiteboard and photographs it. The consultant nods a great deal and writes things in a Moleskine.

Weeks two through eight are analysis and synthesis. The consultant is largely invisible during this period, which is mildly alarming if you think about the day rate. Occasionally they surface to request access to a system, or to ask whether there's anyone else they should be talking to. You suggest three people. They speak to one of them.

Week nine is the presentation. This is the main event, the thing the whole engagement has been building towards. The deck is substantial — never fewer than sixty slides, often more than a hundred. There are executive summaries, detailed findings, and a section called "Strategic Recommendations" that contains between eight and fourteen things you probably already knew, expressed in language that makes them sound new.

Week ten is handover and close-out. There is a final meeting. Everyone agrees it's been a really valuable process. The consultant mentions that they have capacity for a follow-on engagement focused on implementation support. You say you'll be in touch. You will not be in touch.

Then they're gone.

The Accountability Vacuum

Here's the thing about consulting recommendations: they exist in a peculiar temporal bubble. They are produced at a specific moment, based on the information available at that moment, and they carry an implicit assumption that someone else will figure out how to act on them in the context of everything that happens afterwards.

This is not, in itself, unreasonable. Consultants are not employees. They cannot be expected to stay and see it through. But the gap between "strategic recommendation" and "working software" is vast, and it is a gap that the junior developers, the mid-level engineers, and the long-suffering tech leads are left to cross on their own.

What they find, when they open the deck and try to translate vision into implementation, is that the recommendations have a tendency to dissolve on contact with reality. The proposed architecture assumes a level of engineering resource the team doesn't have. The technology choices were made without reference to the existing stack. The timeline was constructed by someone who has never had to get a change request approved by a risk committee.

Nobody rings the consultant to point this out, partly because the engagement is closed, partly because the budget is spent, and partly because there's a lingering suspicion in British professional culture that admitting the strategy isn't working means admitting you paid a lot of money for something that isn't working, which is not a conversation anyone wants to have.

Why We Keep Doing It

The persistent popularity of tech consultancy in Britain, despite this well-documented pattern, is not straightforwardly irrational. There are real reasons organisations reach for external expertise, and some of them are even good ones.

External validation carries weight in organisations where internal voices have been ignored. Sometimes it takes someone with an impressive firm name on their email signature to say "your authentication system is a liability" before the board will fund fixing it, even though the lead developer has been saying exactly that for two years. The consultant, in this reading, is not really being paid for their insight. They're being paid for their credibility as a messenger.

There's also the question of political cover. A failed internal initiative is someone's fault. A failed consultancy recommendation is a shared misfortune. The deck exists. The process was followed. Nobody can be blamed for trying.

And occasionally — genuinely, honestly occasionally — the consultant is excellent. They bring a perspective that genuinely couldn't have come from inside the organisation. They identify a structural problem that was invisible to the people living inside it. They leave behind something that actually gets built and actually works.

But the incentive structure of the industry does not consistently produce this outcome, and the absence of any mechanism for accountability means there's no particular pressure to improve.

What Happens to the Deck

The shared drive folder is worth dwelling on for a moment, because it is where strategic visions go to stop being strategic visions and become historical artefacts.

British tech companies accumulate these documents with the quiet resignation of a loft filling up with things you're definitely going to sort through one day. There's the digital transformation roadmap from 2019. There's the API strategy from 2021 that recommended a technology that turned out to be deprecated six months later. There's the organisational design review that proposed a restructuring which was partially implemented, then partially reversed, and is now partially forgotten.

Each of these documents cost real money. Each of them represented, at the moment of commissioning, a genuine attempt to solve a genuine problem. Each of them is now a curiosity at best and a liability at worst — because the recommendations they contain are not labelled with the assumptions that underpinned them, and those assumptions have mostly stopped being true.

A Better Beermat

The consultancy problem is not, ultimately, about consultants. It's about how organisations define what they're buying. A strategy document is not a deliverable. A working system is a deliverable. A team that understands why it's building what it's building is a deliverable. A set of decisions that can be explained, tested, and revised as circumstances change is a deliverable.

Before you commission the next engagement, try this: write down, on something small, what success looks like six months after the consultant has left. Not what the deck will contain. What will actually be different. If you can't write it down in a few sentences, you haven't defined the problem well enough for anyone — internal or external — to solve it.

The consultant might still leave on Thursday. But at least you'll know what you were hoping they'd leave behind.