One place rule
Every piece of information about a contact lives in one place. Their phone number is in one field, not three (mobile, work and home are not three pieces of information for most small businesses; they are one field called 'best phone number'). Their last contact date is one field, not separately on the contact and on every email thread. Their notes are in one notes field, not split between a 'meeting notes' field and a 'general notes' field and a 'preferences' field. The principle is brutal but it works: when information lives in one place, the system tells the truth. When it lives in three places, none of them is reliable.
When a colleague asks 'where do I put this', the answer should be obvious. If the answer is 'well, you could put it here, or here, or there', the system has too many places. Consolidate and the trust comes back.
No field that nobody updates
Once a quarter, look at every field in the system and ask 'when did this last get updated, and by whom'. Fields that have not been updated in three months are not earning their keep; either you do not need them, or you do need them and the team has stopped maintaining them. Either way, the right response is to remove the field. A field that nobody updates is worse than no field at all, because it gives a false sense that the information is being tracked.
- One place for each piece of information
- No field that nobody updates
- No more than five pipeline stages
- No more than ten tags or labels
- No automation you cannot explain in one sentence
Five stages, ten tags, no more
The natural rate of growth for a customer list system left unchecked is about one new pipeline stage and three new tags per quarter. Within eighteen months the system has fifteen stages and forty tags, and the team has lost track of what any of them mean. Set hard caps. Five pipeline stages. Ten tags or labels in total across the whole system. Adding a new one requires removing an old one. The constraint forces clarity: every stage and every tag has to earn its place.
No automation you cannot explain in one sentence
Customer list software offers automations - 'when a contact moves to stage three, send an email and create a task for the manager and update a tag and notify the team channel'. Most of these are bad ideas in a small business. They make the system harder to understand, they fail silently when something changes upstream and they almost always run on assumptions that drift over six months. The rule we use: if you cannot explain what an automation does in one sentence to a colleague, it should not be running. Most small business customer lists work better with no automations at all and a clear weekly habit instead.
Pruning by hand
Once a quarter, take fifteen minutes to prune. Remove fields nobody updated. Merge tags that mean the same thing. Archive contacts that have been inactive for more than two years and that you have no realistic plan to revive. Pruning sounds destructive; it is the opposite. A pruned list is a usable list, and a usable list is the only kind that pays you back.
What to do this week
Open the system and count the fields per contact, the tags in use and the pipeline stages. Write the numbers down. If you have more than ten fields, more than ten tags or more than five pipeline stages, decide which one to remove this week. Then remove it. Resisting the urge to add will keep the system alive; the urge to remove is what makes it well.
The earlier eBook Sales Basics warned against complexity in conversations; the same warning applies to systems. The next chapter Tagging and Segmenting Without Chaos is the small, structured exception to the simplicity rule - the few tags that genuinely earn their place. Recurring principle: keep existing customers close.
