Illustrative imagery

Consumer health20256–9 months

One brand system for nine markets

Client: A consumer-health brand sold in nine markets

A plain card carton beside a frosted glass jar with a blank label, on a pale stone ledge.
Read the story
  • Brand Design
  • Campaign & Content Design
  • AI Design

At a glance

The goal. Hold one brand across nine markets without slowing any of them down.

Client
A consumer-health brand sold in nine markets
Year
2025
Duration
6–9 months
Scale
9 markets

Picture story

The packs, on one shared grid.

These pictures are examples: licensed stock photos and mock-ups we built in code. They show the setting, not the client’s own work. Credits are at the foot of the page.

A blank pale pink carton and a white tube with a pink cap against a soft pink wall.
Fig. 01Carton and tube: two of the formats one pack grid has to hold.Avtar Singh on Unsplash (opens in a new tab)
An amber glass dropper bottle with a blank label standing on a concrete block.
Fig. 02The smallest label follows the same rules.Avtar Singh on Unsplash (opens in a new tab)
Colour swatch cards fanned into a full circle on a grey surface.
Fig. 03Colour comes from the design tokens, whichever market prints the pack.Andy Brown on Unsplash (opens in a new tab)
Four colleagues lean over printed pages on a wooden table, one pointing at a detail.
Fig. 04Market leads review printed variants against the shared rules.Andreea Avramescu on Unsplash (opens in a new tab)
A night market seen from above, its long street lined with lit stalls between tall apartment blocks.
Fig. 05Nine markets, nine retail settings.Willian Justen de Vasconcellos on Unsplash (opens in a new tab)
Pedestrians cross a wet city street at dusk, car headlights reflected on the road.
Fig. 06The same pack has to work in all of them.Donny Jiang on Unsplash (opens in a new tab)

On screen

The guidelines site, and the brand-check agent that reads it.

Example screens we built in code, like the ones the project made. They are not the client’s own. Open any full screen.

Illustration: a living brand guidelines site open at Colour, listing five colour tokens with their values and the rule for which markets may flex each one.
DesktopThe guidelines site: tokens, pack templates and the flex rules for each market.
Illustration: a phone showing a brand-check result for a pack. Four checks pass; the claim check is flagged and routed to medical-legal review.
PhoneThe brand-check agent on a reviewer’s phone: one claim flagged, routed and logged.

Before and after

The same pack, before and after the shared grid.

An example before and after, built in code, of the kind of change the work made. These are not the client’s screens. Drag across to compare.

Illustration: nine versions of the same pack, each with a different colour, type style and layout. Before · nine local versions
Illustration: the same nine packs built on one grid, colour and type consistent, each with its own market code. After · one grid
Before · nine local versionsAfter · one grid The same product across nine markets, before and after the pack grid. Illustrative.

From goal to result

The programme, from brand rules to rollout.

The goal in full, our approach, what we built and what it set out to change.

The goal, in full

Each market rebuilt packs, claims and campaign assets locally. The same product could look and sound different in each market, and every new asset went through full review again.

The brief: hold one brand across all nine without slowing any market, and keep every health claim traceable to its approval.

Our approach

We started with the rules: what stays fixed, what each market may adapt and who signs off. They became design tokens and pack templates that every market builds from.

Each approved claim is stored with its markets, evidence and review date. The brand-check agent checks every asset against that library before a person sees it.

How it ran

  1. Weeks 1–4Audit

    Every live pack and asset across the nine markets, laid out on one grid.

  2. Weeks 5–10Rules

    Fixed, flexible and local: three tiers written down and agreed with each market lead.

  3. Weeks 11–20Build

    Tokens, pack templates and the claims library, published on a guidelines site.

  4. Weeks 16–24Agent

    The brand-check agent, tested on past assets before it saw a new one.

  5. Months 6–9Rollout

    Market by market, with a person approving every asset the agent flags.

What we built

Design tokens with flex rules for each market, a shared claims library and a brand-check agent that flags off-brand assets before review.

What we made

  1. Brand guidelines website
  2. Design tokens and pack templates
  3. Claims library with approval history
  4. Brand-check agent and audit log

What changed

The system is built so every market starts from the same tokens, templates and approved claims, and every asset is checked before review.

Each market is judged on the three measures below. The figures stay with the client until they approve publishing them.

How it is measured

Brand kit

Colour and type, built to flex by market.

Each colour with its role, share of use and contrast. Each typeface with its job. Press a colour to copy its code.

Colour

  • Slate #1F2A2E

    Text and marks

    On white
    14.7:1 AAA
    On near-black
    1.2:1 Fails
  • Paper #F4EFE8

    Backgrounds

    On white
    1.1:1 Fails
    On near-black
    15.3:1 AAA
  • Clay #C9A68A

    Packs and accents

    On white
    2.3:1 Fails
    On near-black
    7.8:1 AAA
  • Sage #7FA38F

    Category colour

    On white
    2.8:1 Fails
    On near-black
    6.3:1 AA
  • Signal #E4572E

    Warnings and mandatory text only

    On white
    3.7:1 AA large
    On near-black
    4.8:1 AA
Share of use Slate 40%, Paper 32%, Clay 14%, Sage 9%, Signal 5%

Type

  • DisplayMedium 500Semibold 600

    A humanist sans, licensed

    One system. Nine markets.

  • Text and packsRegular 400Medium 500

    A neo-grotesque with wide language support

    Read the label before use. Keep out of the reach of children.

Samples use this site’s own fonts as stand-ins. Each card names the font the project uses.

Field notes

Notes from the project, in detail.

Why the agent never approves

A wrong health claim in one market is a regulatory problem, so the agent never signs off. It compares each asset with the tokens, pack grid and that market’s approved claims. Anything it cannot match goes to a named reviewer.

The agent flags and routes. A person decides.

The programme’s working rule
  • Colours within the token tolerance
  • Type set in the approved families and sizes
  • Every claim present in the approved library for that market
  • Pack grid, mandatory text and warnings in place
  • The decision and the reviewer logged against the asset

Outcomes

Each market, judged on review, speed and reuse.

What each measure is compared with, when we read it and who reports it. Results show once the client approves them.

The measurement plan

  1. Assets passing brand review first time

    Compared with
    Each market’s review log for the year before the system
    Read
    Quarterly, from each market’s first month on the system
    Result
    Awaiting approval Reported by The client’s brand team
  2. Brief-to-approved time per market

    Compared with
    Median days from brief to approval before rollout
    Read
    Three months after each market switches over
    Result
    Awaiting approval Reported by Market leads, from the approval workflow
  3. Share of assets built from templates

    Compared with
    Template use in the asset library before rollout
    Read
    Monthly, from the asset library
    Result
    Awaiting approval Reported by Brand operations

Results

Figures pending client approval

We publish results only with the client’s written approval. Until then, we judge the project on the plan shown here. Ask for a private walk-through.

Credits

The team and the pictures.

People are named only with their agreement.

Team 8 people

  • Programme lead × 1
  • Brand strategist × 1
  • Design lead × 1
  • Designers × 3
  • Design technologist × 1
  • AI engineer × 1

Credits

Strategy, design and engineering
Xterra Edze
Screens and before-and-after views
Xterra Edze (code-built illustrations)
Photography
Licensed stock from Unsplash, credited picture by picture

Pictures 11

Licensed stock photos and mock-ups we built in code, to show the setting. None is the client’s own work.

Next case · 02 · Financial services

A CRM that knows what happened last

Make every customer message aware of the last thing that happened.

Read the next case

Tell us what you need built.

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

Book a call

Three ways to start

  1. 01About 2 minutes

    A quick question

    You get A reply from a named lead

  2. 02About 8 minutesRecommended

    Your project details

    You get Options and prices after one call

  3. 03About 15 minutes

    A request for a quote

    You get Confirmation and a named lead

We always agree a written scope and price before work begins. How each plan is priced