--- title: "A New Logo Is Not a Rebrand: What Really Changes | Murarum" description: "A rebrand is a system of decisions that must reach every touchpoint. What changes after the new logo: website, components, tone, plus a checklist." url: https://murarum.ro/en/insights/new-logo-is-not-a-rebrand language: en alternate_ro: https://murarum.ro/articole/logo-nou-nu-e-rebranding --- 7 min read · Brand and website # A new logo is not a rebrand: what actually changes when you change your visual identity A rebrand changes the system of decisions that makes a company recognizable: what it says about itself, how it sounds, which typefaces and colors it uses and in which roles, and how all of that shows up on every touchpoint, from the website to an offer sent by email. The logo is one visible piece of that system, and a small one. Change only the logo and the old decisions keep running everywhere else. Change the identity without a design system and written communication rules, and you end up paying for a second redesign when the first one drifts. By Mircea Muraru · 2 November 2026 ## What a rebrand actually decides A logo answers one question: which mark goes on things. A visual identity answers dozens more, and most of them are invisible in the meeting where the new logo is shown for the first time. In our identity work, these are the decisions we write down before anyone draws a mark: - Positioning words. Three to five words the company wants to be known for, and a few it wants to avoid. Every later choice, from typeface to headline, is checked against them. - Typography. One or two typefaces with clear jobs: headlines, body text, numbers and tables. They have to work in every language the company writes in, Romanian diacritics included. - Color roles. Which color is the background, which is text, which marks an action and which signals an error. A palette without roles is a list of favorites. - Imagery. What kind of photos and illustrations the company uses, and which kinds it never uses. - Tone of voice. How the company writes: formal or direct, short or explanatory, which words it uses and which it avoids, with the same sentence written in the right and the wrong voice. - Components. The buttons, forms, cards, tables and page sections that carry all of the above into a website or an app. Written down, these decisions let a designer, a developer, a salesperson and an accountant produce material that looks and sounds like the same company, without asking anyone first. ## Where the identity has to arrive An identity lives wherever customers meet the company, and in a small or mid-sized business that list is longer than most people expect. A typical inventory looks like this: - The website, its forms and the automatic emails it sends. - Offers, proposals and contract templates. - Invoices and other documents sent from the ERP or the invoicing software. - Email signatures and presentation templates. - Social media profiles, posts and job ads. - Customer portals and internal applications, if there are any. - Signage, vehicles, uniforms and packaging, where they exist. Count the touchpoints in your own company before you count logo options. The logo appears on most of them, but it is a small part of each. What the customer actually reads is the text, the layout, the colors and the way a form behaves when they make a mistake. ## What happens after the identity is delivered Many identity projects end with a brand book: a PDF with the logo, the palette, the typefaces and a few mockups. Then the work moves to people who were not in the room. A web agency builds the site and interprets the PDF. A colleague makes the offer template in a word processor. Someone else writes the posts. Each of them makes small decisions the brand book did not cover, and within a year several versions of the company are in circulation. The identity usually breaks in three places first. ### The website A brand book usually defines colors, not color roles, so the site invents its own. The accent color ends up on text where it cannot be read, or on links and buttons alike, so nothing looks clickable. The WCAG 2.2 accessibility guidelines ask for a contrast ratio of at least 4.5:1 for normal text, and 3:1 for large text and for the visual parts that identify interface controls. A palette chosen on a presentation slide often fails these numbers, and the site then quietly replaces the colors. ### Components A logo does not tell anyone how a button, a form field, an error message or a comparison table should look. If these are not designed once, as components, every new page designs them again, slightly differently. The site, the customer portal and the next landing page drift apart, and every change has to be made in several places. ### Tone of voice The identity says "direct and approachable", the website says "we are pleased to inform you", and the automatic order confirmation was written by whoever built the form. Tone rules are the cheapest part of an identity to write and the first to be ignored, because nobody owns them after delivery. ## The second redesign you end up paying for When an identity reaches the touchpoints through interpretation, the inconsistencies pile up until someone decides the brand no longer feels right. The usual answer is another redesign. Often the logo was never the problem. What was missing was the system that would have kept every page, template and message in line, and a second identity without that system drifts the same way. A design system is the part that prevents this. In practice it means three things: the identity's decisions written as design tokens (named values for colors, type sizes and spacing that both the design files and the code read), a library of components built once and reused, and short written rules for tone and imagery, with examples. When a color changes, it changes in one place, and every page that uses it follows. ## How we run identity and website as one project At Murarum, branding is a service we offer next to website and product delivery, as part of [product development](https://murarum.ro/en/services/product-development). We run it in the same four phases as any other project, described in [how we work](https://murarum.ro/en/approach): 1. Diagnose. We agree the positioning words, list every touchpoint and read the copy currently in use, so we know what the identity has to carry. 2. Design. We design the identity and the key pages of the site together, on real content, and test colors and type in the interface, not only on a slide. 3. Build. The decisions become design tokens and a component library, and the site is built on them. Tone rules are written with examples taken from your own pages. 4. Scale. We carry the system to the touchpoints outside the site: offer and presentation templates, email signatures, automatic emails, and a short guide your team can use without us. ### Why we do them together Most identity decisions are tested for the first time on a website: whether the typeface holds at small sizes, whether the accent color passes contrast, whether the tone survives an error message. When identity and site are separate projects, those tests happen after the identity is signed off, and every fix becomes either a compromise on the site or a change request to the identity. In one project, the problems surface while changing them is still cheap, and the people who designed the identity are the ones who build it into code. The same logic holds on large sites. For [Sunday](https://murarum.ro/en/work/sunday-website) we redesigned the page and content architecture of teamsunday.com, designed the UI and UX and built the site with templates for each kind of page, across thousands of pages in five languages. Templates and components are what keep a design consistent after launch, whoever adds the next page. ## When a new logo is enough Not every company needs a rebrand. If the positioning has not changed, customers recognize the current identity and the problem is a dated or poorly drawn mark, a redrawn logo applied consistently may be all you need. The test is simple: if the logo is the only thing you would change on every touchpoint in the list above, refresh the logo. If you would also change the words, the colors on the website and the way offers look, you are changing the identity, and it needs a system to hold. ## Checklist: before you approve a new identity - The positioning words are written down, and the people who sell agree with them. - Every touchpoint is listed, including offers, invoices and automatic emails. - Each color has a role (background, text, action, status), and text colors pass WCAG contrast. - Typefaces are tested on the website, at small sizes and with Romanian diacritics. - Buttons, forms, cards and tables are designed as components, with their states (hover, error, disabled). - The identity exists as design tokens the code reads, so a change happens in one place. - Tone rules come with examples: the same sentence in the right and the wrong voice. - One person in the company owns the identity after delivery and approves new templates. - The website is designed in the same project, or at least before the identity is signed off. ## Frequently asked questions ### What is the difference between a logo and a brand identity? A logo is a single mark. A brand identity is the system around it: positioning words, typography, color roles, imagery, tone of voice and the components that carry them into a website or an app. The logo is one visible piece of that system, applied on every touchpoint. ### What does a rebrand include? A rebrand changes the decisions behind how a company looks and sounds: what it wants to be known for, its typefaces and color roles, its imagery and its tone. To last, it also needs a design system, meaning design tokens and components, and written communication rules, applied to every touchpoint from the website to offer templates. ### Should we redo the website when we change our visual identity? Usually yes, and ideally in the same project. The website is where most identity decisions are tested for the first time, such as text contrast, type at small sizes and tone in error messages. Designing both together surfaces the problems while they are still cheap to fix. ### What is a design system, and does a small company need one? A design system is the identity written as reusable parts: design tokens for colors, type and spacing, components such as buttons, forms and cards, and short rules for using them. A small company does not need a large one, but even a small set of tokens and components keeps the website, documents and future pages consistent. ### When is a new logo enough? When the positioning has not changed, customers recognize the current identity and the problem is only a dated or poorly drawn mark. If you would also change the words, the colors on the site and the look of your offers, you are changing the identity, and a logo alone will not hold it together. [Still have questions? Write to us](https://murarum.ro/en/contact) ## Related - [Product Development](https://murarum.ro/en/services/product-development) - [All case studies](https://murarum.ro/en/work) [A new teamsunday.com, in five languages](https://murarum.ro/en/work/sunday-website): Sunday · Branded merchandise platform · 2026 [A speaker management platform for Eventer.NET](https://murarum.ro/en/work/eventer-app): Eventer.NET · Medical congresses and events · 2026 ## Changing your identity and your website? Tell us what is changing in the company and where your customers meet you. We will tell you whether a new logo is enough or whether identity and website belong in one project, and whether we are the right fit. [Let’s talk](https://murarum.ro/en/contact) [office@murarum.ro](mailto:office@murarum.ro) ## Contact - Email: office@murarum.ro - Phone: +40 761 339 149 - Let’s talk: https://murarum.ro/en/contact