Website strategy · 10 minute guide

Should you repair, redesign, or replace your business website?

Repair when the foundation is supportable and the problem is isolated. Redesign when the message, navigation, visual credibility, or customer journey is structurally weak. Replace or migrate when the platform is unsupported, unstable, unsafe to maintain, or unable to support what the business genuinely needs.

Stabilize an urgent problem before deciding the future.

If the website is compromised, offline, or blocking a critical customer action, correct or contain the immediate problem first. A failed form, mixed-content warning, broken mobile menu, or provider outage needs evidence and a recovery path—not an automatic redesign sales pitch.

Use the condition of the foundation to choose the scope.

01

Focused repair

One or two broken features: The supportable foundation still serves the business.

02

Phased improvement

Several related problems on a sound platform: Work can be prioritized without discarding everything.

03

Strategic redesign

Navigation, messaging, and visual trust are structurally weak: Isolated fixes will not correct the full customer experience.

04

Replace or migrate

The platform is unsupported or blocks required capabilities: The limitation is in the foundation.

05

Stabilize first

Malware warning, outage, or failed critical action: Restore safety and customer access before a broader design decision.

Four scopes that should not be confused.

  • Repair: correct a defined defect while keeping most of the current experience.
  • Phased improvement: address several priorities over controlled stages.
  • Redesign: rework the visual system, information architecture, messaging, and customer journey, often while retaining a viable platform.
  • Replace or migrate: move to a new technical foundation when the current system is no longer responsible to maintain.

Review the business and customer evidence.

  • What is actually broken, and what still works?
  • Can the platform be updated and supported?
  • Are critical forms and customer actions reliable?
  • Does the mobile experience work?
  • Is the site served securely without browser warnings?
  • Does navigation match the current business?
  • Which pages already earn traffic, links, or customers?
  • What required capability is blocked?
  • How will the result be validated and measured?

Choose the smallest responsible path.

A focused repair can preserve a useful site. A redesign can correct a structural customer problem. A migration can establish a supportable platform. The right choice follows the evidence, access, risk, and business requirement—not the age of the visual design alone.