@yourbrand/systemv2.4.0Shared brand rules

Brand systems every team can build with.

We design tokens, components, templates and rules for product, marketing and communications teams. Agents check every asset; a named person approves releases.

Typical length
6–12 weeks
Scope
Tokens · components · templates
Release
Versioned
Built on
Tokens → components → templates → channels

Illustration: when a design token such as the primary colour or corner radius changes, the components, templates and channels built on it update in turn.

02/signature/token-editor

Design tokens carry one change to every channel.

Pick a colour, corner radius, type scale and density. Six components update, the tokens export in three formats and an agent reports what changed and what now fails contrast.

tokens / your-brand.json branch proposal/primary Autoplaying · 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

Agent · impact report0 changes

    Contrast · WCAG 2.2

      People decideThe agent flags issues; the system owner approves the release or sends it back.

      03/what-we-build/manifest

      Six parts all teams use.

      Product, marketing and communications build from the same tokens, so an app button and an email call to action follow the same rules. The system comes as six versioned packages, each listing what it depends on, so you can see what a change will affect.

      system install @yourbrand/system

      1. Design tokens

        Colour, type, spacing, radius and motion as named values, exported to design tools and code.

        One source

        No dependencies · the root

      2. Component library

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

        Shared parts

        Requires tokens

      3. Templates & layouts

        Templates for landing pages, decks, email, social and print that stay on 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. Governance & versioning

        Who can change what, how changes are released 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 source of truthSelect a package to trace what it depends onVersions illustrative

      A design system open on a monitor: colour tokens, text styles, widget templates and a component library
      Tokens, styles and components 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 a brief to test the rule.

      Load a brief

      4 of 4 in rangeNo exception needed

      1. 01 · Blue coverage of the surface

        Blue leads, paper carries. Accents may grow for campaigns.

        In rangeInside the band. No exception needed.

      2. 02 · Display size against body

        Outfit display, Montserrat reading. Scale may grow, never flatten.

        In rangeInside the band. No exception needed.

      3. 03 · Crop and treatment

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

        In rangeInside the band. No exception needed.

      4. 04 · Departure from the 12-column grid

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

        In rangeInside the band. No exception needed.

      Bands illustrativeAn agent measures each asset against the ranges before release. Exceptions go to the system owner.

      05/audit/component-inventory

      A component audit that removes duplicates.

      The audit collects components from every file, agency and market, then groups the near-duplicates. You keep one approved version of each, plus the variants you need.

      Variants
      92
      Retired
      0
      Source
      7 files · 3 agencies

      Showing the audit: 92 component variants 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

      AgentGroups near-duplicates by appearance, settings and where they are used, and proposes one canonical version for each group.

      PeopleDesigners and engineers choose and name the canonical version and decide which differences become variants.

      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 enforces

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

      07/governance/releases

      Who changes what, and how everyone finds out.

      Changes are proposed, reviewed and released with a version number that shows whether they fix, add or break something. Each team chooses which releases it hears 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. Agent checks · 2 contrast flags
        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 six-week overlap for migration
      5. v1.4.0 minor

        Illustrative · Q4

        Email and market packs

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

        Illustrative · Q3

        First release

        • AddedToken set, core components and the first templates

      08/documentation/system-site

      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/pipeline

      Four stages, each with a sign-off.

      Tokens come first because they fix most inconsistencies. Components and templates follow where they are used most. A stage closes only when its deliverables pass review, the way code is released only when its tests pass.

      pipeline brand-system / main

      All 4 stages passed · v1.0 tagged

      1. stage 1/4

        passed

        Audit

        Wk 01–02

        We review every touchpoint for where the brand varies, what gets rebuilt by hand and what costs most to keep consistent.

        • Touchpoint auditpassed
        • Consistency reportpassed
        • System scopereviewed

        Gate · sign-off before stage 2

      2. stage 2/4

        passed

        Foundations

        Wk 03–05

        We define and export the tokens, then design the core components with every state and build them in your code.

        • Token setpassed
        • Core componentspassed
        • Code exportreviewed

        Gate · sign-off before stage 3

      3. stage 3/4

        passed

        Extend

        Wk 06–09

        We build templates for the channels you publish to most and test the flex rules on a live campaign or market.

        • Template setpassed
        • Flex rulespassed
        • Live testreviewed

        Gate · sign-off before stage 4

      4. stage 4/4

        passed

        Run

        Wk 10–12

        We write the documentation and governance, set a release schedule, train your team and release version 1.0.

        • Documentation sitepassed
        • Governancepassed
        • v1.0 releasereviewed

        Gate · system owner tags the release

      10/deliverables/release-bundle

      What you receive, versioned together.

      Tokens, components, templates, rules, governance, documentation and release notes carry one version number, so design, code and guidelines always agree on what is current.

      Artefacts
      7
      Version
      1.0.0
      Owned by
      You

      @yourbrand/systemv1.0.0bundle

      Release bundle v1.0.0: artefact, formats, version, hash and owner
      ArtefactFormatsVersionHashOwner
      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
      Governance model Document 1.0.0 7e87f11 System owner
      System documentation site Web 1.0.0 d818e00 Design systems lead
      Release notes & versioning Changelog 1.0.0 d9f825f System owner

      7 of 7 artefacts match v1.0.0Hashes illustrative

      11/outcomes/adoption

      Adoption, measured team by team.

      We track the share of assets built from system parts in each team and channel, and treat the gaps as the next piece of work.

      Assets built from system parts Illustrative

      Share of assets 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

      Services & packages

      Brand systems, bought whole or one part at a time.

      Commission the whole system or start with the part you need most: tokens, components, templates or governance. Each part is built in the tools your teams already use.

      Categories
      04
      Services
      18
      Packages
      06
      Not sure what you need? Describe the problem

      How to buy

      1. 01Pick services. Enquire about one, or add several to a brief.
      2. 02Choose a package. A sprint, a fixed project or an ongoing team.
      3. 03Send the brief. We reply within one working day.

      Browse by category

      Timelines are typical. Every quote follows a written scope.

      01Tokens & components

      5 services
      Typical timeline: 2–3 weeks

      Brand consistency audit

      We review every touchpoint, file and component library for inconsistency, duplication and rework, then deliver a report and a scoped plan.

      What’s included

      • Touchpoint and file inventory
      • Near-duplicate component review
      • Inconsistency and rework report
      • Scoped system roadmap
      • Entry point
      • Sprint
      • Figma

      Best forBrands whose libraries, agencies or markets no longer match

      Typical timeline: 3–5 weeks

      Design tokens

      Colour, type, spacing, radius and motion as named values, exported to Figma variables and code so designers and engineers use the same numbers.

      What’s included

      • Token architecture and naming
      • Figma variables and modes
      • JSON, CSS and platform exports
      • Build pipeline for token releases
      • One source
      • Design + code
      • Figma
      • GitHub
      • TypeScript

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

      Typical timeline: 6–10 weeks

      Component library

      The shared parts every channel is built from, designed once with every state and coded in your framework, so teams stop rebuilding them.

      What’s included

      • Core components with every state
      • Figma library with variants
      • Coded components 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 component library serving several brands, markets or sub-brands through token themes, so a new brand reuses the same parts.

      What’s included

      • Theme architecture across brands
      • Token modes per brand or market
      • Theme switching in Figma and code
      • Rules for adding the next theme
      • Multi-brand
      • Themes
      • Figma
      • Storybook

      Best forGroups running several brands or white-label products on one platform

      Typical timeline: 2–3 weeks

      Accessibility audit

      Tokens, components and templates checked against WCAG 2.2 AA for contrast, focus, motion and structure, fixed at the source so every channel inherits the fix.

      What’s included

      • Contrast and colour-pair review
      • Component-level accessibility tests
      • Prioritised fix list
      • Fixes applied at token level
      • WCAG 2.2 AA
      • Fixed scope

      Best forBrands with legal or public-sector accessibility obligations

      02Templates & channels

      5 services
      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

      • Master deck with a layout library
      • 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 formats with safe areas, type limits and image crops built in, so content written once is laid out for each format.

      What’s included

      • Social formats per platform
      • Modular email templates
      • Safe-area and crop rules
      • Editable source files
      • Channels
      • Always-on
      • Figma

      Best forMarketing teams publishing often across many channels and markets

      Typical timeline: 6–10 weeks

      Web & CMS templates

      Page templates and content blocks in your CMS, built from the component library, so marketers can launch on-brand pages without waiting for designers or developers.

      What’s included

      • Page templates and block library
      • CMS content model
      • 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 presentations, with the brand’s animation curves and timings built in so every edit moves consistently.

      What’s included

      • Editable motion and video templates
      • Brand curves and timings built in
      • Titles, end frames and stings
      • Export presets per channel
      • Motion
      • Video

      Best forBrands producing video every week across social and product

      Typical timeline: 3–6 weeks

      Print & production templates

      Print-ready templates and specifications for stationery, collateral, signage and point of sale, with production notes for your suppliers.

      What’s included

      • Stationery and collateral templates
      • Point-of-sale and signage templates
      • Colour and print specifications
      • Production notes for suppliers
      • Print
      • Supplier-ready

      Best forBrands with physical collateral produced by many suppliers

      03Rules & governance

      4 services
      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

      • Ranges for colour, type, imagery and layout
      • Presets for campaigns and markets
      • Exception route 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

      Governance & versioning

      Roles, a release process and a changelog that set who can change what and show every team which version it is on.

      What’s included

      • Roles and approval rights
      • Release process and version rules
      • Changelog and release notes
      • Contribution guide
      • Governance
      • Versioned
      • GitHub

      Best forSystems with many contributors and no clear owner

      Typical timeline: 4–6 weeks

      System documentation site

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

      What’s included

      • Documentation site build
      • Design and code examples per component
      • Search and version switching
      • Page ownership and editing workflow
      • 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

      Asset library & DAM set-up

      One place for approved logos, images, templates and files, with metadata, permissions and expiry dates, so teams stop working from old downloads.

      What’s included

      • Asset audit and taxonomy
      • DAM configuration and permissions
      • Migration of approved assets
      • Rights and expiry metadata
      • DAM
      • Rights-aware

      Best forBrands whose approved assets live in shared drives and inboxes

      04Build & run

      4 services
      Typical timeline: 8–12 weeks

      Brand system build

      The whole system in one programme: audit, tokens, components, templates, flex rules, governance and documentation, released together as version 1.0.

      What’s included

      • Audit and system scope
      • Tokens, components and templates
      • Flex rules and governance
      • Documentation site and v1.0 release
      • Most complete
      • Phased

      Best forOrganisations replacing a patchwork of libraries with one system

      Typical timeline: 2–6 weeks

      Adoption & training

      Training, office hours and onboarding for the teams who build with the system, plus tracking of how much new work uses system parts.

      What’s included

      • Role-based training sessions
      • Onboarding guide for new teams
      • Office hours during rollout
      • Adoption tracking by team and channel
      • Enablement
      • 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, adding components, reviewing contributions, running releases and reporting adoption monthly, with a named lead and set capacity.

      What’s included

      • Component and template requests
      • Contribution review and releases
      • Monthly adoption report
      • Quarterly roadmap session
      • Retainer
      • Ongoing

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

      Typical timeline: Ongoing · monthly

      Embedded systems squad

      Designers and front-end engineers who join your team, working in your tools and sprints to build or grow the system with your people.

      What’s included

      • Design and front-end specialists
      • Your backlog, tools and meetings
      • Weekly progress reporting
      • Knowledge transfer built in
      • Squad
      • Time & materials
      • Figma
      • GitHub
      • React

      Best forProduct organisations scaling a system faster than they can hire

      Your brief

      Tick “Add to brief” on any service, choose a package, then continue. Or enquire about one service directly.

      How we work with you

      Ways to engage, from a question to an RFQ.

      Ask a quick question, send a project brief or issue a formal RFQ. The lead for the work reads each one in full, and any services already in your brief go with it.

      Or book a thirty-minute call

      What are you sending?

      1. 01

        About 2 minutes4 required answers

        For a first conversation, a press request or anything that does not need a scope yet.

        You get A reply from a named lead

      2. 02Recommended

        About 8 minutes5 short steps

        Goals, audiences, a budget band and timing, so our first reply can outline the work.

        You get Options and a first scope after one call

      3. 03

        About 15 minutesYour documents attached

        Your documents, deadlines and the procurement and security rules the work must meet.

        You get Receipt confirmed and a named bid lead

      How it is priced

      Each package shows its pricing model. Work starts once a written scope and quote are agreed.

      • 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 milestone
      • Typical length
        Ongoing · 6-month minimum
        Pricing
        Monthly fee
      • Typical length
        6–18 months
        Pricing
        Programme fee · by statement of work
      • Typical length
        Ongoing · 3-month minimum
        Pricing
        Time & materials
      Compare what each package includes
      What each package includes and who it suits
      PackageEvery engagement includesBest for
      SprintA short, fixed-scope engagement that answers one defined question.
      • Scope and outcome agreed before day one
      • A senior lead plus the specialists needed
      • A working review every week
      • A decision-ready answer or prototype
      Discovery, a diagnostic, a prototype or a decision you need to make soon
      ProjectA defined scope, delivered for a fixed price.
      • Statement of work with deliverables and acceptance criteria
      • A named project lead and a fixed team
      • A shared plan with dated checkpoints
      • Source files, yours once paid for
      Work you can describe up front: an identity, a platform or a set of tools
      MilestoneA larger build in phases you approve and pay for one at a time.
      • Phases with their own scope, output and sign-off
      • A go or no-go review at every gate
      • Re-planning between phases as you learn
      • Payment tied to accepted milestones
      Programmes too large for one contract, where you want control at each step
      RetainerReserved monthly capacity to run, improve and extend what we built.
      • A reserved block of team time every month
      • Agreed response times for requests and fixes
      • A monthly review and a rolling backlog
      • Planned improvements as well as upkeep
      Live brands and products that need a steady team without hiring one
      EnterpriseA multi-workstream programme with a dedicated team, governance and agreed service levels.
      • An engagement director and a steering group
      • A dedicated team across several workstreams
      • Service levels, reporting and a risk register
      • Security, legal and procurement reviews in the plan
      Large organisations running change across markets, portfolios or business units
      SquadA dedicated team that works inside your stack and sprint schedule.
      • Named specialists matched to your roadmap
      • Works in your tools, meetings and backlog
      • Scale the team up or down each month
      • Knowledge transfer built in from week one
      Teams with a clear roadmap that need more senior people quickly

      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

      A brand system includes one and extends it to marketing and communications. One set of tokens serves the app, website, 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 runs it, with the governance and release schedule we set up together. 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. Design tokens can be bought on their own, and components and templates added when you are ready.

      One source file exports to CSS variables, JSON and design-tool variables on every release. Nobody copies values by hand.

      It works within the flex ranges first. If the need falls outside them, the market proposes a change and the system owner decides whether it joins the system or stays local.

      Agents check assets against tokens, ranges and contrast, group duplicates in audits and draft release notes. People review what agents flag and decide what goes live.

      Tell us what you need built.

      You will speak to a lead who would run the work, and get a straight answer on fit.

      Book a call

      Three ways to start

      Every engagement starts with a written scope and a quote agreed before work begins.

      Choose one of the three ways above