Publishing a rate card is not the norm in bulk property data, so start by giving BatchData credit for putting three product lines, four tiers each and the record allowances on a public page. You can size a budget without a discovery call, which is more than most of this market allows.
The card is also structured in a way that rewards a few minutes of arithmetic. Monthly prices against record blocks convert cleanly into per-record rates, and once they do, three things become visible that the page does not say out loud. This guide does the division and then names what the division leaves out.
Disclosure: Scout Data is our product; treat that entry as a maker’s pitch and the rest as our honest read.
What is published
As publicly advertised on 4 September 2026, with a monthly or annual commitment option on each tier:
| Tier | Records per month | Property data | Skip tracing | Reverse skip tracing |
|---|---|---|---|---|
| Growth | Up to 100,000 | $1,000/mo | $2,000/mo | $3,000/mo |
| Professional | Up to 300,000 | $2,500/mo | $5,000/mo | $7,500/mo |
| Scale | Up to 750,000 | $5,000/mo | $10,000/mo | $15,000/mo |
| Enterprise | Up to 3,000,000 | $10,000/mo | $20,000/mo | $30,000/mo |
Pricing on this page is as publicly advertised at the time of writing — confirm current pricing with each vendor, and with our sales team for Scout Data.
The skip-tracing tiers list mobile and landline numbers, emails, mailing addresses, DNC status verification, a litigator scrub, carrier information and API access, with batch processing appearing from the Professional tier upward. The reverse tiers add tested emails, name aliases, linked property where available, and DNC, TCPA and deceased flags.
Divide it into a unit rate
Monthly price over included records. Nothing here is an estimate — it is long division on the numbers above.
| Tier | Property data | Skip tracing | Reverse skip tracing |
|---|---|---|---|
| Growth | $0.010 per record | $0.020 | $0.030 |
| Professional | $0.0083 | $0.0167 | $0.025 |
| Scale | $0.0067 | $0.0133 | $0.020 |
| Enterprise | $0.0033 | $0.0067 | $0.010 |
Two things fall out immediately. The volume curve is steep — Enterprise buys a property record at roughly a third of the Growth rate — so where you sit on the curve matters more than which vendor you picked. And the unit rates only apply if you actually consume the block. A team using 40,000 of a 100,000-record Growth allowance is paying $0.025 a record, not $0.010, and the pricing page will keep saying $1,000 either way.
The forward and reverse asymmetry
This is the most useful thing on the card and it is easy to miss. The forward skip-tracing tiers are described as up to N skip traces per month. The reverse tiers are described as up to N matched records, with “pay per matched record” printed on them.
Those are different products commercially even when the price per unit looks comparable. An allowance of attempts puts match-rate risk on you: submit a hundred thousand records, get whatever comes back, pay the same either way. An allowance of matches puts it on the vendor. At Growth, reverse costs 50% more per unit than forward — which is the correct direction for that risk transfer to run, and whether it is priced correctly depends on a match rate neither party can know before you send a real file.
The practical move: run the same test file through both and compute cost per usable record, not cost per unit. If your file matches well, paying per attempt is cheaper. If it matches poorly — older addresses, high turnover markets, thin input columns — paying per match can be dramatically cheaper despite the higher sticker. Which of those you are cannot be reasoned out from a pricing page.
Three things the card does not price
- Stacking. The lines are separate purchases. A team that needs property data and skip tracing at 100,000 records a month is looking at $1,000 plus $2,000 — $3,000 a month, or three cents a record before anything else. Model the combination you will actually run, not the cheapest line on the page.
- Add-ons. Listing, property owner profile, demographics, deed history, valuation, contact enrichment, propensity scoring, permit summary and comparables all appear as add-ons whose pricing the page says varies by tier. If any of those are load-bearing for your targeting, you do not have a price yet — get them quoted before you compare against anything.
- What happens at the edges of the block. The card does not state whether unused records roll over, or what an overage costs. Both answers materially change the cost of seasonal volume, and both are one email away. Ask before you commit annually.
The number that actually compares vendors
Per-record rates are comparable between vendors only if every vendor defines a record the same way, and they do not. The comparison that survives is cost per dialable contact: total monthly spend across every line you buy, divided by records that produced a working number reaching the person you meant to reach.
Work an illustrative case to see the shape. A hundred thousand records a month on Growth property data plus Growth skip tracing is $3,000. If 62% of those return a phone and 55% of those reach the right party, the denominator is 34,100 and the answer is about 8.8 cents per dialable contact — nearly three times the three-cent unit rate. The percentages there are invented for the illustration and yours will differ; the point is the ratio between the two numbers, not the numbers themselves. The worksheet is in our skip tracing cost calculator.
Compare that figure against platform pricing, which stacks a subscription and per-record trace fees instead of record blocks — the teardown is in PropStream pricing — and against per-seat models in DealMachine pricing. Three completely different pricing structures collapse into one comparable number once you compute it.
Who this card fits
It fits a team with predictable monthly volume above roughly a hundred thousand records, engineering capacity to consume an API, and a use for raw property data beyond building a call list — which is a real and well-served buyer. It fits badly if your volume is seasonal, if you will not consume the block, or if the only thing you were ever going to do with the data was produce a dialable file, in which case you are paying for infrastructure to rebuild something you could buy finished. Both sides of that argument are in Atlas vs BatchData, and the migration mechanics if you decide to move are in BatchData alternatives.
One last check before you sign anything with “Batch” on the letterhead: confirm which entity you are contracting with. The brand family was reorganised in 2025 and the names no longer identify a single company — BatchLeads vs BatchData has the map.
Frequently asked questions
Why is reverse skip tracing more expensive than skip tracing?
Because the published tiers meter them differently. The forward tiers are described as an allowance of skip traces per month; the reverse tiers are described as matched records, with “pay per matched record” on the card. A price per match should be higher than a price per attempt, because the seller is absorbing the misses. Whether it is enough higher depends entirely on the match rate on your file, which is the number neither of you knows yet.
Can I buy property data and skip tracing on one plan?
They are published as separate product lines with separate monthly prices, so a team that needs both is looking at two subscriptions rather than one. That is normal for infrastructure pricing and it is the most common way a budget built from the headline tier ends up half the size of the invoice. Add the lines you will actually use before comparing anything.
Is a one-cent property record cheap?
For raw data, yes — that is a normal infrastructure rate and there is no argument to make against it. The relevant question is what the record costs by the time it is a dialable contact, which means adding the tracing line, dividing by your match rate, and dividing again by your working-number rate. That arithmetic routinely turns a one-cent record into a materially larger number, for every vendor in the category including us.