A short guide to rebuilding versus refreshing

This is one of those topics that looks small until it costs you something. Everything we would tell a client about rebuilding versus refreshing in the time it takes to drink a coffee.

The projects that go badly are rarely the ones with the hardest technical problems. Assume whoever inherits this will have half your context and none of your patience.

What is actually at stake

A rebuild is not always the answer. There is a version of this that is over-engineered, and it is worth avoiding. It rarely shows up as a line item, which is exactly why it slips.

The practical version

If the structure is sound, styling and content may be enough. In practice this is a scheduling problem more than a technical one. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

Where it usually goes wrong

Rebuild when the platform blocks what you need to do. The reasoning matters more than the rule, because the rule has exceptions. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

The short version

Clear scope protects the client at least as much as it protects the agency. Three things worth confirming about rebuilding versus refreshing before you move on:

• Someone can say what the current setup is without going to look
• Rebuild when the platform blocks what you need to do — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Pick the one that would hurt most if it failed, and start there.