Data Enrichment Cost: The Math per 1,000 Rows

Two founders can both tell you they enriched 1,000 contacts last month and mean bills 16x apart. One paid $16. The other paid $256. Neither was overcharged, and neither list was better than the other. The data enrichment cost of a row is not a property of the row. It is a property of the list of operations somebody chose to run on it, and almost nobody writes that list down before they put in a card.

So here is the list, with our own prices attached, and the arithmetic that turns it into a monthly number.

Data enrichment cost per contact: what a full record actually runs

Pricing pages in this category sell plans. A plan is the wrong unit for answering "what will this cost me", because a plan is a bucket, and the question you have is how fast the bucket drains.

The unit that answers it is the operation. Below is our own card as it stands after the 2026-08-26 repricing, at $0.02 a credit. Dates matter on a page like this. Data enrichment pricing in this category moves two or three times a year, ours included, and a rate card without a date on it is a rumour.

The spread down that last column is the story. Verification costs about six tenths of a cent because it is mostly a DNS lookup and a short exchange with a mail server that follows the SMTP standard. A mobile number costs thirty times as much, because mobile numbers are scarce and the vendors holding them know it.

Now stack the operations into the thing you actually wanted. Nobody wants an operation. People want a row they can act on.

• A company row. Enrich the company from its domain: 0.8 credits, $0.016 each. That is $16 per 1,000 rows.

• A contact you can email. Person enrichment from the email, find the work email, verify it: 0.8 + 2.5 + 0.3 = 3.6 credits, $0.072 each. That is $72 per 1,000.

• A contact you can call. Add the mobile number at 9.2 credits and the row lands at 12.8 credits, $0.256 each. That is $256 per 1,000.

One phrase, "enriched contact", three prices. The entire gap between the second bundle and the third is a phone number. So when a vendor quotes you a cost per enriched contact, the figure means nothing until somebody names the contents of the bundle. That question moves the number more than anything else you will ask during an evaluation, and it takes ten seconds.

The four B2B data pricing models behind data enrichment cost

Underneath the plans, B2B data pricing models come in four shapes. Each one prices a different thing, and each one fails in a different place.

• Per seat with an allowance. You pay per user per month and each seat carries a credit quota. Fine when enrichment is a rep activity. It falls apart the moment one operator, or one script, runs the enrichment for the whole team, because the only lever left is buying seats for people who will never log in.

• Per credit, billed per call. A subscription buys a pool of credits and every attempt deducts from it. Predictable if your workload is predictable. Less so when a job retries, or when a segment has poor coverage and the misses bill anyway.

• Pay on success. Only resolved lookups bill. Misses cost nothing by construction. This is the cleanest of the four and it is worth saying plainly that the framing is not ours: another vendor in this category named it, argued it well, and got there before we did. We agree with them.

• Negotiated annual contract. No list price, seat and volume caps written into the paperwork, and going over the cap is a conversation with a rep rather than a top-up. Common at the enterprise end of the market. If you are a five-person company, this model is not aimed at you and you should not spend a week evaluating it.

Which model you meet depends less on the vendor than on which kind of product you opened, and the five categories of data enrichment tools sorts that out. Most founders end up in the second or third shape, and honestly the line between those two has blurred. Free misses used to be a differentiator and are now closer to table stakes. Where the models still genuinely diverge is on what happens to credits you did not spend, which is the next section but one.

Enrichment credits explained: a credit is never one lookup

Here is the mistake I see most often. Somebody opens two pricing pages, divides the monthly price by the credit allowance on each, and concludes that one vendor is cheaper per credit. That number is not comparable and never was.

A credit is a vendor-private unit. Every platform sets its own credits-per-operation, so the same outcome carries wildly different credit counts across the market. Across the platforms we track, one work email runs anywhere from 0.2 credits to 15. One mobile number runs from 1 to 40. A cheaper credit that buys less work is not cheaper.

The same trap exists inside a single vendor's card, including ours. Enriching a company from its domain is 0.8 credits. Enriching a company from its LinkedIn page is 14.4. Same outcome, same column in your table, 18x apart, because the second chain is deeper and ends on an expensive provider. "Company enrichment" is therefore not a price. It is a price only once you name the input.

Two things follow. Never compare dollars per credit across vendors, only dollars per outcome, computed from each vendor's own published consumption times its own published rate. And never believe a page that tells you one credit equals one enrichment, because on any real catalog that is arithmetically false in both directions.

A prediction I would bet a small amount on, and this has nothing to do with selling you anything: the credit disappears from this category within a few years. It exists mostly because a vendor-private currency can be repriced without touching a headline number, and buyers have started noticing. Fractional credits like ours are a half-step toward just quoting dollars.

Hidden data enrichment costs: misses, expiry, seats, top-ups

The rate card is the part vendors publish. The rest of the bill lives in the terms, and this is where a run that looked like $72 per 1,000 turns into something else. Total cost of ownership is a procurement phrase, but the underlying idea applies at any size: the invoice is not the cost.

• Billed misses. If failed lookups deduct, your effective cost per usable record is the sticker price divided by your fill rate. On a hard segment that is a big multiplier.

• Expiry. Monthly allowances that reset, rollover capped at twice the allowance, annual terms that forfeit whatever is left at renewal. Credits you bought and cannot spend are a real line item.

• Top-up premiums. Running out mid-month is normal. A 30% surcharge on emergency credits is common enough in this category that you should check for it specifically.

• Seat gates. Some plans cap seats at one or two, and put team management itself behind an upper tier. Adding a colleague becomes a plan upgrade.

• Metered exports. At least one vendor publishes credit charges for moving data out: one credit per 25 rows to CSV, one per record pushed to a CRM. You pay to acquire the data and then again to use it.

• Gated destinations. CRM sync, warehouse sync and API access sitting behind a tier several hundred dollars above the one you were quoting.

• Provider choice. On platforms that make you pick the provider for each column, the same mobile number can cost 1 credit or 25 depending on the dropdown. That spread is wider than the gap between any two vendors in the category. Picking badly inside a cheap tool costs more than choosing the expensive tool would have.

That last one surprised us when we first measured it, and it is why our waterfall orders providers on its own instead of handing you a dropdown. How waterfall enrichment works covers the ordering in detail.

Estimating data enrichment cost before you run a job

The arithmetic is not hard, it is just tedious enough that people skip it. Multiply your row count by the credits each column costs, add the columns, multiply by the credit price.

Take 2,000 accounts. You want each company enriched from its domain, plus one contact per company with a verified work email:

• Company enrichment: 2,000 × 0.8 = 1,600 credits

• Contact bundle: 2,000 × 3.6 = 7,200 credits

• Total: 8,800 credits, or $176

Two caveats on that number. Your fill rate will not be 100%, so if misses are free the $176 is a ceiling rather than a forecast, and if misses bill it is a floor. And enrichment columns that read your own systems should not cost credits at all, which changes the shape of the estimate more than people expect. What an account pays you, what it complained about last month, whether it logged in this week: none of that needs to be bought from anyone.

Anyway. That last point is most of why we built Oneprofile the way we did. Enrichment platforms sell you the outside of a company and meter every column, and the columns that told us the most about our own accounts were sitting in Stripe and a support inbox the whole time.

In Oneprofile there is one credit meter and nothing else is metered. Every operation has the published price you saw above, the table shows you what a run will spend before it starts, misses cost nothing, and unspent credits never expire. Top-ups cost the same $0.02 as plan credits, so running out mid-month is not a penalty. Team is $20 for 1,000 credits a month, which is roughly 275 contacts on the email bundle above, and Pro is $200 for 5,000. Columns pulled from your own billing, support and product tools spend no credits at all, and every integration works on every paid plan rather than waiting behind a higher tier.

Two things to do next, in order. Write down your bundle, because the number you are shopping for does not exist until you do. Then run 100 rows through whatever you are evaluating and read the actual ledger, since a real invoice beats every estimate on this page including mine. Get started free.