CRM naming conventions that survive contact with a team

A naming convention is not tidiness. It is the thing that decides whether searching for a company finds it, and whether a report counts one customer or three.

This is not about choosing a name for your CRM system, which is a branding question. It is four decisions, written down once, that stop two people entering the same fact differently.

How should you write company names in a CRM?

The recurring problem is one company under several names. Acme, Acme Ltd, ACME Limited and Acme Ltd. are four records, four pieces of a history, and a revenue report that undercounts your largest account. The rule that works: store the company as people say it, without the legal suffix. Acme, not Acme Ltd. Keep the legal entity in a separate field if you invoice from the CRM, because that is where it is needed. Search, reporting and human recognition all key on the short form, and the suffix is the part that varies between whoever typed it.

For the same reason, drop leading articles ("The Acme Group" files under T) and keep the capitalisation the company uses itself.

How should custom fields be named in a CRM?

Fields get named as questions during setup, then read as labels forever afterwards. "Do they have a warehouse?" reads badly on every record and sorts nowhere useful. "Warehouse" is the same field and reads as a column heading, which is what it is.

Three rules that prevent most of the pain:

No abbreviations that only the person creating them understands. "AMV" is unrecoverable in eight months. "Annual value" is not.

Put the shared word first when fields belong together. "Contract start" and "Contract end" sit together in an alphabetical field list. "Start of contract" and "End of contract" do not, and every field picker in the product is alphabetical.

Do not put the type in the name. "Renewal date date" happens more than you would think, and a field called "Notes text" tells the reader nothing the field did not already say.

What makes a good pipeline stage name?

A stage name should let two people looking at the same deal agree on where it sits. That works when the name describes something that has happened, not a feeling about how it is going. "Proposal sent" is testable. Either it was sent or it was not. "Warm" is not testable, and two salespeople will place the same deal differently, which makes the pipeline report a measure of optimism rather than of position.

Keep them short, keep them in past tense where you can, and number them only if your system does not already preserve their order.

How should you name tags in a CRM?

Tags are the freest field in any CRM and the one that decays fastest, because they are usually a text box that creates whatever you type. Six months later you have "enterprise", "Enterprise", "ent" and "enterprise-2026", and none of them can be trusted in a filter.

Two rules, made once:

Lowercase, single form. Pick lowercase and stick to it, since most tag fields are case-sensitive when filtering even when they look identical on screen.

A tag is a category, not a note. If a tag would only ever apply to one record, it is a note. Tags earn their place by being reused, and a tag list where most entries appear once is a list nobody filters by.

This is the hardest to fix afterwards. Renaming a field updates one label. Cleaning up tags means opening every record carrying the wrong one, and the mess is only visible once it is large.

Where should a naming convention be written down?

Four decisions make a short document, and one nobody can find is the same as no document. Put it where your team already looks: a pinned note, the onboarding checklist, or a description on the field itself if your CRM allows one. A convention works when a new person follows it without being told, and that only happens if it is visible at the moment they are typing.

Frequently asked questions

What is a CRM naming convention?

A short set of rules for how records, fields, stages and tags are named, so that two people entering the same fact produce the same result. It matters because search and reporting both depend on identical values, and small differences split one customer into several.

Should company names include Ltd, Inc or GmbH?

Usually not in the main name field. Store the short form people actually say and keep the legal entity in a separate field if you invoice from the CRM. The suffix is the part that varies most between whoever typed it, so it is the part that creates duplicates.

How should custom fields be named in a CRM?

As labels rather than questions, without abbreviations, and with the shared word first when fields belong to a group. "Contract start" and "Contract end" group together in an alphabetical field picker, which is how most products present them. Name the field for what it holds rather than for the report you want from it, because the report changes and the field does not, and a field called "Q3 campaign" outlives the quarter it was named for.

What makes a good pipeline stage name?

One that two people can test against the same deal and agree on. Stages describing an event that has happened, such as "Proposal sent", are decidable. Stages describing sentiment, such as "Warm", are not, and they turn the pipeline report into a measure of mood.