Support, refresh or rebuild your website?

When a website becomes difficult to live with, a rebuild can feel like the obvious answer. Sometimes it is. Sometimes the site mainly needs someone to take responsibility for it.

Before choosing a platform or commissioning a redesign, separate three questions: is the site being cared for, does the experience work for visitors, and can the current foundation support what the organization needs next?

Start with the problems, not the platform

List the moments that create friction. A form that goes nowhere. An update that takes weeks. A page that is hard to read on a phone. A team that is unsure which person or company owns an account.

Then check them. Try the important journeys yourself, including sending a test inquiry through an agreed test process. Ask the person who maintains the content to show you how a normal change works.

The goal is to describe the problem clearly enough that a provider can explain how they would address it. “It feels old” may be true, but it is less useful than “people cannot find our services and we cannot change the pages without help.”

Better support may be the right first step

If the content structure works and the site still serves its purpose, a support transition may be enough. That could involve reviewing access and hosting, understanding the existing setup, addressing known issues and agreeing on how changes are handled.

For a WordPress site, the conversation should include the theme, plugins, updates and any custom functionality. For another platform, the details differ, but the questions about ownership and support remain.

Do not assume a new provider needs to replace everything to help. Ask what can be preserved and what evidence would justify a larger change.

A refresh can improve the experience without replacing the foundation

A refresh may be appropriate when the technology is serviceable but the message, layout or content has fallen behind the business.

Start with the pages that matter most. Can a first-time visitor tell who the service is for? Is there proof that relates to their situation? Is the next step clear? Are important actions usable on a phone?

A clearer service page and a working inquiry journey can be more valuable than redesigning every decorative detail at once.

Rebuild when the foundation limits the work

A rebuild deserves consideration when the current system cannot reasonably support the experience, performance, integrations or maintenance the organization needs.

The important word is reasonably. Every platform has tradeoffs. Ask the proposed provider to explain the limits, the alternatives and the cost of maintaining the replacement after launch.

An existing site also contains things worth protecting: useful content, search URLs, analytics history, integrations and the knowledge of the people who operate it. A rebuild plan should account for those deliberately. A beautiful launch is not enough if the forms fail or valuable links disappear.

Make the handoff part of the decision

Whichever path you take, agree on ownership and ongoing support before work begins. Know who controls the domain and hosting, how access is managed, what documentation you will receive and how someone else could take over later.

For a custom application, also understand code ownership, deployment, data and the integrations it depends on. The details may be more involved than a content website, but the principle is the same: you should not have to start over just to regain control.

A good first conversation should leave you with a clearer diagnosis and a proportionate next step. Sometimes that is a rebuild. Sometimes it is finally having dependable help with what you already have.