How to name a product: a practical guide from audience to launch

A product name needs to work at the moment people first encounter it and after they learn what it does. The strongest choices connect to a clear user outcome without locking a product into a feature that may soon change.

Start with the product’s job

Describe what the product helps a person do in plain language. Then separate the stable outcome from the current implementation. Naming a product after a temporary feature can create friction when the roadmap evolves; naming it around the durable value often leaves more room.

Know where the name will live

Decide whether this is a standalone product, a feature within a parent brand, a plan, or a product family.
Test how it looks next to the company or master brand, in navigation, app stores, help articles, and a spoken demo.
Choose whether descriptive clarity or distinctive recall matters most at this stage, and keep that trade-off explicit.

Test recognition and instruction cost

Say candidates aloud to someone who did not help create them. Ask what they heard, how they would spell it, and what they expect it to do. A name does not have to explain every feature, but repeated correction or ambiguity can become a daily support cost.

Check the finalist, not the whole brainstorm

After selecting a short list, complete appropriate trademark, domain, company-name, app-store, social-handle, and local-language checks for the markets you plan to enter. A creative suggestion is not a clearance result.