All resources

Repair the website or rebuild it?

Decide what needs to work, not just how new the website should look.

Start with the blockage

Write down what a customer cannot do today: understand the offer, find a product, submit an enquiry or complete payment. Reproduce it on mobile and desktop. Separate broken functionality from unclear content and platform constraints. A website that sells poorly does not, by itself, prove that its technology must change.

When a targeted fix makes sense

Consider a fix when the problem can be isolated, the basic structure supports the offer and the team can maintain the solution. Ask for defined scope, acceptance criteria and a rollback plan. Check forms, checkout, important pages and measurement before commissioning a broader redesign.

When to evaluate a rebuild

Evaluate rebuilding when the same constraint affects many pages or the platform cannot support required processes. Include migration work in the comparison: content, URLs, redirects, integrations, testing and training. A platform change will not automatically improve the offer or create demand.

Bring evidence to the discussion

Prepare the URL, three specific problems, what you want to preserve and who maintains the site. Define acceptance through verified functional steps before assessing commercial impact. Choose FIX or REBUILD from these constraints, not simply from the age of the website.

Apply this to your situation

Let's talk

Before you choose a solution

Four guides for practical decisions. Open access, no form.