Vendor-published estimates put mainstream B2B match rates somewhere between 60% and 85% for typical ICPs. That sounds productive until you realize match rate only measures coverage (records with a returned value divided by records submitted), not whether the returned data is correct, complete, or useful for the workflow you actually care about. A record can "match" and still be missing the verified business email your routing logic requires. So the first question isn't "how many records matched?" It's: how many of those matches turned into something your team could act on?
That gap between coverage and actionable accuracy is where most enrichment budgets leak. And it gets worse at scale, because every credit spent on a bad match is a credit that didn't go toward a record your SDRs can actually use. If you're burning through enrichment credits faster than you're generating qualified pipeline from them, you don't have a data problem. You have a unit economics problem.
The Metric That Actually Matters
Cost per credit is how vendors want you to compare. It's also the least useful number on the invoice. Credits may be charged per lookup, per returned field, or only when a match is found; some vendors price email, phone, and company data on separate rate cards. According to Lusha, choosing a B2B data API for enrichment requires evaluating not just price per call but the completeness and accuracy of what comes back.
The metric worth tracking instead: cost per actionable record. That's total enrichment spend divided by the number of records that met your minimum routing criteria (verified email, correct company match, required firmographic fields populated). If you're paying $0.10 per credit but only 40% of returned records are routable, your real cost per usable record is $0.25. Double what the vendor invoice suggests.
Most teams never calculate this. They watch credit consumption and match rate on the vendor dashboard and assume the gap between "matched" and "usable" is small. It usually isn't.
How Credits Get Wasted at Scale
Three patterns account for the bulk of wasted enrichment spend:
- Duplicate lookups. The same record gets enriched multiple times because there's no dedup logic before the API call. This is common when enrichment runs on form submission and the same person fills out multiple forms, or when marketing and sales ops run separate enrichment workflows against overlapping lists.
- Enriching records you'll never work. If your ICP filter runs after enrichment instead of before it, you're paying to enrich companies outside your target segment. Flip the order: filter first, enrich second.
- Re-enriching stale records without a decay policy. Data decays, and periodic re-enrichment makes sense. But re-enriching your entire database on a flat schedule (quarterly, monthly) wastes credits on records that haven't changed. A smarter trigger: re-enrich only when a record re-engages or when it's about to enter an active sequence.
Each of these is a plumbing fix, not a strategy overhaul. The trade-off: tightening enrichment logic means some records won't get enriched that previously would have. Volume drops before quality improves. That's expected.
Run It This Week
Step 1: Audit your last 30 days of enrichment. Pull total credits consumed, total records enriched, and total records that met your routing criteria (verified email + correct company match at minimum). Calculate your cost per actionable record.
Step 2: Check for duplicate lookups. Query your enrichment logs for the same email or domain appearing more than once in the past 30 days. If duplicates exceed 10% of total lookups, add dedup logic before the API call.
Step 3: Move your ICP filter upstream. If enrichment currently fires on every inbound record, add a pre-enrichment filter that checks company size, industry, or domain against your ICP definition. Only pass qualifying records to the enrichment API.
Step 4: Set a re-enrichment trigger. Instead of batch re-enrichment on a calendar schedule, trigger re-enrichment when a record takes a new action (form fill, site visit, ad click) or when it's queued for an outbound sequence. This concentrates spend on records that are actually in play.
Timeline: Steps 1 and 2 take a few hours of ops work. Steps 3 and 4 require workflow changes in your MAP or enrichment tool, typically a half-day to configure and test.
Owner: Marketing ops or RevOps. Sales doesn't need to be involved unless the enrichment workflow touches their CRM records directly.
What to Measure (and What to Ignore)
Primary metric: Cost per actionable record (total enrichment spend / records meeting routing criteria).
Secondary metrics: Duplicate lookup rate (should trend toward zero). Percentage of enriched records that enter an active sequence within 14 days (measures whether you're enriching records anyone actually uses).
Guardrail: If your total volume of actionable records drops more than 20% after tightening filters, your ICP definition may be too narrow, or your pre-enrichment filter has a logic error. Diagnose before expanding.
What to ignore: Raw match rate on the vendor dashboard. It tells you coverage, not value. A match rate drop after implementing pre-enrichment filtering is expected and fine, because you're no longer enriching junk records that inflated the number.
The hypothesis, stated so you can actually falsify it: if we add dedup logic and pre-enrichment ICP filtering, cost per actionable record will drop by 15% or more within 30 days, because we're eliminating spend on duplicate and out-of-ICP lookups. If it doesn't move, the waste is somewhere else (field accuracy, routing logic, or the vendor's data quality itself).
When This Approach Fails
If your enrichment vendor's underlying data quality is poor (low accuracy on returned fields, stale emails, wrong company associations), no amount of workflow optimization fixes the problem. You're just spending fewer credits on bad data, which is better than spending more credits on bad data, but the output still won't route cleanly. In that case, the next experiment is a vendor comparison: run the same list through two providers, measure actionable record rate from each, and make the switch if the delta justifies the migration cost.
The other failure mode: teams that over-filter before enrichment and accidentally exclude good-fit accounts because their ICP definition is too rigid. Start with your core ICP criteria (the two or three firmographic fields that actually predict pipeline conversion) and resist the urge to add more filters until you've measured the baseline.
Enrichment at scale isn't about finding a cheaper vendor or buying more credits. It's a measurement problem disguised as a procurement problem. Calculate your cost per actionable record this week. That single number will tell you whether your next move is fixing plumbing, switching providers, or (rarely) increasing volume.
