What needs changing and what works well on your website
Your website has been running for years and concerns are accumulating: updates are difficult, some pages are slow or the business needs a missing function. “Should we replace it?” comes up quickly. You do not always need a new website. If the problem affects one feature, a focused fix may be enough. If limitations prevent several things that matter to the business, compare a partial renewal with a new website.
Age and appearance provide context, but do not determine project scope. One area may need substantial work while other parts remain useful.
Describe a few verifiable situations: publishing a service without technical help, completing an enquiry on a phone or synchronising information with another system. They provide a common basis for comparing proposals.
Compare three approaches to the same need
| Approach | When to consider it | What needs checking |
|---|---|---|
| Focused correction | The problem is localised and the rest supports the business. | Cause, dependencies and the affected function. |
| Partial renewal | A section or function needs broader changes. | How it will work with the retained parts. |
| Rebuild | Foundational limitations constrain several important needs. | Feasibility, migration, continuity and future maintenance. |
Include the cost of running the solution: maintenance, licences, hosting and your team’s time. A lower initial price may involve more work later. If the system changes, consider migration and training for the people who will use it.
No approach wins by default. Explain what each resolves, what remains open and the transition risks it introduces. Meaningful cost and timing comparisons require sufficiently defined scope.
A comparison case: a catalogue that is hard to update
Fictional example comparing scope. It contains no client prices, delivery times or results.
A company can display products, but adding references involves manual work and filtering is unhelpful. Its homepage, service content and enquiry form still serve their purposes.
A focused correction might address an import fault. Partial renewal might replace catalogue management and search. A rebuild might be justified if data structure and other underlying limitations prevent those functions and upcoming needs from being supported.
The actual conditions still need investigating. Review how information enters the system, what data the business needs and which systems participate before choosing. The example frames a review; it does not establish a technology choice from outside.
Make what is worth keeping visible
List useful pages, current content, incoming enquiries, essential connections and tasks your team already knows how to perform. Include account ownership, access and available documentation.
If page addresses change, work with your team to decide where each old address should lead. Where appropriate, a permanent redirect will take the visitor to the equivalent new page. Sending every old page to the homepage may leave visitors without the content they wanted. Check internal links and the sitemap too. Google describes that work in its guide to site moves with URL changes. Transition planning belongs in a rebuild, even when it is barely visible in a design mock-up.
For WordPress, a component and dependency inventory helps establish what would stay or be replaced. If speed is the main concern, first document the affected pages and tasks.
Questions to ask when assessing a proposal
- Which specific need does it address, and what evidence supports its scope?
- Which existing parts are retained, replaced or retired?
- Which content, data and integrations must move?
- How will essential journeys be checked before release?
- Who will maintain the system, and what will they need?
- What happens if the change cannot go live as planned?
Involve the existing team or provider where appropriate. Their knowledge can clarify dependencies and avoid unnecessary work. Our guide to improvement scope and acceptance checks helps turn the discussion into a reviewable proposal.
Choose the scope once its consequences are understood
A sound decision may be a focused fix, partial renewal or rebuild. It may also be to keep what works and plan a later change. Be able to explain the need addressed and what remains outside scope.
If you need that foundation before commissioning work, Nodo91 can help with a website assessment. Use our priority matrix to organise the needs you have identified and keep unanswered questions visible.