Design the system, not the pages
Type scale, spacing, components and states. Once the system exists, new pages are assembly and the brand stays consistent without policing.
Graphic Design
Identity and interface work built to survive contact with a real website and a real marketing calendar.
Graphic Design
A logo is the easiest part and the least useful on its own
Most brand projects deliver a mark, a colour palette and a fifty-page PDF, and then the first time someone needs a social post at an odd aspect ratio the whole thing quietly falls apart. What a growing business actually needs is a system: rules that hold up when applied by someone who was not in the workshop.
So our brand work is built forwards from application. We design the pages, ads, forms and emails you will actually produce, and derive the system from what those need. The identity is proven against real artefacts before it is signed off, not after.
The same is true of interface design. We design in components with every state specified — hover, focus, error, empty, loading, too-long-name — because the states are where implementations diverge from designs. That specificity is the difference between a design that ships as drawn and one that gets negotiated down during the build.
How we approach it
Three core principles
Prove it on real artefacts
Every identity is tested on the things you will actually make — a service page, a paid ad, an invoice, a shopfront sign — before it is approved.
Specify the awkward states
Errors, empty screens, loading, long names, missing images. Designs that skip these get invented during the build by whoever is closest.
- Brand discovery: positioning, audience, competitive landscape, tone of voice
- Identity design — wordmark, mark, colour, typography, imagery direction
- Accessible colour system with verified contrast pairings
- Digital design system: type scale, spacing, components, every interactive state
- UI/UX design for web, application or store templates
- Collateral: social templates, ad formats, email, print and presentation
- Written brand guidelines with usage rules and real examples
- Handover files, a component library and a walkthrough with your team
Process
How it works
Six steps, with a real artefact in front of you by week two.
-
Step 01
Discovery
Stakeholder interviews, a look at your market, and an honest read on how you are currently perceived versus how you want to be.
-
Step 02
Direction
Two or three distinct territories, each shown on real applications rather than mood boards, so the choice is between outcomes not adjectives.
-
Step 03
Identity development
The chosen direction refined: mark, type, colour with contrast verified, imagery rules, and the awkward cases like tiny sizes and single colour.
-
Step 04
Design system
Components, states and layout rules built as a system in the design tool, structured the way the front end will be structured.
-
Step 05
Application design
The templates and collateral you will actually use, designed and reviewed against the system so gaps surface before handover.
-
Step 06
Guidelines and handover
Written rules, example artefacts, source files and a session with your team — and with whoever builds it, if that is not us.
Why us for this
Designed by people who know what gets built
Every design decision here is reviewed by the developer who would implement it and the marketer who would run campaigns on it. Ideas that cannot survive that meeting get changed early.
Nothing undeliverable gets signed off
No effects that cannot be built performantly, no type sizes that fail on mobile, no layouts that break with real content lengths.
Accessibility built into the palette
Contrast pairings are verified during colour selection, so accessibility is not a compromise applied afterwards.
Systems your team can extend
We hand over a component library and rules, not a static PDF. Your marketing coordinator can make a new page without breaking the brand.
FAQs
Design and branding questions
Usually the better move. If you have recognition worth keeping, we evolve: tighten the mark, fix the palette and typography, and build the system that was never made. It is faster, cheaper, and does not cost you the equity you have built.
Two or three genuinely different territories, each applied to real artefacts. We do not present ten variations of one idea, and we do not present something we would not be happy to build.
Yes, and we hand over the file with a structured component library. If your team works elsewhere, tell us at kickoff and we will accommodate it.
We work to them. If they are silent on digital — which most are — we extend them into a design system rather than starting over, and flag any conflicts we find.
Yes: print collateral, packaging direction, signage and presentation templates. We coordinate with your printers or fabricators on specifications rather than throwing a file over the wall.
Tone of voice and key messaging are part of brand discovery. Full page copy is a separate line item, either written by us or by your team against our briefs.
Yes. Handover is a real deliverable: component library, specified states, written guidelines and a walkthrough session with your developers. We would rather your build succeeds than have it depend on us.