# SaaS rebrand playbook

> A week by week rebrand plan for software teams, covering the asset inventory, domain migration, launch sequence and the metrics that prove it did no harm.

Source: https://saas-marketing.net/playbooks/saas-rebrand/
Topic: SaaS Branding
Type: playbook
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/playbooks/saas-rebrand/

## Short answer

A SaaS rebrand is a migration project with a creative phase attached, and the migration is what goes wrong. Plan 90 days across four workstreams: strategy and naming, identity design, asset production, and technical cutover. The asset inventory is the step that decides whether launch week is calm or chaotic, because product UI strings, transactional emails, API docs, invoices and partner directories all carry the old name. Announce internally two weeks before the market.

## Key takeaways

- Four reasons justify a rebrand and a new CMO wanting to make a mark is not one of them.
- A domain change typically costs 10 to 30 percent of organic traffic for four to twelve weeks even when executed correctly.
- The asset inventory runs to 200 plus items for a mid-sized SaaS, and the ones people forget are invoices, API docs and partner directories.
- Announce to employees two weeks before the market, because reps hearing it from a customer is the most common own goal.
- Redirect one to one at the URL level. Mass redirecting everything to the new homepage destroys the rankings you were protecting.
- Score the rebrand at 30, 60 and 90 days on branded search, direct traffic, organic sessions, support tickets and win rate.

---

The creative part of a rebrand is the part everyone talks about and the part least likely to fail. What fails is the 340-item asset list, the redirect map somebody generated in a hurry, and the sales rep who found out from a prospect. Treat this as a migration project with a design phase attached and the odds improve considerably.

## The go or no-go test before you spend anything

Four reasons justify a rebrand. Five common ones do not, and most rebrands are launched on the second list.

Justified: the name cannot be legally defended or is blocked in a market you need. The name actively misdescribes what you sell after a category shift. A merger left you with two brands competing in the same buyer's head. Or win loss data shows the name itself blocking deals, which is rarer than people claim but real, particularly for names that read as consumer, as a single-feature tool, or as offensive in a target market.

Not justified: a new CMO wanting a signature project. A competitor shipped an attractive website. The logo feels dated to the four people who look at it daily. An investor made an offhand comment. Or the actual problem is positioning, which a new colour palette will not touch.

That last one is the important distinction. Miro's rename from RealtimeBoard in 2019 was a genuine category and pronounceability fix. Vercel's rename from ZEIT in 2020 came with a real repositioning around the deployment platform rather than the old product set. Slack's 2019 identity update and Zendesk's 2016 one were visual system overhauls on stable names, which is a much smaller undertaking and should not be confused with the first two.

Ask the sales team to name three deals lost in the last two quarters where the brand was cited as a reason, with the call recording. If nobody can produce one, you have a design preference, not a business case. Spend the money on positioning instead and read the [rebrand vs brand refresh](/comparisons/rebrand-vs-brand-refresh/) comparison first.

## The 90 day plan, week by week

This assumes a visual rebrand with a possible name change on the same legal entity, a dedicated project owner, and an executive sponsor who will make decisions inside 48 hours. Without that owner, add six weeks.

| Weeks | Workstream | Output | Gate to pass |
| --- | --- | --- | --- |
| 1 to 2 | Strategy | Positioning doc, audience research, brand brief | Executive sign-off on the brief, not the design |
| 3 to 4 | Naming and clearance | Shortlist, trademark search, domain availability | Legal clearance in all target markets |
| 3 to 6 | Identity design | Logo, type, colour, motion, three applications | One decision maker, not a committee vote |
| 5 to 8 | Asset inventory and production | The full item list, owners assigned, production queue | Inventory signed off as complete by four teams |
| 7 to 10 | Technical preparation | Redirect map, staging build, email templates, product strings | Redirect map tested one to one on staging |
| 9 to 11 | Internal launch | All-hands, FAQ, sales enablement, customer comms drafts | Every rep can answer the top ten questions |
| 11 | Cutover | DNS, redirects, sitemaps, app stores, ad accounts | Rollback plan written and tested |
| 12 to 13 | External launch and monitoring | Press, customers, partners, social, daily metrics review | 30 day scorecard baseline captured |

The gate that gets skipped is the inventory sign-off in week 8. Someone declares the list complete after finance and marketing have reviewed it, and then on launch day the transactional password reset email still carries the old logo. Four teams need to sign: product, marketing, finance and support.

The clearance gate deserves its own attention. A name that survives a quick search and then fails a proper trademark review in month four burns the whole timeline. The mechanics are covered in [trademark and domain clearance for SaaS names](/guides/saas-trademark-and-domain-clearance/), and the naming process itself in [SaaS product and company naming](/guides/saas-product-naming/).

## The asset inventory nobody finishes

Two hundred items is a normal count for a 150-person SaaS company. The visible ones are easy and get done. These are the ones that surface at 4pm on launch day.

**The assets teams forget**

Partner directory listings are the slowest of these because they depend on somebody else's release schedule. A logo update in a large vendor's marketplace can take six weeks. Start those in week 5, not week 11.

App store reviews are the other schedule risk. An iOS or Android listing change with a new name goes through review, and a rejection at the wrong moment means your mobile app carries the old brand for two weeks after launch. Submit early and plan for one rejection.

Roughly 15 to 20 percent of the inventory will not be done on launch day. It is not a planning failure, it is the nature of the work. Decide in advance which items are launch-blocking (anything a customer sees while paying you) and which can trail into weeks 13 to 20. Deciding that on the day produces panic and bad calls.

## The domain and SEO migration sequence

If the domain changes, this section is the highest risk part of the project. If it does not, skip to the launch sequence and enjoy your considerably easier life.

**Domain migration sequence**

Expect the dip. A 10 to 30 percent organic decline for four to twelve weeks is the normal outcome of a competently executed migration, and anyone promising no impact has not done one. Tell your CEO the number before launch, not in the week three review when the chart is already falling.

**10% to 30%** Typical organic traffic dip after a well-executed SaaS domain migration, recovering over one to two quarters

Keep the old domain forever. Renew it for a decade and leave the redirects in place permanently. Old links in documentation, forum posts and email signatures will keep arriving for years, and a lapsed domain is a gift to whoever registers it next.

## The launch sequence across four audiences

Order matters more than content here, and the order is employees, customers, partners, press.

Employees first, two full weeks ahead. Every rep needs the rationale, the new assets, and prepared answers to the ten questions customers will ask. The most common own goal in rebrands is a customer congratulating an account executive on the new name before the account executive has heard of it. That one conversation costs more credibility than any design decision in the project.

Customers next, 48 hours before the public switch. Segment it: your top accounts get a note from their named contact, everyone else gets a single clear email. Say what is changing, what is not changing, whether they need to do anything (usually allowlisting a new sending domain, which support should be briefed on), and whether pricing or contracts are affected. Lead with "nothing changes for you" if that is true, because it is the only question most of them have.

Partners and integrators at the same time as customers, with the asset pack attached so they can update their own listings.

Press and public last, on the day. Keep the announcement about the customer-facing reason rather than the design process. Nobody outside the company cares about your new typeface, and a post explaining the kerning rationale reads as self-regard to the buyers you are trying to reach.

Pair this with the launch mechanics you would use for any major release. The structure in the [B2B SaaS product launch playbook](/playbooks/b2b-saas-product-launch/) transfers almost directly, and the operational detail lives in the [SaaS rebrand launch checklist](/checklists/saas-rebrand-launch/).

## The 30, 60 and 90 day scorecard

Capture the baseline the week before cutover, or the whole exercise becomes unfalsifiable.

| Metric | Baseline source | 30 day expectation | 90 day expectation |
| --- | --- | --- | --- |
| Branded search impressions | Search Console, exact brand queries | Down, new name still building | At or above combined baseline |
| Direct traffic | Analytics, direct channel | Down 10 to 20 percent | Recovered |
| Organic sessions | Analytics, organic channel | Down 10 to 30 percent if domain changed | Recovering, 70 to 90 percent of baseline |
| Support tickets mentioning the change | Zendesk tag | Spike in week one, fading by week three | Near zero |
| Win rate | CRM, closed won over closed | Flat. Do not read noise | Flat or better |
| Pipeline created | CRM | Flat | Flat or better |

Win rate is the one to watch hardest, because it is the metric a rebrand can genuinely damage without anyone noticing for a quarter. If it drops more than a few points and stays down, the new name or story is creating friction in deals, and that is a positioning problem to solve rather than a traffic problem to wait out.

For context on what typically happens to these numbers, the [SaaS rebrand outcomes](/research/saas-rebrand-outcomes/) research is worth reading before you set expectations with a board. Budget planning belongs in the [rebrand cost calculator](/calculators/rebrand-cost-calculator/) and the wider figures in [SaaS branding cost](/guides/saas-branding-cost/), with the strategic groundwork in the [SaaS branding](/saas-branding/) hub.

Next step: run the go or no-go test this week. If the sales team cannot produce three recordings where the brand cost you a deal, put the budget into positioning and revisit in a year.

## Frequently asked questions

### How long does a SaaS rebrand take?

Ninety days is realistic for a visual identity refresh with no name change, assuming a decided strategy and a dedicated owner. A full name change with a new domain typically runs four to nine months once trademark clearance, legal entity work, contract updates and app store approvals are included. The creative work is rarely the long pole. Clearance and cutover are.

### Will a rebrand hurt SEO?

A visual rebrand on the same domain has almost no SEO impact. A domain change does. Expect a 10 to 30 percent dip in organic sessions for four to twelve weeks even with a clean one to one 301 redirect map, full sitemap resubmission and updated internal links. Recovery to previous levels usually takes three to six months, longer for weak domains.

### What are good reasons to rebrand a software company?

A name that legally cannot be defended or is blocked in a key market. A category shift where the name actively misdescribes what you now sell. A merger or acquisition creating two competing brands. A name that consistently blocks deals, evidenced in win loss data. Boredom, a new CMO, and a competitor launching a nice website are not reasons.

### When should employees be told about a rebrand?

Two weeks before the public announcement, with the full rationale, the new assets and answers to the questions customers will ask. Anything shorter and your sales team learns about it from a customer, which is the most common own goal in rebrands. Anything longer with a large company and it leaks, so pair the timing with clear confidentiality expectations.

### What does a SaaS rebrand cost?

A visual refresh with an independent studio commonly runs 25,000 to 75,000 dollars. A full identity and naming programme with a mid-sized agency runs 100,000 to 400,000. Enterprise programmes go well beyond that. The hidden costs are internal time, legal and trademark work, app store and marketplace resubmission, and reprinting or reissuing anything physical.

### Should you keep the old domain after a rebrand?

Yes, indefinitely. Renew it for at least ten years and keep the redirects live permanently. Old links, old email signatures, old documentation and old integrations will point at it for years. Letting an old SaaS domain lapse is how a competitor or a domain squatter ends up receiving your password reset traffic and your inbound links.

### How do you know a rebrand worked?

Branded search volume returns to or exceeds the pre-launch baseline within 90 days, direct traffic recovers, organic sessions return within two quarters, support ticket volume about the change subsides within three weeks, and win rate is unchanged or better. A rebrand that improves perception while losing a quarter of pipeline is not a success, whatever the design press says.