RevOps Janitor
Continuous CRM hygiene, dedupe, and a per-record data-health score — the foundation every other GTM automation depends on.
RevOps Janitor — data-health pipeline
Dirty CRM in, golden records out — watch the cleaning run end to end.
Hit 'Run cleaning' to send all 1,041 contacts down the conveyor.
Swipe to see the full pipeline →
Problem
A CRM accumulates rot: duplicate contacts, missing titles (so persona scoring is blind), free-mail and syntax-broken emails (which burn sender reputation), and stale records. Reps waste time, sequences double-touch prospects, and deliverability quietly degrades — and nobody owns the number.
Who it's for
RevOps / GTM Eng owning CRM integrity at a 50–600-person SaaS company. Stakeholders: SDR leaders (deliverability), AEs (clean handoffs), and the CRO (forecast trust).
How it works
- Weekly cron scores every contact: an issues[] array + a 0–100 health score into a shared table.
- Apply safe, idempotent auto-fixes (normalize email casing, collapse typos).
- Emit a reviewable merge + enrichment plan (deletes/enrichment are never silent).
- Clay waterfall backfills missing titles / LinkedIn; HubSpot merge API handles dupes.
- LLM writes the weekly exec data-quality summary; posted to Slack.
Outcome
On the bundled 1,041-contact dataset: 93 duplicates, 166 missing titles, 278 stale records, and 53 deliverability-risk records identified.
Executing the plan lifts average data health from 86.2 to a projected 93.6, with 344 enrichments queued.
Suppressing the 53 deliverability-risk records protects the sender reputation P1's entire outbound motion depends on — the unglamorous work that makes the rest of the portfolio trustworthy.
How it scales with paid data
- Point the warehouse credential at a HubSpot/Salesforce mirror; execute merges via the Merge API.
- Add email verification (NeverBounce/ZeroBounce) for a verified email status.
- Feed health scores into routing (P3) and outbound suppression (P1).