Brand Development

How your company is understood, felt and remembered

From core values and messaging to visual identity, voice, tone, digital presence and printed materials, so every interaction is consistent, confident and recognisably yours.

Triggers

The situations that lead here

The symptoms usually show up in sales conversations long before anyone calls it a brand problem.

  • Prospects reach the call still unsure what you do
  • Every person in the company explains the product differently
  • The website describes the architecture and not the outcome
  • The deck, the site and the product each sound like different companies
  • You have outgrown the positioning you launched with
  • A pivot happened and the story never caught up
  • You are raising, and the narrative has to hold up to scrutiny
  • Good work is losing to competitors who explain themselves better

Scope

What the work covers

Brand as something the whole company can use, not a document that lives with marketing.

  1. Positioning and values

    What the company is for, who it is for, and what it declines to be. The decisions everything downstream depends on, made explicitly rather than inherited.

  2. The message set

    The claims you make, in priority order, with the ones you will not make written down too. So the site, the deck and the sales call finally agree.

  3. Visual identity

    Identity, typography, colour and the rules for applying them. Enough system that non-designers can produce something on-brand without asking.

  4. Voice and tone

    How the company sounds, including in the places nobody thinks of as brand: onboarding, empty states, error messages, release notes.

  5. Touchpoints end to end

    Website, product, sales materials, printed collateral and support. Coherence is built at the seams, which is exactly where it usually breaks.

  6. Something that survives handover

    Guidelines your team can actually apply after the engagement, rather than a beautiful document that ages badly the first time someone needs a new page.

Kendoo's own material, in the room it was made for.

The argument

Consistency is worth more than cleverness

Most technology companies do not have a brand problem in the sense of looking bad. They have a coherence problem: three good explanations of the product and no agreement on which one is the explanation.

That costs real money in ways that never get attributed to brand. Sales cycles lengthen because the buyer has to assemble the story themselves. Marketing rewrites the same page four times. Engineers write product copy in a voice nobody decided on.

The fix is decisions, written down and applied everywhere. Being recognisable and consistent is worth considerably more than being clever once.

How it runs

The shape of the engagement

  1. Listen first

    Interviews with founders, sales and support, plus whatever the market already says back. The positioning is usually already in the company, unevenly distributed.

  2. Decide the positioning

    What you are for, who for, and what you will not claim. This is the part that needs the person who can actually settle it.

  3. Build the system

    Messaging, identity, voice and the rules for applying them, made concrete enough to use rather than admire.

  4. Roll it through the surfaces

    Website, product, sales materials and support, in the order that matters commercially rather than all at once.

What this is, and what it is not

What it is

  • Positioning decisions the whole company can apply
  • A message set with the prohibited claims written down
  • Identity and voice, including inside the product
  • Coherence across every customer touchpoint
  • Guidelines your team can use unaided

What it is not

  • A logo refresh with no positioning behind it
  • A campaign or media buying
  • Ongoing content production
  • A style guide nobody opens twice
  • Claims the product cannot support

Where the real problem is that the product does not yet do what the positioning would claim, that is said plainly. Brand work cannot fix that and should not paper over it.

Questions executives ask

We are a technology company. Is brand really our problem?

It is if buyers cannot tell what you do. Technical companies usually describe their architecture where the buyer needed the outcome, and every surface says it differently. That is a brand problem with a commercial cost, whatever you call it.

Is this a logo project?

A logo is one output and rarely the one that matters most. The work starts with what you actually stand for and who you are for, because a visual identity applied to unclear positioning just makes the confusion more consistent.

Who needs to be involved?

Whoever can settle what the company is for. If that question is genuinely open, brand work will surface it in week one and the engagement stalls until it is answered. It is usually better to find that out early.

How does this connect to the technical work?

The product is a brand surface, and often the loudest one. Onboarding, error messages, empty states and release notes shape what people think of you more than a campaign does. This line and the engineering work meet there.

Results

See how this looks in practice

Real engagements, shared anonymously. The situation, the decisions, and what changed.

Explore the results

Find out whether people can tell what you do

Thirty minutes on how the company explains itself today, and where that is costing you.