Website Repair or Rebuild? Choose a Sensible Scope
Choose a focused website repair when the problem is understood and the rest of the site can support the intended task. Consider a scoped rebuild when several important journeys depend on a structure that cannot be sensibly corrected in place. Start with evidence and scope, not the age of the design alone.
Define the problem before choosing the project
“We need a new website” is a possible conclusion, not a diagnosis. Write down what customers need to do, what they currently encounter and where that difference is visible. A form that sends to an old mailbox is different from an unsupported system with no maintainable way to update services. Neither observation establishes lost revenue by itself.
Use the lead path guide to inspect the public journey. Record unavailable information as unknown. Private routing, code and account settings need authorized access before anyone can claim to have checked them.
Compare the work you can actually define
| Question | A focused repair may fit | A wider scope may need investigation |
|---|---|---|
| Is the failure contained? | One contact action, layout defect or clearly bounded behavior fails. | Several journeys depend on the same unsuitable structure. |
| Can the site be maintained? | Authorized access and a supported way to make the change are available. | The platform, dependencies or ownership need investigation before a proposal. |
| Is the content usable? | Accurate service content can stay with a local correction. | The service structure and required content need coordinated revision. |
| Can success be tested? | The exact expected result and affected pages can be named. | The wider requirements still need discovery and agreement. |
A rebuild does not automatically solve email delivery, audience mismatch or unclear service facts. A repair is not automatically cheap or safe when its cause is unknown. The right choice depends on the actual system and an agreed boundary.
What a useful repair quote includes
- The observed defect, affected URL or component and supporting evidence.
- The intended change and any required access or client input.
- What is excluded, such as unrelated pages, new functions, hosting or paid plugins.
- A testable acceptance checklist, revision allowance, timing and payment milestones.
- The handover and support terms, including when support starts.
For example, a contact form delivery repair should name the intended record or mailbox and the relevant tests. A mobile repair should name the affected page and behavior rather than promise “perfect on every device.” Compare the mobile audit method with the proposed acceptance test.
What a scoped rebuild needs before work starts
A rebuild should identify the pages, service information, contact paths and client-supplied content. Agree whether existing URLs will remain and how any necessary changes will be redirected. Preserve working destinations and search ownership rather than treating a launch as permission to discard them. Google’s URL-change guidance is relevant when public URLs change.
Confirm account ownership, authorized access, responsibilities for third-party costs and the review process. A design preview alone does not establish functioning enquiry delivery, payment readiness or completed implementation. Do not agree to a date until required inputs and availability are understood.
Three illustrative decisions
Contained issue: The mobile call link points to an outdated number. Verify the correct business number, change the relevant link and check the dialer handoff. A complete visual rebuild is not supported by this finding alone.
Wider issue: The agreed service structure cannot be represented by the current page system without substantial changes. Document those constraints and compare an in-place revision with a scoped rebuild before quoting.
No evidenced defect: The contact path works in the observed conditions and the service information is accurate. Record the result. A new visual preference can still be discussed as design work, but should not be presented as a verified technical failure.
These examples are teaching scenarios, not customer cases or promised outcomes.
Compare scope before comparing prices
Check whether quotes include the same pages, content work, testing, revisions, handover and support. Separate one-off implementation from hosting, domains, licenses and future changes. A headline price without a clear boundary is difficult to assess.
LeadFlowCheck’s current service scope and USD budget tiers are published on the repair page. Paid work is separately quoted in writing. The project terms explain explicit acceptance and the 14-day bug support period; new requests fall outside the agreed defect support.
Start with the smallest justified next step
If the cause is not established, start with a diagnostic rather than choose a large implementation prematurely. The free LeadFlowCheck diagnostic is one page with up to three verified issues, screenshots and recommended fixes. You can use the findings yourself, share them with your existing developer or discuss separately scoped help.
Want evidence from your own website?
Request a free one-page diagnostic with up to three verified issues, supporting screenshots and recommended fixes. Implementation is optional and separately quoted.
Request a free diagnostic