Book a call
All writing

Brand guidelines vs design system in 2026: which do you need?

Guidelines tell people how to use the brand. A design system is the parts your product is built from. Most software companies need both, guidelines first.

Brand guidelines tell people how to use the brand: the mark, colour, type, voice and layouts, with examples, so a marketer or an outside agency can make something that looks like the company. A design system is the product’s parts built to be reused: components, design tokens and the rules for them, in Figma and in code, so everyone building the product uses one set. The difference that matters is who has to use it. If the brand is mostly used by marketing and sales, guidelines are enough for now.

In our view most software companies end up with both, and should not buy the system first. A system built before the brand is settled records whatever the first designer happened to choose. The checks below tell you which one you need now. The glossary defines each term, and our list of design system studios is linked at the end.

1. What does each one hold, and who uses it?

Guidelines are written for people who are not designers, or not your designers. They record the identity and the reasons behind it, and show it on the company’s own material: a deck, a landing page, a social post, an event banner. Nielsen Norman Group describes a brand style guide as the brand-related rules and the foundations that define a brand, such as the palette, the type, the logos and imagery.

A design system is written for the people who build the product. Nielsen Norman Group calls it “a complete set of standards intended to manage design at scale using reusable components and patterns”, and treats a style guide as one of its children, alongside a component library and a pattern library. The GOV.UK Design System is a public one you can read in full. It is organised as styles for layout, type, colour and images, components such as forms, navigation and tables, and patterns for tasks such as entering an address. Each component comes with its code and a note on when to use it.

Brand guidelines and a design system side by side.
ComparedBrand guidelinesDesign system
What it isRules and examples for using the brandThe product’s reusable parts and the rules for them
Who uses itMarketing, sales, founders, agencies, printersProduct designers and engineers
What it holdsMark, colour, type, voice, layouts, templatesTokens, components with their states, patterns, documentation
Where it livesA PDF or a site, with templatesA Figma library and coded components that match
What it answersWhether a piece looks and sounds like the companyWhich part a screen is built from, and how it behaves
Who keeps itThe brand owner, usually in marketingSomeone in product who decides which version stays
The right call whenThe site, the decks and campaigns carry the brandSeveral people build one product

2. Where do they meet?

They meet in the design tokens. The Design Tokens Community Group at the W3C defines a token as “information associated with a human readable name, at minimum a name/value pair”, and its format exists so the same tokens can be shared by design tools and code.

The first tokens in a product’s system are the guidelines’ decisions written as data: the brand colours, the typefaces and their sizes, the spacing steps. The product then needs decisions the guidelines never made, and those become tokens too.

Say a payroll company’s guidelines give it one green, for the logo, headlines and the site’s buttons. The product needs a green for its main button, a darker one for hover, a pale one for a selected row in a table, a red for errors and a colour for the focus ring that people using a keyboard rely on. None of those is in the guidelines. The design system adds them as tokens built from the brand green, and the brand owner agrees them. When the green changes at the next refresh, one value changes and the site and the product pick it up together.

That agreement is the part teams skip. If the product team invents its colours alone, the product drifts from the brand. If the brand owner never hears what the product needed, the next guidelines are written for the marketing site alone.

3. What happens when you have one and lack the other?

Guidelines and no system

The website and the decks look like one company and the product looks like another. Engineers type colour values in by hand from the guidelines PDF, and each new screen gets its own version of a table, a filter and an empty state, because the guidelines say nothing about them. Customers who saw the brand in a sales meeting sign in to something that looks made by a different team.

A system and no guidelines

The product is consistent and nobody decided what the brand is. The first designer’s choices in the component library become the brand by default. Marketing builds the site from a screenshot, sales picks a blue for the deck that is close enough, and the agency running your ads has nothing on voice at all. The system cannot help them, because a sales deck has no buttons or inputs.

4. Which one do you need?

Start with the guidelines and look for evidence that you need the system as well. Run these checks with whoever leads marketing and whoever leads engineering, and the last month of work.

  1. Count who makes material with the brand on it. If it is mostly marketing, sales and outside agencies, you need guidelines. If several designers and engineers are building screens, you need a system as well.
  2. Open the product and the website side by side. If the colours, type and buttons differ between them, start with the guidelines, because the system needs one set of brand decisions to build on.
  3. Find one control in the product that behaves two ways, such as a save button that closes a panel on one page and leaves it open on the next. That is a system problem, and guidelines will not touch it.
  4. Ask your marketing lead what a new agency gets on its first day. If the answer is a logo folder, you need guidelines, whatever the product has.
  5. Look at how often the product changes. If it is a few screens that still change every week, it has few settled decisions to record, and a system can wait.

When to do the system first, or neither yet

If your identity is settled and already written down, and the product is where the inconsistency lives, start the system. The guidelines you have may need a page added for the product’s colours, which the system work will produce. If the identity is about to change, wait: a system built on a palette you are replacing will be rebuilt. If the product is a handful of screens and one engineer, a short shared list of colours, type sizes and spacing in the code will hold until it grows.

Nielsen Norman Group says a design system is best when a company “foresees years of future, replicable design work”, and that building one needs a dedicated team. Someone has to keep it after launch too, so count that before you start.

5. What does each one involve?

Guidelines

Guidelines come at the end of a brand project, or as an extension of an identity you already have. Ours explain the reasoning as well as the rules. We test them before sign-off on the formats your team uses and on your own content, including the awkward cases: a long title, a dense table, the smallest format you need. They come with templates for what your team makes most.

A design system

We start by auditing the interface you have and writing down every type style, colour, spacing value, icon and component in use. We mark what is duplicated, and agree with your designers and engineers which version of each part stays. Each part is drawn in Figma on your product’s own content, with its loading, empty and error states, then built in code in the stack your engineers already use and checked in staging. You get the Figma library, the coded components and a rule for each part, in your own accounts.

6. What do they cost, and how long do they take?

Guidelines are part of a brand project, and our brand projects run from $15,000 to $100,000 or more. A design system has no fixed price of its own. We scope it as product design, which starts from $10,000 a month, or as one part of a larger product design project. Those are our own published prices and say nothing about what other studios charge. We agree the scope and price of either before work starts.

We give no single length for either and set the timeline with you first. A system’s moves with the number of components, how many existing screens move onto them and whether mobile is part of it.

7. Questions

  1. Brand guidelines tell people how to use the brand: the mark, colour, type, voice and layouts, with examples, for marketing, sales and agencies. A design system is the product’s reusable parts, meaning tokens, components with their states, patterns and the rules for them, in Figma and in code, for the people who build the product. They meet in the design tokens, which carry the brand’s values into code.

  2. Usually, yes. A design system’s first tokens are the brand’s colours, type and spacing, so those decisions need to be settled and written down first. A system built before then records whatever the first designer chose, and is rebuilt when the brand changes. If your identity is already settled, the system can start now and add a page on the product’s colours to the guidelines.

  3. No. A design system covers the product’s interface: buttons, inputs, tables and how they behave. It says nothing about how to set a sales deck, brief a photographer or write a campaign headline. A product’s system usually holds the brand’s colours and type as tokens and none of the rest, so most software companies need both.

  4. A design system has no fixed price of its own at Refract. We scope it as product design, which starts from $10,000 a month, or as one part of a larger product design project. The price depends on how many components the product needs and how much of the existing interface moves onto them, and we agree it before work starts.

  5. Guidelines usually belong to the brand owner, often in marketing, who approves new formats and keeps the current version easy to find. A design system needs someone in product who decides which version of a part stays when two exist and keeps the Figma file and the code in step. The two owners should agree any new colour or type the product needs.

Sources and further reading

Written on by RefractStudio notes

Keep reading

Working on something like this?

Tell us where it’s stuck. We’ll tell you what we’d do first, and whether we’re the right team.

Most teams start with a call, then a sprint or an audit.

Book a call
  • Angus
  • James
  • Naiya
  • Lilian
  • Luca
  • Minh
  • Jorge
  • Toffee

The people you’d work with, from the first call to launch