The SaaS brand kit: what's actually inside (12-item checklist)
“Can you send over the brand kit?” is the question that exposes most SaaS brands. An investor wants the deck template, a podcast host wants a logo that survives a dark background, the new marketing hire wants to know which blue is the blue — and what actually exists is a folder called logo_final_v3 with four PNGs and a dead Figma link.
A brand kit is the difference between a brand you have and a brand your team can use. Here is what a real one contains — the checklist we deliver on every brand identity engagement, the formats that survive contact with a real team, and what it should cost.
★ What a brand kit is — and what it is not
A brand kit is the operational package of your identity: every asset, token, and rule another person needs to produce something on-brand without asking you. The test is exactly that — can a freelancer you hired yesterday ship an on-brand social post, sales deck, or landing page section today, with no Slack thread?
What it is not: a logo file dump, a 90-page brand book nobody opens, or a moodboard. If you are still fuzzy on how identity, visual identity, and logo relate, we untangled that in brand identity vs visual identity vs logo — the kit is the deliverable form of the first one.
★ The 12 items a SaaS brand kit actually needs
1. Primary wordmark + lockups
The main mark plus its variants: horizontal, stacked, and the monogram/app-icon version. SaaS-specific reality: your mark will live in a 32 px favicon, a 1024 px App Store tile, and an OG image — all three need to be designed, not resized.
2. Monochrome and inverse variants
One-colour black, one-colour white, and the rule for when each applies. This is the item missing from 80% of the kits we inherit — and the reason your logo disappears on the conference-slide template and the dark-mode footer.
3. Colour tokens with usage ratios
Not a palette strip — tokens. Primary, surface, text, accent, semantic (success/warning/error), each with a name, a hex/OKLCH value, and a usage ratio (the 60-30-10 that keeps the accent an accent). Contrast-checked against WCAG AA for text sizes you actually use.
4. Typography pairing and scale
Heading face, body face, the fallback stack, and a modular scale with named steps — not “make it look right”. Include the licence: half the SaaS teams we meet are shipping a font they never licensed for web embedding.
5. Iconography style
Stroke weight, corner radius, grid size, and a starter set of 20–30 icons in that style. The rule matters more than the set — it is what keeps icon number 31 consistent when someone pulls it from a library.
6. Graphic device or illustration language
The ownable visual move that is not the logo: a shape system, a gradient recipe, a pattern, an illustration style. This is what makes a social card recognisably yours when the logo is 24 px small. It is also the hardest item to fake with a template.
7. Voice and vocabulary one-pager
Three example sentences each for marketing copy, product UI, and support replies — plus the words you use and the words you ban, with reasons. Adjectives (“confident, warm, professional”) are not a voice; examples are. One page, not a chapter.
8. Social templates
Announcement card, quote card, feature-launch card, event card — in the sizes the channels actually use, built from the tokens above, editable by a non-designer. If the template needs a designer to use it, it is not a template.
9. Pitch-deck master
Title, section divider, content, data, team, and closing slides with the type scale and colour tokens applied. Investors see this surface more than your homepage — it is a brand asset, not an afterthought.
10. Product-UI token bridge
The mapping from brand tokens to product design tokens: which brand colours become interactive states, what the border-radius and elevation language is, how the brand type scale adapts to UI density. This is the item that keeps marketing site and product from drifting into two different companies — and the one generic branding agencies skip because they have never shipped product UI.
11. OG and meta images
The 1200×630 template for link previews, the favicon set, the App Store / Play Store assets. Every link your team shares is a brand impression; most SaaS companies ship the framework default.
12. Usage rules — one page of do and don’t
Minimum sizes, clear space, forbidden recolours and stretches, photography treatment. One page with visual examples beats forty pages of prose. The goal is fast “no” answers, not legal completeness.
★ Formats that survive contact with a real team
A kit that only exists as a PDF is already dead. The working format set:
- Figma source — components, styles, and variables published as a team library, so the tokens are usable, not just documented.
- Design tokens file — colours, type, radii as JSON/CSS variables your developers can import instead of retyping.
- One-page PDF cheat sheet — for the people who will never open Figma: sales, finance, the podcast host.
- A shared drive folder with exported logo packs (SVG + PNG on transparent, light and dark) named so a non-designer picks the right file.
★ What a SaaS brand kit costs
Honest ranges, since we publish our prices: as part of a full brand identity engagement, the kit is the deliverable form of the work — included in the $6k–$18k Visual Identity range, scope-dependent. As a standalone “we have a logo, we need the kit around it” engagement, expect the lower half of that range. If someone quotes $500 for “a complete brand kit”, you are buying a template with your logo pasted in — see the red flags below.
Timeline: the kit itself is one to two weeks after identity decisions are made. It is packaging strategy, not producing it — which is why a kit without strategy work underneath is decoration.
★ Five red flags in a cheap brand kit
- No monochrome variants — the first real-world surface (an event banner, a dark UI) breaks it.
- Palette without ratios or contrast checks — you get five pretty colours and an accessibility problem.
- Voice described in adjectives — “bold, friendly, human” describes every SaaS since 2015.
- No product-UI bridge — the marketing site and the app drift apart within a quarter.
- PDF-only delivery — if the tokens are not in Figma variables and a tokens file, your team will eyeball them, and eyeballed tokens drift.
★ FAQ
What is a brand kit for a SaaS company? The operational package of a SaaS brand: logo lockups and variants, colour and type tokens, iconography and graphic device, voice one-pager, social and deck templates, product-UI token bridge, and usage rules — everything a team member or contractor needs to produce on-brand work without asking the founder.
How is a brand kit different from a brand book? A brand book documents and explains; a brand kit equips. The book is prose about the brand; the kit is the working files — Figma libraries, token files, templates — that produce on-brand output. A good engagement delivers a compact book inside the kit, not instead of it.
Can we build a brand kit from our existing logo? Usually, yes. If the logo is structurally sound, the kit engagement designs the system around it — variants, tokens, templates, rules. If the logo cannot survive monochrome or 32 px, you will find out in week one, and that is a rebrand conversation, not a kit one.
Want the kit without the guesswork? Our SaaS brand identity engagement delivers all twelve items as standard scope — see how a full system came together for LegalXSale, or start with the free 15-minute brand audit and we will tell you which of the twelve you are missing.