House name vs product name

Give each name a specific responsibility

A house name identifies the source of an offer. A product name helps someone distinguish what they are choosing. A feature label explains an action or capability inside that product. These roles can overlap, especially in a small business, but treating them as separate questions makes a naming decision easier to reason about.

The confusion often starts when a team asks one word to do every job. It should sound distinctive, explain the first product, support several future categories, and make sense as a button label. Few names can carry all of that gracefully. A simple map lets the house establish continuity while the more specific labels help people navigate what is available now.

Draw the business as it exists today

Put the business or house at the top of a page. Under it, write the current customer offer. Beneath that, list the main things a person can do or buy. Use plain descriptions before inventing any new names. This shows whether the team is managing one product with several features or several offers that need to be distinguished.

A hypothetical consumer app might have a house called Foki, a product described as shared weekend lists, and features labeled Save, Invite, and Vote. The example is a planning exercise, not an operating product. Notice how few invented words it needs. The customer can learn one mark and use ordinary language for the actions that follow.

Ask what the customer needs to choose

Product names become useful when there is a meaningful choice. Two subscription levels may need clear plan labels. Two unrelated tools may need separate product identities. A small variation in color usually needs a color name rather than a new brand. Let the customer's decision determine how much naming structure is necessary.

Try writing a comparison sentence: “Choose this one if you need…” If you cannot complete it clearly for two proposed products, they may not need distinct names yet. They may be versions, features, or a single offer described from different angles. Naming them separately can create an impression of choice while leaving the customer unsure what actually changes.

Keep the house broad enough for a believable future

The house name should make sense across the offers the business has a credible reason to create. That does not mean it must suit every possible category. A company organized around useful home objects might reasonably add another room or material. A sudden move into an unrelated professional service would require more than a broad word to feel coherent.

Write down the reason future products would belong together. It could be a shared audience, a repeated use occasion, or a recognizable point of view. Use that reason to assess the house name. If the only connection is that the same founder likes both ideas, the customer may need a clearer explanation or a different arrangement.

Make product labels carry concrete information

A descriptive product label can save a great deal of explanation. “Shared lists,” “Linen table cloth,” or “Identity workshop” gives a person an immediate clue about the offer. A distinctive house can sit above those descriptions without requiring a second naming puzzle. This is particularly useful when the audience is meeting the business for the first time.

An invented product name can still be appropriate when there is a strong reason for it. Perhaps the product needs to stand independently or has an established audience of its own. If you choose that route, give the name a clear descriptor and decide how it relates to the house in writing. The relationship should be visible in an ordinary sentence, not only in a brand presentation.

Leave features close to the task

Feature names should usually help someone act. A button labeled Save is easier to evaluate in context than a proprietary word whose meaning has to be learned. The more frequently a person uses a feature, the more important it becomes that the label supports recognition. Reserve distinctive naming for places where it adds something beyond novelty.

Review a proposed interface or catalog and circle every unfamiliar term. Ask which ones a first-time customer must understand to make progress. If several invented labels stand between arrival and the first useful action, simplify the path. This review does not require removing personality from the product; it asks that personality coexist with clear instructions.

Use a retail example to pressure-test the map

Imagine a small house offering a cloth, a pouch, and a notebook. The house name can appear consistently on each item. A collection label might connect a seasonal color or material choice, while the product title identifies the object. Size and color can follow in a predictable order. Each layer supplies information the others do not.

Now imagine a repeat customer looking for the same pouch six months later. Can they tell which name identifies the object and which refers to the old collection? If the catalog relies entirely on poetic seasonal names, the answer may be difficult. A good naming map should help reorder an ordinary item as well as introduce a new collection beautifully.

Decide what happens when something changes

Products are revised, combined, and retired. Before choosing a detailed naming system, consider how it handles those events. Will a small update receive a version number? Will a material change require a new description? Does a discontinued product leave a useful reference page? These decisions affect how customers interpret continuity and replacement.

Keep the house stable when the reason for the business remains stable. Change the specific layer that actually needs to change. A new feature should not trigger a company rename, and a new house identity should not silently erase the product names customers already recognize. Mapping the layers makes it easier to explain what has changed and what someone can still rely on.

Check the system in a support conversation

Write a short exchange between a customer and the person helping them. The customer asks about an item or feature; the reply identifies it and gives a next step. Read the exchange without the visual hierarchy of the website. Can both people tell which name refers to the company, the product, and the action?

Do the same with an invoice, an email subject, and a referral. A naming system that works only in a carefully arranged diagram is not ready for everyday use. These simple examples can uncover ambiguous abbreviations or product labels that resemble the house too closely. Fixing those problems early is easier than teaching every new customer the distinction.

Keep the first version of the map small

For a young business, one house name and a few descriptive labels may be enough. Add another naming layer when it solves a real customer problem. A complex architecture can make a modest range look larger, but it also creates more terms to explain and maintain. Size is not the same as clarity.

Finish by drawing your three-layer map on a single page. Put the customer decision beside each product and the customer action beside each feature. Then remove any name that contributes no useful distinction. The result should give the house room to develop while helping a person understand today's offer with as little translation as possible.