A website redesign needs a business case when the decision affects more than the marketing budget. The case should explain what the current site prevents customers or staff from doing, what should change, what could be preserved and how the business will judge the result. It need not promise a return that nobody can yet measure.

A director deciding between a targeted improvement and a full rebuild needs evidence, options and a credible scope. A list of things that look dated is a useful starting observation, but it is not the decision itself. If you are still identifying the problem, begin with the signs that a website may need redesigning.

Start with the decision, not the design

Write down the choice that someone must approve. It might be whether to fund clearer service pages this quarter, replace a site that has become difficult to maintain, or postpone a rebuild until the product range is settled. This makes the case useful even if the eventual decision is to do less work.

Then state the business change in ordinary language. “Our regional teams now sell different services, but the website presents one undifferentiated list” gives a reviewer something to test. “We need a more modern digital presence” does not explain what work is required or why it matters.

Collect evidence that can change the recommendation

Look at the pages people actually use, the enquiries they produce and the questions sales staff repeatedly answer. Search Console may show whether a particular service page is visible for relevant searches; analytics may show which pages visitors enter and leave. Enquiry records can reveal whether people understand the offer before contacting you. None of these measures, on its own, proves that the website caused a lost sale.

Pair the numbers with direct observation. Ask a colleague who did not write the site to find a specific service, its coverage and a way to make an enquiry on a phone. Check whether the content is accurate and who can update it. If the real concern is poor enquiry quality, our guide to diagnosing a website that is not generating useful enquiries provides a more focused investigation.

Record what is uncertain. A quiet page may support a small number of valuable enquiries; a highly visited article may have little commercial relevance. That distinction can prevent the business case from rewarding traffic that does not serve the business.

Compare the smallest credible options

If search visibility forms part of the evidence, use the monthly Search Console routine to identify relevant pages and queries. It helps turn a search observation into a specific investigation without treating clicks as enquiries.

Put at least two scopes beside the option of leaving the site as it is for now. A focused improvement may rewrite three important pages and simplify their enquiry routes. A structural redesign may reorganise the services and create a consistent way to explain them. A rebuild may be justified when the present system makes those changes difficult to deliver or maintain.

For each option, name what it solves and what it leaves unresolved. A visual refresh can make a capable site feel current, but it will not repair a confusing service hierarchy. A complete rebuild may solve that hierarchy, yet require more content decisions, migration work and staff time than the business can currently provide. The distinction between a redesign and a rebuild is useful only when attached to the work behind each label.

Show the internal work as well as the supplier's work

A realistic case includes the time needed to confirm services, review copy, gather credible photographs, approve technical claims and test enquiries. For an established business, those decisions may sit with several people. They are part of the project even if an external studio writes and builds the site.

Note any dependency that could delay approval or delivery: a planned change to the product range, missing project permissions, an unavailable subject expert or an integration controlled by another supplier. Cost discussions are more useful once this scope is visible; our UK redesign cost guide explains the usual scope drivers without turning a headline price into a substitute for a brief.

Use a one-page approval note

A practical internal recommendation can be short:

  • Decision requested: the option and scope to approve.
  • Current problem: specific customer or operational friction.
  • Evidence: page, enquiry and staff observations, with gaps identified.
  • Alternatives: repair, redesign, rebuild or defer, and what each leaves behind.
  • Commitment: external work, internal time, dependencies and an agreed budget range.
  • Success measures: the behaviours and business outcomes to review after launch.

This is an approval aid, not a forecast dressed up as certainty. For example, if an SME sells several specialist services, the proposal might be to rebuild its service structure and make each enquiry route clearer. The success check could compare the relevance of incoming enquiries and whether staff still need to explain basic service distinctions. No invented conversion target is needed to make the decision sensible.

Decide how you will review the outcome

Our redesign ROI calculation connects qualified enquiries to contribution and tests how attribution changes the result. Use it to agree the measurement before launch, with assumptions kept separate from observed commercial outcomes.

Agree what should be checked before the project begins. Record the current enquiry routes, important landing pages and any known maintenance problems. After launch, check that forms work, useful pages remain reachable and staff can make routine updates. Watch search and enquiry patterns over a sensible period, allowing for small samples and other changes in the business.

A good business case does not need to claim that a new website will create a particular number of leads. It should make the decision proportionate, explain what the investment buys and give the business a way to tell whether the result addressed the original problem. Take that note into supplier conversations so each proposed scope answers the same decision.