The Product Naming Brainstorm: 20 Name Candidates With Linguistic and Brand Analysis
Why this prompt matters
A name chosen on instinct in a single meeting skips the checks that catch expensive problems later: a name too close to a competitor's invites a cease-and-desist, a literal translation that means something embarrassing in another market forces a costly re-brand after launch materials are already printed, and a name nobody can spell or pronounce in a sales call quietly suppresses word-of-mouth for years without anyone tracing the cause back to the name itself.
What we use it for
You're two weeks from a product launch and every naming discussion turns into a gut-reaction meeting — people vetoing names on instinct, circling back to options already rejected, with no structured way to compare candidates across styles or catch an embarrassing meaning in another market before it ships.
Prompt
Act as a naming strategist and brand linguist who has named products for [INDUSTRY] companies. Context: My product is [DESCRIBE PRODUCT/SERVICE IN ONE SENTENCE]. Our brand values/personality are [3-5 ADJECTIVES, e.g. "warm, organized, no-nonsense"]. Our target audience is [DESCRIBE BUYER — role, industry, sophistication level]. Names to differentiate from (competitors): [LIST 2-4 COMPETITOR NAMES]. Languages the name must work in: [LIST LANGUAGES, e.g. "English, Spanish, Mandarin" — or write "English only"]. Words/sounds to avoid: [ANY SPECIFIC WORDS, PREFIXES, OR ASSOCIATIONS TO RULE OUT]. Task: Generate 20 name candidates across four distinct naming styles, 5 names per style: 1. Descriptive — communicates what the product does or who it's for 2. Evocative/metaphorical — suggests a feeling or association without being literal 3. Invented/coined — a constructed word with no prior dictionary meaning 4. Compound — two real words fused or juxtaposed For each name, provide: - Phonetic breakdown (syllable count, stress pattern, ease of pronunciation) - Memorability rationale (why it sticks or doesn't) - Cultural/emotional associations, including any negative meanings in the specified languages - A domain-availability likelihood hint (heuristic only, not a live lookup — flag if the name is a common dictionary word likely already registered) Constraints: - No name may closely resemble the listed competitor names - Flag any name with a plausible negative or embarrassing meaning in another specified language rather than silently excluding it - Do not default to invented-word names as the safe answer — generate all four styles with equal creative effort Output Format: Four sections (one per style) with 5 names each, formatted as: Name — phonetics — memorability note — cultural flag (if any) — domain hint. End with a "Top 3 Recommendation" section naming the three strongest candidates across all styles, with one paragraph justifying the ranking.
Result
Descriptive
StudioFlow — 3 syllables, stress on first — clearly signals workflow + creative studio, easy to say aloud in a pitch. No negative associations found. Domain likely taken (common compound).
AgencyBase — 4 syllables — literal and safe but forgettable in a crowded SaaS category; scores low on memorability despite high clarity.
Evocative/Metaphorical
Loom — 1 syllable — evokes weaving disparate threads (tasks, people) into one fabric; warm, tactile image fits "human, organized" brand values. Domain very likely taken (short dictionary word) — would need a modifier like Loom.app or GetLoom.
Harbor — 2 syllables — suggests a calm place work "comes to rest," fits an agency-ops audience managing chaos. No negative associations in English or Spanish (Puerto has similar warmth). Domain moderately likely available as a direct .com.
Invented/Coined
Verado — 3 syllables, easy stress pattern — sounds Latinate/premium without meaning anything specific, low risk of negative associations across English/Spanish/Mandarin transliteration. High domain availability likelihood.
Fluxen — 2 syllables — leans techy/kinetic, but close enough to "flux" that it may read as generic SaaS-speak; moderate memorability risk.
Compound
Craftline — 2 syllables — fuses "craft" (creative agency identity) with "line" (workflow/pipeline); strong fit for brand values, no negative associations found. Domain moderately available.
Warmdesk — flagged: "warm" fits brand tone but "desk" undercuts the creative-agency positioning, reads more like enterprise IT software.
Top 3 Recommendation
1. Harbor — best emotional fit for the calm-amid-chaos positioning, safe across languages, though the domain will need checking immediately. 2. Craftline — most literal connection to the creative-agency audience while still sounding like a product, not a category descriptor. 3. Verado — the safest choice if trademark risk is the top concern, since invented words clear faster than dictionary words in most jurisdictions, at the cost of needing more marketing spend to build meaning into the name over time.
Most product naming sessions produce a shortlist by vibes: someone says a name out loud, three people nod or wince, and the winner is whoever provoked the fewest wince faces. That process skips the actual failure modes that make a name expensive later — trademark collisions, bad translations, names nobody can spell. The prompt below forces the same structured pass a naming consultancy would run, without the consultancy invoice.
Like every prompt on IRCNF, it follows Role + Context + Task + Constraints + Output Format. What makes it useful in practice is that it doesn't return one polished suggestion — it returns 20 candidates across four genuinely different naming strategies, so you're comparing approaches, not just words.
Why four styles, not just one
Descriptive, evocative, invented, and compound names fail and succeed in different ways. Descriptive names are easy to understand and hard to trademark exclusively — a name that just describes the product usually can't be defended against a competitor using similar descriptive language. Invented names trademark cleanly but require marketing spend to build meaning from nothing. Evocative and compound names sit in between, borrowing existing associations without being purely descriptive. Generating all four forces you to see the actual tradeoff instead of defaulting to whichever style the room happens to like on day one.
Why it asks for a cultural/language check on every name
The most expensive naming mistakes are the ones nobody in the room would have caught — a name that sounds fine in English but means something embarrassing or offensive when transliterated into another target market's language. Asking the model to flag this per-name, rather than trusting a general end-of-list caveat, is what actually catches the problem before launch materials are printed rather than after.
Why the domain-availability hint is explicitly a heuristic, not a lookup
The prompt is honest about what it can't do: an LLM can't check live domain registries. What it can do is flag the pattern that predicts availability — common dictionary words and short names are almost always taken, while invented words and unusual compounds are more likely open. Treating this as a directional signal rather than a fact avoids the worse failure mode of trusting a confident-sounding but wrong domain claim.
Adapting it
If you're naming something that needs to work in a single market only, drop the language-check constraint to a single language and the model will generate more aggressively idiomatic options it would otherwise flag as risky elsewhere. If trademark risk is your primary constraint rather than brand fit, weight the Top 3 Recommendation section toward the invented-word category explicitly, since those clear fastest in most jurisdictions.