What problem would a new website solve?
Name the business problem before choosing the work.
“We need a better website” leaves too much open. “People asking about our services cannot tell whether we cover their area” gives you something specific to investigate. So does “Customers complete our contact form, but the team does not receive their requests.”
These problems need different responses. One may call for clearer service information. Another may call for repairing the enquiry process. A new visual design alone does not establish that either problem has been solved.
Start with a priority service, the customer you want to help and the next action they should be able to take.
Should you repair, improve or rebuild?
Use the evidence you have to choose an appropriate scope. These examples are starting points for a review, rather than automatic diagnoses.
| What you observe | Evidence to collect | A suitable first step | How to check the change |
|---|---|---|---|
| People misunderstand what you offer or where you work | Questions from real enquiries; the relevant service page | Clarify the offer, service area and next step | Check whether visitors can answer those questions and whether enquiries fit the service |
| A contact request does not reach your team | The path from form submission to receipt, including any errors | Repair that path and make failures understandable | Confirm a permitted test request reaches the intended destination |
| The website is difficult to use on a phone | The important pages and contact journey on the devices customers use | Improve the affected layout, controls or loading experience | Repeat the same journey on those devices |
| A new campaign has no page explaining its offer | The campaign promise and the page visitors reach | Create or improve a focused landing page | Check that the offer, relevant proof and contact action agree |
| Useful pages are missing from search | Search Console indexing and canonical information; the queries the pages answer | Diagnose search accessibility and content relevance | Review the next crawl and indexed status separately from rankings |
| The current system prevents necessary changes | Required features, editing needs and repeated constraints across the site | Compare a scoped rebuild with continued repairs | Review the new site against the agreed requirements and launch checks |
For missing search visibility, start with our guide to a website that is not showing on Google. For an enquiry problem, follow the walkthrough from a website visit to a received request.
When is a full rebuild justified?
A rebuild can be appropriate when the current structure or technology prevents important changes across the website, when essential integrations cannot be supported reliably, or when the business has changed enough that the current site no longer explains its services.
Be specific about those requirements. List what the new site must support, what can be reused and which constraints a rebuild will remove. Compare that scope with the work needed to improve the existing site.
A website looking old is a reason to review it. The review should also establish whether its content, navigation, mobile experience and contact paths still serve customers.
Our website design service explains how content, design and launch responsibilities fit into the project.
What should you keep if you rebuild?
Keep track of useful service content, established URLs, genuine project evidence and the questions your existing pages already answer.
In our published home services website redesign account, an established business wanted a more current site while protecting its existing search visibility. That concern belonged in the brief before the new design was finished.
For your own project, record which pages will stay, which addresses will change and where changed addresses should lead. Agree how service pages will connect, who controls the domain and hosting, and how search visibility and enquiry delivery will be checked after launch.
That is a more complete brief than a request for a visual refresh.
What belongs in a simple website plan?
Write a short brief that someone else can use to judge the proposed work.
- Priority service: Which part of the business should the website support first?
- Intended customer: Who needs that service, and what do they need to know before contacting you?
- Customer action: Should they call, request an estimate, book an appointment or send project details?
- Current obstacle: What is making that action difficult? Include what you observed and what is still uncertain.
- Proposed scope: Which pages, content, controls or integrations need attention? Explain why.
- Responsibility: Who supplies information, approves the work and handles enquiries after launch?
- Review measure: How will you check that the work addressed the original problem?
Set the budget around that scope. Separate the project fee, ongoing support, tools and any advertising spend. Our marketing budget guide explains how to connect those costs with the work you want to win.
What would that look like for a service business?
Illustrative example, not a client result: An electrical contractor wants more suitable enquiries for planned installation work. The website mainly describes emergency repairs, and the contact form gives visitors no useful way to explain a planned project.
The first task is to investigate that mismatch. A useful brief might call for a clearer installation page, appropriate examples of work and an enquiry path that lets customers describe the project.
If the existing site can support those changes, a focused improvement may address the problem. If its structure prevents those pages or its enquiry system cannot be made reliable, the review may support a wider rebuild.
Check the result against the original goal: can a prospective installation customer understand the service and send a useful request, and does that request reach the team? Later, review which enquiries were suitable and what happened to them. Visits, submitted requests and won work describe different stages.
What should you ask before accepting a redesign proposal?
Ask the provider to connect each part of the scope with a requirement in your brief.
- What evidence supports replacing the existing website?
- Which useful pages and URLs will be preserved?
- What content and genuine project material will the business need to supply?
- How will the important mobile and contact journeys be checked?
- Who owns the accounts, and who makes changes after handover?
- What is included in the project, and what requires ongoing work?
Once the scope is clear, use our website designer comparison guide to compare providers.
Start with the decision your business needs to make
A plan makes a website investment easier to evaluate. It connects the work to a specific problem, gives the team clear responsibilities and provides a way to review the result.
Bring your current website, the services you want to grow, examples of suitable enquiries and any evidence of the problem you are seeing. Talk through your website priorities with AMÁRQUEZ.