Repair or rebuild? Start with the failure your customers can see
Compare focused repairs with a rebuild using a small set of real tasks and access checks.
A slow page, missing enquiry or broken booking button does not automatically mean the entire website needs replacing. Start with the visible failure and the business effect.
Record the page, device, approximate time and steps that produced the problem. Remove private information from screenshots. If customers have reported the same issue, group those reports without assuming every complaint has the same cause.
Check the parts you can keep
A useful service library, approved photography and a familiar editing process may be worth preserving. The problem might sit in an outdated component, an oversized image or a connection that has stopped working.
Access matters too. Confirm which domain, hosting and content accounts the business controls. A repair estimate based only on public pages will carry uncertainty until the underlying system can be inspected safely.
Compare options around outcomes
Ask for a focused repair option and, where justified, a rebuild option. Each should explain what customer tasks it addresses, what remains uncertain and what future work may still be needed. Avoid comparing proposals solely by page count.
The Australian Government's website guidance is a useful baseline for ownership and planning questions. Your decision should also account for content quality, accessibility, staff editing and any connected sales process.
Make acceptance visible
If the problem is lost enquiries, send a clearly labelled test through the form and have staff confirm receipt. If the problem is mobile booking, complete that journey on the intended devices. A developer's statement that the code was updated is only part of the evidence.
Our care and repair service begins with a specific problem and a scoped investigation. When rebuilding makes sense, the findings can inform a better brief rather than disappearing into a second round of discovery.