A business owner can spend weeks planning a new website for the wrong reason.
The homepage feels old. A competitor has a cleaner design. Someone on the team says, “We need something more modern.” A redesign begins, money gets spent, colors change, pages move around—and six months later the business discovers something uncomfortable:
The old website was not the real problem.
Maybe leads were disappearing because the contact form was unreliable. Maybe customers could not understand the offer. Maybe mobile visitors were leaving. Maybe the website was attracting the wrong people. Maybe nobody knew what the site was supposed to accomplish in the first place.
A new design can be useful. Sometimes it is exactly what a business needs. But “this website looks old” is not a strategy.
Before you pay someone to rebuild everything, answer these seven questions.
1. What is actually wrong with the website?
This sounds obvious. It usually is not.
“The website is bad” can mean a hundred different things:
- It loads slowly.
- It looks dated.
- Visitors cannot find important information.
- It gets traffic but few enquiries.
- The checkout is confusing.
- The business has changed but the website has not.
- Staff cannot update it without calling a developer.
- Forms, tracking or integrations are unreliable.
Those are different problems. They do not all require the same solution.
If the navigation is confusing, rebuilding the payment system may accomplish nothing. If the site is slow because of oversized images and poor hosting, changing the logo will not rescue it. And if the offer itself is unclear, a beautiful redesign can simply make the confusion look more expensive.
Start with the problem, not the redesign.
2. What should a visitor be able to do within the first few minutes?
Every useful business website has a job.
A restaurant may want reservations. A consultant may want qualified enquiries. An ecommerce store wants purchases. A software company may want demos. A local service business may want calls or WhatsApp messages.
The problem begins when a website tries to do everything equally.
The visitor arrives and sees nine menu items, three sliders, five buttons, a popup asking for an email address, a chatbot asking how it can help, and a banner requesting cookie consent. At this point the visitor has completed more onboarding than some employees.
Ask a simpler question:
What is the most valuable next action for the right visitor?
Once that is clear, the homepage, navigation, service pages and calls to action become much easier to design.
3. Are you fixing a design problem or a business problem?
Businesses often notice design problems first because design is visible.
A slow sales process is harder to see. So is poor positioning. So is a broken follow-up system. So is the fact that customers keep asking questions the website should already answer.
This distinction matters because websites sit in the middle of many business systems.
A “website problem” may actually be:
- a weak offer;
- unclear pricing;
- poor lead handling;
- slow customer support;
- bad product photography;
- missing social proof;
- the wrong traffic source;
- or a checkout process that asks customers to work too hard.
A redesign can support a stronger business process. It cannot invent one.
4. What evidence do you have that the current website is failing?
There is a big difference between “I don’t like the site anymore” and “customers are struggling to use it.”
One is a feeling. The other can often be observed.
Look at the evidence you already have:
- Which pages get traffic?
- Where do visitors leave?
- Which pages generate enquiries?
- Do mobile visitors behave differently?
- Are important forms actually delivering messages?
- What questions do customers repeatedly ask before buying?
- Which pages are never visited?
- What do sales or support staff complain about?
You do not need enterprise analytics software to begin. Even a basic review of traffic, enquiries, page speed, mobile usability and customer feedback can tell you more than an afternoon spent choosing between two shades of blue.
If you are unsure where the problems are, a structured website health check is a better starting point than immediately commissioning a rebuild.
5. What already works—and should not be destroyed?
Redesign projects have an unusual risk: enthusiasm.
Once everyone agrees the website needs improvement, suddenly everything becomes a candidate for replacement.
The navigation? Replace it.
The copy? Rewrite it.
The URLs? Change them.
The forms? New system.
The platform? Why not?
This is how a redesign quietly becomes a demolition project.
Before changing anything, identify what is already producing value.
- Pages that rank in search.
- URLs other websites link to.
- Forms that generate qualified leads.
- Content customers regularly use.
- Checkout or account functions people understand.
- Integrations staff rely on every day.
A good redesign improves weak parts without casually breaking strong ones.
6. Will the new website be easier to operate after launch?
A redesign is not finished when the homepage is approved.
Someone still has to live with the website.
Products change. Staff leave. Prices move. New services appear. Plugins need updates. Content needs editing. Forms need testing. Search engines crawl new pages. Customers discover creative new ways to break things developers never imagined.
Ask what happens six months after launch.
- Can your team edit normal content safely?
- Is there a backup and recovery process?
- Who maintains plugins, themes and integrations?
- Can the site grow without rebuilding everything again?
- Are analytics and conversion tracking understandable?
- Is the hosting appropriate for the website you are actually running?
A website that looks impressive but becomes impossible to maintain is not an upgrade. It is a very attractive future problem.
7. How will you know the redesign worked?
This may be the most important question.
Suppose the new website launches and everyone says it looks better.
Is that success?
Maybe. But businesses usually need something more measurable.
Success might mean:
- more qualified enquiries;
- higher checkout completion;
- better mobile engagement;
- faster page loading;
- fewer support questions;
- more demo bookings;
- easier content management;
- or stronger organic-search visibility over time.
If you cannot describe the result you want before the project starts, it becomes difficult to know whether the project improved anything.
Sometimes you do need a new website
None of this means businesses should avoid redesigns.
Sometimes the current website really has reached the end of its useful life.
The technology may be difficult to maintain. The design may no longer work well on modern devices. The business may have changed completely. The information architecture may be beyond sensible repair. Performance problems may be structural. The site may no longer represent the company customers are actually dealing with.
In those cases, rebuilding is not cosmetic. It is practical.
But the best redesign projects usually begin with something less exciting than colors, animations or homepage mockups.
They begin with questions.
Before you redesign, diagnose
If your website is underperforming, start by understanding why.
You may discover that you need a full website redesign.
You may discover that you need three focused fixes and should leave everything else alone.
Either outcome is useful—because the objective is not to own a newer website.
The objective is to own a website that does its job better.
If you want an outside view before deciding what to rebuild, start with DevTechi’s Free 5-Point Website Health Check. If you already know the site needs a larger redesign, you can also tell us about the project.