People come to me fairly often having already decided they need a new website. They've made up their mind before the first email. "It's outdated, it's embarrassing, I think I just need to start over."

And a good chunk of the time, my honest answer is: no, you don't. You need three things fixed, and you can keep the site you've got.

That's not me turning down work — it's me turning down the wrong work, which is a different thing. Because there's a real cost to rebuilding a website you didn't need to rebuild: usually a few thousand dollars and a month of your life, spent solving a problem that a few hundred dollars and a couple of days would have solved. So before you blow up your site and start from scratch, it's worth figuring out whether the foundation is actually cracked, or whether a couple of things are just loose.

Why everyone jumps straight to "I need a new site"

The instinct makes sense, even when it's wrong.

When a website annoys you — it looks dated, something's broken, it loads slowly, it embarrasses you when you send someone the link — the feeling is global. The whole thing feels bad. And the obvious response to "the whole thing feels bad" is "replace the whole thing." A rebuild feels like the clean solution, the fresh start, the big lever you can pull to make the bad feeling go away.

There's also, frankly, an industry that benefits from you believing this. A full rebuild is a much bigger invoice than a fix. So if you ask the wrong web person "should I rebuild?", you may not get the most neutral answer in the world, because the honest answer ("nah, I'll patch three things for a couple hundred bucks") is the one that pays them the least. I'm not saying everyone's cynical — most aren't — but the incentive points one direction, and it's worth knowing that when you ask.

Here's the reframe that saves people the most money: a website is not one indivisible thing that's either "good" or "broken." It's a stack of separate parts — design, content, speed, functionality, structure — and usually only one or two of them are the actual problem. The rest is fine. You just can't tell which is which from the inside, because the bad feeling smears across all of it.

The three things that are usually actually wrong

When someone tells me their site is "outdated" or "broken," it almost always comes down to a small number of specific, fixable problems wearing a trench coat and pretending to be one big one. Most often, it's some combination of these three:

1. It looks dated. This is the one that drives most "I need a new site" feelings, and it's often the most fixable. A site can look tired for small reasons — old fonts, a cramped layout, low-res images, a colour scheme that screams a different decade, too much text crammed together. The structure might be perfectly sound; it's the surface that's aged. Refreshing the look — new type, more whitespace, better images, a cleaner layout on the existing framework — can make a site feel current without touching the foundation. You're repainting and refurnishing, not rebuilding the house.

2. It's slow. A site that takes five seconds to load feels broken, because visitors leave before they ever see it. But slowness is almost never a "the whole site is rotten" problem. It's usually a handful of culprits: enormous unoptimized images, too many plugins, cheap hosting, bloated code from some tool. These get diagnosed and fixed individually. You don't rebuild a site to make it fast; you find what's dragging it down and deal with that.

3. It's broken somewhere specific. The contact form doesn't actually send. A button links nowhere. It looks fine on a laptop and falls apart on a phone. An image is missing, a page 404s, the booking widget stopped working after an update. These feel like the site is "failing," but they're discrete bugs — each one identifiable and fixable on its own. One broken form does not mean you need a new website any more than a dead lightbulb means you need a new house.

Notice what all three have in common: they're repairs, not reconstructions. The site's bones are intact. Something on top of them needs attention. And repairs cost a fraction of a rebuild.

How to actually tell the difference

So how do you know which camp you're in before you spend the money? Here's the rough test I use.

It's probably just a fix if:

• The design is dated but the layout basically makes sense — it just needs a refresh.
• A few specific things are broken (forms, links, mobile display) but the rest works.
• The content is stale — old prices, old photos, old info — and mostly needs updating.
• It's slow, but it's slow for findable reasons.
• You can still log in and edit it, and the platform it's built on is still supported.

In all of those, the foundation is fine. You're fixing what sits on top, and that's hundreds of dollars, not thousands.

It's probably genuinely a rebuild if:

• It's built on a platform that's dead, abandoned, or no longer secure, and can't be safely updated anymore.
• Nobody can edit it — you've lost access, or it was hand-coded by someone long gone and changing anything risks breaking everything.
• The structure itself is the problem — it's organized so badly that fixing it piece by piece would cost more than starting clean.
• The business has changed so much that the site is for a company you no longer are.
• It's a genuine security risk — outdated, unpatched, and exposed.

When those are true, patching is throwing good money after bad — you'd spend on fixes and still be sitting on a broken foundation. That's when a rebuild earns its price.

The honest middle ground exists too: sometimes a site needs enough fixes that you're better off rebuilding, and a straight answer accounts for that. If I look at a site and the repair list is so long it approaches the cost of starting fresh — and the fresh version would be dramatically better — I'll tell you to rebuild. Not because more money is better for me, but because there's a point where patching stops making sense, and pretending otherwise would be its own kind of dishonest.

The money math, plainly

Let me put real shape on why this matters, because "it depends" is useless without numbers.

A typical fix — a few broken things, a content refresh, some speed work — runs in the low hundreds. A visual refresh on a sound site, a bit more. A full custom rebuild runs into the thousands, plus the weeks of your time spent gathering content, reviewing drafts, and going back and forth.

So the stakes of getting this diagnosis right aren't small. Guess "rebuild" when the truth was "fix," and you've spent maybe ten times what the problem actually required, plus a month you didn't need to spend. That's not a rounding error. That's a real chunk of a small business's budget, gone to solving a problem you could have solved for a fraction.

Which is exactly why the move — before you commit to anything — is to get the thing diagnosed rather than guessing from the bad feeling. Someone who knows what they're looking at can usually tell you in short order whether you're staring at three loose bolts or a cracked foundation. That diagnosis is cheap. Acting on the wrong assumption is not.

The middle option nobody mentions: the refresh

There's a third path that gets lost in the "fix it or rebuild it" framing, and it's the right answer more often than either extreme: the refresh.

A refresh is a redesign that keeps the existing foundation. Same platform, same underlying structure, often the same pages — but a genuinely updated look: new typography, a cleaner layout, better spacing, fresh images, a modernized colour palette. From the outside it can look like a brand-new site. Under the hood, you kept everything that was working and only changed what had aged.

This is the sweet spot for a lot of businesses, because the most common real complaint — "it looks old" — is usually a surface problem, and a refresh fixes surface problems without the cost and upheaval of a rebuild. You get the "wow, you got a new website" reaction from customers, at a fraction of the price and time, because you didn't actually rebuild anything. You repainted, rearranged the furniture, and let in some light.

So when you're weighing fix versus rebuild, remember there's a middle gear. Plenty of sites that feel like they need a full teardown actually just need a confident refresh — and the person looking at it should tell you if that's the case, instead of defaulting to the biggest possible invoice.

How to know you're getting an honest answer

Since the incentive can quietly push toward "rebuild," here's how to tell whether the person diagnosing your site is being straight with you.

A good one asks what's actually bothering you and looks at the specifics before quoting anything — they don't recommend a rebuild sight unseen. They're willing to say "this is fixable" even though it earns them less. They explain why in plain language you can follow, rather than hiding behind jargon that conveniently leads to the priciest option. And they're comfortable laying out the choices — fix, refresh, or rebuild — with honest pros and cons for each, instead of steering you straight to the one with the biggest number.

The red flag is the opposite: someone who hears "my site feels old" and immediately pitches a full custom rebuild without really looking, or who can't or won't explain in normal words why the cheaper options wouldn't work for you. That's not a diagnosis. That's a sales pitch wearing a diagnosis costume.

You don't need to become a web expert to protect yourself here. You just need someone willing to tell you the truth even when the truth is cheaper for you — and to walk away from anyone who won't.

What to do this week

If your site is bugging you and you're tempted to start over, do this first:

Write down what's actually bothering you, specifically. Not "it's bad" — the real list. "The contact form doesn't work. It looks old. It's slow on my phone. The hours are wrong." Once it's a list of specific complaints instead of one big cloud of dissatisfaction, you'll often see that it's three or four fixable things, not a doomed website.

Then get someone to look at it before you spend a dollar on building anything. A short, honest diagnosis — what's actually wrong, what it'd take to fix versus rebuild, and a real recommendation — costs very little and can save you thousands. If the verdict is "rebuild," fine, now you know, and you're spending on purpose. But more often than you'd think, the verdict is "this is fixable, and here's the short list."

The bottom line

The bad feeling a website gives you is real, but it's not a diagnosis. "I hate my website" almost never means "every part of my website is broken." It usually means a few specific, fixable things have piled up until the whole thing feels rotten — when actually the bones are fine and the surface just needs work.

So before you tear it down: figure out whether you've got a foundation problem or a faucet problem. Most of the time, it's the faucet. And fixing a faucet shouldn't cost what rebuilding a house does.

This is genuinely half of what I do — I fix and refresh existing sites, not just build new ones. If yours is bugging you and you're not sure whether it needs a fix or a fresh start, send me the link. I'll take a look and give you a straight answer, even when the straight answer is "this is cheaper than you think."