Ventures
A name is not decoration. It is the invariant of a product compressed into a sign — and the person who cannot see it is almost always the person who built it. We do the extraction cold, from outside, then package what comes out so it arrives in the same words on every surface and survives being said by someone who was not in the room.
You can demonstrate the product in ten minutes and cannot describe it in ten words.
Every explanation you give is different, and each one is true.
The name is a working title from a folder created two years ago, and nobody has had the standing to change it.
Prospects call it the wrong category, so you spend the first half of every call correcting them.
You have a shortlist of names and no way to decide between them that is not taste.
- 01
Why you cannot do this yourself
Not because you lack the words. Because you remember why every part of the product is there — the compromise, the customer who asked, the sprint it survived — and all of it is equally vivid to you. Salience is not importance. Somebody who was not present sees only what survives explanation, and what survives explanation is exactly what the name has to carry.
- 02
Four questions that do the extraction
What breaks if this is removed, which separates load-bearing from decorative. Who is disappointed, and how exactly — the failure mode names the promise better than any feature list. What must it never do, because constraints define a category and features only populate it. And what is true of every single instance, which is the invariant itself. This is a working session, not a questionnaire, and it is the part clients tell us afterwards was worth the fee on its own.
- 03
Compression into a sign
The invariant is a sentence. The name is that sentence folded until it reads in about half a second, welded from morphemes a reader already owns rather than invented from nothing. Bi + Lex is a bilingual legal instrument in five letters. Neuro + Frame is a systematic frame for assessing behaviour. A reader decodes both without being taught, which is the entire test.
- 04
Plain or institutional, decided first
A name has a job and the job changes with the buyer. An operations manager searching for rental software should not have to decode anything — Carfleet is deliberately plain, and cleverness there would cost conversion. A platform sold to a board has to carry depth and permanence instead. Choosing the wrong register is the most expensive mistake in naming and the least discussed.
- 05
Clearing it, which is where most names die
A name you cannot register, cannot get the domain or the handles for, or that reads badly in Arabic is not a name — it is a proposal. We check the registry position, the domain and handle availability, and the Arabic reading, because in this market the last of those is a live hazard and almost nobody selling naming can look at it.
- 06
One claim at three resolutions
A sentence, a paragraph, a page — the same claim at three magnifications rather than three different stories. Most companies have three, and they were written by three people in three years. A prospect who reads the site and then hears the pitch is quietly reconciling two products, and the cost of that shows up as a longer cycle rather than as a lost deal, which is why nobody attributes it correctly.
- 07
The category sentence, so a prospect can file you
A buyer has to put you somewhere before they can judge you, and if you do not tell them where, they guess — then compare you against the wrong alternatives and price you against the wrong budget. One sentence fixes the shelf: what kind of thing this is, who it is for, and what it does that the obvious alternative does not. Spending the first half of every call correcting the category is this sentence missing.
- 08
A lexicon: the words to use, and the ones to retire
Every company carries vocabulary that leaks the wrong category — a word from the first prototype, a word borrowed from a competitor, a word that means something different to your buyer than it does to your engineers. We hand back both lists with the reason attached to each, because a rule nobody understands is a rule that lasts one quarter.
- 09
Where each version lives
The site hero, the first slide, the opening line of a cold email, the product's own empty state, the LinkedIn description, the invoice footer. Each takes a different length of the same claim, and mapping them is what stops the meaning surviving on the homepage and dying everywhere else. This is also where the surfaces you had forgotten about get named.
- 10
The repeat test
The meaning is packaged when somebody who was not in the room can say it without degrading it. So the last session is with the people who will have to — sales, support, whoever answers the phone — and the test is whether their version a week later is still the same claim. If it is not, the sentence was written for us rather than for them, and we rewrite it. This is the one part of the work that can fail visibly, which is why it is the part we insist on.
- 01
The product's invariant, in one sentence you can say out loud
- 02
A name, with the reasoning that produced it rather than a mood board
- 03
Two alternates at different registers, so the choice is informed rather than aesthetic
- 04
A clearance note: registry position, domain and handle availability, Arabic reading
- 05
A message hierarchy: one sentence, one paragraph, one page, all the same claim
- 06
The category sentence, and the objections it has to survive
- 07
A lexicon — the words to use, the words to retire, and why each
- 08
A surface map: which version of the claim goes where, at what length
- 09
Where it applies, the wordmark and the rules for setting it
Invariant
The name is not the work. The invariant is the work, and the name is what it compresses to.
- Is this branding?
- No. Branding is what a company looks and sounds like across every surface. This is one layer under it: what the product actually is, stated once, and the sign that carries it. Get this wrong and every branding decision afterwards is decoration on a misunderstanding.
- We already have a name. Is this still useful?
- Often more useful. Most engagements end with the existing name kept and the sentence under it rewritten, because the name was never the problem — nobody could say what the product was, and the name was taking the blame.
- Can you do this without a workshop?
- No, and we would not take the work on that basis. The extraction happens in conversation with whoever holds the product in their head. A brief written by someone else is a description of the fog, not a way through it.
- How do you know a name is good?
- It is read cold by someone who knows nothing about the product. If they need the tagline to understand what kind of thing it is, the name has failed and we say so rather than defending it.
- Do you check trademarks?
- We check the registry position and report what we find, and we read the name in Arabic. That is a competence this firm has in house and it is why the clearance is part of the work rather than something we tell you to arrange. It is not a registrability opinion — filing is a separate step and we will say when one is needed.
- What if the answer is that our name is fine?
- Then that is the answer and the engagement is shorter. We have a standing position on this: a product nobody can describe has a positioning problem, and a new name does not fix a positioning problem — it renames it.
- Our website and our sales team say different things. Is that this?
- Yes, and it is the most common reason anyone calls. It is rarely a discipline problem. Nobody wrote the claim down at a length a person can say out loud under pressure, so everyone improvises, and every improvisation is reasonable on its own. The fix is one claim at three lengths and a session with the people who have to use them.
- What do we have on Monday that we did not have on Friday?
- A sentence you can say without preparing, a category sentence that stops a prospect filing you wrongly, two lists of words with reasons attached, and a map of which version goes on which surface. The name, where a name was part of it. Nothing in that list needs a designer or a developer before it can be used.
- Have you done this for yourselves?
- Five times, under our own name and at our own risk: BiLex, Carfleet, NeuroFrame, CyberEGE and the network we run. Each was named by this method before it was built, and each is live and checkable.