Does Your Website Need a Cleanup, Refresh, or Rebuild?

Choose a service, booking, quote, purchase, or contact journey and follow it from arrival through confirmation. Check whether someone can understand the business, recognize fit, find relevant proof, choose the right action, submit information, and know what happens next.

Write down real confusion, repeated questions, abandoned steps, wrong-fit requests, and places where staff must explain what the website should have made clear. This separates useful evidence from a general feeling that the site looks old.

Mark inaccurate services, outdated team details, vague claims, missing proof, duplicated pages, unanswered questions, and content nobody owns. A beautiful redesign cannot rescue information that is wrong, unclear, or disconnected from how the business now works.

When the structure is sound but the message has drifted, a focused content and page cleanup may solve more than a visual overhaul.

Review mobile layouts, navigation, forms, links, headings, keyboard access, image alternatives, page speed, privacy notices, analytics, confirmations, and error states. A handful of serious defects may create most of the frustration while the underlying site remains usable.

Prioritize problems by customer impact and business risk rather than by how easy they are to notice during a visual review.

Confirm that the platform is supported, domain and account ownership are clear, backups and recovery work, content can be updated, integrations are maintainable, and ordinary changes do not break unrelated pages.

Foundation problems are the strongest argument for a rebuild. They are different from disliking the colors, wanting fresher imagery, or needing clearer service language.

A cleanup fits when the platform and page structure are sound but the site contains outdated facts, broken links, inconsistent formatting, weak calls to action, missing metadata, or a manageable set of mobile and accessibility defects.

This is often the fastest way to reduce customer confusion and restore trust without disturbing parts of the site that still perform well.

A refresh fits when the foundation remains usable but the message, visual direction, page patterns, proof, or customer journey need meaningful improvement. It may include rewritten core pages, updated design rules, new imagery, and selective restructuring.

A refresh should make the current business easier to understand—not merely make the old website look newer.

A rebuild is justified when the platform cannot support required functions, ownership is unclear, content management is unworkable, integrations are brittle, or accessibility, privacy, security, performance, and recovery cannot be corrected responsibly.

The rebuild should preserve what is still valuable while replacing the part that prevents the business from operating, maintaining, or growing safely.

A new website will not fix an unattended inbox, unclear request ownership, missing follow-up, or a process that depends on memory. When the public path works but requests become unreliable after contact, the first project may belong behind the website.

Pair website and workflow work only when both are necessary to complete the same customer journey.

Name what the site should communicate rather than asking for an abstract style. Compare a few grounded directions and discuss how each supports the customer, business, and kind of trust the site needs to build.

The brief should name the problem, supporting evidence, selected scope, customer paths affected, pages or systems involved, what will remain, what success looks like, who approves decisions, and who maintains the result.

A clear brief protects the business from vague proposals and protects the project from expanding every time someone remembers another annoyance.