By Mehdi HassanWhat are the steps in a rebranding process?
The rebranding process has nine steps, grouped in three phases: decide (audit, scope, positioning), design (name and domain, identity, product UI) and migrate (website and SEO, sales and support materials, launch). Most guides cover the first two phases well and the third barely at all, yet the third is where SaaS rebrands go wrong.
The goal for a SaaS company is a rebrand that's a non-event for customers: they log in, see a new look, and nothing breaks. That takes planning across marketing, product and engineering. For the strategic background on when and why to rebrand, see our hub on rebranding a startup.
Phase | Steps | Main owner |
|---|---|---|
Decide | Audit, scope, positioning | Founders and marketing |
Design | Name and domain, identity, product UI tokens | Design, with product |
Migrate | Website and SEO, sales and support, launch | Marketing, engineering, sales, support |
How do you start a rebrand: audit, scope and positioning?
Start with an audit of every touchpoint and real customer feedback, use it to decide the scope, and settle positioning before any design begins. These three steps take the least time and prevent the most rework.
1. Audit
List every place the brand appears: site, app, emails, invoices, decks, docs, app stores, socials, review sites, partner listings. Talk to a handful of customers and prospects about how they describe you and what almost stopped them buying.
2. Scope
Decide between a refresh, an evolution or a full rebrand. Our brand refresh vs rebrand guide has a five-question decision tree. Name the two or three people who make final calls.
3. Positioning
Write down who you serve, what they use today, why you're better and the one-line claim you want to own. This document is the brief for every later step.
If you're not sure a rebrand is warranted, run our 12 signs checklist first. A low score often means a website or deck fix is enough.
How do naming, domain and identity design fit in?
Naming and domain come first if they're changing, because the identity has to be designed around the name. The identity step then turns positioning into a visual and verbal system: logo, type, color, imagery, voice and the rules that hold them together.
4. Name and domain (if changing). Generate options from the positioning, check trademarks in your key markets, check domain and social handle availability, and test the shortlist out loud on real calls. Buy the domain before announcing anything.
5. Identity design. Explore directions on real screens (homepage hero, app dashboard, a deck slide, an email) rather than on a logo sheet. Pick one, then build the system: logo lockups, palette with accessible contrast, type scale, imagery rules and voice guidelines.
Showing directions on real screens is the single most useful habit in identity work, because a logo that looks great alone can fail inside a dense SaaS interface. It's why our sprint includes 10 website or product explorations. For the logo specifically, our logo design process covers the eight steps from brief to files.
How do you roll a rebrand into the product UI?
Roll a rebrand into the product by updating design tokens (color, type, spacing, radius, shadows) so the change flows through every component at once, then fixing the high-visibility surfaces by hand. Patching screens one by one leaves a product that's half old, half new for months.
6. Product UI tokens. Map the new palette and type to your token set, check contrast against accessibility guidelines, update the component library, and swap logos, favicons, app icons, loading screens and email templates. Prioritize login, onboarding, navigation and transactional emails.
If your product doesn't have tokens yet, the rebrand is a good moment to add them, because the next change will then be far cheaper. Ship the token change behind a feature flag so it can go live on launch day with the rest. Our guide to designing a SaaS app from scratch explains how tokens and components fit together.
How do you protect SEO and the website during a rebrand?
Protect SEO by keeping URLs stable where you can, redirecting every URL that changes with a permanent redirect, and updating your brand name everywhere search engines read it. If the domain changes, the redirect plan is the most important document in the whole rebrand.
7. Website and SEO plan. Redesign or restyle the site in the new brand. Export every indexed URL, map old to new, and test redirects on staging. Update titles, meta descriptions, structured data, Open Graph images and internal links. If the domain changes, keep the old one redirecting and use Google's change of address tool in Search Console.
Getting this wrong is costly. Big Leap's published case study on the AtTask to Workfront rebrand describes a significant loss of organic visibility after the change and the recovery work that followed. Our guide to rebranding without losing SEO and the SEO-safe relaunch plan cover the details. If the rebrand comes with a full site redesign, our guide to whether to rebrand and redesign at the same time covers sequencing.
What sales and support materials need updating?
Every document a customer or prospect sees needs updating before launch: sales decks, one-pagers, proposals, contracts, help center articles, onboarding emails, status pages and support macros. Sales and support are the teams customers talk to about the change, so they need new materials and a short FAQ in hand on day one.
8. Sales and support materials. Rebuild the master sales deck on the new identity, update proposal and contract templates (and legal entity names if those change), refresh help center screenshots and logos, update email signatures and support macros, and brief both teams with a one-page FAQ: what changed, why, and what customers need to do.
Help centers are one of the most often missed items. Old screenshots showing the previous logo and colors undermine the launch for months. Budget time to replace them, or at minimum the ones on your most-visited articles. For B2B companies, also update partner and marketplace listings, which often take days to approve. Our guide to SaaS branding covers how B2B brands keep these assets consistent.
How do you launch the rebrand?
Launch the rebrand on a single planned day with every change ready: site, product, emails, socials, materials and redirects. Then tell customers and investors, and watch the numbers for a few weeks. A staggered launch with old and new brands live together confuses customers and weakens the change.
9. Launch. Deploy the site and redirects, flip the product feature flag, update social profiles and app store listings, send the customer email, publish a short announcement and update investors. For the next few weeks, monitor Search Console, branded search, sign-ups and support tickets, and fix anything that breaks quickly.
A product launch can share the day if you plan it, which gives the rebrand a story beyond "we changed the logo". Our product launch strategy for SaaS covers how to combine them, and the rebrand launch checklist lists 40 items to tick off.
Hypothetical example: a launch-week plan for a B2B SaaS rebrand
For example, suppose a B2B SaaS company is evolving its brand without changing its name or domain. Two weeks before launch, the new site is on staging, the token update is behind a feature flag and the redirect map for six renamed pages is tested. One week before, sales and support get the FAQ and new deck, and help center screenshots are swapped. On launch morning, the team deploys the site, flips the flag, updates socials and sends the customer email. In the following weeks, someone checks search data and support tickets daily, then weekly. The company and plan are invented to illustrate sequencing.
