A good website redesign business case does not start with colours, trends or a new homepage. It starts with the cost of keeping the current site.
Leadership needs to see what is going wrong now, who it affects and what the business could improve. The case should also show what can be done first if a full rebuild is not yet possible.
In our website discovery sessions, we often hear the same story. The team knows the site is old. Staff work around it every day. Leaders agree it needs attention, but the project keeps moving down the list. A clear business case turns that shared concern into a decision.
Start with the cost of doing nothing
An old website may still load, but that does not mean it is working well. Its cost can sit across sales, marketing, service and IT.
Look for current problems such as:
- People cannot find a service, product, document or contact path.
- Forms go to the wrong inbox, or staff do not know where the data goes.
- The same content must be added to more than one site or system.
- Simple updates take too long or need outside help.
- Old pages, staff details or files stay live because no one can manage them with confidence.
- Search, mobile use or key integrations do not work as expected.
These are business costs. They waste staff time, add risk and make it harder for people to act.
Do not guess a dollar value if you cannot prove it. Record what happens, how often it happens and which team handles it. A short log over a normal work period can give leadership a useful baseline.
Show where leads and trust may be lost
Not every website has to create a large flow of new leads. For many organisations, the website is a point of validation. A person hears about the business through a client, adviser, school, event or friend. They then visit the site to check whether the organisation feels right.
If the site looks out of date, hides the next step or does not explain who the organisation is for, that trust can fade. The referral may never become an enquiry. The team may never know it happened.
Map the main path a person should take. For example: arrive, understand the offer, check the team, review proof and make contact. Note where the current site adds doubt or effort. This is more useful than saying the design feels old.
You can support the case with existing evidence. Review analytics, search terms, form records, calls and staff feedback. Use what is available. If tracking is weak, make better measurement part of the redesign scope rather than inventing a conversion forecast.
Count the staff time hidden in the website
Website admin is often spread across small tasks. A staff member uploads the same article twice. Another person fixes formatting. Someone asks an agency to change a line of text. A form entry is copied by hand into another tool.
Ask the people who use the site to list their common tasks. Note the steps, the time involved and where errors occur. Pay close attention to content that changes often, such as products, news, jobs, team profiles, events and downloads.
This work can reveal a stronger reason for change than design alone. A simpler content system, clear permissions and sound integrations can give time back to a lean team. See our wider digital capabilities for examples of how strategy, design, development and marketing can work together.
Include brand, content and accessibility risk
A website can fall behind the organisation it represents. The services may have changed. The audience may have changed. The team may have stronger proof, better stories and new plans, while the site still shows an older version of the business.
That gap matters. It can weaken trust with a referred lead, a donor, a parent, a job candidate or a business partner.
Content also creates risk when it has no clear owner. Outdated staff details, old offers, broken files and duplicate pages can confuse users. A redesign is a chance to audit what exists, remove what no longer helps and set a simple approval process for future updates.
Accessibility belongs in the business case too. People need to read, move through and use the site with different devices and abilities. Include accessibility in the requirements from the start, then test it during the build. Treating it as a late fix adds cost and can leave important tasks blocked.
Define outcomes before features
A long feature list can make a proposal hard to approve. Start with outcomes instead.
Useful outcomes might include:
- Make the main enquiry path easier to find and complete.
- Help the right audience understand the offer and decide if it fits.
- Reduce the time staff spend on regular content updates.
- Give each important service, product or topic a clear page.
- Connect forms, email tools, customer systems or payment tools in a clear way.
- Improve mobile use, accessibility and search foundations.
Then choose a measure for each outcome. It could be completed forms, calls from the website, use of a key page, task completion in user testing, update time, content errors or failed submissions. Record the current result where possible. If there is no baseline, say that the first phase will create one.
Our website work shows how different organisations have shaped their sites around different goals. Our client reviews also give leadership a way to assess how we work, not only what the finished pages look like.
Present phased options
A business case is easier to assess when leaders can compare clear options. We often find that one fixed proposal creates a yes or no decision when the real choice is about scope and timing.
Set out three practical paths:
- Fix urgent issues on the current site. This may suit a short-term need, but explain which limits will remain.
- Build the core new site. Focus on the main audience, content, enquiry path, accessibility, measurement and essential integrations.
- Add later phases. These may cover a store, member area, new content hub, campaign pages, advanced tools or more production work.
Be honest about work that may be wasted. Repeated repairs to an old system can delay a rebuild without solving the main problem. At the same time, a lean first phase can be the right choice if it creates a sound base that can grow.
Give leadership a one-page decision
Your full research can sit behind the proposal, but the main case should fit on one page. Include:
- The current problem and who it affects.
- The cost and risk of leaving it as it is.
- The outcomes the redesign must deliver.
- The options, timing and main trade-offs.
- How success will be measured after launch.
- Who will own content, approvals and the website once it is live.
Use plain language. Separate facts from assumptions. Avoid a made-up return on investment figure. Leaders can make a sound decision when they can see the current loss, the proposed change and the way results will be checked.
If you need help turning website problems into a clear scope and phased plan, talk to IGNITE. We can review the current site, map the user paths and build a case that your team can take to leadership.