A name that describes the product without being descriptive

The team wanted something a developer would repeat in a pull request. We built around a verb already native to their users' vocabulary and cleared it against an adjacent trademark in the same class.

The brief

Developer tools live or die by word of mouth, and in this category word of mouth is written down: in pull requests, code review, commit messages and chat. The team wanted a name that would turn up there naturally, the way the best tool names become part of how developers talk about the work. A descriptive name would explain the product and never be repeated. A clever one would be repeated once, with a wince.

The work

So we started with how the users already talked. The territory for invention was the vocabulary of the people the product was for, the verbs they already used for the job it did, rather than the vocabulary of the company's own pitch. Candidates generated in that territory were screened for pronunciation, spelling under dictation and meaning across languages, then cut to a shortlist.

The name the team chose was built around a verb its users already said every day. That is what made it work, and what made it risky: a word close to everyday vocabulary sits close to other people's marks. Screening flagged an adjacent trademark in the same class, and we mapped the exposure in plain language for the team's counsel before anything was final.

How it closed

The adjacent-mark risk was cleared before launch, which is the cheapest moment to clear it: before anything is printed, shipped or announced, and before a letter arrives from someone else's counsel. The team went to market on a name that reads as a verb in a pull request and as a company everywhere else.