Before launch: map every surface
Start with an inventory of the places the identity appears. Website, product interface, login and email templates, sales deck, proposal and contract documents, customer support macros, social profiles, directory listings, app store entries, signage, merchandise, the favicon, the sender name on outbound email.
Give each surface an owner and a status: ready at launch, updated within the first week, or updated within thirty days. Not everything has to flip at once, but everything needs a name attached to it. The most common failure is not a bad identity; it is a launch where the homepage is new and the invoice template is two years old.
If the domain is changing, treat redirects and email continuity as first-class workstreams with their own owner, not as an afterthought for whoever manages DNS.
Week one: the surfaces people check first
When the announcement goes out, people do not read the manifesto—they check a small number of places to confirm you are still you. Prioritise those:
- The website homepage and navigation, including page titles and metadata.
- Outbound email: sender name, reply-to address and signature block.
- The product’s login screen and any empty states or transactional emails.
- Social and directory profiles that appear in a search for the old name.
- The sales deck and one-page intro the team actually sends.
Updating these in the first week prevents the strangest failure mode of a rebrand: a prospect who hears the new name, searches the old one, and concludes the company is in trouble.
Domains, redirects and email continuity
If the address changes, plan the cutover before the announcement, not during it. Map every old URL that receives traffic or backlinks to its new equivalent; a blanket redirect to the homepage throws away the context someone was trying to reach. Keep the old domain resolving and redirecting for as long as you reasonably can—years, not weeks.
Email is the part customers feel. Decide the cutover window, keep the old address accepting mail through an alias period, and tell existing customers what will change and when in plain language. A short, practical note (“we are now hello@newname.com; the old address keeps working until [date]”) does more for trust than a launch film.
Update the places that verify you: domain records for email deliverability, security and ownership allow-lists your customers rely on, and any integration where your domain is part of an authentication flow.
Bring the team before the market
The team should hear the new name from you before they hear it from a customer. Run an internal session that covers three things: what has changed, why the new identity fits the company now, and what remains consistent for customers.
Give colleagues the one-paragraph explanation they can use verbatim, plus answers to the two questions they will actually be asked: “why the change?” and “does this affect my account or contract?” Existing customers need reassurance and practical information more than a creative manifesto.
Make the correct assets the easy assets. Put approved wordmarks, templates, signatures and slide masters somewhere obvious, and name a person who owns the system after launch so questions have somewhere to go.
By day thirty: the consistency check
Around day thirty, do a deliberate sweep. Search the old name and walk the first two results pages as a stranger would. Open a real sales email, a support reply, an invoice and a contract. Load the product on a phone. Look at the deck a colleague sent last week.
You are looking for stragglers: an old logo in a template, an old sender name, a profile that never got renamed, a PDF still circulating. Fix them, and add the missed surface to the inventory so the next launch starts from a complete map.
Consistency at day thirty is what makes the identity feel decided rather than improvised. It is also the point where the internal story and the external story finally match.
What to watch after launch
Track the frictions you set out to reduce, not vanity signals. Are introductions landing without spelling corrections? Are mistaken visits and misdirected email down? Is search sending the old name to the right place? Ask the team who talks to customers most what they are hearing in the first weeks.
Expect a quiet period of adjustment; recognition rebuilds with repetition, not with a single announcement. Resist reading early noise as evidence the name was wrong. Judge the change against the problems named in the brief, over a quarter, not a fortnight.
If you are still deciding whether to rebrand at all, start with the founder’s guide to rebranding after funding. If the launch involves a new address, pair this with the .com decision.