Rebrand announcement day: theatre, then receipts

A rebrand has two launches. The first is announcement day: the film, the letter from the CEO, the new site shipping at 9am, the design Twitter hot takes by 9:04. The second is six months later, when someone searches for proof it worked. Most companies plan lavishly for the first and vaguely for the second. The second is the one that compounds.

Here's how we script announcement day — and what we insist happens afterwards.

The narrative is not "we have a new logo"

The single most common failure of rebrand announcements is that they're about the rebrand. Nobody outside your company cares that you have a new logo. They care — maybe — about what changed for them. The announcement that works answers, in order:

What changed in the world or the company that made the old brand wrong? There must be a real reason, and it has to be customer-legible. "We grew up" is not a reason. "We started as a butcher in 1987 and now three-quarters of you order online, so everything from the label to the checkout had to hold together" is a reason — that's the true one that anchored Tallow & Co.'s modernisation.
What stays? This is the reassurance beat, and heritage brands especially must land it. Change framed as continuation reads as confidence; change framed only as rupture reads as panic.
What the new system lets you feel or do that the old one couldn't. Faster, warmer, clearer, more useful — pick true ones.
Only then: here it is.

We call this the "why → what stays → what it unlocks → reveal" spine. Every asset on announcement day — the film, the email, the site's new homepage hero, the CEO post — tells that same four-beat story in its own length. Consistency across surfaces is what makes a launch feel inevitable instead of improvised.

The operational checklist nobody posts about

Announcement day is a deploy with publicity attached. The theatre gets the glory; the runbook gets you through. Ours includes:

One switchboard. A single owner (usually the producer) with a minute-by-minute schedule: DNS, site deploy, email send, social posts, press embargo lift, app-store assets. On the Copperline Mutual launch, the schedule had nineteen items between 6am and noon, and every one mattered to somebody's first impression.
Coordinated surface flip. The site, the app icons, the email headers, the social avatars and the PDF templates flip within the same hour. A half-flipped brand (new homepage, old error pages, old login screen) signals the rollout isn't done — see the rebrand rollout plan for cleaning the long tail before day one, not after.
The 404 and the old-URL redirect map. Press and customers will hit stale links all morning. Redirects decided the week before, not improvised at 9:20.
Support scripts. Your support team will get "what happened to the website?" tickets. Give them a two-line answer that's identical to the public story.
A rollback plan you hope is boring. If the deploy fails at 8:55, who decides to delay, and what's the holding message?

Handling the hot takes

There will be opinions. There will be a screenshot of the old and new logos side by side with a shrug emoji. Plan the posture in advance, because the worst announcements are the ones where the brand panics visibly.

Three rules we give every client:

Never defend the design on launch day. Defending reads as doubt. The brand's account can amplify praise and quietly absorb criticism; the case for the work lives in the narrative, the process write-up and — later — the numbers.
Do respond to corrections. Wrong facts ("they fired their whole team," "this cost $4M") get one warm, factual reply. Opinion gets none.
Watch for real signal under the snark. "I can't find the login button anymore" is not a hot take; it's a usability bug wearing the costume of one. Have someone from the product team triaging mentions for actionable complaints all day — launch traffic is the largest unmoderated user test you'll ever get for free.

Internal champions: the audience everyone forgets

The most consequential viewers of announcement day are your own staff. If the first time a customer-support rep sees the new brand is the public reveal, you've manufactured your first detractors in-house.

Two weeks before launch, we run an internal preview: the story, the system, and — critically — the why, told by someone who was in the room. Give people the language: a one-pager of "if someone asks, say this" that matches the external messaging. Pride is the multiplier here. When GLADE rebranded around ingredient honesty, the fulfilment team got labelled jars of the new packaging the morning before the reveal. By launch hour, the warehouse was posting it. You cannot buy that advocacy; you can only schedule it.

Receipts: the six-month case study

The theatre fades in a week. What remains is whether the new brand moves numbers. Which means the work of announcement day begins the day after: instrument everything.

Before launch, agree the metrics the rebrand is actually accountable for — branded search volume, direct traffic share, conversion rate on the new site, support-ticket sentiment, recruitment-campaign response, whatever matters to the business. Baseline them for a comparable period pre-launch. Then hold your nerve: except for catastrophic usability bugs, change nothing for a quarter, so the comparison is legible.

Six months later, publish the receipts — honestly, including the flat metrics. A "here's what the rebrand did, including what it didn't" case study is worth ten announcement films, because it's the artefact the next client's CFO reads. This is how the studio works on our own case studies too: the numbers on our work pages are illustrative for a concept studio, but the discipline — baseline, hold, compare, publish — is exactly what we run for clients. It's the same honesty-first instinct behind how we measure brand health without voodoo the rest of the time.

If you can't face publishing the numbers, that tells you something about the rebrand. Announcement day is theatre; the case study is the product.

Key takeaways

Script the narrative as "why → what stays → what it unlocks → reveal" — never "we have a new logo."
Treat launch day as a coordinated deploy: runbook, surface flip, redirects, support scripts, rollback.
Never defend the design on launch day; correct facts; mine the snark for real usability signal.
Preview internally two weeks early, with language and artefacts people can be proud of.
Baseline metrics before launch, hold steady for a quarter, publish honest receipts at six months.

FAQ

How long should announcement day run? The coordinated burst is one morning; the narrative campaign around it runs two to four weeks — reveal, process story, customer story, then quiet. Stretching the "ta-da" longer dilutes it.

Do we need a launch film? Only if you have something to show — motion identity, spaces, packaging in the world. A film of swatches and mood boards flatters the agency and bores the audience. A sharp letter plus a strong new site often beats a video.

Should we tease the rebrand in advance? A short tease (days, not months) works for consumer brands with engaged communities. For B2B, surprise-plus-clarity usually lands better than suspense. Never tease before the internal preview.

What if reaction is mostly negative? Distinguish velocity from direction. Loud negativity on day one with stable metrics is normal loss-aversion; it fades in weeks. Negative sentiment plus degrading conversion or retention after a month is signal. Pre-agree with leadership which evidence triggers a response, so nobody improvises under fire.

Where does announcement day sit in the rollout? Near the end, not the start. Sequence: strategy, identity, rollout planning, internal preview, surface flip, announce, measure. The reveal is the garnish; the rollout is the meal.