Most firms treat CRM hygiene as a Friday tidy. Duplicate contacts, empty owners and deals that have sat in the same stage since last spring get a clean-up when someone says the board pack looks wrong. That framing is the problem. CRM hygiene is a revenue system. Dirty records do not merely look messy. They stop follow-up, hide who asked for work, and turn the pipeline report into a story instead of a list of next actions.
A CRM earns its keep when a named person can open a record and know what to do next, by when, with a number they can actually ring. If that is not true, adding more leads makes the lie bigger. You are not short of enquiries. You are short of records you can trust enough to chase.
Dirty records stop follow-up before anyone notices
The lost work is rarely dramatic on the day it happens. A website form creates a contact with a first name and an email, no service, no postcode, no owner. A call is logged against a mobile that does not match the existing client because the old record used a landline. Two people at the same firm exist as three contacts because a receptionist typed the company name three different ways. None of that feels like a lost job at 4pm.
The loss arrives later. The follow-up task has no owner, so it sits. The duplicate means the salesperson works one card while the original enquiry and the last quote live on another. The missing phone number means the chase depends on email the client does not read. A stage called Quote sent is left in place for weeks because moving it requires a conversation nobody has booked. The client went with the firm that rang back on Tuesday.
Hygiene here is not capital letters and consistent job titles. It is whether the record is complete enough to act on, unique enough to be the one record, and owned by someone who will do the next thing. If any of those three is missing, the CRM is a filing cabinet with a dashboard on top. Staff then keep the real list in a notebook or their head. The software still looks populated. The follow-up has already left the building.
False reporting is a CRM hygiene problem
Owners do not lose faith in a CRM because the screens are ugly. They lose faith when the pipeline total does not match the week they just lived. A board pack that shows a fat quote stage is useless if those cards have no next action, no valid number, and no date anyone agreed. The report is not lying with malice. It is adding unfinished, duplicated and abandoned work and calling the sum a forecast.
Decorative stages make this worse. If every live conversation sits in In progress because nobody wrote what the stages mean, the column totals become mood. Staff then keep a private list, which is the moment the CRM has already failed as a system of record. You cannot run follow-up from two truths.
Closed-lost and closed-won need a reason and a date, or they become a skip. Records that should be dead stay open because closing them feels like admitting the work went nowhere. The pipeline then reports hope. Hygiene includes permission to close. A short, honest closed-lost list is more useful than a long live list nobody believes. Duplicates inflate the count of active relationships and split history, so the person who picks up the phone cannot see the last quote, the complaint, or the stop on the account. Merge is not housekeeping. It is how you stop selling twice into a relationship you already have.
What a record must hold to be usable
Write the minimum that makes the next action possible. For most UK service firms that is a usable name, a reachable number or a watched email, the service they asked about, how they arrived, a named owner, a stage that means one thing, and a next action with a date. Extra fields that nobody fills become guilt. Empty required fields that nobody uses become workarounds. Both are dirt. If a field does not change what someone does on the next call, drop it or stop requiring it.
One relationship, one record. Contacts and organisations need a rule for how they join. If the same limited company can be created twice as Ltd and Limited, you will split the history. Match on domain, company number or a canonical trading name before you create. When a duplicate is found, merge it. Do not leave both just in case.
Ownership is a person, not a team name on a dropdown. A queue can hold new items for a few hours. After that, a named human has the card. Cover has to be written: who takes the list when that person is on leave, and what done means for a record in each stage. Unowned live records are defects. They are not a flexible pool. Activity logging only sticks when it is a by-product of the work. Calls, forms and email should land on the same record, or the CRM will always be the last place people update, which means it will always be wrong.
How to run CRM hygiene as a revenue system
If you wait for a data-cleaning project, the dirt returns the week after someone finishes tidying. Hygiene has to sit in the same place as selling. The person who owns the relationship owns the record. Managers review aged next actions the way they review cash, because that is what those dates are: work you said you would do, still undone, still able to become a job or a silence.
Start with the live pipeline, not the whole historic dump. Records with a next action due, or a stage that should have moved, are the ones costing you this week. Fix completeness, ownership and duplicates there first. Archive or close the silent majority once you can see it. A historic cleanse is useful. It is not the first move if today’s follow-up list is already untrustworthy.
Name the stages after work that happens in your firm, not after a template. Survey booked. Quote sent. Waiting on the client. Won. Lost. If a stage does not tell you the next physical action, it is decoration. Then put a rule on age: if a card sits past the window for that stage with no new activity, it surfaces on a list a manager actually reads. Do not measure how many records exist. Measure how many live records have an owner and a dated next step.
Use the CRM you already pay for until the object model is the constraint. Pipedrive, HubSpot, Dynamics and a well-run Microsoft 365 list can all hold a clean pipeline. A new platform will not invent owners or merge rules. Connect the front door before you ask for more traffic. Website forms, the shared inbox and the phone log all have to write a usable card with an owner already set. Volume on a dirty CRM is not growth. It is a larger unread pile with a nicer chart.
- Define the minimum fields that make a next action possible, and stop requiring the rest.
- Create the record at the door from the form, call or email, with an owner already set.
- Match before you create: phone, email domain, company number or canonical trading name.
- Merge duplicates the week they appear; do not leave a second card just in case.
- Give every live record a named person, a stage that means one action, and a dated next step.
- Write cover for leave so unowned cards cannot hide behind a team dropdown.
- Close won and lost work with a reason and a date; hope is not a pipeline stage.
- Review aged next actions weekly the way you would review unpaid invoices.
- Land calls, forms and mail on the same record so activity is not a memory test.
- Measure live records with an owner and a next step, not how many contacts exist.
Chase the records you can trust
A CRM that people dread opening is already telling you the records are not usable. The fix is not a motivational talk about logging activity. The fix is a record that is unique, complete enough to act on, owned, and honest about whether the work is still live. Once that is true, follow-up becomes a list you can work, and the board pack becomes a list you can defend.
Lightning Business Solutions designs that layer for UK organisations: workflow automation, communications, email systems, websites, integrations, and the joins between them. If follow-up is slipping and the pipeline numbers no longer match the week you just had, start with the records, not with another lead source.
Talk through the pathways that matter on our contact page, or see how the pieces fit under capabilities.