
The instinct when a brand starts to feel stale is to scrap the whole thing and start over. Sometimes that is genuinely the right call. More often, it is the expensive version of a fix that a much smaller move would have solved. Knowing the difference saves real money and real time.
What a Refresh Actually Fixes
A refresh keeps the foundation and updates the execution: a modernized color palette, a cleaner logo mark, updated typography, refreshed photography. The core identity of the business — what it stands for, who it serves — stays the same. What changes is how sharply that identity is expressed.
A refresh is the right move when:
- The brand still reflects what the business actually does, it just looks dated
- Customers still understand and trust what the business stands for
- The core name, mission, and positioning are still accurate
- The materials feel inconsistent with each other, more than they feel wrong
What Actually Requires a Rebuild
A rebuild starts over at the strategic level, not just the visual one. It is warranted when the business itself has fundamentally changed — a new audience, a new offering, a merger, a reputation problem serious enough that a new coat of paint cannot fix it. Trying to refresh your way out of a rebuild-level problem usually just delays the real work and spends money twice.
A rebuild is the right move when:
- The business has pivoted to a different audience or offering than the brand was built for
- The current brand actively works against the business — confusing people or repelling the right clients
- The name or positioning no longer describes what the business actually does
- Trust has been damaged badly enough that a fresh start is genuinely warranted
The Honest Test
Ask what is actually broken: the way the brand looks, or what the brand is trying to say. A look can be refreshed in weeks. A message that no longer fits the business needs to be rebuilt from the strategy up — no amount of new color palette fixes a business that has outgrown its own positioning.
The Alder Files starts every project with that question before touching a single visual element, because the wrong diagnosis wastes both budget and time on the wrong problem.