What's the operator playbook for a new CRO inheriting a Salesforce instance with 4 years of dirty data — what gets fixed in week one, month one, quarter one?

New CRO Inheriting Dirty Salesforce Data: The Operator Playbook

The cost of inaction is quantified: bad data costs most companies a revenue loss of 15–25% per year according to MIT, and 44% of companies estimate they lose over 10% in annual revenue due to poor-quality CRM data. Your first move isn't to clean everything — it's to triage, scope, and build governance that outlasts your cleanup sprint.

---

WEEK ONE — Diagnose Before You Touch Anything

Your job in week one is audit, not action. Touching records before you understand the schema causes more damage than the dirty data itself.

1. Build the data dictionary. Build a data dictionary to identify what all fields mean in the system — put current fields in column one, what they *should* be in column two, and possible resolutions in column three. Then do a data assessment to find which fields are actually meaningful and which ones are just collecting dust.

1. Run your dedup diagnostic. Salesforce's native dedup tools work in layers — configure Matching Rules to define how the system identifies potential duplicates by email, company name, or phone, then create Duplicate Rules that determine what happens when a match is found: block, alert, or allow-and-log. Enable the Report option on every Duplicate Rule — without it, you can't generate a Duplicate Report to see the actual scope of the problem.

1. Scope to revenue-critical fields only. Your cleanup scope is not 300 fields across every object. Teams that scope to 5 fields finish cleanup in days, not months. Scope to the use case, clean what matters, then expand. For a CRO, those 5 fields are: Opportunity Stage, Close Date, ARR, Account Owner, and Primary Contact.

1. Identify the data entry points. Many duplicates enter your CRM via integrated apps — your marketing automation platform syncs leads, your sales engagement tool creates contacts, your data enrichment service updates records, and none of them share matching logic.

---

MONTH ONE — Fix What Breaks Forecasting

Dirty data causes you to overestimate or underestimate significantly — inaccurate close dates mean you'll believe opportunities will close in the wrong time frame, making it impossible to forecast capacity or quarterly performance. That's your month-one priority target.

Also: build connected account hierarchies — they show how enterprise accounts are organized including parent/child structure, and give RevOps critical insights for land-and-expand strategy and identifying the "big fish" worth prioritizing.

---

QUARTER ONE — Build Governance That Sticks

Cleanup without maintenance is just postponed chaos. Build healthy habits: schedule weekly deduplication scans to catch problems before they compound, and create a data quality dashboard tracking key metrics over time.

Assign object-level ownership: reps own entry quality, marketing owns list hygiene for every imported list and enrichment batch, admins own validation rules and Flow-based cleanup, and leadership owns accountability — without an executive sponsor, the governance program dies within a quarter.

• Rep comp linkage: tie a small percentage of QBR scorecard to Salesforce hygiene metrics (stage accuracy, contact completeness ≥ 80%)
• Enrichment layer: deploy ZoomInfo, Clearbit, or Clay to backfill stale Account/Contact records — don't manually clean what a tool can enrich
• Poor-quality data breeds mistrust among your user base, which leads to poor adoption and increasingly inaccurate, inconsistent, and stale data — fix this cycle by publishing a monthly data health score to the entire GTM team

---