Company, product family, platform and interface naming for deep tech. Names that a specialist reads without wincing, a trademark search does not kill, and a roadmap does not outgrow at the next generation.
Four ways deep tech naming goes wrong, none of which is about creativity.
Where the company is new, renaming, or a spinout separating from its parent institution.
A system with room for the next generation, not one good word.
The layer most likely to reach a customer as an internal designation.
How company, platform, product and version relate, so the roadmap does not need a rename.
Trademark-shaped sanity checks and linguistic screening before anyone commits.
Applying the name across site, deck, tender document and datasheet.
Cybersecurity for businesses in the UAE, named and built from the position out.
We run trademark-shaped sanity checks and screening so that obviously dead options die early. The formal clearance is your counsel's, and it should be.
Routinely. Naming an unannounced product is the normal case in deep tech, and it happens under NDA.
Whichever survives the roadmap. Descriptive names are easier to understand and harder to own. Abstract names are ownable and cost more to establish. The right answer depends on how crowded the category already is.
Fewer than most agencies show, screened harder. A hundred unscreened names is a longer meeting, not a better decision.
It sits inside brand strategy more often than not, because a name is an output of a position rather than an input to one.
Thirty minutes, no deck from us. We will tell you which category you are being read into and what we would change first.
Book a 30-minute audit →(opens in a new tab)