Why CRM data ages faster than most teams expect
The 25-30% annual decay figure for B2B contact data is not a marketing claim; it reflects the cumulative effect of job moves, company restructures, departmental renamings, and phone number reassignments happening every week across UK businesses. Consider what that rate means in practice. A CRM loaded with 10,000 B2B records in January 2025 will have roughly 2,500 to 3,000 inaccurate records by January 2026, and closer to 5,000 by January 2027. That is not a data quality problem you can route around with good copywriting.
The decay is not uniform across contact fields. Job titles and direct-dial telephone numbers change most frequently, tracking closely with staff turnover. Business email addresses at corporate domains are slightly more stable, because many companies redirect former-employee mailboxes for several months. Postal addresses for registered office locations are the most durable field, with error rates under 5% per year for most UK companies. Understanding which fields decay fastest helps you decide what to prioritise in a partial refresh.
B2C consumer data follows a different pattern. The main drivers of record decay are residential moves (around 7-8% of UK households move each year, per Royal Mail estimates), changes in phone number, and email address turnover. A consumer postal address file loses roughly 10-15% accuracy per year. TPS registration status is a separate consideration: the Telephone Preference Service register is updated continuously, so a list washed against TPS last year may now include newly registered numbers, and the TPS requires re-suppression every 28 days for any telemarketing programme.
For a deeper look at what causes B2B contact records to become unreliable, and the field-by-field breakdown, see our article on B2B data decay and refresh cycles.
B2B vs B2C: recommended refresh frequencies by use case
The right refresh frequency depends on three variables: how quickly the underlying data decays, how frequently you touch those contacts, and what the cost of acting on a stale record is. The table below maps common use cases to a practical schedule.
| Use case | Data type | Recommended refresh | Primary driver |
|---|---|---|---|
| High-velocity outbound SDR team calling C-suite contacts daily | B2B (direct dial, mobile, email) | Quarterly (every 3 months) | High touch frequency; stale numbers waste paid dialler time |
| Account-based marketing (ABM) targeting 500 named accounts | B2B (decision-maker contacts) | Bi-annual (every 6 months) | Relationship investment requires accurate contact data per account |
| Mid-market cold email prospecting (1,000-10,000 sends/month) | B2B (business email) | Every 6 months | Hard-bounce rate above 3-5% risks domain reputation damage |
| Postal direct mail to B2B decision-makers (2-4 mailings/year) | B2B (postal) | Annually, before each campaign | Postal addresses decay slowly; NCOA cleanse before each send is sufficient |
| Consumer telemarketing (opt-in file, regular calling) | B2C (telephone) | Annually; TPS re-wash every 28 days | TPS compliance obligation; phone numbers reassigned over 12-month horizon |
| Consumer direct mail (postal campaigns 1-2 times/year) | B2C (postal) | Annually or before each campaign | 7-8% annual residential move rate; MPS wash before each send |
| Consumer email marketing (opted-in file, monthly sends) | B2C (email) | Every 12-18 months | Email churn lower than phone but still material over 18 months |
| Dormant CRM contacts (no planned outreach within 12 months) | B2B or B2C | Refresh only before reactivation | Spending budget refreshing contacts you are not contacting is waste |
What drives the cost-versus-quality trade-off?
Enrichment is priced per record matched and returned, typically in the range of £0.10 to £0.60 per B2B contact depending on the depth of fields appended (job title only vs. direct dial, mobile, email, and LinkedIn URL combined). For a CRM of 20,000 B2B records, a full enrichment pass might cost £2,000 to £8,000 depending on supplier and field set. Refreshing the entire file quarterly would therefore cost £8,000 to £32,000 per year, which is hard to justify unless your outbound motion operates at scale.
The correct framing is not "how much does enrichment cost?" but "what does acting on inaccurate data cost per quarter?" A sales team of eight SDRs dialling a 40% stale list for one quarter wastes roughly a fifth of its total dialling capacity on calls that cannot connect. At a fully-loaded cost of £45,000 per SDR per year, that is around £72,000 in wasted salary across the team per quarter. Against that number, even a £10,000 enrichment pass looks cheap.
The calculation shifts for postal programmes. Printing and postage for a direct mail campaign run at roughly £0.80 to £1.20 per piece for a basic letter pack. A 10% undeliverable rate on a 50,000-piece mailing wastes £4,000 to £6,000 in print and postage alone, before you account for the missed commercial opportunity. Postal NCOA (National Change of Address) cleansing, combined with a pre-campaign enrichment pass, typically costs £500 to £1,500 for that volume, making the maths straightforward.
For more on the financial case for CRM enrichment, see our detailed guide on CRM enrichment ROI for UK businesses.
Is partial refreshment a reasonable strategy?
For most CRMs above 5,000 records, yes. The practical approach is to segment your contacts by commercial priority before ordering any enrichment. Tier one: accounts you are actively working or plan to work in the next quarter. These need refreshing now. Tier two: warm prospects and previous customers with a plausible re-engagement case. Refresh these bi-annually. Tier three: cold or dormant records with no planned activity. Refresh only before you run a specific campaign against them.
In our experience, this tiering typically identifies 30-50% of a CRM as tier-three dormant contacts, cutting enrichment spend proportionally without compromising the quality of active outbound work.
Event-triggered enrichment: when does continuous refresh make sense?
Batch enrichment, the quarterly or annual refresh model described above, works well for most teams. High-volume operations face a different problem: by the time a contact enters a six-month batch cycle, it may already have moved on. Event-triggered enrichment addresses this by calling an enrichment API each time a defined event fires against a CRM record.
The most common trigger events are:
- A contact's LinkedIn profile signals a job change (picked up by social signal APIs)
- A company files new accounts or changes its registered address at Companies House
- A form submission arrives from an email domain that does not match the stored company
- A hard email bounce fires against a previously active address
- A deal reaches a specific pipeline stage that warrants contact verification before outreach
Event-triggered enrichment requires API access to your enrichment supplier and integration with your CRM's workflow automation (Salesforce Flow, HubSpot workflows, or a middleware layer). The per-record cost is the same as batch enrichment, but you call the API only when a genuine signal suggests the record may have changed, which makes it more efficient than blanket quarterly refreshes for stable accounts.
For operations processing more than 50,000 outbound touches per quarter, the continuous model usually wins on accuracy. Below that volume, the integration overhead is not worth it; stick to a disciplined batch schedule.
GDPR note on enrichment data sources
When you append new fields to existing CRM records using an external enrichment supplier, you are introducing personal data from a third-party source. Under UK GDPR Article 14, you have an obligation to inform data subjects about new data sources if the enrichment materially changes the information you hold about them. For B2B contacts, this is typically addressed within your existing privacy notice if it already covers data obtained from publicly available sources. If it does not, update it before appending. The Information Commissioner's Office (ICO) published guidance on third-party data sourcing obligations in 2022 that remains current.
How to test whether your CRM actually needs refreshing
Before committing budget to a full enrichment pass, run a diagnostic sample. Pull 500 records at random from the segment you plan to refresh, submit them to your enrichment supplier as a test batch, and examine the return rate on key fields. Most suppliers will do this for free or at nominal cost as a match-rate assessment.
The thresholds that should trigger immediate action:
- B2B email hard-bounce rate above 15% on a recent campaign send from that segment
- Telephone number match failure above 20% on the enrichment test sample
- Job title mismatch above 25% (title in CRM does not match current title in reference file)
- Postal address undeliverable rate above 8% on a B2C postal file
Campaign performance metrics are a secondary diagnostic. A sustained decline in email open rates, falling connection rates on cold calls, or increasing direct mail return volumes all suggest data decay rather than creative or timing issues. The mistake many teams make is attributing declining response to messaging when the real problem is record quality.
Should you run a full CRM audit before enriching?
If your CRM is more than two years old and has never been enriched or deduped, yes. A gap analysis before enrichment identifies duplicate records, missing mandatory fields, and formatting inconsistencies that would otherwise reduce your match rate and inflate your enrichment bill. For a guide on running that process, see CRM gap analysis for UK sales teams.
Aligning refresh to your campaign calendar
The most practical way to control enrichment spend without sacrificing quality is to tie refresh cycles to planned campaign activity rather than running them on a fixed calendar. Here is how that looks in a typical UK B2B marketing operation:
A company running four outbound email campaigns and two direct mail pieces per year should enrich the email segments 4 to 6 weeks before each email campaign, and run an NCOA postal cleanse 2 to 3 weeks before each mailing. That gives you fresh data when it matters without paying to maintain perfect records on contacts you are not contacting for another six months.
For ABM programmes targeting named accounts, the cadence is different. Those accounts represent high-value relationships where stale data has outsized commercial impact, so quarterly contact verification on the active account list is justified regardless of whether a campaign is imminent.
Budget planning is cleaner when enrichment is treated as a campaign variable rather than an IT overhead. Each campaign brief should specify the target segment size and the acceptable data quality threshold, which then determines whether an enrichment pass is required and at what cost.
Watch out: over-enriching low-priority segments
A common error in CRM hygiene projects is enriching the entire database when the brief only required refreshing active segments. Enrichment suppliers charge per matched record, so a full-file pass on a 100,000-record CRM where 70,000 records are dormant wastes roughly 70% of the budget on contacts you are not going to use. Always segment before you enrich.
Building a refresh budget: a practical framework
Enrichment budgets work best when set against the expected value of the segments being refreshed, not as a percentage of the total CRM size. A simple framework:
- Segment your CRM by activity tier (active, warm, dormant) and estimate the record count in each.
- Assign a refresh frequency to each tier using the table above.
- Get a sample match rate from your enrichment supplier on a 500-record sample from each tier. Match rates on CRMs not refreshed in two or more years can fall to 60-70%, which affects your budget estimate.
- Calculate cost per tier: (records in tier) x (match rate) x (price per matched record for your chosen field set).
- Compare against the cost of acting on stale data for that tier, using the dialler waste or postal return model above.
Teams that do this calculation properly rarely push back on enrichment spend. The numbers are rarely close: the cost of data decay almost always exceeds the cost of the refresh.