Redesign or rebuild? How we decide

"Can we just refresh the design?" is a fair question with an expensive wrong answer. Redesigning on top of a broken foundation buys a prettier version of the same problems; rebuilding a site that only needed new clothes burns budget that marketing needed. So we check signals, not opinions — here's the actual list.

Four signals that a redesign is enough

• The site already passes a performance audit. If Lighthouse scores sit above 85 and the three usual suspects aren't present, the foundation is worth keeping.
• Content structure matches the business. The pages that exist are the pages needed — the problem is how they look, not what they are.
• The CMS is being used, not fought. Editors publish without a developer on standby.
• Analytics show engagement, not confusion. People find things; they just don't feel great doing it.

Three signals that demand a rebuild

• Accumulated page-builder archaeology. Multiple frameworks, plugins patching plugins, and nobody sure what's safe to delete. Redesigning on top of this is repainting a car with a seized engine.
• Mobile performance below 60 despite optimization attempts — the weight is structural, not cosmetic.
• The next business move doesn't fit. New market, new product line, a switch to e-commerce: if the information architecture has to change anyway, the rebuild pays for itself in avoided rework.

The honest middle: rebuild in disguise

About a third of our projects land in between: we rebuild the foundation — markup, performance, CMS structure — while deliberately keeping the visual identity intact. Stakeholders experience it as "the site got faster and easier to update," not as a rebrand. It's the least dramatic option and frequently the right one, especially when a recent brand identity investment is still fresh.

If you're weighing the same question, our web design and build service starts with the audit either way — you get the signals and our recommendation before committing to a direction.