Your website looks older than your competitors' sites. The obvious response is to start again. But appearance alone cannot tell you whether you need a new homepage, a better content structure, or an entirely different platform.
A useful decision starts with a more specific question: what is the current website preventing your business from doing?
If customers understand your services, inquiries reach the right person, and the team can update pages easily, a focused refresh may be enough. If the site cannot support how you sell, publish, or operate, a larger redesign may be justified. The aim is to choose the smallest scope that solves the real problem without preserving the thing that caused it.
Separate three decisions that often get bundled together
A visual refresh changes presentation: typography, spacing, imagery, colors, and selected page layouts. Much of the existing content and underlying system remains.
A website redesign changes how information and customer journeys work. It may involve a new navigation structure, rewritten service pages, clearer calls to action, and different templates. It does not automatically require a new platform.
A rebuild or replatform changes the technical foundation. This might be necessary when the current system makes essential features impractical, depends on unsupported software, or prevents routine editing.
These projects can overlap, but they have different costs and risks. A proposal that treats them as the same thing makes it harder to understand what you are paying to fix.
Gather evidence before choosing a solution
Review a small set of important pages: the homepage, your strongest service page, a page attracting search traffic, and the contact or booking journey. Then examine four areas.
Customer understanding. Can someone unfamiliar with your business explain what you offer, who it is for, and what happens next? Ask them to find a specific service rather than simply asking whether they like the design.
Task completion. Can a visitor complete an inquiry on a phone? Does the confirmation appear? Does the message arrive? A polished contact page that loses submissions is an operational problem.
Team effort. Can the person responsible for content change a price, update a service, or publish an article without asking a developer? Repeated workarounds are evidence worth recording.
Business fit. Does the website reflect what you sell today? If the business has moved from individual purchases to complex consultations, the original site structure may no longer make sense.
Keep observations concrete. “The site feels dated” is difficult to scope. “Our three main services share one vague page, and callers keep asking which one they need” gives a designer something useful to solve.
Use this decision table
| What you observe | A sensible starting scope |
|---|---|
| The offer is clear, the system works, but the presentation feels inconsistent | Visual refresh and a small set of shared design improvements |
| Visitors struggle to find or compare services | Content and navigation redesign |
| Forms work, but too many irrelevant inquiries arrive | Review the offer, qualification questions, and page messaging |
| Publishing requires fragile workarounds or excessive permissions | CMS and workflow review before deciding on a rebuild |
| The platform cannot support an essential integration or supported upgrade path | Technical assessment and possible replatform |
| Several of these problems occur together | A coordinated redesign with phased priorities |
Treat this as a starting point, not a scoring system. A single serious constraint can matter more than several cosmetic issues.
Compare the cost of keeping and changing
The build quote is only part of the decision. Compare the ongoing cost of each option: subscriptions, maintenance, content updates, staff effort, and the cost of limitations you would keep.
For example, imagine a consultancy with a stable CMS but unclear service pages. Replacing the entire platform adds migration work without necessarily improving its offer. Rewriting two key pages and improving their layouts could be a more useful first investment.
Now imagine a training provider whose booking data is manually copied between three tools. New colors will not remove that administrative burden. The project needs to examine the booking workflow and integration options, even if the current website still looks modern.
Neither example is a client case study. They illustrate why the same visual complaint can lead to very different project scopes.
Protect what already works
Before changing pages, record the URLs that attract relevant visitors, generate inquiries, or receive links from other websites. Save the existing content and take a baseline of meaningful outcomes.
A redesign is also a migration when URLs change. Map each old address to its most relevant replacement, update internal links, and check redirects after launch. Google's site migration guidance explains why URL mapping and ongoing monitoring belong in the project plan.
Preserve useful customer language, accurate content, and successful paths through the site. Familiarity is not a reason to keep a weak page, but novelty is not a reason to remove a strong one.
Write a brief that a team can actually deliver
A useful brief can fit on one page. State the business problem, the customers affected, the task you want to improve, and the constraints the team must respect.
Then define what success will look like. “A more premium website” is a design direction. “Visitors can compare our three services, choose an appropriate next step, and send an inquiry that reaches our sales inbox” is something you can test.
List the parts that must remain reliable during the change: search landing pages, booking tools, email delivery, and staff publishing access. Agree who approves content and who checks the site after launch. Scope becomes easier to manage when responsibilities are explicit.
If you are unsure where the real constraint sits, Opusable's technology advice service is a useful place to start. Bring the problems you have observed; a platform decision can follow the evidence.
Frequently asked questions
How often should a business redesign its website?
There is no universal replacement schedule. Review the site when your offer, customers, or operating needs change, and when recurring usability or maintenance problems appear. A website that still serves the business well may benefit more from steady improvements than a scheduled rebuild.
Can we refresh the design without losing our content?
Usually, but it depends on how the current site stores content and builds pages. Ask the team to identify what can be retained, what needs restructuring, and whether any URLs will change before approving the scope.
Will a redesign improve our search rankings?
It may help if it fixes relevant content or technical problems, but a new design does not guarantee better rankings. It can also introduce migration mistakes. Protect existing useful pages and assess search performance alongside business outcomes.
Can we improve the site in phases?
Yes. Start with a coherent customer journey, such as one service page and its inquiry form. Establish shared design rules so later work builds on the same foundation. Phasing works best when the overall structure is considered before individual pages are changed.