CRM hygiene audit

When to run

• "Clean up the CRM" / "find stale deals" / "why is the forecast off"
• Recurring: monthly, and always two weeks before quarter close

Computer scopes

• CRM: accounts, contacts, opportunities with field history (read + staged write)
• Email + calendar: activity evidence used to judge staleness

Workflow

1. Run the rule set: opportunities past close date and still open; stage age > 2x pipeline median; missing amount, owner, or next step; contacts with no account; likely duplicate accounts (domain + name similarity); activity logged in email but absent from the record.
2. For each finding, draft the specific correction: the new close date implied by the latest thread, the dedupe merge candidate, the "closed-lost, no response 90d" recommendation. Every draft cites the evidence that justifies it.
3. Group drafts into an approval queue by owner and by fix type. Never bury a merge inside a batch of date fixes — destructive-adjacent operations get their own section.
4. On approval, apply changes and write an audit log entry per field touched.
5. Produce the trend line: hygiene score vs. last run, so the team sees decay or progress.

Guardrails

• Autonomy: L1. Every write is drafted, none applied without explicit approval. Merges and deletions require item-level approval — no bulk-approve for destructive operations.
• Full rollback: keep prior values in the audit log; offer one-click revert for 30 days.

Output

Eval fixtures

• Set: sandbox CRM seeded with 200 known defects across all rule types plus 300 clean records.
• Rubric: defect recall and precision per rule; zero incorrect merge proposals on clean pairs; every draft carries evidence.
• Ship gate: recall ≥ 0.9, precision ≥ 0.95 overall; merge false-positive rate 0.