Something I learned recently that pained me as a developer, but intrigued me as a marketer:

a shitty website might not always break revenue.

That's a trap. It’s easy to spot and easy to point to, which is exactly why the website gets blamed first. But looking bad and being the bottleneck are two different things, and only one of them is usually true.

Don’t get me wrong, the visuals are useful clues. They tell you where to start looking. But, they don’t verbalize business impact, and if you treat that as proof alone, projects get sold that never do the numbers they were supposed to.

The real issue might live somewhere else entirely: not enough demand, bad lead qualification, slow follow-up, high churn, limited capacity, or an operational bottleneck that only shows up after the sale is made. 

Those are all different problems, and none of those are fixed by a new homepage.

So before proposing any work, connect the visible issue to a business outcome the company actually wants to improve. If you can't draw that line yet, be honest about what you have: a hypothesis, not a diagnosis.

Separate the symptoms from the underlying constraints

Clients will describe the symptoms for you, but that’s half the story. Your job is to find the problem underneath them.

• “We need more leads” might be exactly right. Or the business might be losing the leads it already gets. Best place to start? Look at how many good leads are coming in, what happens to them (i.e follow up), and how many customers the business needs before deciding what to fix. 
• “The website isn’t converting” is only a useful diagnosis after you know where people are dropping off and why. If the wrong people are arriving, fix targeting. If the right people arrive but don’t understand the offer, fix the message. If they understand it but need reassurance before buying, make the next step a conversation instead of forcing an immediate purchase. 
• "We need automation" often actually means the underlying process is inconsistent, and needs to be cleaned up before it's even worth automating. Chaos on a loop is generally not a good time for a business.
• “Our website is causing problems” may actually mean there’s a breakdown somewhere else in the customer journey. Track what happens before and after people interact with the website to find out where things break. 

Pro tip: ask what happens before and after the visible failure, not just what happens on the page. The page is one frame in a longer sequence, and the real damage is often happening a few steps upstream or downstream of it.

The same symptom can require completely different solutions

This is where diagnosis really earns its keep; since identical symptoms can, at times, point to opposite fixes.

Low form submissions because of confusing page copy? Do messaging and UX work. Low submissions caused by poor-fit traffic? Improve your targeting or distribution. A redesign won't help that problem. Are submissions solid, but receive a slow staff response? That could be routing or CRM changes, not the front end at all. And strong demand with no capacity for it? That’s a different beast: more leads in that scenario can actually make the customer experience worse.

The mechanism of action has to follow the constraint, not the other way around. Sometimes that mechanism is a website. Other times that’s content, video, automation, integration, a process change… or no project at all. (gasp)

Use a short discovery sequence to connect digital friction to business impact

A handful of questions, asked in order, will usually surface the real constraint before you write a single line of a proposal:

1. What outcome are you trying to improve? More qualified conversations, faster service, fewer errors, higher retention or something else?
2. Where is the problem first visible? Traffic, page engagement, form submission, staff handoff, booking, fulfillment, or follow-up?
3. What evidence shows this is happening? Analytics, response times, duplicate records, lost inquiries, customer complaints, staff workarounds?
4. What’s the problem costing? Lost revenue, staff time, customer confusion, operational risk, missed opportunities?
5. What’s already been tried? This separates untested assumptions from problems that keep recurring no matter what's attempted.
6. What would improve if we fixed it? If you don't have a clear answer, the project is probably still premature.

That last question is the deciding factor. A clear, specific answer means you've found a constraint worth solving. A vague one means you're still guessing. You don't get paid to guess unless you're a weatherman.

Sometimes a website redesign is the wrong prescription

The website in a day people will hate me for this, but: the correct recommendation is sometimes no redesign at all.

• A company that’s booked out doesn’t need more leads. Their problem might be elsewhere.
• If leads show up but disappear inside an inconsistent follow-up process, redesigning the front end leaves the actual failure completely untouched.
• If customers trust the company through referrals and buy through direct conversations, visual polish might not add much to the bank account.
• If the offer itself is unclear, a new page design just makes the same confusion more sexy.

A redesign becomes justified only once there's evidence that the current experience is keeping  a valuable customer action or business outcome from happening, and not just because it looks dated or feels behind.

Find the constraint first. The mechanism will follow.