Replace 'when did we last clean the CRM?' with a standing weekly audit

A weekly scan of the CRM for hygiene problems that produces a structured cleanup queue, in place of the someday we should clean the CRM problem.

The full audit runs overnight so the queue is ready on Monday. It skips itself if an audit finished within the last five days.

Accounts on the same domain, with similar names, or the same legal name formatted differently, and users on the same email or the same name and phone. Each candidate pair or group comes with a similarity score.

Accounts with no activity for over a year that are not customers, users whose email bounced more than 90 days ago, and deals stuck in an early stage for over 180 days. Not all of these are deletions, some just need re-engaging, but they all bloat reporting and slow segmentation.

Accounts missing industry, size or region, users missing a role or company, and deals missing a close date or an amount, grouped by what is missing so you can tell whether to enrich them or look by hand.

For each duplicate candidate: which record should survive, judged on how complete it is and how recently it was active, what to copy across from the other, and which conflicts a human has to settle, such as two different industry classifications. Every suggestion carries a confidence score.

The merge and cleanup queue is handed to the bulk update review gate with the total findings, a summary per category, the spread of confidence and links to the records, so RevOps can approve the confident batch and handle the edge cases by hand.

A post to the RevOps channel with the duplicate count, the stale count, the incompleteness rate and the movement week over week, saying plainly when completeness improved and when the stale pile is growing, which usually points at slow follow up upstream.

Validated and published, tracking that the weekly run completes, whether the pile of findings is growing, which points at problems further upstream, and how complete the CRM is after each cleanup.