Skip to content
Simple Spark
News & Insights

InsightBuild

Redesign, rebuild, or leave it alone?

Three different problems get called "we need a new website." Here is how to tell which one you actually have before you spend anything.

Simple Spark4 min read
Redesign or Rebuild — or leave the thing alone

Most website conversations start the same way: our site is dated, we need a new one. Sometimes that’s right. Often what’s actually wrong is something smaller, or something bigger, and the word “redesign” hides both.

There are three different jobs here, and they cost wildly different amounts.

The three options

A refresh changes how it looks. Type, color, photography, spacing, maybe the header and the homepage. The structure stays, the platform stays, the content stays. Weeks, not months.

A rebuild changes how it works. New structure, new page templates, new content model, often a new platform. Everything gets rewritten or reorganized. Months.

Leaving it alone means spending the money on something else — content, photography, advertising, a fix to one specific broken thing — because the site isn’t what’s holding you back.

Signs you need a refresh

The site does its job, it just looks its age.

  • It works on a phone, but looks like it was designed for a desktop and squeezed down.
  • Your brand moved on and the site didn’t. New logo, new colors, old website.
  • The photography is stock, or is yours from eight years ago.
  • People find what they need, but nobody would call it impressive.
  • Your team can update it fine; it just doesn’t look like the caliber of company you are now.

If most of those are true and your traffic and inquiries are steady, you have a surface problem. Don’t let anyone sell you a rebuild.

Signs you need a rebuild

The structure is the problem, and no amount of new paint fixes structure.

  • You can’t add the thing you need. A new location, a new product line, a new service — and there’s no sensible place for it. That’s a content model problem.
  • Your team can’t update it. Every change goes through a developer, so changes don’t get made, so the site drifts out of date.
  • The navigation grew by accretion. Nine top-level items, three of which are the same thing in different words, because nobody ever removed anything.
  • It’s slow, and it’s slow because of how it’s built. Not because of one big image.
  • It fails on a phone in ways that aren’t cosmetic: forms that don’t submit, menus that trap you, tables you can’t read.
  • Customers call to ask things the site answers. Usually means the answer exists but is buried.
  • The platform is a liability. Unsupported plugins, a theme nobody maintains, a CMS version that can’t be updated safely.
  • Accessibility is structural. Missing headings, unlabeled forms and keyboard traps aren’t a paint problem. For public entities in particular, that has a deadline attached.

One or two of those, you might patch. Four or more and a refresh is money spent making a bad structure prettier.

Signs you should leave it alone

This is the option nobody in my business brings up, so here it is.

  • Inquiries are steady and people say they found you easily. The site is working. Being bored of it is not a business case.
  • Your real problem is upstream. Nobody’s visiting. A new site doesn’t fix a traffic problem — content, search and advertising do.
  • The real problem is one thing. A broken form, a missing location page, no online booking. Fix that thing for a fraction of the cost.
  • You’re about to change something bigger. A merger, a name change, a new product line in six months. Wait, and do it once.
  • You can’t staff it. A new site needs someone to feed it. If nobody will own that, you’ll be back here in three years with the same conversation.

A test that usually settles it

Sit down and write the five things a customer most needs to do on your site. Book, buy, compare, apply, find you, get a quote, whatever yours are.

Now do each of them on your phone, out loud, timing yourself.

If they all work and just look tired, you need a refresh. If you find yourself explaining why a step is like that, you need a rebuild. If they’re fast and clear, spend your money somewhere else this year.

What it costs to get this wrong

Choosing a refresh when you needed a rebuild is the expensive mistake. You spend real money, the site looks better, and every original problem is still there — so you do it again in two years and pay twice.

Choosing a rebuild when a refresh would do is the other one. Less damaging, but you spent a year of budget and attention rearranging something that was basically working.

The useful move, before any of it, is an hour with someone who will look at the actual site and tell you which of the three you’re facing — including when the answer is “leave it alone.”


Not sure which one you’re looking at? We’ll go through your site with you and tell you straight, including if the answer is to keep what you’ve got.

Written by Simple Spark

Start Somewhere

Have a project this applies to?

Tell us what you are working toward and we will help you identify the clearest next step.