Reading time:
7 min read
Last updated:
Rebrand or Refresh: Which One Your SaaS Needs
A refresh fixes how you look. A rebrand changes what you claim. How to tell which problem you actually have, and why doing the wrong one costs you twice.
A refresh keeps what you claim and changes how it looks. A rebrand changes what you claim, and the look follows. That is the whole distinction, and it is worth being strict about, because the two are sold under similar names, cost very different amounts, and fix completely different problems.
Most teams arrive asking for a rebrand when they need a refresh, or ask for a refresh when the real problem is that nobody can tell what they sell any more. Below is how to tell which one you are, what each actually covers, and the one mistake that makes founders pay for both.
The test that separates them
Ask one question. Has what we sell, or who we sell it to, changed?
If the answer is no, and the complaint is that the site looks dated, the logo is thin, or the product and the marketing site look like two companies, that is a refresh. The story is fine. The surface is behind.
If the answer is yes, you need a rebrand, and no amount of visual work will substitute for it. A prettier site that describes the old company is worse than a plain site that describes the right one, because it looks deliberate.
What a refresh actually covers
A refresh works within the existing name, positioning and category. In practice it means the visual system and the surfaces it appears on. Type, colour, spacing and components get modernised. The marketing site gets rebuilt on the current system. The product interface gets pulled into line with it, which is usually the part that has drifted furthest.
What a refresh does not touch is the promise. The headline still says roughly what it said. The customer is the same customer. This is why a refresh can be scoped tightly and shipped on a date. There is nothing to decide that has not already been decided.
What a rebrand actually covers
A rebrand starts with the claim and works outward. Who the product is for now, what it does for them, what it is instead of, and what the company is called if the name no longer fits. Everything visual comes after those answers exist, because the visual work is an expression of them.
That ordering is what makes rebrands slow. The design is rarely the bottleneck. The bottleneck is a founding team agreeing on a sentence. Teams that have that sentence already move fast. Teams that do not spend most of the project finding it, and should expect to.
Four signs you need a rebrand
You changed who you sell to. Moving from prosumer to mid-market, or from developers to operations teams, changes every word on the site, not just the design.
You pivoted the product and the old name now points at the wrong thing. A name that describes a feature you no longer lead with actively works against you.
Your team cannot describe the company the same way twice. If sales, the founder and the site each give a different answer, the problem is upstream of design.
You are being compared to the wrong competitors. When buyers keep putting you next to companies you do not think you are like, the category claim is wrong, and that is positioning work.
Three signs a refresh is enough
The story still lands in sales calls, but the site looks older than the pitch. That is a surface problem, and a surface fix will clear it.
The marketing site and the product look unrelated. Common after a fast year of shipping, and cheap to fix relative to what it costs you in trust.
You raised, the company is the same company, and you now need to look like the size you are. This is the most common one, and it is very often sold as a rebrand when it does not need to be.
The mistake that makes you pay twice
The expensive error is buying a rebrand to fix a positioning problem you have not solved yet. Design cannot decide what your company is. If you hand an unresolved strategy to a studio, you get a beautiful expression of an unresolved strategy, and you will redo it within a year.
The reverse error is cheaper but still costly. Refreshing a site that describes the wrong company means paying to make an inaccurate message look more credible. That buys you nothing, and you will pay again when the message changes.
If you are genuinely unsure which one you need, write the sentence first. One sentence naming what you do and who for. If the team agrees on it in an afternoon, you need a refresh. If that afternoon turns into three meetings, you have found your actual project.
What each one costs you in time
A refresh has a knowable shape, so it can be quoted to a fixed scope and a date. The variables are page count, whether the product interface is included, and how many review rounds you want.
A rebrand cannot honestly be quoted the same way until the positioning is settled, because the scope depends on answers that do not exist yet. A studio that quotes a firm date for a rebrand before that work is done is quoting the design phase and calling it the whole project. Ask which phases the number covers.
Where to go next
If you have decided it is a refresh and the site is the surface in question, how a B2B SaaS redesign actually runs covers the sequence, and what web design costs for a tech company explains what moves the number. If you are choosing who to talk to, how to choose a web design agency covers what to ask on the first call.
For names, we keep two shortlists that map onto the two answers here: studios that handle post-raise rebrands for teams that grew into a new size, and studios that rebrand after a pivot for teams whose product changed underneath them.
Studio Maydit is a web and product design studio working with AI and SaaS founders across the US, UK and Europe. A good share of the projects that arrive as a refresh turn into a positioning conversation in the first week, so this is a question we spend a lot of time on. If you want help telling the two apart before you commit budget to either, book a free 30-minute call.
Frequently Asked Questions
Continue Reading

ChatGPT Is Introducing Ads. Here’s the UX Risk Nobody Is Talking About
As ChatGPT prepares to introduce ads, most conversations focus on revenue and scale. But the bigger question is how monetization reshapes user trust, cognitive flow, and product intent. This Studio Notes piece explores the hidden UX risks product teams should pay close attention to.

Siddarth Ponangi

Why designing for power users too early breaks SaaS products
Many SaaS products become difficult to use not because they lack features, but because they introduce complexity before users are ready for it. Designing for power users too early often feels like progress, but it quietly undermines adoption for everyone else.

Siddarth Ponangi

Why second-use experience matters more than first impressions in SaaS
Many SaaS products spend enormous effort optimizing first impressions. What often gets overlooked is what happens when users come back for the second time, which is usually where real adoption either starts or quietly falls apart.

Siddarth Ponangi

