A brand that holds, because it runs.
Type, colour, grid and logo live as operators rather than a 90-page PDF nobody opens. The system is executable, so it can only produce work that is already on brand.
Stop writing rules nobody reads and start shipping rules that run.
The guideline is the thing that makes the work
Not a document describing what the work should look like — the operators that produce it. Type, colour, grid, logo, spacing and treatment are wired together, and everything downstream is built by running them. There is no gap between the rule and the artwork, because they are the same object.
See the identity as one connected system
Type, colour and treatment sit side by side on one canvas, wired to each other. Change the primary colourway and you watch it move through the lockup, the layout and the material at once — instead of checking it page by page across three files and a deck.
Apply the system onto real products and placements in a batch
Point the system at a list — the pack range, the store fascia, the fleet, the social set — and it applies itself across all of them. Not a mockup a designer builds by hand, but the same system placed onto every surface you actually have to cover.
Going off-brand is not an available option
The author exposes a handful of controls and locks the rest. A regional team or an outside agency gets a surface with the choices they are allowed to make — pick a colourway, add a headline, upload a product shot. The wrong version of the logo is not something the interface can produce.
Save the system as a Recipe so the whole team builds from it
The finished system becomes a Recipe — one thing to hand a new designer, a new market or a new agency. Everyone starts from the system instead of from a blank canvas and a folder of old files.
Same identity, two shapes.
Today
The guidelines ship as a PDF, and it is out of date the week it lands. Nobody opens page 47. Everyone improvises from whatever file they were sent last, so the brand drifts — a little in every market, a little on every brief — and policing it is somebody's full-time job.
With nooodles
The system is executable. Work is made by running it, so drift is structurally impossible — the wrong type, the wrong ratio and the wrong colour are not states the system can reach. When the brand evolves, you change the operator once and everything made from it is already correct.
The same system becomes something people can play with.
Applying the brand across products and placements is a workflow — it hands your team files to place. But the system itself can also ship as a scene: a live playground anyone in the organisation opens in a browser and explores.
So instead of a document people ignore, the brand is a surface they use. A product manager in another market tries their idea against the real system and sees, immediately, what it looks like when it is done properly — and cannot break it while doing so.
The brand kit
Lockups, layouts, mockups and applications — files your team places across the business.
- Mode
- Workflow
- Who opens it
- You and your team
The brand playground
A live page where anyone can try the system, in the browser, without breaking it.
- Mode
- Scene
- Who opens it
- Everyone in the organisation
Start from something that already works.
These ship with the beta — open them, run them, or take them apart.
Brand Kit
WorkflowHold type, colour, grid and logo as live operators. The system everything else is built from.
by Jacques ParysMockup Placer
WorkflowPlace artwork onto products and environments, in a batch.
by Jacques ParysType Lockup Kit
WorkflowSet lockups across sizes, ratios and clear-space rules.
by Jacques ParysBrand Playground
SceneLet anyone explore the brand in a browser without breaking it.
by Jacques ParysWhat brand teams ask first.
How is this different from a component library?
A component library holds the pieces and expects a person to assemble them correctly. This holds the rules that do the assembling, and it emits finished work — stills, motion, 3D and live pages — rather than artboards someone still has to export and adapt. The two sit well together: keep the library for design, use the system for production.
Do we throw away the guidelines document?
No. The document is where the reasoning lives — the story, the tone, the why. What it is bad at is being the thing that makes the work, because it can only describe. Keep the rationale as a document and move the executable half into the system.
What happens when the brand evolves?
You change the operator. A new primary colourway, a revised lockup, tighter spacing — edit it once in the system and re-run. Everything made from it comes out correct, and you are not chasing down which files were made before the change.
Does everyone have to learn the node graph?
No. One person authors the system and decides which controls are open. Everyone else — regional teams, agencies, whoever is making the work this week — gets a surface with those controls and nothing else. They never see the graph.
Can outside agencies and partners work inside it?
Yes, and this is where it earns its keep. Send a partner the operator surface or the playground link instead of a PDF and a zip of logo files. They produce work that is on brand by construction, and your review stops being a hunt for violations.
Make the guideline the thing that works.
Free to start, nothing to install. Or tell us how your brand is governed today and we'll walk you through the hand-off with your own system.
Working with a team?
Tell us where to reach you and we'll set up a walkthrough.
No spam. A real reply from a human.