Refresh your website or build a new one: decide using evidence of what fails

First list the tasks that fail on the current website. Outdated text may need editing; a journey incompatible with the business may justify reorganisation; a technical foundation without continuity may require rebuilding. Age and appearance alone do not decide. Compare the cost, risk and expected result of fixing, refreshing or replacing, preserving content, URLs and services that remain useful.

By Lyntev. Updated on .
About 6 minutes to read.

From data to the next decisionChoose the question, define the calculation and act on the result.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Distinguish content, interface and infrastructure problems
  • Compare a limited intervention with rebuilding
  • Preserve what works and define acceptance

Describe the problem as an observable task

Replace “it is old” with descriptions another person can test: I cannot find the services, the enquiry does not arrive or the team cannot update opening hours. Record the device, page and steps. Add the likely operational consequence without inventing lost sales. An observed difficulty justifies investigation; it does not automatically let you estimate how many customers left the business because of it.

Gather customer questions, support incidents and team needs. Separate facts from preferences. An unsuitable visual identity may deserve renewal, but explain it through examples of inconsistency, readability or positioning. Ask the supplier to show how the proposal addresses those points. A beautiful new presentation may retain exactly the same problem in the form or response process.

Know what you are replacing and what needs preserving

Inventory pages, documents, photographs, forms, integrations, accounts and suppliers. Identify content that remains correct and URLs already shared in materials or profiles. Check the domain, email and access. Many rebuilds grow larger because dependencies are only discovered after work starts. Having a list does not mean keeping everything, but it allows an informed decision.

Also record less visible functions: enquiry confirmations, email sending, restricted areas and backups. A new website can look finished without replacing those operations. Request a usable copy of material to preserve, with rights and sensitive data handled appropriately. Do not switch off the source before checking the destination. The plan should include what happens if publication needs to be reversed.

Compare three levels of intervention

Request a proposal for limited corrections, another for renewal and, where necessary, one for rebuilding. Compare the same acceptance tasks. A smaller intervention may be sufficient and allow you to assess the result before investing more. A larger intervention may make sense where the structure or dependencies prevent essential changes with proportionate effort and risk.

Do not choose solely by the lowest construction estimate. Include maintenance, training, content transfer and continuity. If the current foundation still allows safe publishing and meets requirements, a preference for a new tool needs a concrete benefit. If nobody can maintain or recover the system, request a diagnosis of that limitation rather than accepting a vague statement about old technology.

Compare three levels of intervention
InterventionWhen to consider itEvidence requested
Targeted correctionBounded content or functionality problemsThe same task works without side effects
Renewal of presentation and structureThe offer is right but navigation and language are unsuitableJourneys and identity reviewed with content preserved
RebuildingEssential requirements incompatible with the foundation or continuityFunctionality demonstration and migration plan
Successive phasesThere is uncertainty or limited operational capacityA useful first phase, criteria for proceeding and clear costs

Assess quality during the work, not only at the end

W3C evaluation guidance recommends checking accessibility early and throughout development. Initial checks help detect barriers but are not a complete evaluation. Use them to formulate tasks and request competent review where needed. An automated report without reading and practical testing does not demonstrate that the whole experience has been resolved.

Define review points: opening and navigation, service page, contact and other functions. Test with keyboard use, enlargement and mobile without requiring customers to know technical terms. Keep evidence of the approved version. If a visual change makes a button hard to find or moves content during form completion, correct it before extending the design. Renewal should make use and maintenance easier as well as improve appearance.

Fictitious scenario: an equipment maintenance business

A fictitious business considers replacing its website because it receives questions about services it no longer provides. Diagnosis shows that the homepage highlights an old offer and that enquiries arrive correctly. The first phase revises the offer, organises services and updates authorised photographs. Rebuilding the whole system immediately is not necessary to check whether the information is now understood.

Later, the business needs an area for tracking maintenance work. The decision now involves authentication, data and rules absent from the original website. That work receives its own specification and a phased proposal. The example does not prove savings or commercial growth. It shows that an editorial need and a management application can differ in scale, and the choice should follow the actual problem.

Approve the result through the task and continuity

Reuse the cases recorded during diagnosis and compare before and after. Ask someone who did not take part in the project to find the service and submit a test enquiry. Check the destination and the team’s response. Approval should reference the version and test conditions; a screenshot of a different page does not prove the original problem was corrected.

Also check editing, access and handed-over material. If the website uses a new dashboard, the person responsible needs to make a routine change and recognise when to ask for support. Confirm that important old URLs have the planned treatment and email has not been interrupted. Detailed technical migration should be planned with the supplier; this guide helps decide scope and accept the result without forgetting operations.

  • The initial problems have documented test results.
  • Preserved content and functionality have been checked at the destination.
  • The team can maintain information and obtain support.
  • There is a rollback plan and a list of genuine outstanding issues.

Prepare a decision that explains the investment

Complete the worksheet before accepting a proposal. Also record what will not change and why: it may be correct, little used or need further investigation. Deferring a function should be a conscious decision with a review signal rather than an oversight. A small first phase can be a sound option when it addresses a priority need and preserves future development.

After publication, monitor the tasks and contacts the website should support. Do not conclude that a difference in visits during the first days results only from the new design. Campaigns, seasonality and other changes also interfere. Use operational records to confirm that the team receives suitable enquiries and can respond. Future improvements should follow this observation and the problems still found.

Worksheet for your project

Website renewal decision
Observable problems and pages:
Evidence and conditions of current tests:
Content, URLs and functions to preserve:
Dependencies, access and continuity:
Corrections, renewal and rebuilding compared:
Transition, maintenance and training costs:
First phase and acceptance criteria:
Rollback plan:
Outstanding issues and condition for the next phase:
Person responsible for the decision and review:

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.