Bad Salesforce data does not send an invoice. It bills you in small, distributed charges — a rep retyping a phone number, a bounced email, a duplicate account worked twice, a forecast off by a stale amount — and none of those charges is large enough to trigger an alarm. Added up, they are one of the most expensive line items nobody budgets for: Gartner estimates poor data quality costs organizations an average of $12.9 million per year.
You do not need to trust an industry average, though. The costs of bad CRM data fall into four buckets, and each of them can be estimated for your org with numbers you already have.
Where the Money Actually Goes
1. Seller time
Salesforce’s own State of Sales research consistently finds reps spending roughly 70% of their time on non-selling work — and record archaeology is a steady share of it: hunting for the right account among duplicates, fixing contact details mid-call, reconstructing history a previous owner never logged.
The math is uncomfortable at any team size:
20 minutes per rep per day on data cleanup × 20 reps × $60 loaded hourly cost ≈ $100,000 per year — before counting a single lost deal.
2. Wasted marketing and outreach spend
B2B contact data decays at about 2.1% per month — roughly 22.5% per year. People change jobs, companies merge, emails die. Every stale or duplicated contact in a campaign is spend with a guaranteed zero return: emails that bounce, ads served to duplicates, SDR sequences aimed at people who left 18 months ago. If a fifth of your database is stale, a fifth of database-driven spend is burned before the campaign starts — and the sender-reputation damage from bounces taxes the deliverability of everything else.
3. Forecast and reporting errors
This is the bucket executives feel first. A pipeline report is only as good as the Amount, Stage, and Close Date fields underneath it — and those decay like everything else. Stale opportunities inflate the pipeline; missing amounts deflate it; duplicated accounts double-count it. The cost is not the wrong number itself but the decisions made on it: hiring against pipeline that is not real, cutting spend because real pipeline was invisible, quarter-end surprises that were knowable in week two. When the six dimensions of data quality slip on Opportunity records specifically, the forecast is where it surfaces.
4. Automation and AI acting on fiction
Flows, assignment rules, and scoring models execute on field values without judgment — bad value in, wrong action out, at machine speed. A wrong Industry misroutes a hot lead; a missing Amount silently drops a deal from a territory calculation. AI raises the stakes: an agent answering customer questions from incomplete or contradictory records produces confidently wrong answers, and PII sitting in free-text fields becomes compliance exposure the moment an AI reads it. This bucket is why data quality has moved from an ops concern to a launch-blocker for Agentforce initiatives.
Why the Cost Compounds: the 1-10-100 Rule
Quality management research (Labovitz and Chang, Making Quality Work, 1992) established the ratio that still governs data economics: an error costs about $1 to prevent at entry, $10 to correct once stored, and $100 once it reaches a customer or a decision. A malformed email is nearly free to block with a validation rule, cheap to fix in a cleanup sweep, and expensive once a sequence has bounced off it and the domain’s sender score has paid the price. The rule’s practical meaning: every month a known issue sits unfixed, it migrates toward the expensive end. Prevention controls are not a nice-to-have; they are the only point where the fix costs a dollar.
Estimate It for Your Org
Four line items, one afternoon:
| Line item | Formula | You need |
|---|---|---|
| Seller time | min/day on cleanup × reps × loaded rate × 220 days | A quick poll of 5 reps |
| Wasted outreach | stale+duplicate share × database-driven spend | Bounce and duplicate rates |
| Forecast at risk | pipeline value in records with missing/stale Amount, Stage, or Close Date | A report on those fields |
| Rework and incidents | incidents/quarter traced to bad data × hours × rate | Ops ticket history |
The ROI calculator runs this arithmetic for you — enter team size, database size, and spend, and it produces the annual figure. The stale-share and missing-field inputs are guesses until you measure them; a Data Quality Score per object replaces the guesses with evidence.
How DQS Helps
Data Quality Sense turns the cost argument from anecdote into a number. A scan gives you the measured inputs — completeness of forecast-critical fields, duplicate rates, stale-record share, PII exposure — broken down by object and field, entirely inside Salesforce. Paired with the ROI calculator, that is a business case an executive can act on: this is what bad data costs us, these five fields drive most of it, here is the trend since we started fixing it.
FAQ
How much does bad data cost a company? Gartner puts the average cost of poor data quality at $12.9 million per year per organization. For a single Salesforce org, the visible costs concentrate in four places: seller time lost to fixing and hunting records, marketing spend wasted on undeliverable or duplicate contacts, forecast and reporting errors that misdirect decisions, and rework caused by automation and AI acting on wrong values.
How do I calculate the cost of bad data in my Salesforce org? Estimate four line items: rep time (minutes per day spent on record cleanup × loaded hourly cost × team size), wasted outreach (share of contacts that are stale or duplicated × campaign spend), forecast risk (pipeline value sitting in records with missing or stale amounts and dates), and rework from failed automations. A measured Data Quality Score per object turns these from guesses into evidence.
Why does bad data cost more the longer it stays? The 1-10-100 rule from quality management: an error costs about $1 to prevent at entry, $10 to fix once stored, and $100 when it reaches a customer or a decision. Bad data compounds — a wrong email is cheap until a sequence sends to it, a duplicate is harmless until two reps work the same account, a stale amount is invisible until the quarter misses.
Next Steps
- ROI Calculator: put your own numbers on it
- How to Measure Data Quality in Salesforce: replace estimates with a baseline
- How to Improve Data Quality in Salesforce: the detect–fix–prevent loop
- Why Agentforce Agents Give Wrong Answers: the AI cost bucket in detail