Every agency conversation about an underperforming website tends to arrive at the same recommendation, and it's worth noticing that the recommendation is also the more expensive one. That doesn't make it wrong — sometimes a full rebuild genuinely is the right call — but a business owner should be able to reach that conclusion independently, before the conversation with the person who benefits from the bigger number.
When repair is the right call
Repair covers a wider range of problems than most owners assume: broken forms, slow-loading pages, outdated content, a design that's dated but still structurally sound, missing pages the business now needs. None of these require rebuilding the site around them — they require someone competent going in and fixing the specific thing. If the underlying structure of the site can still do what the business needs, and the problems are specific and nameable, repair is very likely cheaper and faster, and it carries less risk than starting over.
When rebuild is the right call
A rebuild earns its cost when the foundation itself can't support what the business now needs from it — a platform that can't add features a competitor already offers, a structure so tangled that a simple content change takes hours of developer time, or a business that has changed enough (different offering, different customer, different positioning) that patching the old site would mean bolting a new identity onto an old skeleton. Accumulated small fixes are also a signal worth watching: if every fix this year has cost almost as much as last year's major project, the arithmetic is already arguing for a rebuild before anyone says the word out loud.
The tell most people miss
The question that actually separates these two isn't "how old is the site" — plenty of older sites are fine, and plenty of new ones are already limiting. The real question is whether the current foundation can support the specific change the business needs next. A five-year-old site that just needs a booking form added is a repair. A two-year-old site built on a platform that can't add a booking form at all is a rebuild, regardless of its age.
What to ask before agreeing to either
Before signing off on a number, ask for the specific list of what's broken and what each fix addresses, ask whether the current platform can support what's on the roadmap for the next year or two, and ask what repair would look like as the alternative. A legitimate rebuild quote should be able to explain why repair wasn't recommended instead, not just assert that a rebuild is needed. A vague answer to that last question is worth treating as a signal in itself.
Getting this right protects the part of a functioning business system that already works from being thrown out along with the part that doesn't. Our web team will tell a client honestly when repair is the cheaper, faster and correct answer, because a rebuild sold on inertia rather than need is a worse outcome for everyone except the invoice.
