A rebrand costs roughly whatever its rollout costs, because the identity itself (name, logo, colours, type) is usually the smaller part of the bill. What sets the price is how many places the brand has to change, and how the brand was built in the first place. A brand that lives in a PDF has to be redone by hand everywhere it appears. A brand built as a system can be changed in one place and pushed out everywhere, which makes this rebrand cheaper and every change after it cheaper still.
Where the money actually goes
When people picture a rebrand they tend to picture the reveal: the new logo on a big screen, a short film, a round of applause from staff who have been asked to clap. That part is real work, and it isn't free. In most established businesses, though, it's the smaller part of the bill.
The money goes on rollout, which is to say getting the new brand onto every app screen, web page, branch, form, email template and statement the business already has. Digital products are usually the priciest, because the brand tends to be hard-coded into them screen by screen. A change of colour becomes a small software project, and a few dozen of those become a large one.
What moves the cost, roughly in order:
Scope. A refresh of an existing identity costs far less than a new name and positioning built from scratch, which needs research and testing behind it.
Touchpoints. How many places customers meet the brand, and how hard each one is to change.
How the brand is built. If it lives in shared, reusable parts, much of the change happens once. If every screen and template was made separately, each one gets changed separately, and paid for separately.
Whether the business keeps moving. Freezing product work for a rebrand carries its own cost, usually a larger one than anybody budgets for.
Ask for the identity and the rollout to be quoted separately. It's the only way to compare one proposal with another without being charmed by the mood boards.
The trouble with the brand bible
Most brands are still handed over as a book. Sometimes a very large one, with a section on the exact clear space around the logo and another on which blue may stand next to which grey. It's thorough, it's beautifully laid out, and almost nobody reads it twice.
The effort isn't the problem. A document can only describe a brand, so somebody still has to interpret it by hand every time a new screen, form or campaign gets made, and every interpretation drifts a little. Spread that across a few agencies, three product teams and five years, and the brand now exists in several slightly different versions, each of them on-brand according to someone. When something finally needs to change, every one of those versions has to be found and fixed. That's the rollout bill, arriving in instalments for as long as the brand lives.
Build the brand like software
The alternative is to build a brand the way good digital products are built. Atomic design, a term the designer Brad Frost coined for assembling interfaces from their smallest parts, is a useful way to think about it. Start with the brand's indivisible building blocks: colour, type, spacing, shape, motion, tone of voice. Define each one once. Then define how they relate to one another in context: which combinations work, how they scale, and what shifts between a phone screen and a billboard. A responsive website manages this with a handful of breakpoints instead of a separate design for every device, and a brand can do the same.
What you get is a few simple rules instead of a thousand pages of them, and the rules live inside the assets instead of in a document describing them. Colours, type and components are stored as design tokens and exported ready to use, in the design files and in the code. Designers and developers draw from the same source, so there is nothing left to interpret.
The payoff arrives the first time anything changes. Adjust a colour, a typeface or the curve of a corner in the system and it flows through every product and template that uses it, in one release. Version control stops being an act of faith, and the next evolution of the brand (there is always a next one) costs a fraction of this one.
Pay a little more once, a lot less every year after
A brand built this way usually costs a little more to make, because someone has to think in systems before anyone gets to the mood boards. That premium is easy to win back. Every later change, whether it's a refreshed palette, a new product line or an acquisition, becomes an update to the system instead of a project of its own.
The bigger saving is in the running costs that never appear in a rebrand budget. A traditional brand needs people to police it: brand managers checking layouts against the guidelines, QA teams catching the wrong blue before it ships, agency hours spent rebuilding the same banner in twelve sizes. An unbreakable set of ready-made components takes much of that work off the table, because the rules are enforced by the components themselves rather than by someone with a PDF open in another tab.
It also makes the brand usable by machines. Components with their rules built in are exactly what AI tools and automated production need to turn out on-brand work at volume, from a hundred ad variants to a different email for every customer. A brand that lives in a document can't be handed to software. A brand built as a system already speaks its language.
Designed for experience from day one
A system like this has a second benefit, and it matters more than tidiness. Because it's built for screens from the outset, it can carry how the brand behaves as well as how it looks: the way a page moves, say, or how it feels when a payment goes through. Those interactions and motion patterns can be designed into the system as ready-made components and code snippets, which product teams can paste into whatever they're building and ship.
That's where most people actually meet a brand now, in the many small moments of using a product. A logo gets admired once. Those moments get experienced every day, and designing them into the brand from the start costs a great deal less than retrofitting them later.
Most rebrands stall after the launch party
The reveal goes well, as reveals do. Then the rollout begins, budgets tighten, product teams return to their own roadmaps, and eighteen months later the new brand lives on the website and the billboards while the app, the forms and the statements carry on in the old one. Customers, who were never consulted on any of this, now deal with two companies that happen to share a name.
It's the most common way rebrands go wrong, and it's a planning failure far more often than a design one. A brand delivered as a book has to be rolled out by hand. A brand delivered as a system does much of the rolling out by itself.
How to roll out a rebrand without a rebuild
Audit every touchpoint first. List everything a customer sees, how much traffic each one gets and how hard it is to change. You can't plan a rollout you haven't mapped.
Build the system before the screens. Define the brand's building blocks as design tokens and components, wired into your design files and your codebase, so the brand lives in one place instead of inside individual screens. Do this first and much of the rollout becomes an update.
Prioritise by exposure. Change what most customers see first, like the app home screen, the website and the most-used emails, and let the long tail follow on a schedule.
Run it alongside live work. Agree with your product teams how brand changes will slot into their existing releases, instead of freezing everything for a big-bang launch.
Set a date for done. Decide what must change for launch, what can follow, and the day the old brand is officially retired. Without that date, it never quite is.
Before any of that, do you need one?
Sometimes the answer is no, which also happens to be the cheapest answer available. If customers don't understand what you do, a sharper proposition and better messaging may fix it for a fraction of the price.
A rebrand earns its cost when the business itself has changed, after a merger, a move into new markets or a genuinely new strategy, and the old brand is actively holding it back. If you can't say what the new brand needs to do that the current one can't, the honest advice is to wait.
What it looks like when the rollout is planned
When Momentum introduced its new brand, the Momentum Money app and web experience needed to come into line with it. The brief was to get there without the cost and delay of rebuilding the product, and without pausing live product work.
We brought the app and web experience in line with the new brand in 12 weeks, without a costly rebuild and without stalling that work. Read the Momentum case study.
Quick answers
What is atomic design in branding?
Building a brand from its smallest indivisible parts, like colour, type, spacing, shape, motion and tone of voice, each defined once, with a few simple rules for how they combine in context. The idea comes from Brad Frost's approach to interface design. The result behaves like software: change one element and it updates everywhere it's used.
What are design tokens?
Named values for a brand's basic decisions, such as a primary colour, a type size or a corner radius, stored in one place and used by both design tools and code. Change the token and every screen and template that uses it updates with it.
How long does a rebrand take?
A refresh can take a few months. A full rebrand with research, naming and rollout across apps and branches can run well over a year, and most of that time goes on rollout. Building the brand as a system first is the surest way to shorten the back half.
Where we stand
The time to think about a rebrand's rollout is before anyone opens a design file, and the best rebrand is the one that makes every future change cheaper than this one. In practice that means a brand built as a system with a few clear rules, not a book that gets more expensive every time somebody opens it.
Brand experience design is a core part of what we do at Armada. Ernst van der Merwe, our co-founder, has 19 years in marketing strategy and customer experience design, and was ranked among the top five information architects in Africa and the Middle East in the 2020 Loeries Official Rankings. We help businesses decide whether they need a new brand at all and, when they do, build it as a system that's ready for digital from the first day, then roll it out across apps, sites and services without a rebuild.
If a rebrand is on next year's list, talk to us before you brief anyone.
Let’s keep in touch.
Follow Armada on LinkedIn for new articles as they go up.