Skip to main content
DE-3 · Data & Enrichment · 100 XP · ~18 min
Garbage in, garbage out. It’s the oldest rule in data work — and the most consistently ignored. Data comes in with inconsistent capitalization, broken company names, duplicate records, titles that haven’t been held in three years, and phone numbers in 12 different formats. Every one of these problems compounds downstream: bad personalization, failed validation, wrong routing, broken integrations. This module covers the cleaning operations that should run on every dataset before enrichment begins.

The Six Most Common Data Quality Problems

ProblemExampleImpact
Inconsistent capitalization”VP of sales”, “VP Of Sales”, “vp of sales”Personalization breaks, segmentation fails
DuplicatesSame contact appears 3x with slightly different namesOver-sends, burns relationship
Stale titles”Head of Growth” at a company they left 18 months agoSends to wrong person, wastes outreach
Malformed emails”john.doe@company..com”, “john doe@company.comBounces immediately
Non-standardized company names”Acme Corp”, “Acme Corporation”, “ACME”De-duplication fails, wrong grouping
Mixed data in one field”John Smith (CEO)” in the name fieldBreaks every downstream variable reference

Building a Data Cleaning Layer in Bitscale

Run these cleaning operations in sequence before any enrichment or outreach.

Clean 1: Name normalization

Clean 2: Title standardization

Clean 3: Company name normalization

Clean 4: Email format validation

Clean 5: Duplicate detection


The Cleaning Pipeline Order

Run cleaning operations in this order — each step feeds the next:
  1. Email format validation — remove malformed addresses first (cheapest to check)
  2. Name normalization — clean names before they’re used in any AI column
  3. Title standardization — standardize before segmentation or routing
  4. Company name normalization — standardize before de-duplication
  5. Duplicate detection — run after normalization so similar records match correctly
  6. Data freshness check — query LinkedIn or data provider to verify title/company is current

Freshness: The Invisible Problem

A clean record with stale data is worse than a messy record with current data. Job titles change every 18–24 months on average in SaaS. If your list was built 6 months ago, 15–25% of titles may be wrong. Freshness check column:
For lists older than 3 months, run a freshness check on your highest-value segments before enrichment.

Data Quality Scoring

After the cleaning layer, add a composite quality score for each row:
Use this score to route records:
  • 80–100: proceed to enrichment
  • 60–79: clean before enrichment
  • Below 60: manual review or discard

Quick Check: What are the six most common data quality problems? What order should you run cleaning operations? What quality score threshold should trigger manual review?

DE-3 Challenge: Clean a Messy Dataset (+100 XP)

Download a sample messy dataset (we’ll provide one via the challenge form, or use your own) and build the full cleaning pipeline in Bitscale. Requirements:
  • All 5 cleaning columns implemented
  • Duplicate detection column
  • Data quality score column
  • Record the starting vs. ending quality score distribution
  • A short paragraph on the most common data quality issues you found

Submit DE-3 Challenge →

Share your grid + quality score distribution (before/after). +100 XP on approval.

Next: DE-4 — Company Intelligence →

With clean contact data in hand, DE-4 adds the company context layer — firmographics, growth signals, and competitive intelligence.