Pick any client your firm has lost in the past two years. Not the ones where the relationship ended cleanly because the work was done. The ones that stung. The ones where the partner said something like "I don't really know what happened - they just didn't renew" or "they moved to a firm that frankly isn't as good as us."
Now trace the experience that client actually had with you. Not the experience the partner thinks they had. The real one. Starting from whatever first brought them to your website, through the proposal process, onboarding, the work itself, invoicing, and every interaction in between.
I'd bet good money that the reason they left wasn't one catastrophic failure. It was a dozen small ones. An enquiry form that took three days to get a response because it sat in a shared inbox nobody monitored. An onboarding process that asked them for the same information twice because your CRM doesn't talk to your project management tool. An invoice format so confusing that their finance team called yours every single month. A partner who delivered excellent advice but whose team sent status updates in a PDF attached to an email with no subject line.
Each of those failures belongs to a different team. And that's exactly the problem.
Most mid-market professional services firms have someone who "owns" client experience. Usually it's marketing. Sometimes it's a hybrid role - Head of Client Experience, or Director of Digital - that reports into marketing or operations. Occasionally it's IT, because someone decided that "experience" was really about the technology.
We have a marketing team that handles the digital experience. That's their job.
I hear this constantly, and I want to push back on it - not because your marketing team isn't doing good work, but because the framing itself guarantees the outcome you're trying to avoid. When you assign client experience to one function, you're essentially saying that the quality of a client's entire relationship with your firm is the responsibility of the team that controls the website and maybe the CRM. Meanwhile, the decisions that actually shape that experience - how fast proposals go out, what the onboarding workflow looks like, whether invoices are comprehensible, how knowledge gets shared between teams when a client's needs change - are being made by operations, finance, practice management, and IT, none of whom think of themselves as being in the experience business.
This isn't a people problem. It's a structural one. And I think the distinction matters, because blaming individuals doesn't fix anything. Most firms have organised themselves around functions - what we do internally - rather than journeys, which is what the client actually goes through. Every function optimises for its own efficiency, which makes total sense from the inside. Finance wants clean processes and timely payments. Operations wants predictable workflows. IT wants stable systems. But the client doesn't experience your functions. They experience the seams between them. And the seams are where everything falls apart.
I was talking to the COO of a 250-person consulting firm a few months back. Sharp operator, deeply committed to the firm's growth, had just invested in a new client portal. He was frustrated because client satisfaction scores hadn't moved despite the investment. "We've given them a better digital experience," he said. "What more do they want?"
So we dug in. The portal was genuinely good - clean, fast, well-designed. But the onboarding process that fed into it was still manual and inconsistent. Different practice groups collected different information at different times. Some clients were set up within a day; others waited a week. The portal showed project status, but the data behind it was updated by hand, so it was often two or three days behind reality. Clients were logging in, seeing stale information, and concluding that the firm wasn't on top of things. The portal was a window into a messy room.
His investment in digital experience was being undermined by operational decisions that nobody had thought of as experience decisions. That's the pattern I see over and over again.
Finance decides to change the invoicing cycle from monthly to quarterly because it's more efficient internally. Nobody asks what that does to the client's cash flow planning or their perception of transparency. Operations standardises a handoff process between the sales team and the delivery team, but the standardisation means the client has to re-explain their situation to the new team because the briefing document doesn't capture context. IT upgrades the email system and the auto-reply templates reset to something generic and slightly robotic. None of these teams are trying to make the experience worse. They're trying to make their own bit work better. But the cumulative effect on the client is death by a thousand well-intentioned cuts.
Here's one I find particularly telling. A mid-market law firm we worked with had a genuinely excellent commercial real estate practice. Partners were well-regarded, client retention was strong within ongoing matters. But they kept losing clients between matters - the gap between one piece of work ending and the next one starting. When we looked at it, the issue was simple and maddening. When a matter closed, the file got archived, the billing got finalised, and... nothing. No follow-up. No check-in. No "how are things going with the property you just acquired?" The CRM had no trigger for post-matter engagement because it had been set up around matter management, not relationship management. A technology decision, made by IT, that created a relationship gap, felt by the client, blamed on the partners.
Whenever I talk about cross-functional ownership of client experience, someone in the room gets nervous. Usually it's the person who's been through a "cross-functional transformation initiative" that produced a steering committee, a set of principles nobody read, and a quarterly meeting that everyone dreaded.
I'm not talking about that. God, no.
So what does it actually look like? Three things, and they're all practical.
The first is shared metrics. Right now, your marketing team probably measures website traffic and enquiry volume. Operations measures utilisation and project delivery. Finance measures revenue and cash collection. Each function is optimising for its own numbers, and none of those numbers capture the experience that sits between them. What if your monthly leadership meeting included two or three metrics that crossed functional boundaries? Something like time-from-enquiry-to-first-meaningful-response, which spans marketing, practice management, and the partner who actually picks up the phone. Or client effort score during onboarding, which spans operations, IT, and whatever poor soul is manually creating logins. Or post-matter re-engagement rate, which spans practice management, CRM, and business development. These aren't vanity metrics. They're the joints in the skeleton. When they work, the body moves smoothly. When they don't, you limp.
The second is named accountabilities for handoff points. Not for entire journeys - that's too abstract. But for the specific moments where a client passes from one team's domain to another's. Who is accountable for what happens when a new enquiry comes in and needs to be routed to the right partner? Not "marketing does it" - who specifically, and what's the SLA? Who is accountable for the quality of the brief when a client moves from sales to delivery? What information must be transferred, in what format, and who checks it happened? A financial services firm we worked with reduced client complaints by about 30% in a single quarter just by naming one person accountable for each of four handoff points and giving them a one-page checklist. No new technology. No restructuring. Just clarity about who owned the seams.
The third is the one people resist most. A standing 45-minute session, once a month, where someone from each function shares what they're seeing from their vantage point. Marketing says "we're getting a spike in enquiries about X but the response time is lagging." Operations says "we changed the onboarding form and it's created confusion." Finance says "clients are querying this new invoice format." IT says "the portal uptime was rough last week." No agenda beyond: what are clients experiencing right now, and what's causing friction? This costs you 45 minutes a month. The insight it generates is staggering, because most of the time, no one in the room knew what the other teams were dealing with. The problems are obvious once they're visible. They're just never visible, because everyone's looking at their own bit.
This sounds like more process. We're a mid-market firm, not a FTSE 100. We don't have the bandwidth for governance frameworks.
Fair. And honestly, I'm sympathetic - I've seen plenty of firms suffocate good ideas under layers of governance. But what I'm describing isn't bureaucratic. A shared dashboard with three cross-functional metrics, named owners for four or five handoff points, and a monthly 45-minute conversation is basic operational hygiene. You probably spend more time than that each month discussing the office Christmas party.
The real resistance, in my experience, isn't about bandwidth. It's about territory. Functions don't want to be held accountable for outcomes they can't fully control. Finance doesn't want to be measured on client satisfaction when they're just sending the invoices they've been told to send. IT doesn't want to be blamed for portal problems when the data feeding the portal comes from operations. And partners definitely don't want anyone suggesting that their client management could be improved.
All of which is understandable. But the client doesn't care about your org chart.
At Distinction, we've seen this play out dozens of times across the 170-plus projects we've delivered. The firms that get this right aren't the ones with the most sophisticated technology or the biggest CX budgets. They're the ones where leadership has made it clear that client experience is a shared outcome, not a departmental responsibility - and backed that up with visible, simple mechanisms that make the invisible visible.
Let me connect this back to money, because that's what gets things moving in a partnership.
I sat with a managing partner last year who told me, quite candidly, that his firm's client satisfaction scores had been flat for three years despite investing meaningfully in their website, their portal, and their CRM. "We've done everything the consultants told us to do," he said. And he wasn't wrong - each individual initiative had been well-executed. The website generated enquiries that took too long to reach the right partner. The portal displayed information that was entered inconsistently by different practice groups. The CRM tracked matters but not relationships. Three good investments, producing mediocre outcomes, because nobody was looking at the joins.
That's the tax you pay for treating experience as one team's job. Not a dramatic failure. Just a persistent, quietly expensive underperformance that's hard to diagnose because each function's metrics look fine in isolation. Forrester's research puts it starkly: CX leaders outperform laggards by nearly 80% in customer retention. And if you've read our guide on The Customer Experience Dividend, you'll know the firms that treat every client interaction as an investment opportunity - rather than an operational cost - are seeing meaningful revenue growth and satisfaction lifts as a result. But those gains don't come from marketing doing a better job with the website. They come from the whole firm operating differently.
Better experience benefits every function. Marketing gets better conversion because response times improve. Operations gets fewer complaints and less rework because onboarding is consistent. Finance gets better retention - and retention is dramatically cheaper than acquisition. Partners get clients who actively refer, rather than clients who merely tolerate. Everyone wins. But only if everyone's involved.
If you've read this far and you're thinking "right, but what do I actually do on Monday morning?" - here's what I'd suggest.
Pick one client journey. Not all of them. One. Probably new client onboarding, because it crosses the most functional boundaries and the friction is usually most visible there. Map it - not theoretically, but actually walk through what happens, step by step, from the moment someone submits an enquiry to the moment they're a fully set-up, active client. Get someone from marketing, operations, finance, and IT in the room. Ask each of them to describe what happens from their perspective.
I promise you, within twenty minutes, someone will say "wait, is that what happens after I hand it over?" Because they've never seen it from the other side. The experience gaps aren't hidden. They're just invisible to any single function.
Then identify the two or three worst handoff points and name an owner for each one. Simple brief: make this handoff smoother for the client within 90 days. No committee. No transformation programme. Just fix the seams.
If you want a more structured starting point, our Customer Experience Dividend scorecard takes about ten minutes and tends to surface the gaps between what leadership thinks is happening and what's actually happening. Which, come to think of it, is kind of the whole point.
If you're a managing partner or COO reading this, the experience your clients have with your firm is a reflection of how well your leadership team works together across functions. Not how good your marketing team is. Not how modern your technology is. Those things matter - but they're ingredients, not the meal.
The firms I've seen genuinely shift their client experience didn't start with a technology project or a rebrand. They started with a conversation - usually an awkward one - about who actually owns the client relationship end-to-end and what happens in the gaps between teams. Then they did something about it. Not a massive restructuring. Not a six-month initiative. Usually just a handful of practical changes that made the invisible visible and gave people permission to care about things that weren't technically their department's problem.
Your client experience is everyone's problem. The question is whether you've made it everyone's job.