Naming a product without boxing the company in

Product naming should leave the company room to grow. A good name survives three tests: it can live in a short URL, it can sit in a sentence a stranger will actually say, and it does not forbid the next product you are likely to ship. A clever name that fails one of those tests becomes a tax on every page, every title, and every introduction.

The company name and the product name can be the same while you have one offer. They should be allowed to diverge later. The tests below are how you notice, early, whether you are naming a company, a product, or a feature that does not deserve a name of its own.

The URL test

Say the name, then type it. If you have to spell it every time you tell someone, the name is a puzzle. Puzzles feel delightful in a workshop and expensive in a sales call. Prefer a string people can hear once and write down.

Check the domain you can own, and the path it will occupy if the product lives under the company site. company.com/billing is often a healthier home than a invented word that requires its own brand, its own site, and its own explanation. A separate domain is justified when the product will be evaluated by buyers who should not have to learn the parent company first. It is a burden when you are still the same three people.

Look at the name in a title, because that is where many people will meet it. Google's documentation on title links says titles are truncated to fit the device width, that the title is often the primary clue for a click, and that you should brand concisely: the site name at the beginning or the end, separated by a hyphen, a colon, or a pipe. A name that only works inside a paragraph will be cut off or look like boilerplate. "Lark" can sit in "Lark: notes for field teams." "Larkfield Collaborative Workspace Cloud" will be shortened by the results page, and you will not choose the cut.

Avoid a name that exists only to hold search terms. Google's same guidance warns that stuffing a title with repeated phrases looks like spam to people and to the ranking systems. A product called "Invoice Invoice Billing Software Invoices" is a title pretending to be a name. Name the thing. Let the sentence around it carry the category.

Also reject names that force awkward paths: mixed punctuation, underscores, or a string that looks like a tracking code. The URL is an interface. People read it on a slide behind you, in a browser bar, and in a message they forward to a colleague.

The sentence test

Write the sentence the name has to inhabit on the homepage and in an introduction at a dinner. "This is [name]. It [does the job] for [the person]." Read it aloud to someone who has not been in the workshop. If they ask you to repeat the name, the name is failing. If they ask what the job is, the sentence is failing. Fix the one that failed. Do not paper over a vague offer with a more elaborate name.

The name should be easy to say beside ordinary verbs: use, open, buy, cancel, export. Feature-shaped names often collide with those verbs. A product called "Sync" makes every sentence ambiguous. A product called "Northwind Sync" is a little longer and much clearer. Length is acceptable when it buys a sentence that does not need a footnote.

Check the name against the words you refuse to say. If your voice page bans hype, the name should not be hype with a trademark. If you speak in plain verbs, a name made of Latin fog will stick out on every button: "Launch the paradigm." Buttons reveal a bad name faster than a strategy deck does.

Try the name in an error and in a receipt. "We could not save your Harbor project" is a human sentence. "We could not save your Qxly project" forces the reader to slow down at the worst moment. The stressful sentences are part of the test, because they are part of the product.

The future-product test

List the next two things the company might sell or ship. Be plain. A second module. A service engagement. A physical good. A different buyer. Put the candidate name in front of each one and see what becomes a lie.

A name that means "only invoices" traps a company that is about to add estimates and payroll. A name that means "only for dentists" traps a tool dentists and orthodontists will both want. You can still choose a narrow name when the narrowness is the strategy and you are willing to start a second brand later. Write that cost down before you fall in love. A second brand is a second site, a second voice, and a second set of files.

Names that describe the company as a feeling travel further than names that describe a feature, and they also risk meaning nothing. The way through is the sentence test, already done. If the feeling-name needs the sentence every time, keep the sentence glued to it in the title, the nav, and the first line. The name is the handle. The sentence is the definition. Neither has to do both jobs.

Watch for names that block a category you will want to be understood in. If buyers search and speak using a plain category, the title can carry that category next to a distinctive name. The name itself can stay short. This is the concise branding pattern from Google's title guidance, used on purpose: distinctive name, specific page, ordinary words for the job.

Company, product, and feature

Give a name to something a customer chooses on its own. The company has a name. A product with its own buyers can have a name. A feature inside a product usually wants a description: "shared inbox" ages better than a whimsical label you then have to teach, translate, and defend in the interface.

Use one name in the logo, the title element, the visible heading, and the way you answer the phone. Google may build a title link from the heading and other prominent text when the title element is vague or inconsistent. Different names on the same page give that system, and your customers, a reason to pick the wrong one.

If you are still only a company with a single offer, resist the urge to name the offer as if it were a startup inside the startup. Ship the offer under the company name until a real second product would confuse people. Premature product names create logos, domains, and empty homepages that you then feel obliged to feed.

Choosing among the names that survive

Score the survivors in writing, on the three tests, with a yes or a no. A maybe is a no for this round. Show the last two to a handful of people in the audience, in the sentence, not on a slide full of options. Ask them to type the URL from memory a minute later. Ask them what they think you sell. Their answers are evidence. Their taste in shapes is not.

Then stop renaming. A working name that passes the tests will gather meaning from the product. A perfect name that arrives after six months of delay is a luxury the first customers will never see. You can revisit the name when the offer truly changes. Until then, put the energy into the sentence beside it, the page it heads, and the product that has to deserve it.

When the name is stable enough to put on a site, the identity work and the page can be the same project. That is the kind of engagement described in Hanabi's services. If you are earlier than that, and you only have the company name, start with the audience, the offer, and the sentence, which is the work of Brand identity when you only have a name.