CRM hygiene is the work everyone agrees matters and nobody budgets: the deduping, enriching, standardizing and pruning that decides whether every downstream system - routing, scoring, reporting, every lifecycle marketing motion - runs on records or on noise. The quarterly cleanup project fails structurally (decay is continuous, projects are episodic), which makes hygiene the canonical standing- mission workload: small, scheduled, cumulative, boring. This article is the mission set in working detail, with the confidence thresholds and write-safety rules that make automated hygiene trustworthy.
The rot rate
The inputs to decay are all continuous. People change roles constantly, so contact data ages into fiction at a steady background rate. Every form fill is a duplicate candidate (the same human, a new UTM, a typo'd company name); every imported list is a hundred of them. Integrations write conflicting formats into shared fields; reps under quota fill the minimum; and "just one more picklist value" compounds into taxonomies nobody can report across. None of it is misconduct - which is why exhortation ("keep the CRM clean!") has never worked, and why the fix is structural: missions that run on the same continuous clock as the decay.
The five standing missions
| Mission | Cadence | Output |
|---|---|---|
| Dedupe sweep | Weekly | Confident merges executed; ambiguous queue for review |
| Enrichment pass | Weekly | Sparse records filled with sourced, dated fields |
| Verification refresh | Monthly | Active segments re-verified before anyone sends |
| Standardization | Weekly | Formats normalized to the canonical scheme |
| Staleness audit | Monthly | Untouched records surfaced with recommended actions |
Each is deliberately narrow - one job, computed exactly per the sandbox rule, reporting a small diff. The narrowness is what makes the set trustworthy enough to run unattended: a mission that only normalizes country fields can be promoted up the autonomy ladder fast, while broad "clean everything" automations stay ungated forever because nobody can reason about their blast radius.
Dedupe: confidence and the merge queue
Dedupe is the mission where write-safety earns its keep, because a wrong merge destroys history that a wrong field edit does not. The working pattern: candidate pairs are scored on converging evidence (email match beats name similarity; name-plus-company-plus-phone convicts; fuzzy name alone never does), and the score routes the action - high-confidence pairs merge automatically with the survivor record chosen by completeness and recency, mid-confidence pairs queue for a human per the gate pattern, low-confidence pairs are left alone rather than nagged about. Every merge logs both prior states, making the one genuinely destructive hygiene operation reversible in practice. The threshold discipline matters more than the algorithm: teams that auto-merge at aggressive thresholds spend their trust budget on the first bad merge a rep discovers.
Enrichment: filling with provenance
Enrichment fills what the record lacks - firmographics, verified contacts, technographics - from the same live sources the ideal customer profile machinery reads. Two rules keep it honest. Provenance per field: every filled value notes its source and date, so a rep reading "employee count: 240" can see it came from an enrichment pass in July rather than a guess in 2023 - and the pillar's inspectable- trust property holds at field granularity. Never overwrite observed with inferred: a value a human entered from a real conversation outranks a vendor's inference, so enrichment fills blanks and flags conflicts rather than stomping them. Verification refresh rides the same pass - deliverability decays per the email deliverability guide, and re-verifying active segments monthly is what keeps sends from inheriting rot.
Standardization and staleness
Standardization is the least glamorous mission and the one reporting depends on most: countries, titles, industries and phone formats normalized to a canonical scheme, weekly, so "pipeline by region" is a query instead of a data-cleaning project. The staleness audit closes the set: records untouched past thresholds surfaced monthly with a recommended action each - re-enrich, re-verify, archive - because a CRM that only ever grows becomes a haystack whose needles cost more to find every quarter. Archiving is gated (it is destructive-adjacent), but the recommendation engine runs free, and the monthly list is the kind of small decision batch a owner clears in minutes.
The first 90 days on a neglected instance
Frequently asked questions
What CRM hygiene can agents automate?
The continuous set: duplicate detection and confident merges, enrichment with per-field provenance, deliverability re-verification, format standardization, and staleness audits with recommended actions - each as a narrow scheduled mission.
How do automated merges avoid destroying records?
Confidence tiers: converging-evidence scores route high-confidence pairs to automatic merge (both prior states logged), ambiguous pairs to a review queue, and weak pairs to nothing. The thresholds are tuned against observed precision, conservatively.
Can enrichment overwrite data a person entered?
No - observed beats inferred: human-entered values outrank vendor inference, so enrichment fills blanks and flags conflicts. Every filled field carries its source and date.
How long until a neglected CRM is actually clean?
Roughly a quarter: month one quantifies and works backlogs, month two tunes thresholds and clears the queues, month three reaches the steady state of small weekly diffs nobody notices.
What makes these missions safe to run unattended?
Narrowness plus the write-safety triad: one job each, idempotent writes, provenance on every change, and gates on anything destructive - which lets each mission earn autonomy on its own track record.
Sources
- Google - Email sender guidelines (why verification refresh has a deadline)
- DMARC.org - the sending-trust standard hygiene protects
Every playbook on this blog ships as a runnable mission.
Open a workspace and the playbook library is waiting - describe the outcome and the agents carry it end to end, on your plan's monthly credits.