The core problem: Data quality is invisible until it explodes. When it's working, nobody notices. When it fails — a duplicate invoice goes to a customer, a report shows the wrong revenue, a campaign goes to unsubscribed contacts — it's suddenly very visible. This invisibility is why data quality consistently loses budget battles to things that have visible metrics.
This guide gives you the framework, the numbers, and the email to make the case clearly.
Why the Standard Pitch Fails
Most people pitch data quality like this: "Our data is messy and it's causing problems. We should invest in fixing it."
The manager's response: "I agree in principle. What else is on the list?"
And data quality goes to the bottom — again.
Sohovi profiles your datasets for quality issues in minutes — see what's broken before it breaks your pipeline — try Sohovi free.
The pitch fails because it's abstract. "Our data is messy" isn't a business problem with a dollar sign. "We're losing $47,000 per year to data problems, and I can show you the math" is a different conversation.
The 3-Part Business Case Framework
Part 1: Quantify Current Waste
Calculate the annual cost of your specific data problems. Three components:
A. Staff time: How many hours per week does your team spend fixing data, re-entering data, chasing missing information, or correcting reports? Multiply by loaded hourly cost and 52 weeks.
Sohovi gives you the data quality picture you need to make the case for fixing it — and to track improvement over time.
Example: 3 people × 2 hours/week × $30/hour × 52 weeks = $9,360/year
B. Business losses: Have any of these happened in the past year?
- A campaign sent to wrong or duplicate contacts (wasted budget, damaged reputation)
- A report that turned out to be based on wrong data (a decision made from a bad number)
- A customer who received duplicate or incorrect communication (relationship damage)
Estimate the cost of each incident conservatively. One embarrassing duplicate invoice to a key account might be worth $5,000 in relationship risk.
Sohovi automatically finds every duplicate in your dataset — including near-matches — and shows you exactly which rows are affected.
C. Opportunity cost: What could your team do with the time currently spent on data fixes? If 2 hours/week per person was redirected to analysis, campaign building, or sales follow-up, what would that produce?
Use the bad data cost calculator to build out your specific number.
Aim for a range, not a precise figure. "We estimate we're losing between $15,000 and $30,000 per year" is more credible than a suspiciously precise "$23,847" and still makes the case clearly.
Part 2: One Concrete Recent Incident
Abstract numbers are forgettable. One specific incident is not.
"Remember when we sent the renewal campaign to contacts who had already churned? We got 3 angry replies and at least one person who tweeted about it. We traced it back to the suppression list not being applied to the export. That's the kind of thing a data quality process catches before it happens."
If your team has a recent incident that caused visible problems, this is your most powerful evidence. Your manager almost certainly remembers it.
If you don't have a recent incident: run the free Sohovi profile on your most-used dataset and present what you find. "I ran a quick check on our contact list. We have 340 duplicate email addresses and 12% of phone numbers are in the wrong format. Here's the export." Concrete findings beat abstract descriptions.
Part 3: A Small-Ask Pilot Proposal
Don't ask for a full budget commitment immediately. Ask for permission to run a pilot on one dataset over one month.
The request:
- Scope: One specific dataset (your CRM contact list, your email list, or your product catalog)
- Duration: 30 days
- Cost: Sohovi free tier ($0) or a single month of a paid plan
- Success metric: Defined before you start (e.g., reduce duplicate rate from X% to under 2%, reduce time spent on weekly list cleanup from 3 hours to under 30 minutes)
The pilot structure converts a budget conversation into a proof-of-concept. After 30 days, you come back with before/after numbers — and that's a much easier conversation than a year-1 budget request.
The Email Template
Copy, edit with your specific numbers, and send:
Subject: Data quality — 30-minute pilot proposal
Hi [Name],
Quick one. I've been looking at the time we spend on [data problem — e.g., cleaning the CRM before quarterly reporting / validating lists before sends] and I think there's a real efficiency win available.
Rough estimate: we spend about [X hours/week] across the team on manual data fixes — that's roughly [$Y/year] at loaded cost, before we count any impact on [campaign deliverability / reporting accuracy / customer experience].
I'd like to propose a 30-day pilot:
- Dataset: [the specific file/dataset]
- Tool: Sohovi (free to trial, no IT setup needed)
- Measure: [specific before/after metric — e.g., duplicate rate from X% to under 2%]
- Time commitment: About 4 hours of my time over 30 days
If it works, I'll have concrete numbers to justify the ongoing cost (around [$Z/month]). If it doesn't, we've spent nothing and I'll tell you why it didn't work.
Happy to walk through the details whenever convenient.
[Your name]
Objections You'll Hear and the Answers
"We'll clean it up later."
"Later" means the problem continues compounding. [X] duplicate contacts become [2X] after another 6 months of imports. The team spends [Y hours] on manual cleanup every week between now and "later." The cost of waiting is real and quantifiable — it's $[Z per month] in staff time alone.
"An intern can do it."
One-time cleanup is possible — but it doesn't address the ongoing problem. New data arrives constantly. Without a repeatable process, the data is dirty again within 60 days. We've done this before (point to specific past cleanup effort). The issue isn't the one-time fix; it's the recurring cost of not having a process.
"We're too small for this."
The data quality statistics show that SMBs with under 50 employees spend an average of 12% of staff hours on manual data correction. We're [your team size] — that math applies to us. "Too small" is when you have no data at all. Once you have customers, a CRM, and campaigns, data quality directly affects revenue.
The After-Pilot One-Pager
If the pilot works, you'll want a one-pager for the budget conversation. Fill this in:
| | Before pilot | After pilot | |--|-------------|------------| | Duplicate rate (email list / CRM) | X% | Y% | | Hours/week spent on manual data cleanup | X | Y | | Email bounce rate (most recent campaign) | X% | Y% | | Estimated annual time savings | — | $Z | | Tool cost (monthly × 12) | — | $W | | Net annual benefit | — | $Z - $W |
With that table, the budget decision is arithmetic.
Frequently Asked Questions
Q: What if my boss doesn't know we have a data quality problem? Run the free Sohovi profile on your most-used dataset first. Present the findings before making any ask — "I ran a quick check on our contact list and here's what I found" shifts the conversation from your opinion to objective data. It's much harder to deprioritize a problem that's sitting in front of you as a report.
Q: What if the pilot doesn't show clear results? This is valuable information — either the data quality problem is smaller than you thought (also good news), or the tool wasn't the right fit. Report honestly: "Here's what we found, here's what didn't work, here's what we'd do differently." That's credible and builds trust for the next proposal.
Q: How long should the business case conversation be? Short. The email above is intentionally concise — a busy manager reads it in 90 seconds. The pilot proposal is your ask; the detailed ROI math is your backup if they ask for more. Don't over-explain in the initial ask.
Run the pilot on Sohovi's free tier first. Get your before/after numbers without asking for budget, then come back to your manager with proof rather than a pitch.