Repair versus rebuild: compare the actual work

A long list of findings can make a rebuild sound inevitable. Before making that decision, group the issues by the work that resolves them. Several findings may belong to one fix package.

Compare scope as well as totals

A repair keeps the useful parts of the current site and addresses agreed problems. A rebuild can change the content model, templates and editing workflow. Those are different outcomes, so a fair comparison explains what each option buys and what remains afterwards.

Use thresholds as prompts, not conclusions

If a repair estimate crosses a comparison threshold, it is worth discussing the alternatives. It does not mean a rebuild is automatically cheaper. For example, a $1,900 WordPress repair shortlist should be compared with the scope of a $3,500 rebuild, not described as more expensive than one.

A practical checklist

• Deduplicate overlapping fixes.
• Identify structural limitations.
• Compare full scope and future maintenance.
• Agree the best-value option before payment.

What to do next

Start with one important page and one clearly defined problem. Keep a record of the original behaviour, make a controlled change and check the result. If you are not comfortable changing the site, the record gives a developer a useful starting point and makes the scope easier to agree.

A CHD website check can add public-page evidence to that conversation. The free result includes a score and up to three findings. The full $29 teardown includes the measured findings, practical guides, a private report and a PDF. Any repair work is reviewed and quoted before payment.