How to Build a Business Case for Website Redevelopment

Web Development, Front End Development, Tip and Tricks, Web Design, Web Support
19 November 2026

You might already know your website needs attention. Customers struggle to find the right information. Simple updates take too long. The sales team says enquiries aren’t what they used to be.

 

Getting agreement that something is wrong is one thing. Getting approval to invest in fixing it takes a stronger argument.

 

A website redevelopment business case should explain what the problem means for the organisation, what could improve and why the proposed investment is a sensible response. It also needs to give leadership room to ask whether a smaller change would achieve enough.

 

You don’t need every answer before you begin. You do need a clear starting point—and a willingness to test the assumptions behind your request.

 

Start with the problem behind the request

 

“We need a new website” usually comes after months of frustration. By that point, the team may have a long list of things they’d like to replace.

 

The useful conversation starts with what’s driving that frustration.

 

Take a website that generates plenty of enquiries but few worthwhile opportunities. A shorter contact form might increase submissions while giving sales even more unsuitable leads to sort through. Understanding who is enquiring, what they expected and where the mismatch occurs could point to a different solution.

 

The same applies to publishing. If launching a campaign takes weeks, find out where the time goes. A restrictive editing experience may be responsible. So might an approval process that requires six people to sign off every update.

 

Your business case becomes stronger when it can explain that connection: here’s the problem, here’s the consequence, and here’s why changing the website could help.

 

This is where an experienced agency can help you work through the uncertainty. Through discovery and digital strategy, JTB can bring the right people into the conversation, investigate the initial brief and help define the problems worth solving.

 

Our Westbourne Grammar project, for example, used analytics reviews, a content audit and stakeholder input to inform how information was organised around different audience needs. That investigation gave the design work a clear purpose.

 

Establish what happens today

 

Before estimating the benefit of a new website, get a reasonable picture of how the current one performs.

 

For a business seeking better leads, that means looking beyond form submissions. Follow enquiries through to qualification and, where possible, sales. Talk to the people handling them. They may recognise recurring misunderstandings that analytics alone won’t explain.

 

For a service organisation, the useful evidence might sit with customer support. If people regularly call because they cannot find instructions online, review those calls alongside the relevant website journey. You can then investigate whether clearer information would help them complete the task themselves.

 

Keep the measurement proportionate. You need enough evidence to assess the problem, not a dashboard covering everything the website does.

 

From there, define the improvement you want to see. “Improve customer experience” becomes more useful when it means helping customers complete a particular task with fewer errors or less assistance.

 

Be careful about how you describe the value. Saving a team several hours each week creates capacity, but it doesn’t automatically reduce the payroll. Explain what that time could be used for, and keep it separate from savings that genuinely reduce expenditure.

 

Give the alternatives a fair hearing

 

Leadership should be able to see why your recommendation makes more sense than the other options.

 

Sometimes the existing website can support what the business needs with better content, clearer navigation or improvements to a few important journeys. In other cases, deeper constraints make continued patching expensive and limiting.

 

There is evidence that focused changes can matter. In a published Rakuten 24 case study, a month-long A/B test found that improving a landing page’s performance increased conversion, without changing its visual design or functionality. That result isn’t a forecast for your business. It is a reason to investigate whether a specific intervention could solve the problem.

 

Compare realistic scopes for optimisation, redesign, rebuilding or moving platforms. Consider what each would achieve, how long it would take and what it would require from your team.

 

Include maintaining the existing site as an option. Give it a realistic maintenance cost and acknowledge any known limitations. Avoid assuming that performance will inevitably collapse if investment is delayed.

 

A recommendation earns credibility when the alternatives have been taken seriously.

 

Make the financial argument believable

 

The build fee is only part of the investment.

 

Someone will need to prepare content, review designs and test the new experience. There may be migration work, connections to other business systems and training before launch. Afterwards, the website will need maintenance and ongoing improvement.

 

Bring those costs into the discussion early. Comparing the full cost of each option over the same period gives finance a more useful basis for evaluation.

 

Then consider the benefits. For a lead-generation website, an estimate needs to account for how many additional enquiries are likely to be suitable, how many become customers and the contribution those sales make after associated costs. Treating every new enquiry as revenue will quickly undermine the case.

 

A useful way to test your assumptions is to work backwards: what improvement would be needed to recover the investment, and does the evidence suggest that improvement is achievable?

 

ROI can help compare financial benefits with costs. Payback helps show when the investment could be recovered. Neither removes the uncertainty, particularly when delivery takes time and results depend on other parts of the business.

 

Show what happens if the improvement is smaller than expected or takes longer to arrive. If the recommendation only works under an optimistic forecast, leadership needs to know.

 

Some investments also protect an essential capability or address an established risk. Explain those benefits directly, supported by evidence. You don’t need to invent a revenue figure for every reason to act.

 

Give leadership a clear decision to make

 

By this point, your business case should tell a coherent story. The final document needs to make that story easy to assess.

 

A short summary supported by the relevant evidence can cover:

  • The decision: what you’re asking leadership to approve now.
  • The problem: who is affected and what it means for the business.
  • The recommendation: the proposed approach and why it is preferable to the alternatives.
  • The value: expected outcomes, their supporting assumptions and how they will be measured.
  • The commitment: the full cost, internal effort and likely timing.
  • The uncertainty: risks, dependencies and questions still to resolve.
  • The accountability: who will own delivery and review the results.

 

Involve finance, technology and the teams affected before the final approval meeting. They can help test the assumptions while there is still time to improve the recommendation.

 

For example, an anticipated increase in leads may depend on sales having the capacity to respond. Faster publishing may require someone to take ownership of content. These dependencies belong in the case because they affect whether the benefits will materialise.

 

You don’t need to solve everything before asking for help

 

There is a point where gathering more information internally stops being productive. You may know that the website is holding the business back without knowing how much needs to change.

 

A defined discovery phase can help resolve that. Its purpose should be explicit: investigate the questions that materially affect the investment decision, then use the findings to recommend a scope.

 

At JTB, we help guide that process through workshops, research and review of the available evidence. You can bring the problems you see, the priorities you need to support and the questions you haven’t been able to answer. Together, we can develop a clearer brief.

 

Once investment is approved, that brief should carry the business case into delivery. The agreed outcomes give everyone a basis for prioritising features, making trade-offs and assessing whether the finished website is doing its job.

 

If you’re considering website redevelopment, talk to JTB about establishing what needs to change and building a clear case for the next step.

Blog

You made it this far
Let's chat
Let's chat
1300 66 99 58
333 Drummond Street Carlton 3053 Melbourne, Australia

    Hi, my name is

    I'm from

    You can call me on

    and email me at

    I would like to chat about...

    (optional)
    (optional - 10mb max)

    Wow, so nice of you  
    We’ll be in touch shortly to learn more about your project.

    Projects

    4

    St Leonard's College

    Education

    Industry Beans

    Food & Drink Hospitality & Leisure

    Small Wonder

    Hospitality & Leisure Retail

    Sushi Sushi

    Food & Drink Technology