Flat-Rate vs Per-Record Property Data Pricing: What a Project Really Costs

Property data is sold in two basic ways. Per-record pricing charges for each row you download. Flat-rate pricing charges a fixed amount per month or year and gives you an allowance. Comparing the two by looking at a headline price does not work, because they scale with different things: one with volume, the other with time.

This guide shows how to turn a project into numbers you can compare: how many records, how often, and how fast. The worked examples use the Bulk Property Records plans. These are proposed launch prices and may change before exports open, but the method works for any price list.

What each model charges for

Neither model is cheaper in general. Per-record pricing suits small, one-off pulls. Flat-rate pricing suits projects that are large, repeated, or both. The rest of this guide is about finding where your project falls.

The plans used in the examples

Every plan includes every column, so there is no per-field cost to add. Plans differ only in how many records you can export each day. That makes the daily allowance the number that matters most: it decides how long a project takes, and how long you pay for.

Throughout this guide, a month is 30 days, and the Annual plan’s monthly cost is its yearly price divided by 12 ($667). Real billing months vary slightly.

Step 1: Estimate the record count

Start with the area. The free search on the home page shows how many records a state, county, city or ZIP contains. Then think about what you will filter out: if you only want single-family homes or absentee owners, your final count is a subset of the area total.

On a flat plan, what counts against the allowance is what you export, so filtering before exporting matters. Under per-record pricing it matters even more, because every unwanted row is a cost.

Step 2: Decide how often you will refresh

The dataset is refreshed monthly. A one-time research pull and a mailing list you rebuild every month are very different projects, even if both cover the same county. Write down how many times a year you will pull the same records again. For per-record pricing, each refresh is a new purchase. For a flat plan, each refresh uses allowance but costs nothing extra if it fits.

Step 3: Work out how fast you need it

A daily allowance turns volume into time. Divide the record count by the plan’s daily allowance to get the number of days the pull takes, then convert days into billing periods:

• Starter: 5,000 records a day, so 150,000 in a 30-day month.
• Pro: 15,000 records a day, so 450,000 in a 30-day month.
• Annual: 100,000 records a day, so 3,000,000 in a 30-day month.

If the deadline is tight, a higher plan can be cheaper overall because you pay for fewer months. Example 3 below shows this.

Step 4: Compute the effective rate

To compare a flat plan with any per-record quote, convert the flat plan into a rate: what you pay divided by what you actually pull. The result depends heavily on usage.

# Flat-rate plan: the price is fixed, so the rate depends on how much you use
effective_rate_per_1000 = plan_cost_for_period / records_pulled_in_period * 1000

# Per-record pricing: the rate is fixed, so the total depends on volume
per_record_total = records * pulls_per_year * rate_per_record
                   + per_field_charges + order_minimums

# A per-record offer is cheaper only when its rate is below the flat plan's
# effective rate at the volume you will actually pull.

The table below shows the effective cost per 1,000 records for each paid plan at different monthly volumes. A dash means the volume is more than the plan’s daily allowance permits in a month.

Two things stand out. First, every plan gets cheaper per record the more of its allowance you use. Second, a plan used lightly can cost more per record than a bigger plan used fully. The useful question is not which plan is cheapest, but which one matches your volume.

Worked examples

Example 1: One county, one time (40,000 records)

You need every residential property in one mid-sized county for a single analysis. You will not refresh it.

The cheapest option here is Starter, at $249. The pull fits inside a single billing month on any plan, so the lowest-priced plan wins. A larger plan only buys speed you do not need. To compare with a per-record quote, divide that cost by 40,000: any per-record rate below $6.23 per 1,000 records, with no extra charges, would be cheaper for this project alone.

Example 2: A regional list refreshed monthly (300,000 records a month)

You maintain a list of 300,000 properties across several counties and re-pull all of them every month to pick up ownership and mortgage changes.

Here the deciding factor is capacity, not price. Plans whose monthly allowance is below 300,000 cannot keep up with the refresh, however cheap they are. The least expensive plan that fits is Pro, at $449 a month, or $1.50 per 1,000 records.

Under per-record pricing, the same project costs the per-record rate times 300,000 times 12 each year. Repeated pulls are where per-record costs add up fastest, and where a flat plan’s fixed price makes the most difference.

Example 3: A statewide build (3,000,000 records)

You are loading a full state into your own database for analysis. The first pull is large; after that, you may or may not refresh it.

For a one-time pull, the cheapest option is Pro at $3,143, but look at the days column: the lower the daily allowance, the longer the project runs and the more months you pay for. A smaller plan can end up costing more than a larger one simply because it takes longer.

If you also need to refresh all 3,000,000 records every month, only plans with at least that much monthly capacity work: Annual (3,000,000 a month). At that scale, the effective cost per 1,000 records falls to $0.22, and the question becomes whether you can use the capacity, not whether you can afford the rate.

Costs that do not show up in the headline rate

Whichever model you are looking at, check for these before you compare totals:

• Re-downloads. Does pulling the same record again next month cost again? Under per-record pricing it usually does. On a flat plan it uses allowance.
• Field charges. Some price lists charge more for mortgage, equity or owner fields. A low base rate can rise quickly once you add the columns you need.
• Minimums and expiring credits. Order minimums raise the real cost of small pulls. Prepaid credits that expire raise the real cost of slow ones.
• Unused allowance. The flat-rate equivalent: a plan sized for your busiest month costs the same in a quiet one.
• Your own time. A cheaper source that needs heavy cleaning or comes with fewer fields can cost more in staff time than it saves.

Sizing a plan when volume varies

Real projects rarely pull the same number of records every month. A common pattern is a large first pull to build the dataset, followed by smaller monthly refreshes of the records that matter. Another is seasonal work, with busy and quiet months.

For a flat plan, split the year into those phases and price each one separately. A build phase is a one-off pull: use the days-to-pull calculation from the examples to see how many months each plan needs. A refresh phase is recurring: use the monthly capacity table to find the smallest plan that fits the refresh volume. The total for the year is the cost of the build months plus the cost of the refresh months.

Then compare that total with the Annual plan’s yearly price. A plan with a higher price can still be the cheaper choice for the year if its allowance shortens the build enough. For per-record pricing, the same split works: the build is one large purchase, and each refresh month is another.

When per-record pricing is the better choice

Flat-rate plans are not always the answer. Per-record pricing is usually better when:

• You need a small number of records, once, and do not expect to come back.
• Your volume is unpredictable and mostly low, with no regular refresh.
• You only need a few columns and the per-record offer genuinely charges less for fewer fields.

The break-even point is simple to find with the formula above: divide the flat plan’s cost for the period by the records you will actually pull in that period. If a per-record offer, with all its extra charges, comes in under that number, it is the cheaper option for your project.

A short worksheet

1. Record count after filters, from the free search and your criteria.
2. Number of times a year you will pull the same records.
3. Deadline for the first full pull, in days.
4. For each flat plan: days to pull, billing periods, total cost, cost per 1,000 records.
5. For each per-record offer: records × pulls × rate, plus field charges, minimums and expiry. Use records × pulls, not just records.
6. Compare totals over the same period, usually a year.

If you are working out how many of those pulls you actually need, the guide on how often property records change covers which fields move between monthly refreshes.