@yourbrand/systemv2.4.0Shared brand rules

Templates and rules every team can use.

We make a shared kit of colours, fonts, buttons and templates for all your teams. AI checks every file. A named person approves each update.

Typical length
6–12 weeks
Scope
Styles · parts · templates
Updates
Numbered
Built on
Styles → parts → templates → channels

Illustration: a design token, such as the main colour or corner rounding, changes. The parts, templates and channels built on it then update.

02/try-it/live-editor

Design tokens carry one change everywhere.

Design tokens are your colours, fonts and spacing saved as code. Change one below and 6 parts update. AI lists what changed and what is now hard to read.

tokens / your-brand.json branch proposal/primary Demo running · touch any control to take over
color.primary
type.ratio
space.unit

Exports
tokens.css · tokens.json · tokens.dtcg.json
Read by
web app · email CMS · slide templates · social kit
Merge
proposal/primary → main · nothing to merge

AI · impact report0 changes

    Contrast · WCAG 2.2

      People decideAI flags issues. The system owner approves the change or sends it back.

      03/what-we-build/packages

      6 packages all teams use.

      Every team uses the same colours, fonts and spacing. A button in your app and in an email follow the same rules. Each package has a version number. It lists what it needs, so you see what a change affects.

      system install @yourbrand/system

      1. Design tokens

        Colours, fonts, spacing, corners and motion saved as code, for design tools and software.

        Set once

        Needs nothing · the base

      2. Component library

        Buttons, forms, cards and other parts, designed once and shared by product, marketing and communications.

        Shared parts

        Requires tokens

      3. Templates & layouts

        Templates for web pages, slides, email, social and print that fit your brand without a designer.

        Rules built in

        Requires tokenscomponents

      4. Flex rules

        How far a campaign, market or sub-brand can stretch the brand, written as clear ranges.

        Written ranges

        Requires tokenstemplates

      5. Ownership & updates

        Who can change what, how changes go live and how every team knows which version it is on.

        v2.4 · locked

        Requires tokenscomponentstemplatesflex-rules

      6. System documentation

        A searchable site showing the system in use, with design and code side by side, updated with each release.

        Searchable site

        Requires componentstemplatesflex-rulesgovernance

      6 packages · one placePick a package to see what it needsVersions illustrative

      A design system open on a monitor: colour tokens, text styles, widget templates and a component library
      Colours, styles and parts in one place

      04/flex-rules/ranges

      Ranges anyone can check.

      Each element gets a floor and a ceiling. Within them, a campaign, market or sub-brand can adapt without asking. Drag a marker or load an example to try it.

      Load an example

      4 of 4 in rangeNo exception needed

      1. 01 · Blue coverage of the surface

        Blue on a white base. Campaigns may use more blue.

        In rangeInside the range. No exception needed.

      2. 02 · Display size against body

        Outfit headlines, Montserrat text. Headlines always stay larger.

        In rangeInside the range. No exception needed.

      3. 03 · Crop and treatment

        People at work, natural light. Crops may tighten, subjects stay.

        In rangeInside the range. No exception needed.

      4. 04 · Departure from the 12-column grid

        12 columns. Campaigns may break the grid on one element per view.

        In rangeInside the range. No exception needed.

      Ranges illustrativeAI measures each file against the ranges before release. Exceptions go to the system owner.

      05/audit/duplicates

      An audit of your parts that removes duplicates.

      We collect the parts from every file, agency and market and group the near-duplicates. You keep one approved version of each, plus any other versions you need.

      Versions
      92
      Retired
      0
      Source
      7 files · 3 agencies

      Showing the audit: 92 versions of parts found.

      Buttons

      23 found23 → 3

      Inputs

      14 found14 → 2

      Cards

      19 found19 → 4

      Badges

      11 found11 → 2

      Email headers

      9 found9 → 1

      Social tiles

      16 found16 → 3

      AIGroups near-duplicates by look, settings and where they are used, and suggests one version to keep for each group.

      PeopleDesigners and engineers choose and name the approved version and decide which differences to keep.

      Counts illustrative
      Trays of clear pots, each holding one kind of button, sorted and labelled by hand
      Every near-duplicate, sorted before one is chosen

      06/templates/channels

      Templates hold the rules.

      Write the content once. Each format lays it out, drops what it cannot carry and warns when a line will not fit. Type a headline and switch formats.

      content.json

      eyebrow
      Spring range
      body
      Three ways teams use Product C in the first month.
      cta
      Book a demo
      image
      hero / pattern-04
      market
      M03 · en-GB

      Rules this template follows

      • Single column, 600 px wide
      • Image above the headline at 2:1
      • Headline up to 2 lines
      • Legal line pulled from the market pack

      07/ownership/releases

      Who changes what, and how everyone finds out.

      Any team can suggest a change. Leads review it. Each release gets a number that shows if it fixes, adds or breaks something. Teams pick which releases they hear about.

      Watch releases

      Watching minor and major releases · 4 of 6 shown would notify you.

      1. v2.5.0-rc.1 minor

        In review

        Brighter primary for campaign surfaces

        • Addedcolor.primary.bright, campaign templates only
        • Changedbutton.primary label weight 500 → 600
        1. Proposed
        2. AI checks · 2 contrast issues
        3. Maintainer review
        4. System owner
        5. Released
      2. v2.4.0 minor

        Illustrative · Q3

        Density tokens

        • Addedspace.density compact, default and comfortable
        • Deprecatedspacing.sm, use space.2 · removed in 3.0.0
      3. v2.3.2 patch

        Illustrative · Q3

        Focus and safe areas

        • FixedFocus ring visible on ink surfaces
        • ChangedSocial tile safe area 64 → 72 px
      4. v2.0.0 major

        Illustrative · Q1

        Tokens renamed to category.role

        • Breakingcolor-blue is now color.primary
        • BreakingCard drops the legacy shadow prop
        • AddedCodemod and a 6-week overlap for migration
      5. v1.4.0 minor

        Illustrative · Q4

        Email and market packs

        • AddedEmail header template with 3 slots
        • AddedMarket 03 locale pack
      6. v1.0.0 major

        Illustrative · Q3

        First release

        • AddedToken set, core components and the first templates

      08/documentation/website

      Searchable docs, kept current.

      The documentation site shows the system in use, with design and code side by side and a named owner on every page. It updates with each release. Search it below.

      A small team gathered around a monitor, one person pointing at the screen
      Design and code, documented together

      Your brand system

      Components / Button

      Button

      The main action on a surface. One primary per view; secondary and text buttons for everything else.

      <Button variant="primary">Book a demo</Button>
      • DoUse one primary button per view.
      • Don’tSet label text below 4.5:1 contrast.

      Owner · Design systems leadUpdated in v2.4.0

      09/how-it-runs/stages

      4 stages, each with a sign-off.

      Tokens come first because they fix most mismatches. Parts and templates follow where they are used most. Each stage ends only when a person approves its work.

      pipeline brand-system / main

      All 4 stages passed · v1.0 released

      1. stage 1/4

        passed

        Audit

        Wk 01–02

        We check every place your brand appears. We find what varies, what is redone by hand and what costs most.

        • Brand checkpassed
        • Consistency reportpassed
        • System scopereviewed

        Check · sign-off before stage 2

      2. stage 2/4

        passed

        Foundations

        Wk 03–05

        We set and export the tokens, then design the core parts and build them in your code.

        • Token setpassed
        • Core partspassed
        • Code exportreviewed

        Check · sign-off before stage 3

      3. stage 3/4

        passed

        Extend

        Wk 06–09

        We make templates for where you publish most and test the flex rules on a live campaign or market.

        • Template setpassed
        • Flex rulespassed
        • Live testreviewed

        Check · sign-off before stage 4

      4. stage 4/4

        passed

        Run

        Wk 10–12

        We write the guide and ownership rules, set an update schedule, train your team and release version 1.0.

        • Documentation sitepassed
        • Ownership rulespassed
        • v1.0 releasereviewed

        Check · system owner signs off v1.0

      10/what-you-get/release-bundle

      What you get, under one version number.

      Tokens, parts, templates, rules, docs and release notes share one version number. Design, code and guidelines always agree on what is current.

      Items
      7
      Version
      1.0.0
      Owned by
      You

      @yourbrand/systemv1.0.0bundle

      Release bundle v1.0.0: item, formats, version, hash and owner
      ItemFormatsVersionHashOwner
      Design tokens JSONFigma variablesCSS 1.0.0 f0ec682 Design systems lead
      Component library Figmacode 1.0.0 b35a006 Design systems lead
      Template set FigmaOfficeCMS 1.0.0 e2825b6 Content lead
      Flex rules & ranges Guidelines 1.0.0 2325d9b Brand lead
      Ownership rules Document 1.0.0 e8d1ae0 System owner
      System documentation site Web 1.0.0 d818e00 Design systems lead
      Release notes & versions Changelog 1.0.0 4941afe System owner

      7 of 7 items match v1.0.0Hashes illustrative

      11/outcomes/adoption

      Adoption, measured team by team.

      We track each team’s use of system parts and work on the gaps. Screens marked Illustrative are examples, not client results.

      Work built from system parts Illustrative

      Share of work built from system parts at month 12, by team and channel. Illustrative.
      TeamAppWebEmailSocialSlidesPrint
      Product 96 92 70 40 62 20
      Marketing 60 90 94 88 80 72
      Communications 30 76 86 82 90 66
      Market 01 58 84 88 90 74 70
      Market 02 44 72 80 84 66 62
      Market 03 40 70 78 86 60 58
      Agency A 18 66 74 80 52 44
      A team gathered around a laptop in an open office, talking through what is on screen
      Adoption review · Market 03

      Offers & plans

      Brand systems, all at once or one offer at a time.

      Order the whole system or only what you need most, such as templates. We build everything in the tools your teams already use.

      Categories
      04
      Offers
      18
      Plans
      06
      Not sure what you need? Tell us the problem

      How to buy

      1. 01Pick offers. Ask about one, or add several to one enquiry.
      2. 02Choose a plan. A small job, a fixed project or ongoing help.
      3. 03Send your enquiry. We reply within one working day.

      Browse by category

      Timelines are typical. We write the scope before we quote.

      01Tokens & parts

      5 offers
      Typical timeline: 2–3 weeks

      Brand consistency check

      We check your files and libraries for mismatches, duplicates and repeated work. You get a report and a plan for what to fix first.

      What’s included

      • Every file and channel listed
      • Review of near-duplicate parts
      • Report on mismatches and rework
      • Plan of what to build
      • Entry point
      • Sprint
      • Figma

      Best forBrands whose libraries, agencies or markets no longer match

      Typical timeline: 3–5 weeks

      Design tokens

      Your colours, fonts, spacing and motion saved as named values. Designers and engineers then use the same numbers in Figma and in code.

      What’s included

      • Token structure and names
      • Figma variables and modes
      • JSON, CSS and platform exports
      • Automatic token releases
      • One place
      • Design + code
      • Figma
      • GitHub
      • TypeScript

      Best forTeams where product and marketing run different versions of the brand

      Typical timeline: 6–10 weeks

      Component library

      Shared parts, such as buttons and cards, that every channel uses. We design and code each once, so teams stop rebuilding them.

      What’s included

      • Core parts in every state
      • Figma library, all versions
      • Coded parts in your framework
      • Storybook with usage notes
      • Shared parts
      • Figma · code
      • Figma
      • Storybook
      • React
      • TypeScript

      Best forOrganisations building many screens, pages or products on one brand

      Typical timeline: 4–8 weeks

      Multi-brand theming

      One shared library for several brands or markets, each with its own colours and fonts. A new brand reuses the same parts.

      What’s included

      • Theme structure for all brands
      • Tokens for each brand or market
      • Theme switching in Figma and code
      • Rules for adding the next brand
      • Multi-brand
      • Themes
      • Figma
      • Storybook

      Best forGroups with several brands on one app or site

      Typical timeline: 2–3 weeks

      Accessibility check

      We check tokens, parts and templates against WCAG 2.2 AA, so people with disabilities can use them. Fixes go in at the source, so every channel gets them.

      What’s included

      • Colour contrast check
      • Accessibility tests for each part
      • Ranked list of fixes
      • Fixes made in the tokens
      • WCAG 2.2 AA
      • Fixed scope

      Best forBrands with legal or public-sector accessibility duties

      02Templates & channels

      5 offers
      Typical timeline: 3–5 weeks

      Deck & document templates

      Decks, reports and documents with the brand rules built in, made in the office tools your teams already use.

      What’s included

      • Main slide deck with many layouts
      • Report and proposal templates
      • Slide and chart styles
      • Short guide for authors
      • Office
      • Ready to fill

      Best forSales, consulting and leadership teams that work mostly in slides

      Typical timeline: 3–5 weeks

      Social & email templates

      Social and email layouts with text limits, image crops and safe margins built in. Write once, and it fits every format.

      What’s included

      • Social formats per platform
      • Modular email templates
      • Margin and crop rules
      • Editable source files
      • Channels
      • Daily use
      • Figma

      Best forMarketing teams publishing often across many channels and markets

      Typical timeline: 6–10 weeks

      Website templates

      Page templates and content blocks in your website editor (CMS), built from the shared parts. Marketers can then launch new pages without waiting for developers.

      What’s included

      • Page templates and block library
      • Content structure
      • Build in your CMS
      • Editor guide and training
      • Web
      • Editor-ready
      • Contentful
      • Sanity
      • Webflow
      • WordPress

      Best forMarketing teams waiting on developers for every new page

      Typical timeline: 3–5 weeks

      Motion & video templates

      Editable motion templates for social, product and slides. Your brand’s speed and timing are built in, so every video moves the same way.

      What’s included

      • Editable motion and video templates
      • Brand speed and timing built in
      • Titles, end frames and logos
      • Export settings by channel
      • Motion
      • Video

      Best forBrands producing video every week across social and product

      Typical timeline: 3–6 weeks

      Print templates

      Print-ready templates for stationery, brochures, signs and in-store displays, with notes for your printers and suppliers.

      What’s included

      • Stationery and brochure templates
      • Sign and in-store display templates
      • Colour and print specifications
      • Production notes for suppliers
      • Print
      • Supplier-ready

      Best forBrands whose printed materials come from many suppliers

      03Rules & ownership

      4 offers
      Typical timeline: 3–4 weeks

      Flex rules

      Written limits on how far a campaign, market or sub-brand can stretch the brand, with a floor and a ceiling for every element.

      What’s included

      • Colour, font, image and layout ranges
      • Examples by campaign and market
      • Exceptions go to the system owner
      • Tested on a live campaign
      • Clear ranges
      • Campaign-ready

      Best forBrands running many campaigns, markets or sub-brands at once

      Typical timeline: 2–4 weeks

      Ownership & updates

      Roles and a release process that set who can change what. A changelog shows each team which version it is on.

      What’s included

      • Roles and approval rights
      • Release process and version rules
      • Changelog and release notes
      • Suggesting changes
      • Ownership
      • Versioned
      • GitHub

      Best forSystems with many contributors and no clear owner

      Typical timeline: 4–6 weeks

      System documentation site

      A searchable website showing the system in use, with design and code side by side. Every page has a named owner.

      What’s included

      • Documentation site build
      • Design and code examples per part
      • Search and version switching
      • Page owners and editing steps
      • Searchable site
      • Run by your team
      • Storybook
      • React
      • GitHub

      Best forSystems that have outgrown a PDF or a single Figma page

      Typical timeline: 4–8 weeks

      File library set-up

      One file library (DAM) for approved logos, images and templates, with labels, access rights and expiry dates. Teams stop using old downloads.

      What’s included

      • File review and sorting
      • DAM set-up and access rights
      • Approved files moved across
      • Rights and expiry labels
      • DAM
      • Rights tracked

      Best forBrands whose approved files live in shared drives and inboxes

      04Build & run

      4 offers
      Typical timeline: 8–12 weeks

      Brand system build

      The whole system in one project: audit, tokens, parts, templates, rules and documentation. We release it all together as version 1.0.

      What’s included

      • Audit and system plan
      • Tokens, parts and templates
      • Flex and ownership rules
      • Documentation site and v1.0 release
      • Most complete
      • In stages

      Best forOrganisations replacing many mixed libraries with one system

      Typical timeline: 2–6 weeks

      Adoption & training

      Training, drop-in help and a starter guide for teams that build with the system. We also track how much new work uses system parts.

      What’s included

      • Training for each role
      • Starter guide for new teams
      • Drop-in help during rollout
      • Use tracked by team and channel
      • Training
      • Measured by use

      Best forSystems that have launched but are not yet used by every team

      Typical timeline: Ongoing · monthly

      System editor retainer

      We stay on as the system’s editor, led by a named person with set hours. We add parts, review changes and run releases. Each month we report how teams use it.

      What’s included

      • Parts and templates on request
      • Change reviews and releases
      • Monthly report on use
      • Planning every 3 months
      • Retainer
      • Ongoing

      Best forTeams that own the system but lack the time to run it

      Typical timeline: Ongoing · monthly

      Our team inside yours

      Our designers and engineers join your team. They work in your tools and schedule to build or grow the system with your people.

      What’s included

      • Design and front-end experts
      • Your tasks, tools and meetings
      • Weekly progress report
      • Your team learns as we go
      • Squad
      • Billed by time
      • Figma
      • GitHub
      • React

      Best forProduct teams growing a system faster than they can hire

      Your enquiry

      Tick “Add to enquiry” on any offer, choose a plan, then continue. Or enquire about one offer.

      How we work with you

      Ways to start, from a question to a quote.

      Ask a quick question, send your project details or request a quote. The person who will lead the work reads each one in full. Services in your enquiry go with it.

      Or book a 30-minute call

      What are you sending?

      1. 01

        About 2 minutes3 short answers

        For a first chat, a press request or anything not ready to plan yet.

        You get A reply from a named lead

      2. 02Recommended

        About 8 minutes5 short steps

        Goals, who it is for, budget and timing, so our first reply can outline the work.

        You get Options and prices after one call

      3. 03

        About 15 minutesYour documents attached

        Your documents, deadlines and the purchasing and security rules to meet.

        You get Confirmation and a named lead

      How it is priced

      Each plan shows how it is priced. Work starts once we agree a written scope and price.

      • Typical length
        1–3 weeks
        Pricing
        Fixed fee
      • Typical length
        4–12 weeks
        Pricing
        Fixed price
      • Typical length
        3–9 months
        Pricing
        Fixed price per stage
      • Typical length
        Ongoing · 6-month minimum
        Pricing
        Monthly fee
      • Typical length
        6–18 months
        Pricing
        Priced per written scope
      • Typical length
        Ongoing · 3-month minimum
        Pricing
        Paid by time used
      Compare what each plan includes
      What each plan includes and who it suits
      PlanWhat you getBest for
      SprintA short, fixed job that answers one clear question.
      • Scope and result agreed before we start
      • A senior lead and the right specialists
      • A weekly review with you
      • A clear answer or a test version
      An audit, a brand check or a test version of an app
      ProjectOne clear job for one fixed price.
      • A written scope: what you get and how we agree it is done
      • A named project lead and a fixed team
      • A shared plan with checkpoint dates
      • Source files, yours once paid for
      A brand identity, a website, a simple app or a set of tools
      MilestoneA bigger build in stages you approve and pay for one at a time.
      • Stages, each with its own scope and approval
      • A go or stop review at each stage
      • Re-plan between stages as you learn
      • Pay for each stage you approve
      Work too big for one contract, such as a large app
      RetainerA monthly team that runs and improves what we built.
      • Team time set aside for you every month
      • Agreed response times for requests and fixes
      • A monthly review and a to-do list
      • Planned improvements, not only fixes
      Monthly social media and ads, or care for live sites and apps
      EnterpriseA large, long project with its own team and agreed response times.
      • A project director and a decision group
      • A team for each part of the work
      • Response times, reports and a list of risks
      • Security, legal and purchasing checks in the plan
      Large companies making changes across markets, brands or business units
      SquadOur specialists join your team and work in your tools.
      • Named specialists matched to your plan
      • Works in your own tools and meetings
      • Grow or shrink the team each month
      • We teach your team from week one
      Teams with a clear plan that need senior people fast

      12/reference/questions

      Questions teams ask before they start.

      Filter by topic or search. If your question is not here, bring it to the first call.

      7 questions

      It includes one, and more. A design system is your app’s kit of buttons and screens. The same tokens also serve web, email, social, slides and print.

      Yes. We build in the tools your teams already use, with tokens exported as Figma variables and as code.

      Your team does, using the ownership rules and update schedule we agree. What we make for you is yours once it is paid for. Tools we already had stay ours, and you get a free, permanent licence to use them. We can also stay on as the system’s editor.

      Yes. You can buy design tokens on their own and add parts and templates when you are ready.

      Automatically, from one file. Each release exports CSS, JSON and design-tool variables. Nobody copies values by hand.

      First, the market adapts within the flex ranges. If that is not enough, it proposes a change. The system owner decides if it joins the system or stays local.

      To check and draft, never to decide. AI checks files against tokens, ranges and contrast, groups duplicates and drafts release notes. People decide what goes live.

      Tell us what you need built.

      You will talk to the lead who would run your work.

      Book a call

      Three ways to start

      We always agree a written scope and price before work begins.

      Choose one of the three ways above