SaaS
Rebrand.

Rebrand vs refresh (the diagnostic)

The fastest way to get into the wrong engagement is to use the two words interchangeably. They are different jobs.

A refresh repaints the surface. Palette gets tightened, type pairing modernised, wordmark sharpened, application templates redrawn. Positioning, audience, and voice stay where they are. Three to five weeks. The team running it can be the in-house designer with an outside studio doing one or two directions.

A rebrand re-decides the underlying strategy and then rebuilds every surface to match. Positioning is the lever, not the colour. Eight to twelve weeks for a live product. Requires a Strategy phase that signs off before any direction work begins, an Audit phase that inventories every surface the current brand lives on, and a Rollout phase that runs the swap on a schedule rather than dragging it across the next quarter.

The diagnostic question — and the one most founders skip — is "has our positioning actually moved?". If the deck and the site are saying the same thing and the founder is still happy with the sentence at the top of the deck, the right answer is a refresh. If the deck and the site are saying different things and the founder cannot agree with the marketing lead on which version is true, the right answer is a rebrand. Anything in between is a refresh until proven otherwise.

The intent-landing for the engagement itself is /saas-rebrand/. For green-field SaaS that has not yet shipped a brand, the closer fit is brand identity for SaaS.

The five signals it is actually time to rebrand

You usually want at least two of these — preferably three — before the disruption of a rebrand is worth it.

1. Positioning has shifted. The product has moved from "AI for X" to "the platform for Y", or from SMB self-serve to enterprise sales-led, and the brand is still telling the old story. The sales team has noticed. The buyer has noticed. The brand is the lagging indicator.
2. The category has moved. What looked distinctive at launch is the genre default now — five competitors copied the same lavender gradient and the same geometric sans. The brand has stopped doing differentiation work because the category caught up.
3. The next round / partnership / geography needs polish the current system cannot carry. A Series A brand at a Series B fundraise feels thin. A US-only brand moving into EU procurement decks feels casual. The bar moved because the buyer moved.
4. The team has outgrown the system. Marketing improvises a different visual treatment per campaign because the original system has nothing to say. Product invents its own UI language because the marketing brand never wrote down how it should show up in-product. Every surface is drifting and the design lead is firefighting.
5. The founder cannot defend the current brand to a hostile reviewer. The pricing meeting, the deck review, the board update — all of them now go through a moment where the founder apologises for the brand. That is the cheapest signal to detect and the most reliable.

What is NOT a reason to rebrand on its own: a new CMO who does not like the colour. The team got bored. A redesign of the marketing site is overdue. Those justify a refresh, not the expensive thing.

How a SaaS rebrand runs (six phases)

1. 01 Audit. Inventory of every surface the current brand lives on — marketing site, in-product UI, sales decks, support docs, paid creative, social, partner pages. Output: a written map of what the rebrand has to touch, and a redirect plan for every URL that has received traffic in the last 90 days.
2. 02 Strategy. Founder interviews, competitive scan, positioning refresh, voice refresh. Output: a one-page brief that locks the audience, the positioning sentence, and the three things the visual system has to encode. Direction work does not start until this is signed off.
3. 03 Direction. Two to three brand directions, each with wordmark + lockup, palette, type pairing, and one application surface (usually the home-page hero or the in-product header) so the founder compares directions in real context, not on a moodboard slide.
4. 04 System. Picked direction expanded into the full system — every token, every application template, every state. Brandbook drafted in parallel. This is the longest phase and the one where the unglamorous decisions get made.
5. 05 Rollout. Surface-by-surface swap on a published schedule. The audit map from Phase 1 drives the order; high-traffic surfaces go last so the system has time to settle on low-traffic ones first. Launch is a single cutover, not a drag across the next quarter.
6. 06 Handoff. Brandbook ships (PDF + Figma), application templates handed to the team, support voice-and-vocabulary update circulated, and a 30-minute walkthrough video on file so the next hire or the next agency can pick up the system without re-pitching the rationale.

If your situation maps to the rebrand profile, the SaaS rebrand engagement is the closest match. The Brand for SaaS pillar covers the broader strategy work that informs Phases 1 and 2.

What changes — and what stays

A rebrand that throws away every existing equity signal is a rebrand that started without an audit. Recognition is expensive to build and free to keep. The audit phase splits the existing system into three buckets:

Carries forward (almost always)

• The name. Renaming a SaaS is a separate engagement and almost never the right call inside a brand-only rebrand.
• One equity signal — usually the colour, sometimes the mark shape, occasionally a type pairing — that has earned recognition the buyer associates with the product.
• The tone-of-voice spine, if there is one. The vocabulary changes; the underlying register does not.

Up for re-decision

• The wordmark and any secondary lockups.
• Type pairing (display + body) and the type scale.
• Application templates — marketing site, sales decks, social, OG cards, in-product accents.
• Motion language — duration, easing, when animation triggers.
• The positioning sentence at the top of the marketing site.

The wordmark re-decision is its own discipline — five phases, four common red flags, and a brief format that survives a hiring committee. The logo design process pillar covers it end-to-end so the rebrand engagement does not relitigate it in every status call.

Always replaced

• The brandbook. The old one was a record of decisions that no longer hold; the new one captures the new rules.
• The internal handoff materials — the 30-minute walkthrough video, the engineering-handoff Figma file, the support voice-and-vocabulary update.
• Whatever default OG image is on the marketing site. (If you do not know what your default OG image is, that is the answer.)

When the marketing site is in the "Up for re-decision" pile and Webflow is the right platform for the next stage, our Webflow design agency engagement covers the marketing-site rebuild end-to-end — discovery, custom design (no templates), component library, performance budget, and editor handoff.

What it costs

Funky Rabbit publishes pricing — the same numbers every visitor sees. No discovery-call quote game.

• SaaS Rebrand (8–12 weeks): $25k–$50k. Audit, strategy, system, applications, rollout schedule, handoff. For live products with real surface counts.
• Enterprise / Multi-Surface (12–16 weeks): $50k+. When the surface count, geography, or stakeholder list pushes the engagement past the standard Rebrand tier.
• Identity Sprint (2–3 weeks): from $9k. For founders who actually need a refresh, not a rebrand. We will tell you which one applies in the first call.

Industry context: agencies in the same bracket charge $40–120k for a SaaS rebrand. Below $20k you are buying a logo refresh; above $100k you are paying for an account-management layer you may not need at this stage.

Full breakdown on the pricing page.

How to choose a studio (or build in-house)

The list of studios pitching SaaS rebrands is long. The list that has actually shipped systems that survived 18 months post-launch is short. Filter by:

• Public case studies with real client names. "A leading SaaS company" is not a case study; it is a placeholder.
• The studio's own brand survives the test you are about to put it through. If their site is generic, your rebrand will be too.
• Pricing on the site. Studios that hide pricing usually charge what they think they can extract from each prospect.
• A founder you would actually want on a 10-week call cadence. Rebrand work is intimate. The studio principal will see your strategy decks, your churn graphs, the parts of the product you are embarrassed about.
• Rollout in scope, not just direction. Studios that ship the wordmark and disappear leave the in-house team holding the rollout — and the rollout is where most rebrands fail.

In-house option: viable if you already have a senior brand designer + the rollout capacity to swap every surface on a schedule. Most early- and mid-stage SaaS teams do not — the in-house designer has three full-time jobs already and a rebrand adds a fourth. Hybrid (in-house designer + outside studio for Strategy / Direction / System, in-house owns Rollout) is the third option and the cheapest when the in-house designer is senior enough to QA the system.

Risks + mitigations

Three risks worth planning for explicitly, in descending order of damage:

1. R1 SEO drop on cutover. A rebrand that ships without a redirect map for every URL that received traffic in the last 90 days loses 30–60% of organic for the quarter. Mitigation: the audit captures every URL, the redirect map is signed off before launch, and the launch includes a Sunday-morning crawl re-submission in Google Search Console.
2. R2 In-product UI drifts before the marketing brand catches up. Engineering ships a feature in the old visual language two weeks before the rebrand goes live and the team has to redo it. Mitigation: engineering gets the new tokens (colours, spacing, radii) in Phase 4, not Phase 5, so anything shipped in the final two weeks lands in the new system already.
3. R3 Customer confusion at the launch moment. Users open the dashboard, see the new mark, and email support thinking they got phished. Mitigation: a one-paragraph "what is changing and why" goes out 48 hours before launch and lives on a /rebrand/ page until the support volume normalises (usually 7–10 days).