"We need a new website."
Four words. And probably the most expensive sentence in B2B professional services.
I'm not saying it's always wrong, sometimes you genuinely do need one. But in about seven out of ten conversations I've had with managing partners, COOs, and marketing directors over the past couple of years, "we need a new website" turns out to be a conclusion someone jumped to before they'd actually diagnosed the problem. The gap between that premature conclusion and what's really going on underneath? That's where firms burn £200k, £400k, sometimes more - on a shiny new platform that solves precisely nothing.
A COO at a 400-person professional services firm rang us a few months back. She'd been quoted over £400,000 for a full website and CRM rebuild. Big scope. New design, new platform, new integrations, the works. She called because something didn't feel right - not the quote itself, but the whole premise. She couldn't actually articulate what the current website was failing to do. She just knew it "wasn't good enough."
So we ran a 14-day assessment. Turns out roughly 60% of the original brief was unnecessary. The real problem wasn't the design or the CMS. It was a broken handoff between the enquiry form and the onboarding process - leads were coming in and dying in a spreadsheet somewhere between marketing and client services. We fixed that first. Ninety-day sprint, about £80k. Within three months, enquiry-to-client conversion improved by 22%.
She nearly spent £400,000 solving the wrong problem. And honestly, she's won't be the last.
The pattern goes like this. Someone in the firm - a partner, the head of marketing, a board member who just saw a competitor's new website - says "we need a new website." Because that person has authority, the statement gets accepted as a brief. It becomes the starting point for vendor conversations, budget requests, project scoping. Nobody stops to ask what should be the first question: what problem are we actually trying to solve?
"We need a new website" is a solution. And once you've committed to a solution, everything that follows gets shaped by that commitment. You start evaluating CMS platforms before you've worked out what your content needs to do. You brief designers before you've mapped the customer journey. You start building before you've diagnosed.
It's like walking into a doctor's surgery and saying "I need surgery." The doctor would - hopefully - ask a few questions first. Where does it hurt? How long has this been going on? Have you tried anything else? They wouldn't just book you in for an operation because you arrived with conviction.
But in the world of digital investment, we do this constantly. And the reason is understandable.
We know we need a new website. Why do we need to complicate things with a "problem definition" exercise?
I get it. When something feels broken, the instinct is to fix it - and "fix it" usually means "replace it." That instinct isn't wrong, exactly. It's just premature. The urge to do something is healthy. The urge to jump straight to the biggest, most visible something is where things go sideways.
Solutions are tangible. A new website is something you can picture, budget for, and put a timeline against. A problem definition exercise sounds... vague. Abstract. Like consultants creating work for themselves.
I remember sitting in a boardroom - must have been two years ago now - trying to convince a group of partners at a mid-sized consulting firm that they should spend three weeks understanding their problem before spending six months building a solution. One of the senior partners said to me: "James, we're paying you to do things, not to think about things." I laughed, because he was being funny. But he also meant it. There's an impatience in professional services that I honestly respect - these are people who bill by the hour, who've built careers on getting things done.
Getting the wrong thing done quickly is not progress. It's expensive motion.
And here's something I should be honest about. Early in Distinction's history - fifteen, maybe eighteen years ago - we were guilty of this too. A client would come to us and say "we need a new website" and we'd say "great, let's build you one." We were a digital agency. Building websites was what we did. Why would we talk them out of it?
Because sometimes the website wasn't the problem. When you build a beautiful new website on top of a broken process, or a confused value proposition, or a content strategy that doesn't exist, you end up with a beautiful new website that doesn't perform. The client blames the website. Or worse, they blame themselves. And the whole cycle starts again in three years.
We've seen it enough times that it stopped being surprising. Which is a bit depressing, actually.
Right, so if "we need a new website" isn't a good starting point, what is?
Start with what's actually going wrong. Not what feels wrong - what you can measure, observe, or hear directly from the people who matter. There are four lenses I'd suggest, and none of them require a six-month research programme.
Client feedback. Not the sanitised version from your annual survey. The real stuff - what clients say when they ring up confused, what questions your BD team keeps fielding that the website should be answering, what the prospect said in that debrief after you lost the pitch. One law firm we worked with discovered that prospective clients were landing on the website, struggling to work out which practice area handled their issue, and picking up the phone to a competitor instead. That's not a design problem. It's an information architecture problem. The fix was a two-sprint restructure, not a full rebuild.
Operational data. Where are things getting stuck internally? Is the marketing team spending three days to publish a blog post because the CMS is hostile? Are enquiries sitting in someone's inbox for 48 hours before they get routed? Is the sales team building proposals from scratch every time because there's no content library? These are process problems that can look like technology problems if you squint - but they're fundamentally different beasts.
Competitive benchmarking. And I don't mean "their website looks nicer than ours." I mean: what are competitors doing that's generating results? Are they publishing thought leadership that's ranking? Have they built self-service tools that reduce friction? Are their conversion paths shorter? This isn't about copying - it's about understanding what good looks like in your market.
Conversion analysis. If your website gets 30,000 visits a month and generates four enquiries, something is broken. But where is it broken? Are people landing and immediately bouncing? Reading three pages and then leaving? Starting the contact form and abandoning it? Each of those failure points implies a completely different fix. A bounce rate problem might be a messaging problem. Form abandonment might be a UX problem. High traffic, low conversion might be a targeting problem. None of them necessarily require a new website.
We worked with a top-50 UK law firm - 30,000+ monthly visitors, fewer than 4% of new client enquiries coming through the site. The partners assumed they needed a new website. When we looked at the data, the traffic was healthy, the content was decent, but the site had essentially zero conversion paths. No clear calls to action, no structured journeys from "I'm interested" to "I'd like to talk to someone." We restructured the existing site around buyer intent and built enquiry paths that actually worked. Six months later, qualified enquiries were up 67%.
No new website required.
This is the bit that makes people uncomfortable, so let me just say it plainly: sometimes the problem is your proposition. Sometimes it's your pricing. Sometimes it's that your best people are invisible online and your weakest people are the ones prospects meet first. Sometimes your competitors have simply got better and your market position has shifted underneath you while you were busy delivering client work.
A new website won't fix any of those things. It'll dress them up, temporarily.
I worked with a 120-person MSP a while back - they'd been quoted £220k for a full rebrand and website rebuild. The MD brought us in for an independent view before committing. Our 14-day assessment found that the real problem wasn't design. The firm had evolved from break-fix IT support into a serious managed security and cloud services provider, but the website still presented them as a generalist IT company. Bit like a barrister handing out business cards that say "odd jobs." We recommended a two-sprint approach at about a third of the original quote: restructure around buyer personas, rewrite service pages around business problems, build sector-specific landing pages. No rebrand, no platform migration. Within seven months, qualified marketing leads had tripled and three prospects who'd previously gone elsewhere came back.
The point isn't that websites don't matter. Of course they do - I run a consultancy that builds them. The point is that a website is a vehicle for something, and if you don't know what that something is, the vehicle is irrelevant. It's like buying a lorry when you haven't decided what you're shipping.
You might read all of this and think "yes, that makes sense, we should diagnose before we prescribe." Then you walk into the partners' meeting and someone says "I just saw [competitor]'s new website and it makes us look amateur" and suddenly the pressure is on to do something visible, quickly.
I've been in that room. Multiple times. It's hard to hold the line. The person who says "let's take three weeks to understand the problem" sounds cautious. The person who says "let's brief an agency and get moving" sounds decisive. In most professional services cultures, decisive wins.
A few things that help, for what it's worth.
Frame the diagnostic work as risk reduction. You're not slowing things down - you're making sure you don't waste money. That COO I mentioned earlier nearly spent £320k on work she didn't need. The 14-day assessment cost a fraction of that. Frame it in those terms and suddenly the cautious option looks like the smart one.
Put a time box on it. "Let's spend two weeks understanding what's actually wrong before we commit to six months of build" is a much easier sell than "let's do some research." Two weeks. That's it. If the answer turns out to be "yes, we do need a new website," you've lost a fortnight. If the answer is "actually, the problem is somewhere else entirely," you've potentially saved the firm hundreds of thousands of pounds.
And - this one requires a bit of backbone - be willing to present findings that contradict the brief. We've done this more times than I can count. A firm comes to us saying "we need X" and our assessment says "you actually need Y." Not a comfortable conversation. But it's the right one. The firms that listen are the ones that get the best outcomes. The ones that don't... well, they usually come back in three years with the same problem and a different website.
At Distinction, we've built our whole approach around this. Our WHNN framework - The What and the How, for the Now and the Next - is fundamentally a problem-first methodology. Before we talk about what to build or how to build it, we get clear on where the organisation is now and where it needs to be. The gap between those two things defines the problem. Only then do we work on the What and the How.
It sounds almost obvious when I say it like that. But the discipline of staying in the problem space long enough to actually understand it is genuinely rare. The gravitational pull of solutions is strong - everyone wants to talk about platforms, designs, features. Nobody wants to sit with the uncomfortable question of "what's actually going wrong here and why?"
That question is where the value is. Every time.
If you're reading this thinking about your own firm's digital presence - a website that feels tired, a portal that frustrates clients, a platform your team has been working around rather than with - resist the urge to start with the solution. Just for a moment.
Ask the diagnostic questions first. Where are you actually losing clients, enquiries, or efficiency? What does the data say? What are your clients telling you - not in the formal survey, but in the offhand comments and the frustrated phone calls? Where are the bottlenecks you've normalised because they've been there so long?
The answers might point to a new website. They might point to a CMS migration, a content restructure, a process fix, or something else entirely. But whatever they point to, you'll know you're solving the right problem.
If you're not sure where to start with that diagnostic process, we've built a scorecard - The Fragility of Digital Foundations - that helps you benchmark where your platform actually stands. It won't tell you everything, but it'll surface the questions worth asking.
Because the most expensive digital project you'll ever commission isn't the one that goes over budget. It's the one that delivers exactly what you asked for - when what you asked for was the wrong thing.