Do We Need a New Website?
Sometimes. First, identify what the current site cannot do.
A dated appearance does not explain every website problem, and a rebuild does not automatically fix the offer or follow-up. Start with the user tasks, business needs, and constraints the site must support.
Separate the problem into useful categories.
Content and message
People cannot understand the offer, find answers, or see a relevant next step.
Experience and function
Navigation, mobile layouts, forms, accessibility, or performance interfere with the task.
Structure and maintenance
The platform or content model makes necessary updates fragile, slow, or impractical.
Compare improvement with replacement.
Both options need a clear scope.
Focused improvement
Appropriate when the foundation works and the main problems can be addressed in specific pages, components, or workflows.
A larger rebuild
Worth considering when fundamental architecture, maintainability, or required capabilities cannot reasonably be improved within the existing setup.
Decide what must survive either path.
Inventory valuable content, working forms, important URLs, search visibility, analytics, integrations, and editor workflows. A new design should not accidentally discard those assets.
Use the findings to write acceptance criteria. For example, editors can maintain a service page without changing code, or a mobile visitor can complete a request with clear feedback. Concrete criteria make a rebuild easier to evaluate than a general instruction to make the site modern.
Useful follow-up questions
Can design and content changes happen before a full rebuild?
Yes, if the current architecture supports them safely. A phased plan can address high-priority friction while the larger requirements and migration needs are assessed.