Every stalled transformation I've seen got the sequence wrong, building inside-out. Here's the single question that tells you which direction you should be going.
Every digital transformation I've seen stall in the last five years has had one thing in common. It wasn't budget. It wasn't technology. It wasn't even a lack of executive support - at least not at the start.
It was sequence.
The firm started in the wrong place. And by the time anyone noticed, they'd spent six to twelve months building something that was technically sound, operationally sensible, and completely invisible to the people who actually pay the bills.
I get why it happens. If you're a managing partner or a marketing leader at a mid-sized professional services firm, and someone says "digital transformation," the instinct is to look inward first. The CRM is a mess. The intranet hasn't been touched since 2019. Finance is running on spreadsheets that would make a first-year analyst wince. Three systems don't talk to each other, and the workaround involves someone called Dave who's been manually exporting CSVs every Thursday for four years.
So you start there. You fix the plumbing. You rationalise the tech stack. You spend eight months migrating to a new CRM, another three months getting people to actually use it, and then you resurface and ask: "Right, what's next?"
The answer is usually: the website still looks like it was built in 2018 (because it was), your clients are still filling in PDF forms and emailing them back, and your competitors have quietly rebuilt their entire client-facing experience while you were sorting out your internal data model.
We need to sort out our internal systems before we can improve the client experience. You can't build on weak foundations.
I hear this constantly. And honestly? It sounds completely reasonable. It's the kind of thing a sensible, diligent leader says. The problem isn't the logic - it's the assumption buried inside it. The assumption that internal systems need to be finished before external experience can begin. That assumption will quietly eat two years of your roadmap.
Starting outside-in doesn't mean ignoring your internal systems. It means beginning your transformation with a different question. Instead of "what's broken internally?" you ask "what does our client actually experience when they interact with us digitally?"
That question tends to produce some uncomfortable answers.
I was working with a mid-market management consulting firm last year - about 150 people, strong reputation in operational transformation, built almost entirely on referrals. The partners were convinced their digital priority was a new knowledge management system. Internal teams were frustrated, documents were hard to find, onboarding new consultants took too long. All legitimate problems.
But when we actually looked at their client-facing digital experience, it was dire. Their website generated fewer than three enquiries a month. Prospects who'd been referred to the firm were landing on the site and seeing nothing that matched the quality of the conversations they'd had over dinner. The firm had 40-plus published thought leadership pieces - frameworks, research papers, the kind of thing that takes senior consultants weeks to produce - and they were essentially invisible online. No structure, no taxonomy, no way for a prospect to find them unless they already knew to look.
I remember sitting in a partners' meeting going through the traffic data. One of the senior partners - someone who'd spent twenty years building a reputation in his field - looked at the screen and said, quietly, "So nobody's reading any of it." That was the moment the conversation shifted.
We started with the thing clients could see and feel. Built a content platform structured around how prospects actually evaluate firms like this one - open articles, gated deeper resources, a CRM integration that meant the marketing team could see which companies were reading what. Within six months, inbound enquiries had gone from three a month to thirteen-plus. Within twelve months, 18% of net new revenue was attributable to the website.
The knowledge management system? Still on the roadmap. But now there's commercial momentum funding it, and a leadership team that's seen what "starting with the client" actually produces.
I'm not going to pretend outside-in is always the right starting point. Sometimes the internal foundations genuinely are so broken that you can't deliver a credible client experience on top of them.
I've seen this firsthand. A financial services firm we worked with had a client portal where 40% of applications contained errors - not because the clients were careless, but because the underlying system forced brokers through a workflow designed for internal processing, not for the person actually using it. You couldn't just put a nice frontend on that. The plumbing was actively creating the problem.
So how do you tell the difference? Here's the honest diagnostic:
If your internal system is causing a client-facing problem - errors, delays, data loss, compliance risk - fix it first. That's not inside-out transformation, that's triage.
If your internal system is merely inconvenient for your team while your client experience is silently losing you business? That's a sequencing choice. And the right sequence is the one that produces something your clients notice.
Most firms, if they're being really honest with themselves, are in the second camp. The internal systems are annoying, not catastrophic. The client experience is where the commercial damage is compounding.
I'll also admit I've got this wrong before. Early in my career I convinced a professional services firm to start with a full CRM overhaul before touching anything client-facing. The logic was sound. The execution was fine. And eighteen months later, the partners were asking why nothing felt different. The clients hadn't noticed a thing. We'd built a very tidy engine room for a ship that was still losing passengers off the side. I wouldn't make that call the same way now.
The approach I'd recommend for most firms - and this is what we use at Distinction through our WHNN framework - is what I'd call "minimum viable foundation, then outside-in for everything else."
Spend the first phase identifying the genuine internal blockers. Not the wish list - the actual things that would prevent you from improving the client experience. Maybe it's a data integration that doesn't exist. Maybe it's a permissions model that means your marketing team can't publish without raising a developer ticket. Maybe it's a single API connection that needs building. Fix those. Quickly. In weeks, not months.
Then shift everything else to outside-in. Rebuild the client journey. Fix the website. Sort out the portal. Make the onboarding experience something you'd actually be proud to walk a new client through.
The reason this works isn't just commercial, though the commercial case is strong. It's psychological. When the first phase of a transformation produces something visible - something a client comments on, something a partner can point to in a pitch - it creates momentum. People believe in the programme. The board sees returns. Budget for the next phase gets approved without a fight.
When the first phase produces a new CRM that the internal team is still learning to use? You get a very different board conversation. One that usually starts with "remind me what we spent on that?"
The inside-out versus outside-in question isn't a technical decision. It's a strategic one. It determines whether your digital investment produces commercial returns or just operational tidiness. Both matter. But one pays for the other.
And if you're sitting there thinking right, but our situation is genuinely complex - we have legacy systems and regulatory requirements and a board that wants to see infrastructure investment - I get it. I've been in that exact conversation dozens of times. The complexity is real. But complexity isn't an argument for starting internally. It's an argument for being more deliberate about sequencing.
The firms I see getting this right aren't the ones with the biggest budgets. They're the ones who asked a simple question at the start: "Will our clients notice?"
If the answer is no, you're probably building in the wrong direction.
I've written separately about how to diagnose whether your client experience is actually costing you business - understanding that gap is where the outside-in approach begins. And if you've decided which direction to take, here's how to scope the first phase.