← All insights

Does your website need a rebuild?

How to decide whether your website needs a few focused improvements or a fresh start, and what to include in the brief.

Architectural website panels lifted to reveal a green foundation, illustrating a considered redesign.
Editorial illustration created with AI for Profable.

A website can look dated and still bring in good enquiries. It can also look impressive and leave visitors unsure what you actually do. Before commissioning a redesign, work out which problem you need to solve.

For a service business, the useful questions are straightforward: can the right visitor understand the offer, trust the business and take the next step? A redesign should improve those things. A new colour palette alone will not.

Start with the enquiry

Pick one important service and walk through the journey on your phone. Start on the page a customer would actually land on, which may not be the homepage. Can you see who the service is for, what it includes and what happens after you enquire?

Then submit a test enquiry. Check the confirmation, where the message arrives and who takes responsibility for it. A broken form or an unmonitored inbox needs attention before a visual refresh.

Look at recent enquiries alongside website data. If visitors are asking questions your page should answer, the copy may be the problem. If qualified visitors start the form but abandon it, investigate the form. If hardly anyone reaches the page, a redesign on its own may not solve the visibility problem.

Improve or rebuild?

Targeted changes make sense when the structure is sound and the issues are specific. You might rewrite the service pages, simplify navigation, repair mobile layouts or connect the forms to your CRM.

A rebuild becomes more reasonable when the existing system prevents those improvements: routine changes require fragile workarounds, the business has outgrown its structure, or the site cannot support the content and integrations you need.

WordPress and a custom build can both be appropriate. The decision depends on who will update the site, the features it needs and what you can maintain. Ask to see how an ordinary content change will work before choosing the technology.

Write a useful brief

Give your designer more than a list of websites you like. Include:

  • Your priority services and the customers each one serves.
  • The questions customers ask before they buy.
  • The action each important page should lead to.
  • Real photographs, credentials and approved evidence you can publish.
  • The systems that need to receive enquiries.
  • Who will own updates, hosting and maintenance after launch.

Agree how you will assess the result. Completed enquiries, their quality and the ease of managing the site are more informative than whether everyone likes the new homepage.

Protect what already works

A launch plan should account for existing URLs, redirects, search metadata, analytics and form testing. Keep useful content unless there is a reason to change it. Review the site on real phones, and test the full enquiry journey again after launch.

Our website service starts with these decisions. If the real gap is what happens after someone contacts you, begin with your enquiry process instead.

Make it practical.

Try your own website as a customer.

Your action checklist

Use any unchecked items as the starting point for your website brief.

About the author

Constantinos builds websites and growth systems, with experience across engineering, product, marketing, sales and revenue operations. He writes about connecting those disciplines to help businesses attract customers and follow through on enquiries.

· Editorial standards & AI use

Also worth reading

Let’s talk.

If this article describes your situation, tell us about it.

Discuss your project