If you’ve run a CRM cleanup project, you’ve probably hit the same wall: the database is full of duplicates and incomplete records. Which problem do you tackle first?
This comes up constantly with RevOps and sales ops teams, and the honest answer is that you need to do both, in the right sequence, for different reasons. Here’s the logic.
Why the Order Actually Matters
Most teams treat enrichment and deduplication as two independent tasks. They assign one to marketing, the other to ops, and hope it sorts itself out. The result: expensive enrichment credits burned on duplicate contacts, or merges that destroy data because one record had critical information the other didn’t.
The order matters because each pass changes what the next one is working with:
- Enrich first, and you reduce the total records needing deduplication. Some duplicates become obviously identical once you fill in missing fields.
- Deduplicate first, and you cut enrichment costs. There’s no point enriching a contact you’re about to merge or delete.
Both arguments are valid. That’s exactly why the answer is two passes, not one.
Pass 1: Light Deduplication Before Enrichment
Before spending a single credit on data enrichment, run a first-pass deduplication focused on obvious, low-hanging duplicates. The goal isn’t perfection here; it’s cost reduction.
What to target in Pass 1
- Exact email matches: same email address, two records. Merge immediately.
- Company plus full name matches: “Jean Dupont at Salesforce” appearing twice.
- Phone number duplicates: less common but highly reliable as a match signal.
Tools like Dedupe.ly make this first pass straightforward. You can run automated rules for high-confidence matches and flag lower-confidence ones for manual review later.
Why this pass saves you money
If your CRM has 40,000 contacts and 20% are duplicates, you’re potentially enriching 8,000 records you’ll eventually discard. At typical enrichment pricing anywhere from €0.05 to €0.30 per contact depending on depth, that’s hundreds or thousands of euros wasted on noise.
A rough first-pass dedup before enrichment is one of the most underrated cost-saving moves in RevOps.
Pass 2: Enrich With Full Context
After removing the obvious duplicates, you’re working with a leaner dataset. Now enrich it, and don’t cut corners.
What enrichment should cover
Good B2B enrichment goes beyond email verification. For each contact or company record, aim to fill in:
- Professional email (verified, not guessed)
- Job title and seniority level
- Company size, industry, and tech stack
- LinkedIn URL
- Phone number
- Company website and revenue range
For email finding and verification, Fullenrich is strong for multi-source waterfall enrichment. Dropcontact is particularly well-suited for French B2B contacts and handles basic duplicate detection natively, which becomes relevant for Pass 3.
For company-level firmographic data, the Rodz API can surface intent signals alongside enrichment data, giving you not just who the company is but what they’re doing right now: fundraising rounds, job postings, tech stack changes, and more. This is useful if you’re building prospecting workflows, as covered in the guide on creating B2B prospecting lists with intent signals.
The enrichment flywheel effect
Enrichment often reveals duplicates that weren’t detectable before.
Take two records:
- Record A: “J. Martin” | Company: blank | Email: blank
- Record B: “Jean Martin” | Company: “Qonto” | Email: jean.martin@qonto.com
Without enrichment, these don’t match. After enriching Record A with a job title, company, and email, you’ve got two identical contacts. Enrichment surfaces hidden duplicates by filling in the context needed to identify them.
Pass 3: Deep Deduplication After Enrichment
This is the pass most teams skip, and it’s the most valuable one.
Now that your records are enriched, you can run fuzzy matching and semantic deduplication with far greater confidence. Your matching logic can compare:
- Verified email addresses (not blank fields)
- Standardized job titles
- LinkedIn URLs (an excellent unique identifier)
- Company domains
Dedupe.ly handles this well with configurable match scoring. You can weight certain fields like email or LinkedIn URL more heavily than others. The result is a more accurate merge operation with fewer false positives.
What to watch for during deep dedup
Don’t auto-merge without reviewing enriched fields. When two records have different email addresses but the same LinkedIn URL, you need to decide which email is canonical. When one record has a phone number and the other doesn’t, the merge has to preserve that data.
A good dedup tool shows you field-by-field conflicts and lets you choose which value wins. This matters especially for records that may represent the same person at different points in time, for example a contact who changed jobs, which is relevant if you’re running post-promotion prospecting workflows.
The Full Sequence at a Glance
| Pass | Action | Goal |
|---|---|---|
| 1 | Deduplication (exact match) | Remove obvious duplicates before spending on enrichment |
| 2 | Full enrichment | Fill missing fields, verify emails, add firmographics |
| 3 | Deduplication (fuzzy match) | Catch hidden duplicates revealed by enrichment |
This three-step sequence balances cost efficiency with data quality. It’s what any serious CRM cleanup project needs to work through.
Practical Workflow for RevOps Teams
Here’s how to put this into practice.
Step 1: Audit your current state
Understand your baseline before anything else. How many contacts do you have? What’s your empty-field rate per column? What percentage of records lack a verified email?
Export a sample of 500 records and analyze them manually if needed. You’ll quickly see which fields are most consistently missing, and that tells you where enrichment will have the biggest impact.
Step 2: Run your first dedup pass
Use Dedupe.ly or your CRM’s native dedup tool for exact-match rules. Focus only on high-confidence matches:
- Identical emails
- Identical first name plus last name plus company domain
- Identical phone numbers
Set a threshold: only auto-merge if match confidence is above 95%. Flag everything else for manual review.
Step 3: Enrich the deduplicated dataset
Use a waterfall enrichment approach. Try multiple providers in sequence to maximize fill rates without overpaying. Start with your cheapest or most accurate source for the target audience, then pass unresolved records to the next provider.
If you’re working with French companies or SMBs, Dropcontact is a strong first layer. For international databases or hard-to-find contacts, Fullenrich aggregates across multiple providers automatically.
For company signals like job postings, tech stack, and growth indicators, layer in Rodz API data to add behavioral context to your records. This is useful for ABM targeting where you need to prioritize accounts based on what they’re doing right now, not just static firmographics.
You can automate the enrichment workflow using Make; there’s a practical walkthrough in the article on automating intent signals with Make and Rodz.
Step 4: Run your second dedup pass
Run fuzzy matching against the enriched dataset. Match on:
- Email (verified)
- LinkedIn URL
- Company domain plus full name (fuzzy)
Review the conflict queue carefully. For any record where match confidence falls between 70% and 95%, have a human make the call. Above 95%, auto-merge with the rule that the more complete record wins.
Step 5: Set up ongoing hygiene
The real win isn’t the one-time cleanup; it’s stopping the mess from coming back. Set up:
- Dedup rules at entry point: block or flag duplicates when new contacts are created.
- Enrichment triggers: enrich automatically when key fields are missing.
- Periodic audits: quarterly dedup passes, especially after list imports or trade show uploads.
A Note on CRM-Specific Considerations
Different CRMs handle this differently.
HubSpot has native dedup for contacts and companies, but it’s limited to exact email matches. You’ll still need a third-party tool for fuzzy matching.
Pipedrive has a merge function but no automated dedup, so you’ll need Dedupe.ly as an integration.
Salesforce has a built-in Duplicate Management feature, but it’s complex to configure and often ignored in practice. External tools still produce better results.
Whatever your CRM, the underlying sequence stays the same: light dedup, enrichment, deep dedup, ongoing prevention.
Why This Matters Beyond Hygiene
Clean, enriched data isn’t just an ops problem. It hits pipeline quality and revenue outcomes directly.
When your CRM contacts are properly enriched and deduplicated:
- Segmentation actually works: you can filter by accurate job title, seniority, or industry.
- Personalization holds up: your outreach references the right company, the right role, the right context.
- Reporting is trustworthy: your sales KPIs reflect reality instead of inflated contact counts.
- Intent signal matching works: if you’re overlaying signals from tools like Rodz, clean data means the signals map correctly to the right accounts.
If you’re building a serious B2B prospecting database, data quality is the foundation. Intent signals, personalization, sequencing, none of it works if the underlying records are messy.
Bottom Line
The enrich-first vs. deduplicate-first debate has a practical answer: do both, in three passes.
First dedup to reduce enrichment costs. Then enrich to fill context and reveal hidden duplicates. Then a second dedup to clean up what enrichment surfaced.
It’s not glamorous and it takes time, but it’s the only approach that produces a CRM you can actually trust. A trustworthy CRM is the difference between prospecting at random and prospecting with real precision.
If you’re working through a CRM cleanup and want to think through the tooling, the workflow, or how to layer intent signals on top of clean data, Rodz is a good place to start.