A rebrand is a legitimate move for legitimate reasons. Used as a treatment for relevance decay it addresses the symptom and leaves the mechanism entirely intact.
Why it appeals
Decay presents as a business that feels dated, and a rebrand makes it feel current immediately. It is visible, it is a project with an end date, and it produces a moment where everyone can see something happened. Almost nothing else about this problem offers that.
What it actually fixes
Genuinely quite a lot, briefly. Language drift is corrected, because everything is rewritten. Evidence gets refreshed, because the new site needs proof. Some expectation inflation is addressed, because the rebuild adopts current conventions.
Three of the four mechanisms are reset at once, which is why it works and why it feels like a solution.
What it does not fix
The absence of any process that would have caught the drift. On the day the rebrand launches, alignment is perfect and decay resumes at the same rate, from a new starting point, with the same nothing watching it.
It also frequently damages the slowest and most valuable signal the business had: independent references built up under the old name, records that no longer resolve, and a public history that now looks shorter than it is.
The cost nobody prices
Corroboration accumulated over a decade is partly attached to a name. Changing it does not transfer that automatically, and rebuilding it takes years. A business that rebrands to feel current can lose the thing that made it credible, and the loss appears long after the project is declared a success.
When a rebrand is the right answer
When the name or identity is actively wrong: it describes a business that no longer exists, it carries a genuine liability, or it prevents the company from being understood at all. Those are structural problems that maintenance cannot fix.
The case on this site is the exception, and it is worth saying why
This site's proof story is a rebrand, which makes it a fair question whether the argument above contradicts it. It does not, and the reason is the test in the paragraph before this one. Stratus Building Solutions sounded like a construction company and was a commercial cleaning franchise. The name did not merely feel dated; it prevented the company from being understood at all, which is the one condition under which maintenance cannot help.
The more useful half is what happened around it. The identity change was not the treatment, it was the last piece of a four-year transformation of reviews, recruitment, training, data and accountability, and the growth it is often credited with happened before the new name existed. A rebrand used on its own would have reset the clock here too. What made the difference was recognizing that the system underneath had moved, which is a condition to keep watching rather than a project to finish.
The alternative
Continuous maintenance is duller, cheaper, and does not produce a launch moment. It also does not reset the entity, does not discard the history, and does not require the same conversation again in four years. That is the whole argument for treating alignment as a condition rather than a project.