How to Name a Startup: A Practical Shortlist Process

A product name has to work before someone sees the logo. People hear it in a meeting, type it from memory, search for it and decide whether it belongs to the category they need. A useful naming process tests those situations before anyone buys a domain or commissions an identity.

Write the naming brief before generating names

Start with a one-page naming brief: audience, product promise, category, likely expansion and unacceptable associations. For a fictional team scheduling app, the promise might be fewer coordination messages, not better calendars. That distinction opens different naming territories and prevents a list dominated by generic calendar words.

Use the meta tag previewer to try candidate names inside a realistic page title and description. Pair each with the same plain-language category descriptor. This tests whether a stranger could understand the offering in a search or sharing context; it does not establish search demand or name availability.

Set decision criteria before sharing candidates. For example, require comfortable pronunciation in two launch languages, room to expand beyond scheduling and no dependence on unusual capitalisation. Decide who recommends, who checks legal risk and who makes the final decision. A large voting group rarely produces a coherent name.

Generate distinct territories rather than spelling variations

Explore four or five naming territories with genuinely different ideas. Descriptive names explain the task. Suggestive names evoke a benefit. Metaphorical names borrow associations. Coined names create a new sound. Founder names can signal personal accountability but may complicate succession or a later sale.

For the scheduling example, territories might include shared rhythm, clear passage and reclaimed time. Write ten candidates in each territory before judging individual words. Avoid spending the whole session adding vowels to an unavailable favourite. Those variations often preserve the original confusion while reducing readability.

Give every candidate a short rationale: what it suggests, how it is pronounced and what misunderstanding it could create. Do not invent elaborate origin stories to rescue weak options. A name that requires a paragraph of explanation may be appropriate in some markets, but the explanation is still an acquisition cost.

Apply a category descriptor separately. A distinctive name followed by team scheduling software can communicate more reliably than a generic name asked to do every job. Keep the identity and headline working together, as outlined in the SaaS hero guide, without turning the brand name into a keyword list.

Screen for practical and legal obstacles

Run an initial knockout screen before testing with customers. Search ordinary web results, app stores, software directories and relevant company registers. Look for similar sounds as well as exact spellings. A differently spelled name can still create confusion when spoken in a sales call.

Check domains and relevant social handles, but treat domain availability as a separate question from permission to use a name. Owning a domain does not provide trademark clearance, and a free handle does not prove that another business has no rights. A modified domain can be workable if the name itself is strong and legally usable.

Use official trademark resources for preliminary research, such as the USPTO trademark search and WIPO Global Brand Database. Coverage, jurisdiction and goods or services matter. These databases are screening resources, not substitutes for advice from a qualified trademark professional in the markets you plan to enter.

Ask native speakers to flag unwanted meanings, awkward sounds and cultural associations in priority markets. Machine translation can suggest questions but cannot provide reliable cultural clearance. Document who reviewed which language and where uncertainty remains. Remove obvious conflicts early rather than emotionally investing in a risky finalist.

Test recall, pronunciation and comprehension

Take three to five plausible finalists into behavioural tests, not a popularity contest. Recruit people resembling likely users and give every candidate an equivalent presentation. Avoid giving one a polished logo while showing another as a plain word; you would be testing design finish as much as naming.

Try these tasks with a small exploratory group:

1. Show a name briefly, then ask the participant to pronounce it.
2. Say it aloud once and ask them to type what they heard.
3. Show the name with its descriptor and ask what the product does.
4. After another task, ask which names they remember.
5. Ask what existing companies or products the name brings to mind.

Record the actual errors. Three people independently inserting the same extra letter is more actionable than an average preference score. Small samples reveal problems; they do not predict market-wide performance. If a candidate fails a critical launch language, do not conceal that failure inside a weighted total.

Check names in sentences too: I invited you to X, your X subscription renews tomorrow, and contact X support. A name that looks elegant on a slide can become awkward as a possessive or sound like an instruction. General GOV.UK content design guidance offers a useful clarity benchmark for the surrounding language.

Make the decision and protect the rollout

Use a short decision memo with evidence against the original criteria. Separate fatal issues from preferences. A legal conflict, persistent mishearing or offensive association should not be averaged away by a high distinctiveness score. Ask the accountable owner to choose among viable options, not to reopen the entire brainstorm.

Before announcing, complete appropriate legal review and acquisition checks. Secure essential domains and accounts through business-controlled credentials, with renewal ownership recorded. A founder's personal email should not be the only route to recovering the company's primary identity.

Create a usage sheet covering spelling, capitalisation, pronunciation, descriptor and any approved shortened form. State whether the name is a noun, whether it can be used as a verb and how product editions relate to the parent company. Link that sheet from your broader branding documentation.

Finally, test the name on an invoice, browser tab, support reply and social preview. Revisit social sharing previews when designing the launch assets. Consistency across these small surfaces builds recognition more effectively than repeatedly explaining a clever origin story. Schedule a post-launch review of misdirected searches and support confusion, without treating every subjective complaint as a reason to rename again.

Key takeaways

• Define audience, promise and constraints before generating candidates.
• Explore different ideas rather than endless spelling variants.
• Keep legal clearance, domain ownership and user testing separate.
• Test spoken and written use with realistic product descriptions.
• Record the decision and publish exact name usage rules.