Writing on Brand, Design,
and B2B Technology

Every few months we speak to a company that went through an expensive redesign twelve to eighteen months ago and is now unhappy with the result. Not because the design was poor — often it was competent, sometimes genuinely good — but because it didn't solve the actual problem. Sales were still slow. Enterprise prospects still seemed confused. The website still didn't convert.

What these companies discovered, usually after the invoice was paid, is that the visual problem was a symptom. The underlying issue was a positioning problem: a failure to clearly articulate what the company does, who it does it for, and why a specific buyer should choose it over the alternatives they're already evaluating. A new logo doesn't fix that. Neither does a new colour palette.

What brand strategy actually is

Brand strategy is not a mood board or a set of adjectives on a slide. It's the answer to four specific questions: What is your category? Who is your primary customer? What is the job they're hiring you to do? And what makes you genuinely different from the alternatives? These sound simple. They are not. Most companies that think they've answered them have answered a softened, consensus-driven version that doesn't actually distinguish them from anyone.

The value of working through these questions rigorously — through interviews, competitive analysis, and structured workshops — is that the answers produce constraints. And constraints are what make design decisions possible. Without them, every creative choice is equally valid, which means no choice is defensible, which means the process becomes a series of subjective preferences with no shared reference point.

The competitive differentiation problem in B2B SaaS

B2B SaaS has a specific version of this problem. Most categories are crowded. Most value propositions sound identical. If you compare the hero sections of any ten project management tools, twelve CRM platforms, or fifteen analytics products, you will find near-identical language: "streamline your workflow," "get visibility into your pipeline," "make better decisions with data." These statements are not wrong. They're just not differentiating.

Differentiation in B2B comes from specificity — specificity of customer, of use case, of stage, of problem. "Analytics for supply chain teams at mid-market manufacturers" is harder to say than "analytics platform," but it's also harder to ignore if you are a supply chain team at a mid-market manufacturer. Narrow positioning feels risky. Broad positioning is actually the higher-risk choice, because it leaves the buyer with no reason to choose you specifically.

How strategy informs design

When a brand strategy is properly documented, design decisions become answerable. Should the visual language be warm or formal? Depends on the buyer — is this an enterprise procurement team or a developer-led product? Should the typography be geometric or humanist? Depends on whether the brand needs to signal precision or approachability. Should the palette include colour or stay monochromatic? Depends on the category conventions and whether the intent is to conform or deliberately contrast.

None of these questions can be answered by taste alone. They can be answered by a documented understanding of who the brand needs to communicate to and what it needs to communicate to them. That's what brand strategy produces. That's why it comes first.

A visual system is not the same as a brand identity, though the two overlap. A brand identity answers the question "what does this company look like?" A visual system answers the question "how does everything we produce stay consistent at scale?" The second question requires the first one to be answered first — but answering the first one doesn't automatically produce the second.

What most companies discover when they start growing is that design decisions that felt manageable at ten people become unmanageable at forty. Every new hire makes their own interpretation of the brand guidelines. Every new marketing campaign requires a decision about whether the button should be navy or gold. Every product sprint involves a debate about which shade of grey belongs to which element. These are all symptoms of a visual system that doesn't exist.

The difference between guidelines and a system

Brand guidelines are a document. A visual system is an infrastructure. Guidelines tell people what the brand looks like. A system makes it possible to produce brand-consistent work without needing to interpret the guidelines every time.

The difference is practical: guidelines require a human to read, understand, and apply them. A system — properly implemented as Figma tokens, a component library, or a CSS design token file — applies the brand automatically at the point of production. When the primary colour changes, it changes everywhere. When a component is updated, every instance of that component updates. The system removes the human error layer.

What to include in a scalable visual system

The minimum viable set of components that a B2B SaaS company needs to maintain visual consistency across its marketing and product surfaces:

• A colour token system with semantic naming (not "navy" but "colour-primary-action")
• A typographic scale with named levels (heading-xl, heading-l, body-m, caption-s)
• A spacing system based on a consistent unit (usually 4px or 8px base)
• A set of interactive components (buttons, inputs, cards, modals) built from the tokens
• A library of brand-consistent icons, either custom or from a licensed source with defined usage rules
• Clear rules for when to use what — not just what exists

The last point is underappreciated. Companies invest heavily in building the components and almost nothing in documenting when each component is appropriate. The result is a design system that nobody actually uses consistently, because consistent use requires judgment that hasn't been documented.

A practical note on scope

Early-stage companies often overbuild. A Seed-stage company with twelve people doesn't need a design system with 200 components. It needs a design system with twenty components that are well-documented and actually used. Start narrow. Add components when the absence of a component creates a real problem. The goal is not completeness — it's reducing friction at the point of production.

There's a body of research in cognitive psychology — stretching back to work by Robert Cialdini and more recently to attention research by Nielsen Norman Group — that establishes something most designers know intuitively but most marketers underweight: visual processing precedes semantic processing. Before a buyer reads a single word on your website, they have already formed a preliminary judgment about whether this company is credible, professional, and worth their attention.

This judgment is formed from signals that are pre-cognitive: colour, typography, whitespace, and compositional density. It happens in roughly 50 milliseconds — fast enough that it cannot be a conscious, reasoned response. It's pattern recognition against an internal model of "what legitimate companies look like," built from thousands of prior exposures to business communications.

The specific signals B2B buyers read

B2B buyers are not the same as consumer buyers. Their credibility model is calibrated to a different set of signals:

• Typographic restraint. Consumer brands can use expressive, variable typography. B2B buyers read expressive typography as amateur. The typefaces that signal institutional competence are geometric, neutral, and legible at small sizes.
• Whitespace. Dense layouts signal cheapness. Generous whitespace signals that the company has made deliberate decisions about what matters. Enterprise buyers, in particular, read whitespace as confidence.
• Colour discipline. Companies with one or two primary colours and a clear hierarchy of how they're used signal more competence than companies with five colours applied inconsistently. Inconsistency signals a company that hasn't thought carefully about itself.
• Photography and illustration coherence. Mixed visual styles — three different illustration systems, or stock photography next to custom photography — signal the absence of someone who owns the brand. This is noticed.

The enterprise vs. SMB calibration

The visual signals that read as credible to an enterprise procurement team are not identical to those that resonate with an SMB buyer or a developer-led product evaluation. Enterprise signals: formal typography, restrained colour, institutional photography, dense content with clear hierarchy. Developer and SMB signals: clean minimal interfaces, technical credibility cues, less formal voice, social proof from companies they recognise.

This matters because many B2B SaaS companies are trying to serve both markets simultaneously. When they do, they often produce visual language that fails both: too formal for the developer-led segment, not formal enough for the enterprise procurement team. The solution is usually segmented entry points with distinct visual treatments, or a clear decision about which market is primary.

What this means practically

The first practical implication is that investing in brand identity is not a vanity exercise for growth-stage B2B companies. It is a conversion rate optimisation exercise. If the visual credibility signals on your website are miscalibrated for your primary buyer, you are losing deals before a single word has been read.

The second implication is that the sequence matters. Fix the visual credibility layer before you invest in content, copywriting, or paid acquisition. Sending traffic to a website that fails the four-second credibility test is expensive. Fixing the credibility problem first changes the return on everything downstream.