Branding & Design
Consistent, whoever makes the next thing.
Logo and identity, brand guidelines, packaging, UI/UX and the pitch decks that have to work without you in the room.
A recording rhythm you can actually sustain
How we think about it
A brand is not a logo. It is the set of decisions that stop the fiftieth thing you make from looking unrelated to the first. Type scale, colour, spacing and tone, written down and handed over, so the next person to open the file does not have to guess. Built to be used by people who are not designers.
The design system is built as real tokens and components by the people who will implement it, so the guidelines and the shipped site cannot drift apart.
What this covers
The work, specifically.
- 01
Logo and brand identity
A mark and system that survives being scaled, printed and stitched.
- 02
Brand guidelines
Written clearly enough that someone who has never met us stays on-brand.
- 03
Packaging design
Print-ready, with the regulatory panels and dielines handled.
- 04
UI/UX design
Designed in components, handed to build as a system rather than a picture.
- 05
Pitch decks and profiles
The document that gets forwarded and has to argue on its own.
Need Branding & Design for something specific?
Tell us what you're trying to ship and we'll say plainly whether this is the right service for it — including when the answer is no.
How it runs
The same four steps, whatever we're building.
No account-manager relay. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy.
Scope
A week of hard questions. We map what you actually need and say plainly which parts we'd cut.
Prototype
Something real in front of you early, not a document about it. Opinions get cheaper.
Build
Two-week cycles, a demo at the end of each. You see progress, not status reports.
Hand over
Documentation, a walkthrough, and the keys. Support if you want it — never as a hostage.
Questions
The things people ask before they enquire.
It depends on scope, but we will give you a number before you commit to anything. Most engagements start with a paid discovery — a fixed fee, a week or two — which ends in a written scope and a real budget. If the budget does not work, you leave with the scope document and no obligation to continue.
A typical first ship is around six weeks. Larger builds run in two-week cycles after that, each ending in a demo of something that actually runs. You will know within the first cycle whether the timeline is holding, rather than finding out near the deadline.
The people you meet. The lead on your project is someone who builds, and they stay on it from the first call to the last deploy. There is no account manager relaying messages between you and an unseen team.
You own everything — code, assets, accounts, domains. We hand over with documentation and a walkthrough, and your team can run it without calling us. If you would rather we stayed on for maintenance or a next phase, that is a separate agreement, not something buried in the original contract.
Yes. Most of our work is remote, and we keep a few hours of overlap with your working day for calls. Timezone has not been the hard part; unclear scope has.
Where it meets the others