Brand strategy
Brand strategy for tech companies
Most technology companies do not have a messaging problem. They have a decision problem. Nobody has said out loud which customer matters most, which competitor they are trying to beat, or which of the four things the product does is the one worth leading with. Strategy is where those decisions get made, and written down in language a salesperson, a founder and a candidate can all repeat without checking a document.
What brand strategy actually resolves
A brand strategy engagement with us produces three things: a position, a narrative, and a language system. The position is the sentence that says who you are for and why you are the obvious choice for them, narrow enough to be a real claim, not a category description. The narrative is the longer argument that gets someone from where they are now to believing that sentence. The language system is the vocabulary: what you call your product, your features, your categories, and what you deliberately refuse to call them.
The most common failure we see in tech branding is a company describing the technology rather than the change it produces. An inference layer, a rules engine, an orchestration platform: these are accurate and they are inert. Strategy is the work of finding the version that is equally accurate and actually lands with a buyer who has a budget and a problem.
How we work
We start with interviews: founders, the two best salespeople, the two most engaged customers, and, where the product is technical enough to warrant it, the engineers who built it. This is the part most agencies skip or delegate, and it is the part that determines whether the output is true. We come from inside the technology industry, so those engineering conversations go somewhere. We are not asking you to translate for us.
From there we map the competitive language landscape: what every adjacent company claims, which claims are saturated, and where the open ground is. Then we draft positions, usually three, deliberately different in ambition, and pressure-test them against real sales conversations rather than a workshop wall.
The output is a strategy document you will actually reread, plus a working session with the team that has to use it. A typical engagement runs four to six weeks.
Where naming fits
Naming is part of strategy, not a separate creative exercise. We name companies, products and feature sets, and we run the checks that matter before you fall in love with something: UK and EU trademark screening, domain availability, and a plain search for who else already owns that word in your buyers' minds. A name that collides with a better-funded company in an adjacent category is a name that costs you money every quarter.
Where we have done this
Launches we’ve had a hand in.
Common questions
- How is brand strategy different from marketing strategy?
- Brand strategy decides what you stand for and how you say it. Marketing strategy decides where you say it and to whom, and how the budget is spent. Brand strategy comes first: a channel plan built on an unresolved position just spends money faster.
- Do we need brand strategy before a rebrand?
- Yes, if the rebrand is meant to change anything other than how the logo looks. Design decisions are downstream of positioning decisions. Skipping strategy is how companies end up with a beautiful identity that says the same undifferentiated thing as before.
- How long does a brand strategy project take?
- Four to six weeks for most technology companies. Research and interviews take two weeks, drafting and pressure-testing another two, and the final week is documentation and the handover session.
- Can you do strategy without doing the design?
- Yes. Plenty of teams have an in-house designer who can execute well but needs a settled position to execute against. We hand over a document built to be used by other people, not one that only works if we stay.