Most data enrichment and cleaning contracts don't include meaningful quality commitments. The vendor promises "high quality data" and you discover what that means after you've paid.
A good SLA turns vague promises into measurable obligations. It protects both sides: the vendor knows exactly what's expected, and you have recourse if the data doesn't perform.
Here's what to include.
Match Rate SLAs
The match rate is the percentage of your submitted records that the vendor can successfully enrich. This should be defined per field, not as an overall average.
Typical thresholds:
- Email addresses: 75-85% match rate (US mid-market)
- Direct dial phone: 55-70% match rate
- Job title: 80-90% match rate
- Company firmographics: 85-95% match rate
Match rates vary by market. SMB and niche industries will be lower. Enterprise and well-known companies will be higher. Set thresholds based on your test batch results, not the vendor's general claims.
Important: Specify whether the match rate is measured against all submitted records or only records where the vendor had enough information to attempt a match. These produce very different numbers.
Accuracy SLAs
A match isn't useful if it's wrong. Accuracy measures whether enriched data is correct, not just present.
How to define accuracy:
- Email accuracy: % of delivered emails that are deliverable (measured via SMTP verification or test campaign). Target: 90-95%.
- Phone accuracy: % of delivered phone numbers that connect to the named contact. Target: 80-85%.
- Title accuracy: % of delivered titles that match the contact's current role. Target: 85-90%.
Measurement method:
Specify how accuracy is measured. Options include:
- Random sample audit: You manually verify 50-100 records within 30 days of delivery
- Full email validation: Run all delivered emails through a third-party verification tool
- Call test: Attempt to reach 25-50 delivered phone contacts
Turnaround Time SLAs
Define when the clock starts and what the delivery commitment is:
- Start trigger: When the vendor receives your complete data file (not when the contract is signed)
- Delivery commitment: X business days for Y records (e.g., 5 business days for up to 50,000 records)
- Rush options: If you need faster delivery, define the premium and timeline
- Delay notification: Vendor must notify you within 24 hours if delivery will be delayed
Remediation Terms
What happens when data doesn't meet the SLA? Define this upfront:
Tiered remediation:
- Minor miss (within 5% of threshold): Vendor re-enriches or re-cleans the shortfall at no cost
- Significant miss (5-15% below threshold): Vendor re-processes affected records and provides credit toward future work
- Major miss (15%+ below threshold): Partial or full refund for the affected portion of the project
Measurement timeline:
You should have 30 days from delivery to identify quality issues and invoke the SLA. This gives you time to import, test, and audit without feeling rushed.
Data Freshness SLAs
For ongoing enrichment or maintenance contracts, define freshness requirements:
- Re-verification frequency: How often are records re-checked? (Monthly, quarterly)
- Staleness threshold: What's the maximum age of a delivered record? (e.g., verified within the last 90 days)
- Change detection: Does the vendor proactively flag records where the contact has changed jobs?
What Not to Include
Avoid SLAs that are unmeasurable or create perverse incentives:
- Don't SLA on database size. "Access to 200M contacts" doesn't mean 200M contacts in your market.
- Don't SLA on response rates. The vendor controls data quality, not your messaging or timing.
- Don't SLA on revenue impact. Too many variables between data quality and closed deals.
Focus SLAs on what the vendor can directly control: match rates, accuracy, deliverability, turnaround time, and freshness.
Frequently Asked Questions
What SLAs should I include in a data enrichment contract?
Minimum match rate per field, email deliverability guarantee (90%+), phone accuracy threshold, turnaround time, and remediation terms for data below thresholds.
What is a reasonable email deliverability SLA?
90-95% for SMTP-verified emails. Below 90% suggests pattern-guessing. Specify how deliverability is measured and what happens if the threshold is missed.
How do you enforce data quality SLAs?
Build measurement into the contract: who measures quality, how, within what timeline, and what remedy applies. A 30-day measurement window after delivery is standard.