We build brand systems for companies that ship software, which is a different problem from branding a physical product. A logo has to work at 16 pixels in a browser tab. A palette has to pass contrast requirements. A typeface has to load fast and support every script your customers read in.
Digital constraints come first
We design against real constraints rather than discovering them later: contrast ratios checked at the palette stage, type scales tested at body sizes on a phone, the mark drawn so it survives being shrunk to a favicon. It is less romantic than a brand book and considerably more useful.
- Every colour pair checked against WCAG 2.2 AA before it enters the palette
- Type tested at 14px on a mid-range phone, not at 96px in a presentation
- Marks drawn to survive a 16px favicon and a monochrome print
- Multi-script support specified where you operate in more than one
Guidelines people follow
A 90-page PDF nobody opens is not a brand system. We ship design tokens in code alongside the documentation, so the palette is the same object the engineers import — the guidelines and the product cannot drift apart, because they are the same source.
Enough assets to actually launch
Identity work often stops just before it becomes useful. We include the unglamorous set: social templates, email headers, presentation masters, favicon and app icons at every required size, and Open Graph cards.