Brand guidelines
A working document covering logo usage, type scale, colour tokens, photography direction and tone of voice.
What we offer
Four services.
One team delivering them.
Most engagements combine two or three of these. We'll tell you which ones you actually need — including when the answer is "fewer".
01 / 04
Brand Identity
Positioning, naming, logo systems, typography, colour and the written guidelines that keep it coherent once twenty people start using it.
02 / 04Product Design
User research, information architecture, interface design and component libraries built against real engineering constraints.
03 / 04Web Engineering
Marketing sites and application front-ends. Semantic markup, real accessibility, and performance budgets we hold ourselves to.
04 / 04Motion & 3D
Interface motion, brand animation and lightweight 3D — used where it clarifies something, not where it merely impresses.
Deliverables
What lands in
your drive at the end.
No vague "strategy documents". Everything below is a real file your team can open and use.
Source design files
Organised, named and componentised — not a canvas of loose frames you have to reverse-engineer.
Component library
Coded components with usage notes, states and accessibility behaviour documented per element.
Performance report
Lighthouse and Core Web Vitals measured on real hardware, with the budget we committed to at the start.
Handover walkthrough
A recorded session covering structure, decisions and the parts that will bite you if you change them carelessly.
Thirty days of support
Bug fixes and questions answered after launch, included. Not an upsell, not a retainer you have to negotiate.
Engagement
How a project
usually runs.
A typical engagement is ten to sixteen weeks. Shorter sprints are possible when the scope is genuinely narrow — we'll say so if it isn't.
See pricingStakeholder interviews, an audit of what exists, and a read of your analytics. We end this phase with a written problem statement you have to agree with before we continue.
Two or three distinct creative routes with the trade-offs spelled out. You pick one. We do not average them together into something nobody chose.
Design and engineering run in parallel on a shared staging URL. You get a demo every Thursday and can click through the real thing whenever you want.
Content migration, QA across browsers and assistive tech, performance verification, then documentation and a recorded walkthrough for your team.
