What are the five inputs to a CRM enrichment ROI model?
Most ROI calculations for data enrichment fail at the spreadsheet stage because practitioners conflate inputs or ignore the ones that are inconvenient to measure. There are five, and each one materially changes the output.
Input 1: records to enrich. Start with the count of CRM records that are missing the field you want to append. If you are doing a B2B email append, this is the subset of your contact records with no business email, or where the existing email is bouncing. Pull that count precisely; a rounded "about 50,000" hides the fact that 12,000 of those records may lack the company name field required for matching, reducing your matchable universe before you spend a penny.
Input 2: cost per append. Pricing varies by data type, volume, and supplier. UK B2B email-only appends typically run £0.08-£0.15 per record at volumes above 10,000. Add mobile or direct-dial telephone and that rises to £0.20-£0.35. Firmographic fields (SIC 2007 code, employee band, turnover range, Companies House number) are often bundled at a flat rate rather than priced per field, which can lower the blended cost per enriched contact significantly if you need several fields.
Input 3: expected match rate. The match rate is the percentage of your input records for which the data supplier finds a corresponding contact in their file. This is the input most buyers treat as a given and least verify. See the dedicated section below on how match rate mechanics work and how to test yours before full spend.
Input 4: incremental value per enriched record. This is either a lost-opportunity cost (what was a dead record costing you in missed pipeline?) or a forward-looking conversion uplift (what is a newly reachable contact worth at your current conversion rate?). For B2B the simplest approach is: average contract value x conversion rate from cold outreach = revenue per contacted record. For B2C, use average order value or lifetime value x response rate for the channel being unlocked.
Input 5: compliance value. Under UK GDPR Article 5(1)(d), personal data must be kept accurate and up to date. Enrichment contributes to that obligation. It also reduces hard-bounce rates, which matter particularly if the CRM data feeds an email platform where high bounce rates attract deliverability penalties. Quantify this as avoided cost (suppression washing savings, ESP fee reductions, reduced manual cleansing time) rather than as primary revenue.
Worked example: 50,000-record B2B email append
Take a mid-market B2B company with 50,000 contacts in Salesforce, 30,000 of which have no valid email address. The sales team is targeting IT Directors and Operations Managers in UK manufacturing businesses with 50-500 employees.
The table below walks through the full calculation, including a conservative case that stress-tests the conversion assumption.
| Input / Output | Base case | Conservative case |
|---|---|---|
| Records submitted for append | 30,000 | 30,000 |
| Matchable records (good company name + postcode) | 25,000 | 25,000 |
| Match rate applied | 70% | 55% |
| Records with email appended (net matched) | 17,500 | 13,750 |
| Cost per append (email only) | £0.10 | £0.10 |
| Total enrichment cost (on matched records) | £1,750 | £1,375 |
| Decay discount (3 months to campaign, ~7%) | 1,225 records removed | 963 records removed |
| Usable enriched contacts | 16,275 | 12,788 |
| Cold email conversion rate | 1.0% | 0.7% |
| Converted deals | 163 | 90 |
| Average deal value | £450 | £450 |
| Gross incremental revenue | £73,350 | £40,500 |
| Net ROI (revenue minus append cost) | £71,600 (41x) | £39,125 (28x) |
The base case looks compelling, but the conservative case is the one to present to budget holders. The actual ROI multiple at even the lower scenario is high because the append cost is small relative to deal value. For businesses with lower average deal values (say, £50 for a consumer services upsell), the math tightens considerably, which is why the worked-example inputs matter more than the methodology.
In our experience, the most frequent surprise is on the matchable-record side. A CRM that has been populated by manual sales entry over four years will have company names like "Tesco plc", "TESCO", "Tesco Express Ltd", and "Tesco Stores" all referring to the same buyer. That inconsistency reduces matchable record counts by 15-25% on messy files before any supplier match rate is applied.
B2B vs B2C enrichment: how do the economics differ?
The ROI model structure is the same for both, but the inputs shift significantly. Understanding where they differ prevents you from applying B2B assumptions to a B2C project and getting a wildly wrong forecast.
| Factor | B2B enrichment | B2C enrichment |
|---|---|---|
| Typical match rate (UK) | 50-85% | 40-70% |
| Cost per append | £0.08-£0.35 (email, telephone, mobile) | £0.05-£0.25 (email, telephone, postal, demographic fields) |
| Data decay rate | 25-30% per year (job changes, company closures) | 18-22% per year (moves, opt-out churn) |
| Lawful basis (receiving side) | Legitimate interests (requires LIA) | Consent required for electronic marketing (PECR) |
| Suppression required | TPS for telephone; no mandatory email suppression list but honour opt-outs | TPS for telephone, MPS for direct mail, honour opt-out preferences on each record |
| Value driver | Pipeline conversion, deal value uplift | Response rate on incremental channel (postal, telephone, email) |
| Attribution complexity | Moderate (longer sales cycles obscure attribution) | Lower (shorter purchase cycles, clearer uplift signal) |
The lawful basis difference is load-bearing for the model, not just for compliance. B2B enrichment compiled under legitimate interests from publicly available sources can be used for cold outreach subject to a Legitimate Interests Assessment (LIA) by the receiving organisation. B2C enrichment must come from a fully opt-in consumer file under UK GDPR and PECR consent; if the channel being unlocked is email or telephone, the consent flag on each record dictates whether you can use it. That consent-channel filter can reduce your usable B2C matched count by a further 10-30% depending on the split of channel preferences in the file.
For more background on what data enrichment covers as a discipline, see our guide to what is data enrichment and, for the related question of how quickly enriched data stales, our piece on B2B data decay and refresh cycles.
How does match rate affect the ROI calculation, and can you test it?
Match rate is the single variable with the greatest influence on the final ROI figure. A swing from 55% to 75% on a 30,000-record project adds over 6,000 usable contacts with no change in unit cost. That alone can be the difference between a project that pencils out and one that does not.
What drives match rate variation?
Match rate is a function of two things: the quality of your input data, and the coverage depth of the supplier's file. On the input side, the key variables are:
- Company name accuracy and format. A supplier matches your records against their file using a combination of company name, postcode, and sometimes Companies House number. Abbreviated or abbreviated names reduce match probability.
- Postcode completeness. Missing or truncated postcodes (e.g., just "SW1" instead of "SW1A 2AA") reduce geographic disambiguation, particularly for large national employers with multiple sites.
- Record age. A contact who left a company two years ago will not match to their former employer's current contact record. Records older than 18 months carry meaningfully higher non-match risk.
On the supplier side, coverage depth varies by sector and company size. A file strong on FTSE 350 and mid-market companies (100-999 employees) may have thinner coverage for micro-businesses (1-9 employees), which are the majority of UK Companies House registrations by volume. Always ask a prospective supplier for their coverage statistics at the employee band that matters most to your targeting.
How to run a match-rate pilot
Submit 2,000-5,000 records from a representative slice of your CRM, not your best-quality records. A pilot on your 5,000 cleanest contacts will produce an artificially high match rate that you cannot replicate across the full file. Pick records at random, or deliberately include your messiest-formatted company names, and treat the result as a realistic floor.
Pilot cost at £0.10 per match: typically £200-£500. That is a negligible spend relative to the cost of committing a full-scale project to a supplier whose match rate against your file turns out to be 40% rather than 70%.
What are the most common mistakes in enrichment ROI models?
Three errors recur so consistently that it is worth naming them directly.
Counting gross records, not net matched. Applying your conversion rate to the total CRM file size rather than the matched subset inflates the revenue projection. If you submitted 30,000 records and matched 17,500, the 12,500 unmatched contacts generated zero revenue from the enrichment. Build the model on 17,500.
Ignoring data decay between append and campaign. A batch of emails appended in January and not deployed until September will have a meaningful staleness rate built in. UK B2B contacts change jobs at roughly 2-2.5% per month; over eight months that is a 16-20% reduction in the usable pool. Factor in a decay discount for any gap longer than 60 days between the append date and first use.
Treating compliance benefits as the primary ROI driver. Compliance benefits are real: cleaner data helps satisfy the UK GDPR Article 5(1)(d) accuracy principle, reduces hard-bounce rates, and limits the exposure that comes from continuing to contact leavers. But these benefits are notoriously difficult to assign a revenue number to. Use them as a secondary argument in the business case, not as the headline figure. If the revenue-return calculation does not stack up on its own, compliance value is unlikely to save the project.
Attribution challenge in B2B
B2B sales cycles of three to twelve months make it genuinely difficult to attribute a closed deal to a specific enrichment project rather than to wider marketing activity running in parallel. The cleanest attribution method is a holdout test: enrich half the target cohort, leave the other half unenriched, and compare pipeline generation over 90 days. If a holdout is not feasible, use incremental email open and reply rates on the enriched cohort as a leading indicator, then extrapolate to revenue using historical conversion benchmarks.
How to build the business case for sign-off
A good internal business case for CRM enrichment has four components: the base-case ROI model, a conservative-case model (reduce match rate by 15 percentage points and conversion rate by 30%), a pilot proposal, and a compliance section that covers the LIA for B2B or consent validation for B2C.
Budget holders are most often blocked by uncertainty about the match rate, because it is the input they cannot control. Address it directly: propose the pilot in the same document as the full-project model, and offer to reforecast after pilot results are in. That framing converts an uncertain commitment into a phased one, which is far easier to approve.
On cost: always present the append cost on a per-matched-record basis, not per-submitted-record basis. Paying £0.10 per submitted record when your match rate is 60% means you are effectively paying £0.167 per usable contact. That is still competitive, but transparency at sign-off avoids the perception of being surprised later.