Rebrand or refresh, and how to tell which you need
The three situations that justify a full rebrand, why most deep tech companies need a refresh instead, and how to build the internal case for either.
- Three situations justify a rebrand: the category moved, the name is wrong or blocked, or the brand actively misdescribes the product. Everything else is a refresh.
- A refresh settles the position again and makes the surfaces agree. It is smaller, faster and usually the honest answer.
- Redesigning the visual system without resettling the position fixes the symptom and keeps the disease.
- The business case is not aesthetic. It is the gap between how good the engineering is and how quickly a qualified stranger understands it.
Most companies asking for a rebrand need a refresh, and most companies asking for a refresh have not settled the position that would make either work. Here is how to tell them apart.
What is the actual difference?
A refresh changes how the company presents. A rebrand changes what it claims to be.
That is the useful line, and it is not about how much visual work is involved. A refresh can include a new type system, new photography, a rebuilt site and a new deck, and still be a refresh, because the category, the name and the fundamental claim survive.
A rebrand replaces the claim. New category, new name, or a fundamentally different account of what the company is. The visual work is the consequence, not the definition.
When is a rebrand genuinely justified?
Three situations, and none of them is that the founders are bored of the logo.
The category moved. A component supplier becoming a platform company, a tools company becoming infrastructure, a services business becoming a product. The old brand accurately describes a business you no longer run.
The name is wrong, blocked or borrowed. A trademark problem, a name inherited from a lab or a parent you have separated from, or a name built around one product that the roadmap has outgrown.
The brand actively misdescribes the product. The one case where doing nothing is more expensive than acting. If a qualified buyer reads your page and forms a wrong impression of what you do, every marketing pound after that is spent attracting the wrong people.
Why is a refresh usually the right answer?
Because the common problem is incoherence, not wrongness.
By Series B most deep tech companies have three years of accretion. The deck says one thing, the site another, the booth panel a third, the product pages were written by whoever had time. Nobody chose to become incoherent; it happened one deadline at a time.
That does not need a new identity. It needs the position settled again now the company knows what it actually sells, and then the surfaces made to agree. Smaller, faster, and it does not spend the recognition you have already built.
What goes wrong when companies get this call wrong?
Two failure modes, in opposite directions.
Rebranding when a refresh was needed throws away accumulated recognition and buys eighteen months of explaining that you are the same company. In a category with forty real buyers worldwide, that recognition is worth more than it looks on a slide.
Refreshing when a rebrand was needed is the more common and more expensive error. The visual system gets redone, the position underneath stays wrong, and eighteen months later the same conversation happens again with a larger budget. Redesigning without resettling the position fixes the symptom and keeps the disease.
How do we build the internal case?
Not aesthetically. Nobody approves a budget because the logo feels dated.
The case is the gap between how good the engineering is and how quickly a qualified stranger understands it. That gap is measurable in a crude but persuasive way: show the current page to three technical people who have never seen the company and time how long before they can say back what you do. Under twenty seconds, your problem is elsewhere. Over a minute, you have a number to take to a board.
The second half of the case is the calendar. Brand work sequenced against a real date, a raise, a tender, a product launch, is easier to justify and easier to schedule than work with no deadline attached. The corollary is that if there is no date, the work will keep slipping regardless of how much everyone agrees it is needed.
Does the timing change the answer?
It changes what is affordable, not what is correct.
Ahead of a raise, the constraint is usually the calendar. Nine to sixteen weeks is the full sequence, so a rebrand started six weeks before a round is a compressed run with fewer routes explored, and the compression comes out of exploration rather than out of technical review.
After a raise is the more comfortable moment and the one most often wasted, because the urgency disappears the day the money lands.
What if we cannot tell?
Answer one question: if you kept the current name and visual system exactly as they are, but rewrote every word on the site to be accurate and well ordered, would the problem be solved?
If yes, you need a refresh, and possibly only the narrative half of one. If no, and the reason is that the words would still be describing the wrong category or the wrong company, that is a rebrand.
Most companies who sit with that question honestly find they are in the first group.
Written by Mejo Kuriachan. More in the blog, the glossary and the FAQ.