What should happen before you replace a business website?
Define the customer and operational job of the website before committing the company to a visual redesign or platform replacement.
Start with the reason for change
“The website feels old” may be true, but it is not yet a useful scope. The business may need clearer positioning, better qualified inquiries, easier publishing, customer self-service, stronger search visibility or a more reliable handoff to the team.
Each need points to different work. Naming the outcome prevents a broad redesign from absorbing problems it cannot solve.
Decision tool: define the job before the project. Complete this sentence without naming a platform or design style: “The website needs to help [specific visitor] [complete or understand something] so the business can [observable outcome].” If the team cannot agree, the replacement scope is not ready.
Follow a real visitor into the operation
Choose important customer journeys and trace them end to end. What question brings someone to the site? What must they understand? What action should they take? Which person or system receives that action? What information is required to serve it well?
A form is not successful merely because it submits. It must create a useful next step for the visitor and the business.
Separate content, process and platform problems
Weak positioning is not fixed by changing a content-management system. A slow internal response is not fixed by increasing button contrast. A platform should be replaced when its real limits prevent an important outcome or create unacceptable risk—not because another platform is fashionable.
Sometimes focused content, performance, accessibility or integration work is enough. Sometimes a new site is justified. The distinction matters to cost and disruption.
Preserve what already has value
Before migration, identify pages that attract useful visitors, links that support authority, analytics or search data worth retaining, and content the team still relies on. Document redirects, forms, integrations, ownership and deployment before the old site disappears.
Agree on the measure before launch
Useful measures may include qualified inquiries, completion of a customer task, response time after submission, publishing effort, accessibility, page speed or search visibility. The metric should match the original reason for change.
A new website is worthwhile when it becomes better infrastructure for the business, not simply a newer collection of pages.
See how Ashford approaches websites as business infrastructure.