by BrandName Gen (LX AI)
A copy-ready list of ten ideas beats a blank page. Treat each as a hypothesis.
Next: search USPTO TESS / your jurisdiction, check domains/socials, and ask counsel before filing.
I open BrandName Gen and type a short industry note plus one vibe word that captures the feeling I want the brand to evoke. The tool returns ten copy‑ready strings instantly. I copy those strings into a plain text file and give each line a simple two‑digit ID from 01 to 10. The ID lets me refer to a candidate later without retyping the full name.
I treat every line as a testable hypothesis. First I say the name out loud three times fast. If I stumble on a syllable I flag it for later review. Next I check the visual weight: I set the name in all caps and look for odd letter combinations or unintended acronyms. I write any immediate concerns in a column titled “First impression”.
After the quick gut check I keep the shortlist open in a side pane so I can paste a candidate into each search box without leaving the workflow. I move to the formal clearance steps described in the following sections.
I begin with the USPTO TESS database for a federal search in the United States. If my market is outside the US I replace TESS with the equivalent national portal (e.g., EUIPO for Europe, IPONZ for New Zealand). I open the basic word mark search and enter the exact candidate string.
I record the number of live results for each variation in a simple table. If any variation returns a live mark in the same International Class I consider the candidate blocked and move to the next ID.
| Variation | Live US marks | Live EU marks | Verdict |
|---|---|---|---|
| Exact | 0 | 0 | Clear |
| Plural | 2 | 0 | Blocked (US) |
| Misspelling | 0 | 1 | Blocked (EU) |
| Phonetic | 0 | 0 | Clear |
When the table shows zero live marks across all relevant jurisdictions I add the candidate to a “Passed trademark” list. I repeat the same process for the next ID until I have at least three names that survive the trademark screen.
After trademark clearance I move to the digital identity layer. I open a bulk domain checker (many registrars offer a free CSV upload) and feed the passed list. I look for the .com TLD first; if unavailable I note the next preferred TLD (e.g., .io, .app, .dev) but I flag any alternative as a potential branding compromise.
I use a private spreadsheet to record the availability of each platform. I place a green check for a free handle and a red X for a taken one. If a handle is taken I note whether I could add a prefix or suffix (e.g., getio or hqio) without losing readability. I also verify that the chosen domain does not resolve to a parked page or a site with conflicting content.
Once I have a domain and a set of social handles that are all free I move to the legal review stage.
Before I run the tool I write a brief that captures the core of the product. I answer three questions: what problem does the product solve, who is the primary user, and what single adjective describes the desired brand personality. I keep the brief under 150 words so the model receives a clear signal.
I include any hard constraints such as prohibited words, required length, or preferred letter patterns. For example, if I know the name must be two syllables I note that. I also note any linguistic considerations, like avoiding sounds that are hard to pronounce in my target market.
I save the brief as a text file and open BrandName Gen. I paste the brief into the input box and press generate. The tool returns ten strings that I treat as the starting point for the checklist.
Pronunciation matters because customers will say the name in conversation, over the phone, and in video ads. I say each candidate aloud three times in a row. If I trip on a consonant cluster or a vowel shift I mark the name for further review. I also ask a colleague to say the name without seeing the spelling; if they hesitate I note it.
Visual weight is about how the name looks in logos, signage, and UI buttons. I set the name in all caps and in lowercase and look for awkward letter pairs like “vv” or “mm”. I check whether the name creates an unintended acronym when the first letters are taken. I also verify that the name does not contain a sequence that could be read as a word in another language that has an unwanted meaning.
I record my findings in two columns: “Pronunciation score” (0‑5) and “Visual score” (0‑5). Names that score four or higher in both columns move to the trademark search stage.
Before I file a trademark application I send the shortlisted names to an attorney who specializes in intellectual property. I provide the attorney with the following items:
The attorney checks for any subtle conflicts that a basic database search might miss, such as common‑law rights or foreign marks that are not yet in the USPTO system. I also ask the attorney to review the domain name for any potential cybersquatting issues.
I use the following external resources to inform the discussion:
Those lookups are yours or your counsel’s. BrandName Gen only proposes the ten names. It does not search the trademark register and it does not register a domain.
After the attorney confirms that a name is clear to proceed I give it a final go‑ahead and prepare the filing documents.
This checklist does not guarantee that a name will never face opposition. Trademark law is complex and rights can arise through use even if no registration appears in a database. The process described here reduces risk but does not eliminate it.
It is not a substitute for professional legal advice. The steps are based on my own experience and should be reviewed by qualified counsel before any filing.
The method does not promise a 100 % success rate in securing a domain or social handle. Availability changes quickly and a name that is free today may be taken tomorrow.
Finally, this guide is not a promise that the generated names will be creative or market‑winning. It is a practical way to move from a blank page to a set of testable candidates.
I keep a written checklist next to every release that touches this topic. The list is boring on purpose: name the owner, name the evidence artifact, and name the rollback. If a step cannot produce a file, a ticket, or a log line, it is not a step — it is a wish.
| Signal | What to record | Stop-ship? |
|---|---|---|
| Unexpected write or send | Tool name, args, identity | Yes until gated |
| Missing confirmation on destructive action | Call path and bypass | Yes |
| Untrusted text treated as instruction | Source surface and resulting action | Yes for agent reach |
| Scanner clean, judgment open | Deferred items + owner | Only if core path safe |
brandname-gen helps with the measurable first pass. Architecture choices, legal sign-off, and customer-facing claims still need a human owner. Treat every checklist row as decision support, not a certificate.
When a prospect asks whether the product "covers everything," I answer with the boundary: automated checks catch known patterns; novel chains and policy judgment still need review. That honesty keeps support load down and keeps the blog aligned with what the product actually does.
If you need a second opinion, pair this write-up with the references below and with your own staging reproduction. Do not skip the reproduction step just because a model wrote a confident summary.
BrandName Gen is a naming tool that gives you 10 on-brand name ideas from an industry and a vibe, for products, newsletters, or side projects.
It returns 10 names per run, formatted as a copy list you can review and riff on.
Yes. It is vibe-aware, so the suggestions reflect the tone and feeling you specify rather than random words.
No. You provide an industry and a vibe and get ideas back; no thesaurus or branding background required.
Want to try the product? BrandName Gen
Generated 2026-09-17 · primary sources only · no fabricated traffic metrics