Name the problem before the solution.
A redesign makes sense when the current structure, content or platform gets in the way of the work the site needs to do. Age or a new visual trend is not enough to decide.
Start by writing one concrete issue: “The contact button points to the old address” is actionable. “The site feels dated” needs more investigation. A focused correction may solve the first issue without replacing the site.
Repair, refresh or rebuild?
- Repair
- The service information is clear and the platform still works, but a few links, photos or details are wrong. List the corrections and request a focused scope.
- Refresh
- The structure is useful, but the copy, phone layout or visual hierarchy needs work. Keep the pages and URLs that still serve a purpose; agree which sections change.
- Rebuild
- The site cannot support the required customer action, is difficult to maintain, or needs a substantially different structure. Review the platform and migration work before choosing a replacement.
A service changed. The site didn’t.
A business now focuses on repair visits, but its homepage still leads with an older service. If the existing site is usable, changing the headline, navigation emphasis, photos and inquiry instructions may address the mismatch.
If customers also need to book a time and the platform cannot support the agreed booking process, that is a different scope. Confirm whether booking is required before paying for an integration or a rebuild.
Know what you must keep.
- List current pages and their URLs, including useful downloads.
- Identify accurate service copy, permitted photos and branding worth keeping.
- Record the main contact route and the person who confirms it works.
- Identify who owns the domain, hosting and business email accounts.
- Check which outside tools, licenses and integrations depend on the site.
- Use existing search reports, where available, to find pages visitors already use.
When a URL changes, plan its destination and any redirect. Keep a recoverable copy of the old site and test the new contact route before launch. Updating the website should not accidentally interrupt business email.
Define a useful finish line.
Agree observable acceptance checks: service facts are accurate, the intended pages work on phone and desktop, links reach the right places, the inquiry reaches the intended inbox, and the owner has the agreed files and account access.
Later, review actual received inquiries and business outcomes separately from visits. A visual change does not establish a sales increase; rankings, inquiries and sales cannot be guaranteed.
A clear problem list makes it easier to compare a repair quote with a rebuild quote. Use the website quote checklist and see Quattro’s current options.
