"We need a new logo" is one of the most common briefs an agency receives, and one of the least accurate. What the business usually needs is for everything it puts in front of a customer — the website, the proposal, the van, the invoice, the Instagram grid — to look like it came from the same competent company. A logo cannot do that on its own. A system can. And in that system, the logo is the cheapest, fastest part.
What the logo does, and does not, do
A logo identifies. It is the signature at the bottom of the page — recognisable, ownable, consistent. What it does not do is communicate: it cannot tell a prospect that you are precise, or warm, or expensive, or fast. That work is done by everything around it — colour, type, imagery, language, layout — applied consistently enough times that the customer stops noticing the parts and starts recognising the whole.
This is why a business can change its logo and nothing happens, and can keep its logo, fix everything else, and be perceived as a different company. Recognition is built by the system.
What a real identity system contains
1. Positioning, written down
Before anything is drawn: who the business is for, what it stands against, what it should own in the customer's mind. One page. Every later decision — is the palette warm or cool, is the voice formal or direct — gets checked against it. Identity work that skips this stage produces attractive things that do not add up.
2. The logo suite
Not one file. A primary lockup, a secondary (stacked or horizontal) version, a standalone mark for small spaces, mono and reversed versions for dark backgrounds and single-colour print, and a favicon and app icon. All as vector (SVG, PDF) with raster exports at defined sizes, plus clear-space and minimum-size rules.
3. Colour, with the pairings that pass
A palette is a list of colours. A system says which colour goes on which, and proves it: every text-on-background pairing checked at WCAG 2.2 AA contrast (4.5:1 for body text, 3:1 for large text and UI). Values supplied in HEX, RGB and CMYK and as CSS custom properties, so the developer and the printer are working from the same source. A palette that fails contrast is a palette that will be quietly overridden the first time a developer runs an audit.
4. Typography, with a loading strategy
A display face, a text face, a scale of sizes and weights, and the rules for headings, body, captions and UI. And — the part most guidelines omit — how it loads on the web: which weights are actually used, whether a variable font replaces four files, how it is subsetted, and what the fallback stack is so text does not jump when the font arrives. A beautiful four-weight serif that adds 300 KB and a flash of unstyled text is a design decision with a performance cost, and it should be made knowingly.
5. Imagery and iconography
Photography style (candid or staged, warm or neutral, people or product), illustration style if any, an icon set with consistent stroke and corner rules, and guidance on what not to use — which is where most inconsistency creeps in once the stock-photo account is shared.
6. Tone of voice
How the brand writes: sentence length, formality, humour or none, how it handles jargon, what it calls its customers. With before-and-after examples, because "friendly but professional" means nothing without them. This is the part of the identity that shows up in every email your team sends.
7. Layout and component rules
Grids, spacing, how the logo sits on a page, how cards and buttons and callouts are constructed. For digital products, this becomes a design system — tokens and components in Figma that map one-to-one onto code, so the website and the app stay consistent long after the agency has gone.
8. Templates for the touchpoints you actually use
Not a brochure you will never print. The proposal document, the email signature, the pitch deck, the social post formats, the invoice, the vehicle livery if you have vehicles. Whatever the business produces every week is what the system must make easy.
Why the production details decide everything
An identity is judged in a mood board and lives in production. The four-weight display font looks superb in the presentation and adds a second to every page load. The pale grey body copy is elegant and fails contrast for a third of your visitors. The logo arrives as a 4 MB PNG and becomes the heaviest object on the homepage. None of this is visible in the pitch, and all of it is visible to Google, to accessibility auditors, and to anyone on a mid-range phone.
The way to avoid it is to have the people who will build the thing in the room while it is designed. Palettes checked for contrast before approval. Type chosen with load cost as a constraint. Logos delivered as SVG. Interfaces prototyped against the same performance budget the developers will be held to. This is not a compromise on the design; it is what makes the design survive.
How to tell real guidelines from a PDF of swatches
Open the document and ask:
- Could a developer build a page from this without asking the designer anything? Are there CSS values, contrast-approved pairings, and a type scale in pixels or rems?
- Could a printer produce a business card without a phone call? Are CMYK values and clear-space rules there?
- Could a new marketing hire write a post in the brand's voice from the examples given?
- Are the mono, reversed and small-size logo versions present, or just the full-colour one on white?
- Does it say what not to do — the stretched logo, the off-palette blue, the wrong photo style?
If the answer to most of those is no, you have a style sheet, not a system — and consistency will erode within a quarter.
When a logo alone is the right brief
To be fair to the small brief: a startup that needs to exist by next month, a side project, a business testing a name before committing. A clean mark with a palette and a typeface, delivered fast, is a legitimate deliverable — our Basic Logo package exists for exactly this. The mistake is not starting small; it is believing the small thing is the whole thing, and then wondering three years later why nothing looks like it belongs together.
Buy a logo when you need to be identified. Buy an identity system when you need to be recognised — and make sure the people building the website are in the room when it is designed, because that is where it will live.
Our design and branding service runs positioning first, delivers the full system with production-checked colour and type, and hands over guidelines your team or the next designer can actually extend. When the identity is for a product, the UI/UX phase runs inside the web build so nothing is designed twice.
Frequently asked questions
What is the difference between a logo and a brand identity?
A logo is a single mark. A brand identity is the whole system that makes a business recognisable and consistent: the logo suite, colour palette, typography, imagery style, tone of voice, layout rules and the guidelines that let anyone apply them the same way across a website, a proposal, a vehicle and a social post.
What should brand guidelines include?
Logo versions and clear-space rules; exact colour values in HEX, RGB, CMYK and as CSS variables, with approved contrast pairings; the type system with sizes and a web loading strategy; imagery and iconography style; tone of voice with examples; and templates for the touchpoints the business actually uses. Guidelines that stop at swatches are not guidelines.
How long does a brand identity project take?
A logo suite alone takes two to three weeks. A full identity with strategy, system, guidelines and collateral typically runs four to eight weeks, governed mostly by how quickly decisions come back from the client side.
